Use this like an operator console: confirm which chains are local vs remote, fund the correct authority wallets, create fixtures, and watch queue/sync state in one place.
Local wallets
0
only shown for local runtimes
Collections
0
sync bootstrap targets
Tokens
0
fungible fixtures
Active syncs
0
current loader sessions
Operator Flow
Do these in order
The testbed works best when you treat it like a deployment console: confirm runtimes, fund the correct authority wallet, provision if needed, then create fixtures and watch the queue.
No MPC treasury is registered in this node database right now, so treasury wallets will not appear on this page.
1
Check environment mode
All three chains have a runtime attached. You can work locally, remotely, or both.
2
Fund the right wallets
This node can already execute one-click actions for BTC, ETH, SOL through its master node wallet.
3
Provision or create fixtures
Start the local backend for BTC, ETH, SOL, then click Initialize Runtime before trying to create assets.
4
Watch the queue and sync
No backlog right now. After creating a fixture, the queue panel will show chain wait time and the operation trail.
Step 1
Create or mint test assets
Create collections first, then mint from those existing collections whenever you need assets in a specific wallet. The destination address only matters on mint actions while the master node wallet pays for deploy, mint, and inscription work.
Bitcoin Ordinals Fixtures
Create a parent-child collection scaffold once, then inscribe new children into that collection whenever you want to test wallet ownership or collection discovery.
CollectionName
Used for the root metadata that the ordinal scraper will later detect.
LineageDepth
Use 2-4 when you want grandparent lineage in the collection scaffold.
This only creates the collection scaffold. It keeps destination choice out of setup and lets you mint children later to any wallet.
ExistingCollection
Choose a tracked BTC collection or paste a collection id directly.
No BTC collections yet
DestinationAddress
Each minted child inscription will be sent to this BTC address.
MintCount
How many new child inscriptions to create under the selected collection.
StandaloneInscriptionName
Used only for the loose inscription action below.
StandaloneDestination
One-off inscriptions are sent to this BTC address.
Remote fixture execution is enabled through this node's master node wallet. Treasury ownership is listed separately in the authority panel.
Mint from an existing collection when you want the asset in a specific wallet. Use the one-off path only for loose ordinals that are not meant to belong to a detected collection.
EVM NFT Collection
Deploy the contract first, then mint NFTs from that contract to any wallet whenever you need them.
CollectionName
Contract display name.
Symbol
Ticker-style short code.
Remote fixture execution is enabled through this node's master node wallet. Treasury ownership is listed separately in the authority panel.
Collection creation only deploys the contract. Minting happens in the next section so destination choice stays out of setup.
DeployedCollection
Choose a tracked contract or paste an EVM contract address directly.
No EVM collections yet
DestinationAddress
Minted NFTs from the selected contract will be sent to this EVM address.
MintCount
How many new NFTs to mint from the selected collection.
Use this to mint more NFTs later without redeploying the contract or rebuilding the collection.
EVM Fungible Token
Deploy a simple ERC-20 and mint the requested supply into any EVM wallet so token market and swap flows have something to work with.
DestinationAddress
The master node wallet deploys the token and mints the opening balance into this EVM address.
TokenName
Human-readable asset name.
Symbol
Short ticker.
MintAmount
Whole-token amount to mint with 18 decimals.
Remote fixture execution is enabled through this node's master node wallet. Treasury ownership is listed separately in the authority panel.
Use this when you need a fungible asset for swap pools, token markets, or contract upgrade tests that depend on ERC-20 balances.
Solana Fixtures
Create the collection shell first, then mint NFTs from it to any wallet. Fungible mints still work as one-shot token fixtures.
NFTCollectionName
Collection display name for the Solana NFT path.
NFTSymbol
Ticker-like symbol for the collection.
This registers the collection first so you can come back and mint NFTs into any wallet later.
ExistingCollection
Choose a tracked Solana collection or paste a collection id directly.
No Solana collections yet
NFTDestinationAddress
New NFTs from the selected collection will be sent to this Solana address.
NFTMintCount
How many NFTs to mint from the selected collection.
TokenName
Name for the fungible mint path.
TokenSymbol
Short symbol for the fungible mint.
TokenDestinationAddress
The minted fungible supply will be sent to this Solana address.
TokenAmount
Whole-token amount to mint with 6 decimals.
Remote fixture execution is enabled through this node's master node wallet. Treasury ownership is listed separately in the authority panel.
Mint NFTs from an existing collection when you need them in a specific wallet. The token path is still a separate one-shot mint.
Step 2
Fund and inspect the network
Use these panels to see which wallet actually controls deployments, where to send testnet funds, and whether the live chain queue is still catching up.
Authority wallets
Governed treasury addresses, current master node wallets, and local deploy/funder wallets.
This is the persistent wallet assigned to the master node for remote BTC funding and ordinal fixture actions. Treasury ownership is tracked separately.
This is the persistent wallet assigned to the master node. The dashboard uses it today for deploy, funding, and mint actions on BTC. It is separate from the governed treasury.
Send testnet funds to this master node wallet once. After that, the dashboard can deploy contracts and fund recipient wallets automatically.
Master Node Wallet
ETHmaster node walletexternal funding
0x29A60E08A34c5169A317830006353D2FA49491DC
Source: NODE_WALLET_MNEMONIC
Balance: 0.029882 ETH
This is the persistent wallet assigned to the master node for EVM deploy, funding, and mint actions. Treasury ownership is tracked separately.
This is the persistent wallet assigned to the master node. The dashboard uses it today for deploy, funding, and mint actions on ETH. It is separate from the governed treasury.
Send testnet funds to this master node wallet once. After that, the dashboard can deploy contracts and fund recipient wallets automatically.
Master Node Wallet
SOLmaster node walletexternal funding
CFGk5oKWaeP2zxKkhXhWJwaRjitztbqxrmhrcYnug9mS
Source: NODE_WALLET_MNEMONIC
Balance: 0 SOL
This is the persistent wallet assigned to the master node for Solana mint and funding actions. Treasury ownership is tracked separately.
This is the persistent wallet assigned to the master node. The dashboard uses it today for deploy, funding, and mint actions on SOL. It is separate from the governed treasury.
Send testnet funds to this master node wallet once. After that, the dashboard can deploy contracts and fund recipient wallets automatically.
Tracked so reset or replay flows can still recognize historical marketplace transactions.
Tracked Solana Marketplace Program
SOLexternal ownerauthority updatable
5DCHff5kiKPdVjbnKxNTxGag6yNGPZXRuqWF8E4t9Kei
Owner: unknown · Deployer: unknown
Tracked so program-derived marketplace state can be rebuilt after resets.
Step 3
Watch queue and sync results
Confirm that the chain accepted the action, then watch the collection sync and token fixture panels update from the same manifest-backed state the marketplace uses.
Chain queues
Live chain backlog plus the most recent dashboard operations.