Delete Wallet
Permanently remove your wallet from this device. Make sure you have backed up your seed phrase.
Loading your wallet...
Your privacy-focused dApp on Solana that enhances user privacy by separating deposits from withdrawals through pooled execution and rotating addresses.
Restore your Private Bay wallet using your 12 word seed phrase.
Privacy-Enhanced Cash on Solana
The Private Bay is a privacy-focused wallet system on Solana that enables users to deposit, manage, and withdraw SOL and SPL tokens while reducing on-chain linkability between their actions. The platform abstracts direct interaction with individual deposits by using a shared execution layer, allowing users to interact with assets without withdrawals being directly tied to the original deposit addresses.
By combining rotating deposit addresses with automated fund consolidation, Private Bay improves unlinkability between deposits and withdrawals while maintaining reliable balance enforcement and consistent asset accounting.
When assets are deposited into Private Bay, they are converted into internal balance credits within the platform. These credits represent a claim on deposited assets and are managed by the platform’s accounting layer rather than remaining tied to individual on-chain tokens or the original deposit transaction.
Each balance credit contains the asset type and amount associated with a user’s deposit, independent from the original on-chain transaction. Internal identifiers are assigned through platform accounting to track available balances and ensure that each unit of value can be withdrawn only once. This model decouples deposits from withdrawal execution by treating all funds as part of a shared pool, with ownership represented through internal balances rather than by the original deposit address.
User activity is represented internally as accounting records that track deposits, withdrawals, and fees. These records are updated as funds are consolidated and as users perform withdrawals, ensuring that available balances remain consistent with platform liquidity. While these records are not on-chain objects, they provide a deterministic representation of user balances and platform state used to enforce single-use withdrawals and accurate accounting.
When value associated with a balance credit is used for a withdrawal, it is marked as spent within the platform and cannot be used again. This enforces balance consistency and prevents double withdrawals while maintaining separation between the original deposit transaction and the withdrawal destination.
When processing a withdrawal request, the platform verifies that:
Once these checks pass, the platform processes the withdrawal by transferring funds from the platform wallet to the user’s specified destination address. This ensures that all withdrawals are valid while keeping withdrawal execution separate from the original deposit transaction, reducing the ability to correlate the two on-chain.
Users deposit SOL into a rotating deposit address assigned to them. Once the transaction is detected, the funds are automatically consolidated into the platform wallet. An internal credit is issued to represent the deposited amount and associate it with the user’s balance. SPL tokens may be deposited to cover platform fees. This process separates the deposit address from later withdrawals, reducing on-chain correlation between where funds were received and where they are ultimately sent.
Within the platform, user balances are updated based on deposits, withdrawals, and applicable fees. All SOL and SPL tokens are held collectively in the platform wallet, while individual ownership is represented through internal balance credits. This shared liquidity model allows many users to interact with the system simultaneously without exposing which specific deposits relate to which user. Internal accounting manages balance changes, fee deductions, and withdrawal eligibility in a consistent and deterministic manner.
When a user requests a withdrawal, the system verifies that the available balance covers the requested amount and any required SPL token fees. Funds are then transferred from the platform wallet to the user’s specified Solana address. After completion, the corresponding value is marked as used to prevent double withdrawals, ensuring balances remain consistent while keeping the withdrawal separate from the original deposit transaction.
The Private Bay supports relay-style transaction submission in which platform operations are executed through the Private Bay execution layer rather than directly by the user on-chain. This abstracts users from broadcasting their own transactions and separates the observable transaction sender from the final destination.
Relaying capabilities may expand over time to support additional privacy and usability features.
A rotating Solana address used for receiving user deposits. A new address may be assigned to reduce correlation between multiple deposits from the same user.
Optional read-only access used to observe incoming activity and balances
Any standard Solana address provided by the user as the recipient of a withdrawal.
The Private Bay does not require users to manage specialized cryptographic spending or viewing keys; ownership is represented through platform balances rather than user-side cryptographic notes.
| Concept | Implementation |
|---|---|
| Balance Model | Internal balance credits representing claims on pooled assets |
| Transaction Signing | Standard Solana Ed25519 transactions executed by the platform layer |
| Address Rotation | Generation of rotating deposit addresses to reduce correlation between deposits |
| Ledger Structure | Deterministic accounting enforcing single-use of value and balance consistency |
| Value Tracking | Deterministic internal credits representing user claims |
| Identifier Model | Platform-assigned references for accounting and single-use enforcement |
Users pay a withdrawal fee deducted from their internal balance, supporting platform operations while keeping every transaction simple, consistent, and fully controlled.
The Private Bay prioritizes usability and privacy through abstraction, trading direct on-chain interaction for a managed execution layer that enforces platform rules and accounting.
Future versions may introduce automated allocation of $TPB and SOL fees into the liquidity pool, strengthening liquidity, supporting transfers, reliability and stable performance.
A burn mechanism can remove part of collected fees, creating deflation, regulating overall liquidity, and maintaining long-term sustainability within the platform.
Loading your wallet...
No transactions yet
Start by receiving SOL or $TPB
Deposits are consolidated into the platform pool and credited to your privacy-enhanced balance
Deposited funds are automatically consolidated into the platform pool
Your wallet data is stored locally on your device. Always keep a secure backup of your seed phrase.
Download a backup file of your wallet
Permanently remove your wallet from this device. Make sure you have backed up your seed phrase.
SOL is sent directly to Starpay for card issuance
Cards are generated and delivered via email