SUNPHI
Your keys. Your transfers. A verified state across your devices.
One wallet across your devices
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.
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 network. A second device does not need to run a server or create another network.
Open SunPhi in Chrome or Safari. Connect with your invitation, then create a wallet or restore its encrypted backup.
A Windows application with local encrypted storage. Restore your latest backup to keep the same address and verified balance.
Install the computing application, prepare this computer and submit its connection request for owner approval.
NODE SOFTWARE / 0.16.3
Windows and Linux share the same transaction rules and quorum protocol. Install a node, view its status and set a reward wallet address. New installations generate keys locally; admission and voting assignments require separate network certificates.
An automatic Windows service with an optional wallet interface. It runs without an open wallet or Windows login. Your reward address can belong to another device.
The node runtime, installation script and local status console. Choose an automatic service with or without a link to the web wallet.
Follow the installation, provisioning and recovery steps. Verify the package checksum before installation.
Operator registration & register ↗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 access the same wallet, save its encrypted backup on the first phone and restore it on the second using the same password.
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.
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 network gateways. They do not grant ownership of a wallet. Access can be revoked through the server's private administration interface.
Wallets check signatures, token versions, history and fresh quorum evidence. Interrupted transfers retain the same signed instruction; reconnecting verifies the result before another operation. Node registration and voting authority require separate network certificates.
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. SunPhi is a separate digital-token network. The institutional product and its documentation remain at coin.sun-phi.com .
CURRENT NETWORK STATUS
This deployment uses test tokens with no promised monetary value. Server rewards, payouts and redemption are not activated. Windows installers are not yet Authenticode-signed; verify the published SHA-256 checksums before installation.
100 server controller identities are distributed equally between Hetzner and OVHcloud, with one additional registered Windows node. The current active group has 64 voting identities and requires 43 confirmations. Two public gateways provide alternate wallet access. All servers remain under one operator; losing either controller host pauses confirmations safely. Primary-host dependencies remain in peer routing and device admission.
The four-level certificate architecture is implemented with public, verifiable rotation. Hidden rotation, proof of execution on hostile hosts, open admission, independent security audit and production financial readiness are not established. Browser wallets are available on phones; native mobile, macOS and ARM packages are not included.
New operators submit signed applications and consent to public identity disclosure. The network owner verifies and approves admission through the existing Admin panel. Approval prepares a connection; certified registration and voting assignment remain separate. Application release 0.16.3 uses the approved controller core 0.15.0. Wallet addresses and balances are retained when updating.
