Security Model & Permissions
Yieldbay follows a non-custodial, least-permission design philosophy.
Wallet Permissions
When connecting a wallet, Yieldbay:
Reads public on-chain data
Indexes positions linked to your address
Displays portfolio and strategy context
Yieldbay does not:
Request private keys
Sign transactions without user approval
Move or custody assets
All transaction execution remains user-initiated.
Data Sources
All portfolio data is derived from:
Public Solana blockchain state
Protocol-specific on-chain accounts
Yieldbay does not rely on:
Off-chain balances
Centralized custody
User-submitted data
Execution Safety
Today:
Yieldbay links out to protocol-native interfaces for execution
Planned:
Guided execution using Solana-native primitives, while keeping transactions explicit and user-signed
At no point will Yieldbay execute transactions without clear user consent.
Infrastructure Principles
Yieldbay is designed to:
Preserve composability
Avoid opaque abstractions
Keep protocol risk isolated to underlying protocols
Make permissions explicit
Security is treated as a product feature, not an afterthought.
Last updated