Transaction Flow
Every transaction in Solident follows a secure and transparent flow.
From user intent to on-chain confirmation, each step is protected by biometric + pattern verification and hardware-level signing.
"Every send, every swap, every stake — verified by you, signed by your device."
Step 1 — User Action
User initiates a transaction: transfer SOL, swap tokens via Jupiter, or interact with a dApp.
The wallet UI displays transaction details: token, amount, recipient, and fees.
Nothing proceeds until the user explicitly confirms.
Step 2 — Step-Up Authentication
Before execution, Solident requires re-verification:
Face scan: to prove physical presence.
Pattern unlock: as the secondary factor.
Both checks must succeed before moving to signing.
Step 3 — Local Transaction Signing
Transaction data (amount, recipient, token program) is passed into the secure enclave (TEE).
Private keys bound to the user identity sign the transaction inside the enclave.
Keys never leave the hardware — only the signed payload is released.
Step 4 — Broadcasting to Solana
Signed payload is sent to the blockchain via Helius RPC.
Helius ensures low-latency broadcasting and reliable confirmation tracking.
User sees real-time updates: pending → confirmed → finalized.
Step 5 — Confirmation & Logging
Once confirmed, the transaction appears in the Transaction History.
Log includes details + timestamp + biometric event link.
Data is encrypted locally and optionally synced across devices.
Security Principles in the Flow
Biometric + pattern re-check: Prevents malware or automation from sending funds without the user.
Hardware signing: Keys never exposed to OS or apps.
Trusted RPC: Helius provides stable endpoints to reduce failures or reorg issues.
Encrypted logs: Every action tied back to the rightful identity.
The transaction flow ensures that every move on Solana from simple transfers to complex swaps is not only fast, but also verified at the deepest level of user presence and device security.
Last updated