SUNPHI WANDER / EXPERIMENTAL NETWORK
Your keys. Your transfers. A verified state across your devices.
Test tokens only · No real funds · Separate from the institutional SunPhi wallet
01 / FOUR-LEVEL CERTIFICATES
Wallets sign and verify transfers. Server controllers check wallet operations, a third level certifies those checks, and a rotating control group checks their evidence and network freshness. Version 0.15 checks stalled transfer approvals; the current two-host network remains an experiment under one operator.
02 / CRYPTOGRAPHIC VERIFICATION
Wallets verify signed transaction history and fresh quorum evidence before enabling transfers.
03 / VALIDATION WITHOUT MINING
Validation uses signatures and quorum certificates. Token holdings do not determine voting weight; server compensation is a separate economic mechanism.
WALLET & DOWNLOADS
The browser and Windows desktop wallets connect to the same test network. A second device does not need to run a server or create another network.
Use a current Chrome or Safari browser. Connect with your personal invitation, then create a wallet or restore its encrypted backup.
Open walletYou can add this website to your home screen. This is a web wallet; no APK or App Store installation is required.
A desktop application with local encrypted wallet storage. Restore your latest backup to keep the same address and load its verified balance.
Download Windows wallet ↓Experimental installer · Unsigned publisher build · A device invitation is required. Browser wallets are not imported automatically.
Installation and backup guideA short guide to invitations, encrypted backups and checking the same wallet from another phone.
Download connection guidePlain text · No private keys, passwords or invitation codes are included.
NODE SOFTWARE / PREVIEW 0.15.0
Windows and Linux share the same transaction rules and quorum protocol. Install the software, set your reward wallet address and export a registration request. Registration requires approval and a separately provisioned configuration. Only a certified active controller set votes; registering a device does not increase the voting threshold.
Installs an automatic Windows service, with an optional wallet interface. The node runs without an open wallet or Windows login. Your reward address can belong to another device.
Download Windows node ↓Unsigned preview installer · Administrator approval required. Automatic startup and crash recovery; signing data is preserved during updates and uninstall.
Includes the runtime, an installation script and a user-service template. Choose with or without a link to the web wallet.
Download Linux node ↓Tested on Ubuntu · Native Linux wallet, ARM and macOS packages are not included.
Follow the installation, provisioning and recovery instructions. Verify package checksums before installation.
Download setup guide ↓Download SHA-256 checksums ↓Registration does not activate rewards or redemption. Test tokens have no promised monetary value.
In an isolated 100-process test, transfers continued with 69 standby processes offline and 21 of 31 active controllers available. A certified handover to a different group preserved history; 20 active controllers could not finalize. These are process-level checks, not proof of independent physical infrastructure. A device pool can grow without increasing the active quorum. Existing wallet addresses and balances are preserved.
GET STARTED
Ask the network administrator for a separate invitation for each phone. Open the invitation link on that phone and confirm. Each code can be used once and expires after ten minutes.
For transfers between people, create a different wallet on each phone. To test access to the same wallet, save its encrypted backup on the first phone and restore it on the second using the same password.
Ask the host administrator to allocate test tokens to your public address. Check the network indicator, enter a recipient, review the amount and sign. An interrupted connection does not mean a transfer failed: reconnect and let the wallet verify its result.
The test network runs on a dedicated virtual server with automatic startup and daily backups. The administrator's laptop can be switched off. A server or provider outage can still interrupt service. A green connection indicator confirms a fresh quorum response; it does not mean the nodes have independent operators.
SECURITY & ACCESS
Private signing keys and wallet passwords stay on the client device. Keep an encrypted backup outside browser storage. There is no password reset service. Global password changes replace the signing key after network confirmation. Save the new backup before confirming, then restore it on other devices; older copies lose spending authority.
Device invitations control access to the test gateway. They do not grant ownership of a wallet. Access can be revoked through the server's private administration interface.
The original 100 processes remain on Hetzner, with one additional identity on a Windows laptop. The current configuration has 101 registered devices, 64 active voting identities and a quorum of 43. Both hosts share one operator. Version 0.15 reuses observer signatures to complete stalled transfers and retries through an alternate coordinator. Both the active set and its quorum are derived from verified history. Rotation is publicly verifiable. Controller groups are replaced automatically after sustained, independently observed failures. A failed transfer stage is reproduced with the actual signed instruction and verified predecessor certificates. Valid observer responses help complete the original operation; a complaint alone cannot trigger replacement. Timeouts are suspicions, not proof of malicious intent, and do not permanently ban identities. Replacement still requires the surviving global quorum. A minority partition stops; it cannot lower its own threshold or release a prepared transfer lock. Signed file hashes check approved software on honest hosts; they do not prove execution on a hostile server. This build does not yet demonstrate independent ownership, hidden rotation or production financial security.
The wallet checks retained certificates against its authenticated network identity and saved trust anchor, then requests fresh quorum evidence. It keeps sending disabled when it cannot verify current state.
No. Wander is a separate independent-token experiment. The institutional product and its documentation remain at coin.sun-phi.com.
