One explicit enrollment creates the member’s testnet wallet, canonical SiloID, and SiloMerchantServices profile. From there, the member can preserve evidence, create assets, verify state, operate infrastructure, connect commerce, and optionally enable SiloCloud services.
The member begins with one explicit enrollment. The platform creates a testnet wallet, establishes the canonical SiloID, and provisions a SiloMerchantServices profile after the member accepts the applicable terms.
Private keys and credentials are never placed on the public ledger.
SiloID issues a short-lived, scoped platform session. The dashboard shows the member’s tenant, security context, wallet, connected services, node installations, and recent finalized activity.
The network creates one idempotent testnet wallet for the canonical SiloID. The member can view balance, address, nonce, fees, pending requests, finalized transactions, and receipts.
Testnet and MainNet wallets, keys, balances, and endpoints remain isolated.
The member reviews the recipient, amount, fee, network, nonce, and expiry before signing. SiloMerchantServices can request payments or issue payouts, but it cannot sign as the user.
Uncertain submissions remain verification pending until reconciled.
From SiloDrive, the member selects a clean immutable image version, confirms rights, reviews canonical metadata and fees, and explicitly signs a testnet mint.
The member defines allowed states, transition authorities, evidence requirements, fees, expiry, disputes, and recovery. Example uses include escrow, licensing, approvals, merchant settlement, and controlled release.
Deployment remains disabled until execution, audit, and governance rules are ratified.
Search the explorer by block, transaction, receipt, or wallet. Confirm validator signatures, block linkage, ENUM pulse, asset hashes, and final status.
Current testnet: height 1, pulse 1, quorum 2 of 3.
Install an observer/archive node, generate a unique local key, synchronize finalized history, and verify chain data without relying on a public explorer.
The node runs in the background. The dashboard and terminal open only when requested.
A SiloID-bound node owner may submit technical and governance information. Eligibility considers key custody, uptime, security, network diversity, monitoring, and policy compliance.
Promotion requires approval and a signed validator-set update; a node cannot grant itself consensus authority.
Developers define an application, audience, callback, approved scopes, service authority, API keys, webhooks, idempotency behavior, and revocation policy.
Public reads need no credentials. State changes require wallet or registered service signatures.
MainNet requires its own genesis, validator set, keys, balances, fee policy, governance, security review, and legal disclosures. It is never a UI switch over testnet.
No production value or production validator rewards are currently enabled.
Every completed journey ends with a stable identifier, canonical hashes, block reference, validator proof, timestamp, and final state. The receiptâ€â€not a success animationâ€â€is the durable evidence.
