RADIX WikiRADIX Wiki

Overview

Mainnet is accepting transactions again

Step 3 below deploys to Mainnet, which was halted for ten days and is not any more. The ledger dates its own restart more precisely than any status page does. Mainnet's last pre-halt round is state version 557,840,627, epoch 339,897 round 4, at 21:19:48.939 UTC on 31 August 2026. Rounds resume at 557,840,628 at 11:35:28.960 UTC on 11 September – but under an upgrade moratorium that committed no user transaction, so a package upload would still not have gone through. The first user transaction is 557,840,694, epoch 339,898 round 2, at 11:39:25.129 UTC: three minutes fifty-six seconds later, on the far side of the Eagle Ray fork. Read at 11:07 UTC on 12 September the network stands at epoch 340,179, state version 557,923,055, and /state/validators/list answers HTTP 200 after five hundred-ing throughout the halt. Background: Hyperlane asset drain and network halt; live status on Radix ecosystem operational status.

Read the ledger, not the status endpoint

An earlier version of this page quoted the Gateway status endpoint, which during the halt returned state version 557,840,622 at epoch 339,896 round 102. That is five states short of what the ledger actually committed. The endpoint reports how far the Gateway's own database has read, and a Gateway that has fallen behind reports its own position, not the network's. Pin a read to a state version through at_ledger_state when the answer matters. See Verifiability.

Stokenet was reset on 29 August 2026

Anything you had put on Stokenet before that date – the package, the component instantiated from it, the test XRD that paid for both – is gone. The tutorial still works; what you build on Stokenet is disposable by design. See After the reset below.

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 was unaffected throughout, and for the ten days of the Mainnet halt that made it the load-bearing half of this page: the testnet kept committing rounds while Mainnet did not, and its Gateway answers at babylon-stokenet-gateway.radixdlt.com – epoch 4,311 at state version 8,365,764, read 11:08 UTC on 12 September 2026. Both networks take deployments again; it is the hosted Stokenet web tooling that is gone, and that has nothing to do with the halt.

After the reset – what you re-run

Stokenet was wiped on Saturday 29 August 2026, and the wipe is visible in the ledger itself. Eight hours after the window opened, the Stokenet Gateway returned epoch 51 at state version 137,506 – against epoch 254,946 and state version 425,013,339 ten days earlier – on the same node release, v1.10.6. The date had been set on 18 August 2026 by the network’s community operator and relayed to the Radix Developer Discussion group; the network went down at 07:00 UTC (09:00 CEST) and several hours of downtime followed, because the operator took the window for server maintenance as well. The ledger it replaced was not small. The replacement ledger has been running since: read at 19:05 UTC on 4 September 2026 it stood at epoch 2,103, state version 5,384,258, advancing about a hundred state versions every twenty seconds – so a Stokenet deployment made today behaves normally.

What survives is what is derived rather than stored. Network ID 2, the Gateway URL, the well-known addresses (test XRD, the faucet, the native packages) and your own account addresses are all unchanged, so nothing in a client config or in a console instance built as above needs editing. What it points at is an empty ledger. Taking the steps on this page in order, that means:

  1. Step 1, test XRD – balances are gone; re-fund the same account from the faucet.
  2. Step 2, build – unaffected. The .wasm and .rpd are local artefacts.
  3. Step 3, publish – every package is destroyed; re-publish, and expect a new package address. Anything that hard-codes the old one (a front end, a manifest, a test fixture) has to be updated.
  4. Step 4, instantiate – components go with their packages; re-instantiate and record the new component address.

Two things outside this page’s steps also go: on-ledger persona data, so wallet personas are recreated, and dApp Definition metadata, so a verified dApp stops verifying until its metadata is re-populated. How often this recurs has been stated twice, differently, by the same side. The 16 August announcement gave 9–12 months. Asked on 3 September 2026 why the reset happened at all, Timan Rebel answered for the operator – “we simply did a reset” – that it was “to be able to keep it running < 1TB needed storage. It was a cost issue.. By heart the plan is to do this every 6 months or so” (t.me/radix_dlt/1001768, embed-verified), and, asked whether that was a problem for developers, “you will have to redeploy your packages and resources, but that is about it” (1001787). The later figure is offered from memory, so take the cadence as somewhere between the two and the principle as settled: a Stokenet deployment is disposable by default, and the constraint driving it is the cost of storing the ledger. Full terms: 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 2d agov3.0.014 revisionsVerified Sep 12, 2026