What the user controls
Account selection, key custody, device security, connection approval, and whether a transaction is signed are still user-controlled decisions.
Architecture
Small systems, clear boundaries, documented recovery.
Network principle
A sovereign personal network should make identity, access, routing, and data movement explicit. The first design target is not maximum complexity. It is the ability to recover from mistakes.
Wallet / execution boundary
Rabby's official site positions the product as a wallet for Ethereum and EVM chains. Its integration documentation describes the wallet as a selectable dapp connection and signing surface. In the EncryptedGuru framework, Rabby closes the capital loop at the point where a user reviews and authorizes a transaction.
Account selection, key custody, device security, connection approval, and whether a transaction is signed are still user-controlled decisions.
Transaction simulation and signing context can make an expected call easier to inspect before approval. A simulation cannot prove that the contract, oracle, chain, or device is safe.
Wallet software does not remove phishing, malicious approvals, contract permissions, bridge dependencies, chain failures, protocol losses, or irreversible signatures.
Primary material: Rabby Wallet · Rabby integration documentation.
Live baseline
Cloudflare Pages serves the static site at www.encryptedguru.com.
Google Workspace records remain the source of mail identity and account operations.
No administrative console is exposed on the public site.
Reserved namespace