Chain profile
Blockchain-native
Solana.
Abstract. Solana Foundation (Swiss non-profit — protocol research + ecosystem grants; protocol itself is permissionless and operated by the validator set)
Facts
Chain identity at a glance.
- Type
L1
- Native settlement
- SOL · USDC · USDT · PYUSD
- Account model
- SVM (Solana Virtual Machine) · ed25519 keypair-derived account addresses · accounts owned by programs · program-derived addresses (PDAs) for program-managed accounts (not EOA/AA in the EVM sense)
Vendor stack · L5 → L1
The 5-layer Stable Stack.
Each row is one named vendor slot from the chain's vendorStack. Solid markers are code-enforced
(the chain blocks or signs); dashed markers are
policy-enforced (the chain flags, humans or systems act on
the signal).
L5 → L1 — application down to network
L5 · Application
wallet
Phantom · Backpack · Solflare · Coinbase Wallet (Solana support) · Fireblocks (Solana institutional custody surface)
C1 ◇ policy-enforced
payment-protocol
Solana Pay (URL-scheme-based payment protocol · merchant-acceptance primitive)
C6 ◇ policy-enforced
tokenized-rwa-issuer
PayPal PYUSD (Paxos-issued · NYDFS limited-purpose trust posture; Solana deployment via Paxos multichain expansion) · other Token-2022-based tokenized-asset issuers
C13C14 ◇ policy-enforced
L4 · Account
account
Solana Program Account (ed25519 keypair-derived account addresses · accounts are owned by programs · program-derived addresses (PDAs) for program-managed accounts)
C1 ◆ code-enforced
custody
Coinbase Custody · Anchorage Digital Bank (OCC-chartered) · BitGo · Fireblocks (institutional custody surfaces for SOL and SPL-token assets; extension-aware custody is a non-trivial integration burden)
C1 ◇ policy-enforced
L3 · Execution
swap
Jupiter Aggregator (routing meta-DEX across Solana DEX liquidity) · Raydium · Orca
C13 ◆ code-enforced
sanctions-oracle
TRM Labs on-chain monitoring (Solana coverage) · Chainalysis Solana coverage (the Chainalysis OFAC Oracle is Ethereum-native; Solana sanctions enforcement routes through off-chain TRM / Chainalysis surfaces and issuer-level freeze actions)
C2 ◆ code-enforced
token-extensions
Token-2022 Transfer Hooks + Extension Set (the load-bearing compliance differentiator: transfer hooks, required memos, non-transferable tokens, permanent delegate authority, default account state, CPI guard, interest-bearing tokens, confidential transfers)
C13C16 ◆ code-enforced
bridge
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport between Solana and Ethereum / other CCTP-supported chains) · Wormhole (Solana ↔ multichain transport · Wormhole originated as Solana-Ethereum bridge and remains a load-bearing primitive on Solana) · Mayan / deBridge
C7 ◆ code-enforced
L2 · Consensus
consensus
Tower BFT consensus over Proof-of-History (VDF-derived timestamping) · permissionless validator set with effective concentration via Jito / Helius / Figment / Solana Foundation / Coinbase stake
C10 ◆ code-enforced
validator-client
Jito-Solana (dominant validator client · bundle-auction MEV model) · Agave (Solana Foundation-maintained reference client) · Firedancer (Jump Crypto-developed second client; long-awaited client-diversity inflection)
C10 ◆ code-enforced
L1 · Network
network
Turbine block-propagation protocol + Gulf Stream mempool-less transaction forwarding · RPC layer operationally concentrated (Helius · QuickNode · Triton · Solana Foundation-operated RPCs)
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- CCTP v2 (canonical USDC burn-and-mint)
- Wormhole (load-bearing Solana ↔ multichain transport)
- Mayan
- deBridge
Related paths
Paths that route through Solana.
Compliance paths whose settlementChains
include solana or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/solana.ts —
full discipline header, sources, and per-field VERIFY
inventory live in the chain-profile source file. See the path resolver to see
this chain in a resolved compliance journey.
Explore the architecture
Pick a thread.