SUNPHI NETWORK
How the network works
Your wallet signs a transfer. Assigned groups validate it in ordered stages. The active voting quorum certifies the resulting state.
Four levels of validation
- 01
Wallet authorisation
Your signing key authorises the exact transfer instruction. The protocol checks ownership, token versions and account state against the verified history.
- 02
Account controllers
Assigned controller groups check the proposal for the sender and recipient. Successor groups confirm readiness to hold the proposed state.
- 03
Validation of controller evidence
The next validation level signs confirmations bound to the proposal and the account-controller certificates.
- 04
Validation across levels
The fourth level checks evidence from the preceding levels and signs a certificate bound to that evidence.
After these checks, the active voting quorum completes the finalisation rounds. Each node verifies the required certificates before applying the state change. The wallet verifies the certified history to calculate your balance.
Sequential validation cycles
Validation stages follow a defined order. Within each group, nodes can check and respond in parallel. A quorum certificate collects enough valid signatures from the assigned members to satisfy that stage's threshold.
How groups are assigned
Controller assignments are computed from the active registry, public network state and hash rankings. Account epochs and certified state changes determine which groups hold each role. The same inputs produce the same assignment, so participants can verify it.
Continuity between cycles
Nodes retain signed votes, pending locks and certified history in durable journals. Recovery resolves a pending decision before a conflicting state change can complete. Progress resumes when the required groups and quorum are available.
Your wallet and connection
The wallet encrypts its signing key on your device. To use the same wallet on another device, restore its latest encrypted backup with the backup password. The wallet then checks network history and current signing authority.
Before enabling a transfer, the wallet requests fresh, challenge-bound quorum confirmations for the verified state. After an interruption, reconnect and check the recorded outcome before initiating another transfer.
The wallet establishes gateway access automatically using a device connection key. Wallet operations require the wallet's signing key. SunPhi reviews computer connection requests; signed assignments authorise computing tasks. Active voting membership follows a separate certified network decision.
SunPhi Node runs assigned computing tasks in a dedicated environment with its own state. Keep the computer awake, signed in and online while participating.
Security assumptions
Validation relies on authentic network configuration, protected signing keys, correct verification software and the required honest quorum. A saved checkpoint helps detect history older than the retained state; protection against long-range compromise of quorum keys remains an unresolved security requirement.
Node identities, physical computers and operator groups are distinct. Infrastructure under common control shares operational risks. The deployed server infrastructure is under common control, and admission is reviewed by SunPhi.
Independent security assessment, independent operation and production financial readiness remain to be established. Public, reproducible controller assignment is the implemented selection method.
Tokens and service scope
The deployed network uses test tokens and test fee credits to exercise transfers and validation. These units carry no promised monetary value or redemption entitlement. Reward payments and redemption are inactive.
SunPhi Network covers digital-token transfers. The separate tokenised financial-products project and its documentation are at coin.sun-phi.com ↗.
Applications and installation
Use the web wallet on phones and desktop browsers. Downloads include Windows x64 wallet and node installers and a Linux x64 node package.
Windows installer signing status: unsigned. Compare your download with its published SHA-256 checksum and keep antivirus protection enabled.