Safety

Safety Model

DRIP is designed to make stream actions understandable and bounded, but no wallet interaction is risk-free. The safety model combines non-custodial wallets, previews, simulation, allowlists, and conservative access behavior.

Safety principles

No private key custody

DRIP does not ask for or store your private key. Transactions are approved through your wallet.

Transaction preview

Users should see the intended action, affected stream, and expected outcome before signing.

Simulation before signing

When possible, transactions are simulated before the wallet prompt to catch failures and reduce surprises.

Onchain allowlist

Private alpha access can be restricted to approved wallets through an onchain allowlist.

Fail-closed configuration

If access state cannot be verified, alpha and agent access should default to blocked rather than allowed.

Payer controls unvested funds

The payer can pause, resume, or cancel streams and recover unvested funds according to stream rules.

Limitations and risks

DRIP is not claiming to be fully audited.
A transaction preview or simulation can reduce risk, but it cannot guarantee every outcome in all conditions.
Wallet drain is not impossible in the general sense of wallet security. Users must still verify prompts, domains, accounts, and amounts.
Private alpha may change as testing continues.
Native SOL is the supported asset for now, so users should not assume token support unless announced.

User responsibility

Use small amounts during alpha, verify the app you are using, and do not sign a transaction unless the preview and wallet prompt match what you intended to do.