Wallet apps + trust-currency designDevnet transfers available · mainnet signing locked

Networks / available tools and setup

Different networks. Different jobs.

Think of networks as separate systems. Each has its own accounts, rules and test funds. A balance on one does not automatically become a balance on another.

Find the network you need ↓

Solana Devnet

Practice with IUNUA

Read the test token balance, request funds when the faucet is available and review supported test transfers. Accounts and test SOL for fees require setup.

World Chain Sepolia

Try a different test network

Electron supports named accounts and reviewed TEST ETH transfers. Create the right account and obtain that network’s test funds first.

Monero Stagenet

Intended treasury test rail

Electron offers an optional workflow requiring wallet and node setup. Choose a reviewed remote connection or a self-hosted node. IUNUA records the authorized debit on its private ledger; Monero is not the public IUNUA mint.

World ID staging

Explore an identity check

A proof system, not a currency. The staging workflow requires backend configuration; activation and production verification have not been completed.

RENDER

View public holdings

Electron can read public RENDER balances. This does not buy tokens, swap assets, run rendering jobs or contribute your computer’s GPU.

Local nodes

Run a test network yourself

Optional developer tools use your computer’s resources. Electron’s contained Solana validator needs Docker and explicit setup; the legacy host helper remains blocked.

These are supported workflows, not a live check of your connections. An unknown or failed connection stays unknown or failed. Mainnet signing remains locked.

Technical details: network configuration and node options

Network lab · capabilities and prerequisites

Move outward one reversible gate at a time.

This map describes wallet capabilities. The website holds no wallet keys and signs no transactions. Check the Token & Status page for the live faucet response.

Current boundary

The website remains disconnected from identity providers and does not start a local Solana validator. The no-value IUNUA Token-2022 mint and its dedicated faucet reserve exist on Solana Devnet; live readiness is reported separately by the faucet health panel. IUNUA, SOL, XMR, WLD, and RENDER remain separate assets; RENDER is the supported Render Network asset on Solana, legacy RNDR is not the target, and World ID is a proof system rather than a token. No bridge, custody reserve across assets, basket, or combined token exists.

1 live test-only Devnet mint lane
Environment readiness mapEvidence gates, not a timeline

Each lane advances independently. “Planned” never means configured.

  1. Local simulator

    The browser-only Trust Lab and downloadable clients use fixed demo state.

    Available now

  2. Solana localnet

    The Electron wallet can manage a contained local validator. It requires Docker, explicit activation and a verified loopback-only setup. The legacy host helper remains blocked.

    Requires local setup

  3. Solana Devnet

    The existing IUNUA mint is live on Devnet. Use a test wallet to read balances, request faucet funds when available, and review transfers.

    Available in test wallets

  4. Proof staging

    Use the World ID simulator with a staging action and server-side verification.

    Staging setup required

  5. World Chain Sepolia

    Electron supports named World Chain Sepolia accounts and reviewed TEST ETH transfers. TEST WLD remains unverified. World ID is a separate proof lane.

    Electron test transfers

  6. Monero Stagenet

    Intended private treasury rail (Stagenet first). Electron can send after node and wallet RPC are running. IUNUA records the send on the private ledger; it is not a public IUNUA mint.

    Explicit opt-in only
SOLTest-mint rail

Solana localnet → Devnet mint

Use the existing public Devnet mint for IUNUA tests. For local Solana tests, Electron has a contained-validator lane; its service must be installed, started and checked independently.

Today
Electron: contained localnet controls. Native and Electron: Solana test accounts. Devnet token balances remain separate from simulation balances.
Next evidence
Keep disposable Devnet keys off mainnet; satisfy verified-loopback-container-v1 before any host validator
Hard boundary
Do not start a Solana validator on the host. Devnet IUNUA has no monetary value. Mainnet is out of scope.
Local-network writing guide Clusters and Devnet
XMRIntended treasury rail

Monero Stagenet

Stagenet is the safe Monero network for treasury testing. Electron can create or import a Stagenet wallet, talk to wallet RPC, and review a send. IUNUA's private ledger records the authorized debit; Monero itself is not the public IUNUA mint and must never silently start a node.

Today
Electron implements Stagenet account creation/import, wallet RPC and reviewed transfers. A configured node and wallet RPC are required; native support remains limited.
Next evidence
Choose self-hosted or explicitly trusted remote Stagenet node
Hard boundary
Node choice changes storage, bandwidth, availability, and metadata exposure.
Monero network guide Running your own node
HUMEligibility verification

World ID staging

Use a staging action and the official simulator to exercise proof requests. Verification belongs on a backend boundary; the browser should not treat a returned payload as authoritative or retain proof material by default.

Today
The Trust Lab simulates eligibility. Electron exposes a separate staging workflow requiring configured backend verification and replay protection.
Next evidence
Staging RP, purpose-bound action, verifier, and replay store
Hard boundary
Staging and production actions are separate; no biometric data enters IUNUA.
IDKit integration and staging Official staging simulator
WLDTest-only programmable rail

World Chain Sepolia / mock WLD

Use World Chain Sepolia (chain ID 4801) with a project-owned mock ERC-20, or faucet-provided testnet WLD where the test calls for it. Keep the asset name visibly marked as test-only everywhere.

Today
Electron implements Sepolia account creation/import, balance reads and TEST ETH transfers. Native does not provide the same signing workflow.
Next evidence
Fund test-network fees and verify the account-bound receipt. TEST WLD is not a verified transferable asset.
Hard boundary
Never reuse development keys or imply that mock/test WLD is production WLD.
World Chain Sepolia details Testnet WLD guidance
GPUPLANNED · REQUEST ACCESS

Render Network compute access

Render Network describes programmatic GPU access through approved third-party Compute Clients. IUNUA currently provides only a readiness lane: there is no approved account, Compute Client adapter, API credential, job submission, billing connection, or token custody.

Today
Electron can inspect public RENDER holdings without signing. Compute jobs, billing and node onboarding remain separate and unimplemented.
Next evidence
Choose creator, Compute Client, or node-operator onboarding through official Render Network paths
Hard boundary
RENDER on Solana remains separate from IUNUA. Legacy RNDR is not the target, and this Mac or mobile wallet does not contribute compute automatically.
Compute Client access Creator rendering guide Node-operator onboarding RENDER / legacy RNDR FAQ

Render compute lane · planned / request access

Use compute through the correct official door.

Electron supports read-only RENDER holdings. The following is a compute readiness checklist: there is no purchase flow, compute API access, job runner, automatic download, or GPU node.

  1. 01

    Choose the role before choosing software

    Creator rendering belongs in the official OTOY / Render Network artist flow; a Compute Client is a third-party application requesting programmatic GPU access; a node operator supplies eligible hardware after separate onboarding. These are different roles, accounts, costs, and responsibilities.

    Open the official Render portal
  2. 02

    Request Compute Client access

    For an IUNUA application or automation pipeline, start with Render Network's Compute Client information and access process. An application or information request is not approval, and no adapter should be enabled before the network supplies current API, billing, and operational terms.

    Compute Client program
  3. 03

    Onboard node hardware separately

    Node operation is not a wallet feature. Render Network requires official onboarding and currently documents CUDA-enabled NVIDIA hardware and operational prerequisites. The IUNUA desktop or mobile app installs no node, opens no port, and contributes no GPU time.

    Node-operator requirements
  4. 04

    Keep RENDER outside IUNUA custody

    Use the currently supported RENDER asset on Solana only within an approved official Render workflow. Legacy RNDR is not the target. IUNUA does not buy, upgrade, bridge, hold, transfer, or ask for a wallet secret, and RENDER ownership alone does not connect compute.

    Official RENDER upgrade FAQ
  5. 05

    Approve budget, consent, and job data

    Before any future job, record a hard spending cap, an explicit human approval, the permitted workload, data classification, upload and result locations, retention and deletion rules, and a stop condition. Never submit secrets, personal data, customer material, or unlicensed assets by default.

  6. 06

    Keep credentials outside the repository

    Store future access tokens in an OS keychain or dedicated secret manager, scope and rotate them, and never place them in source, browser storage, screenshots, logs, downloadable guides, or the IUNUA demo contract.

  7. 07

    Run one isolated non-value test only after approval

    After official access and human approval, start with a disposable, non-production job containing no valuable or customer data. Pin the engine, model, dependency, input, and parameter versions; use the smallest approved budget and do not automate retries.

  8. 08

    Verify the result before expanding

    Record input and output hashes, API and engine versions, cost, timing, logs, failures, and cleanup evidence. Independently validate result integrity and reproducibility. A successful sample authorizes neither production data nor background compute.

Exact inspection quickstart

Inspect IUNUA, then mint on Devnet without starting Solana.

These commands require the full project source on macOS. Local validator start stays blocked (containment-required). Devnet IUNUA minting is acknowledgement-gated public RPC and uses the live coin-logo metadata host. Monero remains a separate explicit opt-in.

Download the inspection guide 
npm run network:doctor
npm run network:install  # prints choices; installs nothing
npm run token:plan       # dry run; creates nothing
npm run token:create:devnet -- --metadata-uri https://iunua-t-metadata.iunua-trust-currency-prototype.workers.dev/token-metadata/iunua-test.json

Step-by-step environment guide

A promotion ritual for test networks.

Complete and record each evidence gate. Return to the previous environment when an invariant fails.

  1. 01

    Freeze the local contract

    Keep ASTRA-7F2C, 120 private units, +80 reward, 25 private transfer, 40 public mirror, audit revocation, and policy v7 → v8 identical across clients.

  2. 02

    Inspect the Solana mint plan

    Run the prerequisite doctor and dry-run Token-2022 plan. They create no keys, contact no RPC endpoint, and broadcast nothing.

    Solana development reference
  3. 03

    Verify containment before execution

    Use a reviewed container or VM, inspect effective listeners after startup, expose nothing to the host LAN, mount no host wallet or production-key paths, limit resources, and pass negative network tests.

    Solana installation reference
  4. 04

    Inspect the live Devnet mint

    After acknowledgements, register a no-value IUNUA Token-2022 mint on Solana Devnet with the coin logo in Token-2022 metadata. Keep disposable test keys off mainnet.

    Solana clusters and Devnet
  5. 05

    Add eligibility in World ID staging

    Create a staging action, use the simulator, verify on the backend, bind purpose and signal, persist replay protection, and log no raw proof beyond operational need.

    World ID integration
  6. 06

    Exercise World Chain Sepolia

    Deploy a clearly named mock asset or use faucet-provided testnet WLD, then test caps, pause, failure messages, confirmations, and explorer links without touching mainnet.

    World Chain testnet details
  7. 07

    Offer—not impose—a Stagenet node

    Let operators choose no Monero lane, a trusted remote Stagenet endpoint, or a self-hosted node. Show disk, bandwidth, privacy, trust, and recovery consequences before activation.

    Monero Stagenet
  8. 08

    Review evidence before any next environment

    Require passing integration tests, threat-model updates, key rotation drills, monitoring, incident ownership, and an explicit human approval. No testnet success authorizes production value.

Technical details: verification instructions and legacy reports

Network verification · operator reference

Know what ran. Know what remains locked.

Verification is target-specific evidence, not a green aura around the whole system. Local simulation, public test networks, and mainnet activation remain separate realms.

Hosted page boundary

This section is a legacy verifier reference, not a live report. Its structural checks describe the simulator and setup tools; they do not certify the current wallets. It cannot inspect your machine or configuration. Unknown runtime results remain NOT RUN. For the dated Devnet snapshot and package comparison, see Token & Status.

NO LOCAL COMMAND EXECUTION
VERIFIEDNamed evidence passed within its stated scope.
NOT RUNNo current observation was collected.
BLOCKEDA required safe prerequisite is absent.
LOCKEDThe verifier intentionally refuses activation.
LOCAL

Local simulation

REFERENCE · local execution not observed

Static contract evidence can pass without a network. Live loopback health still belongs to the current Mac and must be rerun there.

  • demo-contractVERIFIED

    Demo contract

    The fixed simulation contract and its no-value, no-private-key, no-chain boundaries pass structural verification.

  • wallet-openapiVERIFIED

    Wallet OpenAPI

    The loopback API description matches the bounded simulated wallet surface.

  • game-api-contractVERIFIED

    Game API contract

    The guide declares /v1/game/rewards and /v1/game/events, no blockchain private key, and no browser CORS access.

  • wallet-mcp-boundaryVERIFIED

    Wallet MCP boundary

    The MCP surface uses stdio, pins the runtime to http://127.0.0.1:8787, and refuses non-loopback hosts.

  • wallet-loopback-healthNOT RUN

    Wallet loopback health

    The hosted page cannot observe this Mac. Run the explicitly acknowledged local live-read-only report to probe 127.0.0.1:8787.

TEST

Testnet evidence

REFERENCE · runtime results require a fresh run

Each public-test lane advances independently. Read-only evidence is not deployment, custody, or permission to transact.

  • network-lab-policyVERIFIED

    Network Lab policy

    Test-only targets and mainnet denial rules are present in the checkout.

  • setup-policyVERIFIED

    Setup policy

    Install and node actions remain acknowledgement-gated and testnet-only.

  • world-id-staging-configBLOCKED

    World ID staging config

    Needs local app_id, rp_id, server-held signing key and RP signature, backend verification, and nullifier storage. The simulator must use staging.

    World ID integration
  • world-chain-sepolia-configNOT RUN

    World Chain Sepolia config

    Electron 0.8.4 includes a World Chain Sepolia lane (chain ID 4801). Its configuration and a successful transfer must be checked on the actual wallet; this page has no current runtime result.

    World Chain network details
  • solana-containmentBLOCKED

    Solana containment

    The optional legacy setup helper blocks host validator execution pending containment evidence. Electron can use public Devnet RPC without a local validator; this helper gate is not a wallet-wide failure.

    Solana network guide
  • monero-stagenet-runtimeNOT RUN

    Monero Stagenet runtime

    Stagenet is the correct normal-user and application-development lane; no runtime evidence has been recorded by this page.

    Monero network guide
  • solana-devnet-readNOT RUN

    Solana Devnet read

    Application development targets Devnet. Solana Testnet is for validator and stress testing; public RPC is rate-limited and not a production endpoint.

    Solana clusters
  • world-chain-sepolia-readNOT RUN

    World Chain Sepolia read

    The optional outbound verifier has not recorded a read-only response from chain ID 4801.

    World Chain Sepolia
  • render-compute-adapterBLOCKED

    Render compute adapter

    A production compute adapter and billing path have not been verified. Electron can already display read-only SPL RENDER holdings; holdings do not execute compute jobs.

    Render Compute Clients
  • iunua-testnet-deploymentNOT RUN

    Integrated testnet workflow

    An IUNUA Token-2022 mint exists on Devnet, verified on 8 September 2026. Complete wallet and governed settlement workflows remain unverified; the Token & Status page carries the dated chain snapshot.

MAIN

Mainnet activation

OVERALL LOCKED · production prerequisites outstanding

Mainnet is a locked boundary. The only verified property is the lock itself; every activation prerequisite remains unavailable.

  • mainnet-policy-lockVERIFIED

    Mainnet policy lock

    The verifier recognizes mainnet only as a denial target; it contains no activation command.

  • mainnet-network-accessLOCKED

    Mainnet network access

    Solana Mainnet, World Chain Mainnet (chain ID 480), and Monero Mainnet are outside this test release.

    World Chain network details
  • mainnet-custodyBLOCKED

    Production custody and recovery

    Requires independently reviewed custody, recovery, authorization, and separation-of-duties controls.

  • mainnet-external-security-auditBLOCKED

    Independent external security audit

    Requires protocol, cryptography, wallet, API, operations, and dependency review with findings resolved.

  • mainnet-testnet-evidenceBLOCKED

    Repeatable testnet evidence

    Requires contained local and public-testnet evidence, including failure modes, that can be rerun.

  • mainnet-deployment-reconciliationBLOCKED

    Signed deployment and reconciliation evidence

    Requires commit and build hashes, signed deployments, network addresses, authority inventory, supply and treasury limits, and cross-adapter reconciliation.

  • mainnet-legal-complianceBLOCKED

    Legal and compliance review

    Requires jurisdiction-specific classification, privacy, sanctions, consumer, tax, and operator review.

  • mainnet-governanceBLOCKED

    Governance and accountability

    Requires defined issuance, upgrade and emergency authority, monitoring, disclosure, and accountable operators.

  • mainnet-rollback-incident-responseBLOCKED

    Rollback and incident response

    Requires tested rollback, pause, recovery, incident communications, and post-incident review.

Source-checkout commands

Generate evidence on the machine that owns it.

STATIC COMMAND REFERENCE
01 / LOCAL

Refresh local evidence

Plan, inspect local status, then emit the verifier report. The hosted page does not run these commands.

node scripts/network-verification.mjs plan --target local
node scripts/network-verification.mjs status --target local
node scripts/network-verification.mjs report --target local
node scripts/network-verification.mjs report --target local --live-read-only --acknowledge-outbound-read-only
02 / TESTNET · OFFLINE

Inspect configured testnet gates

The default testnet path evaluates repository and local configuration evidence without opting into public reads.

node scripts/network-verification.mjs plan --target testnet
node scripts/network-verification.mjs status --target testnet
node scripts/network-verification.mjs report --target testnet
03 / TESTNET · OUTBOUND OPT-IN

Request live read-only evidence

This explicit acknowledgement allows only bounded public-testnet reads. Providers and networks can see your source IP, timing, target, and the verifier's fixed request method and body. No credentials, wallet addresses, or account identifiers are sent; this authorizes no signing, faucet, deployment, transfer, or mainnet call.

node scripts/network-verification.mjs report --target testnet --live-read-only --acknowledge-outbound-read-only
04 / MAINNET

Confirm the policy lock

This command reports the lock. It does not unlock, configure, connect, or activate a mainnet environment.

node scripts/network-verification.mjs mainnet

Step-by-step evidence ritual

Five moves. No silent promotion.

The full guide explains report fields, outbound consent, official environment choices, failure handling, redaction, and why mainnet stays locked.

Download the verification guide
  1. 01
    Plan

    Read the exact targets and boundaries before a probe or report.

  2. 02
    Run locally

    Use the source checkout on the machine that owns the configuration. Never paste credentials into arguments.

  3. 03
    Read every status

    Keep VERIFIED, NOT RUN, BLOCKED, and LOCKED intact. Do not translate missing evidence into success.

  4. 04
    Inspect the report

    Review targets, timestamps, redactions, and reasons before retaining or sharing evidence.

  5. 05
    Promote nothing automatically

    A passing testnet read never authorizes deployment, custody, real value, or mainnet.