RADIX WikiRADIX Wiki

Overview

Once you have tested locally with resim, the next step is putting the package on a live network. Deployment is a transaction: you upload the compiled package to a web console, it builds a transaction manifest for you, and your wallet signs it and pays the fee.

Which network you can do that on has changed. The hosted console covers Mainnet; the Stokenet console was retired during 2026 and nothing replaced it, so deploying to the testnet now means running a console yourself. Both paths are below.

Stokenet vs Mainnet

Stokenet XRD is free and has no value. Never send Mainnet XRD to Stokenet addresses.

1. Get Test XRD

Skip this if you are deploying straight to Mainnet, where you pay fees in real XRD.

Stokenet has a faucet that hands out free test XRD, reached from the wallet itself. Add the Stokenet gateway first (Settings > App Settings > Gateways; the URL and the developer-mode step are on the Stokenet page), create an account on it, then per the official example walkthrough: tap the account name, the three dots, Dev Preferences, then Get XRD Test Tokens.

2. Build Your Package

scrypto build

Your compiled WASM file is at:

target/wasm32-unknown-unknown/release/<package_name>.wasm

The build also generates an RPD (Radix Package Definition) file at the same location, which describes your blueprints and their interfaces.

Where the Developer Console lives now

The Developer Console is no longer served by Radix. Checked with a browser user agent on 14 August 2026, console.radixdlt.com answers HTTP 302 to console.radixscan.io and preserves the path, so /deploy-package and /transaction-manifest both arrive at the same route on the new host. The page that loads is titled RadixScan Developer Console. dashboard.radixdlt.com redirects the same way.

That is deliberate rather than a lapsed domain: the redirects are issued from Radix's own edge, and the Foundation's operational-stack post of 26 January 2026 lists the Developer Console, Dashboard and Sandbox as P3 items – the tier it described as "prime opportunities for community teams" to take over. RadixScan, the team now hosting them, runs deployments of the same open-source dApps monorepo the originals were built from.

Nothing you click is broken, but the tool you are handing a package to is a community deployment. Nothing about the flow below changes; the hostname in your address bar does.

3. Deploy via the Developer Console

This deploys to Mainnet. The hosted console has no network selector – the network is fixed when the instance is built (see Deploying to Stokenet below).

  1. Open console.radixscan.io/deploy-package.
  2. Click Connect and connect your Radix Wallet, sharing the account that will pay the fee.
  3. Upload both files: the .wasm and the .rpd.
  4. Set Owner role and Owner role updatable. These decide who may later change package metadata and royalties; the official example selects None for both, which is the right choice only if the package needs no owner-gated behaviour. This is the owner of the package, not of the components instantiated from it.
  5. Review the generated manifest, click Send to the Radix Wallet, and approve in the wallet.

Once the transaction commits, the console displays your package address. Save it – you need it to instantiate components.

Deploying to Stokenet: no hosted console

There is no hosted Stokenet Developer Console. Checked 14 August 2026: stokenet-console.radixdlt.com returns HTTP 530 from the Cloudflare edge with no origin behind it, on /deploy-package and /transaction-manifest alike, and no stokenet- hostname resolves under radixscan.io.

Radix's own documentation has not caught up. The step-by-step learning path hands its Stokenet section off to the official-examples repository, whose instructions still open with "Go to the Stokenet Developer Console Website" pointing at that 530 host. A developer following the documentation as written cannot complete the first deployment to a real network.

The working substitute is to run the console yourself from radixdlt/dapps-monorepo (Apache-2.0). The network is read from PUBLIC_NETWORK_NAME at build time, which is why one deployment serves one network:

git clone https://github.com/radixdlt/dapps-monorepo.git
cd dapps-monorepo
# .env: PUBLIC_NETWORK_NAME=stokenet
#       PUBLIC_DAPP_DEFINITION_ADDRESS=<your Stokenet dApp definition>
npx turbo run build --filter=console
node apps/console/build

It serves on port 3000, with the Gateway endpoints already carried in the repository, so you do not need a node of your own. The dApp definition address is yours to create first – see dApp Definition and Wallet Verification. Leaving it empty falls back to Radix's addresses, which the README warns will cause errors. apps/console can also go on Vercel by swapping @sveltejs/adapter-node for the Vercel adapter.

Stokenet itself is unaffected: the network runs, and its Gateway still answers at babylon-stokenet-gateway.radixdlt.com. It is the hosted web tooling that is gone.

A full reset of Stokenet is coming, and it will take your packages with it. On 16 August 2026 the network’s community operator announced a hard cutover targeted within 30 days, with the exact date given at least seven days ahead and no resources carried over. Packages published to Stokenet, the components instantiated from them, and the accounts that own them all have to be recreated afterwards. The network ID and Gateway address are kept, so a console instance built as below keeps working – what it points at will be an empty ledger. Terms and dates: Stokenet.

4. Instantiate a Component

Go to the Send Raw Transaction section of the console and submit a manifest that calls your instantiation function:

CALL_FUNCTION
  Address("<PACKAGE_ADDRESS>")
  "GumballMachine"
  "instantiate"
  Decimal("5")
;
 
CALL_METHOD
  Address("<YOUR_ACCOUNT>")
  "deposit_batch"
  Expression("ENTIRE_WORKTOP")
;

The resulting component address is your live dApp on Stokenet.

Next Steps

HydrateLast updated 8h agov2.1.09 revisionsVerified Aug 16, 2026