Introduction
Building on Radix asks you to unlearn one habit before anything else works. On most networks a token is a number your contract keeps in a mapping, and moving it means writing code that decrements one entry and increments another. On Radix the engine owns the asset. A resource moves between vaults through the engine’s own rules, and a blueprint that tries to lose it will not compile into a transaction that commits.
That single change removes a category of bug rather than a line of code, and it is why the learning path below starts with resources rather than with syntax.
Where to start
Installing Scrypto is step one for everyone – the toolchain, a first blueprint, a package deployed to Stokenet. After that these four are a sequence, each assuming the one above it. Give manifests more time than their position suggests: a Radix transaction states what it intends to do in a form the wallet can show a user before they sign it.
- 1Getting StartedInstall the toolchain, write a first blueprint, deploy to Stokenet and then mainnet.
- 2ScryptoResources and NFTs, authorization and badges, testing, and the design patterns.
- 3TransactionsThe manifest language, the transaction lifecycle, fees, addresses and entity types.
- 4FrontendThe dApp Toolkit, the Gateway SDK, ROLA wallet login, and dApp verification.
Then, as the project needs it: Infrastructure, AI Agents, Tools.
Agents
The newest branch here is for software that acts on its own behalf. Radix Context and Radix Skills package the protocol’s documentation for coding agents, and x402 payments covers the emerging way an agent pays for a request it has just been refused. Radix’s subintents make that pattern unusually clean, because a client can commit to an exact payment without holding the XRD to pay the network fee.
What to expect
Scrypto is Rust, so the borrow checker is part of the job and the compile times are real. In exchange, most of what a Solidity audit looks for is unrepresentable: there is no reentrancy path through a resource transfer, no approve-and-drain, and no way to mint an asset a blueprint was not authorized to mint. Whether that trade suits a given project is a judgment about the team as much as the protocol, and it is worth making before the first blueprint rather than after.
Official documentation
Radix Technical Documentation – the canonical docs site for the entire stack.
Scrypto: Learning Step-by-Step – from first blueprint to full dApp.
Official code examples and community Scrypto examples – working blueprints to read and adapt.
Radix Engine – the asset-oriented state machine that runs transactions.
Radix dApp Toolkit – Connect Button, Wallet SDK, and Gateway SDK in one interface.
ROLA (Radix Off-Ledger Auth) – prove wallet ownership for login.
Radix Engine Toolkit – manifest construction, SBOR, and address derivation.
Network APIs – Gateway, Core, and System API overview.
Radix Wallet – wiki reference for the Babylon wallet.
API specifications
Gateway API – read aggregated ledger state and submit transactions (mainnet Swagger).
Core API – full-node API for integrators and the
/stream/transactionsevent stream.System API – node operations and health.
SDKs and libraries
Radix dApp Toolkit – the recommended front-end integration library (Connect Button + SDKs).
Gateway API SDK (npm) – typed JS/TS client for the Gateway.
Core API SDK (npm) – typed JS/TS client for the Core API.
ROLA (npm) – verify Radix Off-Ledger Auth signatures server-side.
scrypto / scrypto-test / radix-engine – Rust crates on docs.rs.
Radix Rust SDK (GitHub) – pure-Rust off-ledger primitives: ROLA auth, address derivation, keystores, and Radix Connect over WebRTC and iroh/QUIC.
radix-web3.js (GitHub) – a nine-package community TypeScript suite built on Effect: core client, Gateway client, wallet connect, transaction and streaming helpers, an SBOR “ez mode” schema builder, and the agent-first rdx-cli.
Radix Wallet Connector – browser extension that bridges dApps to the wallet.
Scrypto crates
scrypto-math – high-precision math (exp, ln, pow) for Scrypto.
scrypto-avltree – an on-ledger AVL tree data structure.
RRC-404 (ice_rrc404v1) – a hybrid fungible/non-fungible token standard for Radix, with a reference implementation in Scrypto.
Community tools and explorers
As the Radix Foundation winds down, much developer infrastructure is now community-hosted. The following are actively maintained; the Tools section covers several of them at length.
RadixScan Console – developer console and step-by-step Manifest Builder that sends transactions straight to your wallet (switches between Mainnet and Stokenet).
RadixScan Dashboard – account, resource, and transaction explorer.
GenkiPool Community Tools – wallet connection, batched transactions, and one-transaction staking/unstaking across multiple validators.
ShardSpace – create and manage dApp definitions (Mainnet and Stokenet).
Instruct (app) – visual transaction manifest builder for Mainnet and Stokenet, from The Radix Billboard team.
Hookah (GitHub) – a self-hostable Radix event-monitoring and webhook-delivery platform (MIT-licensed): register triggers on on-ledger events and receive webhook callbacks when matching events appear in the transaction stream. Runs as a hosted service at hookah.ing.
Radix Desktop Tool (GitHub) – open-source MIT desktop utility for batched single→multiple and multiple→multiple token transfers.
For agents
The AI Agents section covers these in depth; what follows are the endpoints and indexes themselves.
RadixScan Agent Layer – keyless MCP server for reading the ledger and building, validating, and simulating manifests (non-custodial; signing happens in the wallet).
RADIX.wiki MCP Server – this wiki’s own keyless MCP endpoint at
radix.wiki/api/mcp, plusllms.txt, markdown twins and a ROLA-gated write path.Awesome Radix MCP Servers – curated index of Radix MCP servers.
x402 – the open HTTP-402 payment standard for AI agents and APIs; multi-chain implementation with Radix support in development.
Hyperscale (Xi’an)
Hyperscale is the in-progress sharded execution layer for Radix’s Xi’an release, written in Rust, and the most active area of protocol development. It is expected to run a purpose-built VM written from scratch rather than a sharded Radix Engine, with the migration cost for existing dApps put at best case a recompile, worst case an automatic source transpiler. The wiki’s account is at hyperscale-rs.
hyperscale-rs – the implementation, including the POLARIS leaderless BFT beacon-chain prototype.
Web3 Modules: Hyperscale – community learning notes on the architecture.
Learn-Hyperscale-rs – community guides and flowcharts for Rust and distributed systems with Hyperscale-RS.
Community and funding
Radix Developer Discussion on Telegram – where protocol and tooling questions actually get answered.
Official Discord – the developer channel.
Radix ecosystem funding – grant programmes, past and present, and how to apply.

