Ecosystem Context
Why Solana
Solana has the rails. Real World Commerce needs business context.
Solana provides credible rails for fast, low-cost, internet-scale payments and portable actions. RWC Guide defines the business context layer that those rails still need. This page explains how the two fit together — and what is live versus roadmap today.
Rails plus business context
1. Why crypto rails matter
Crypto rails settle value programmatically, across borders, without depending on a single payment processor or a multi-day clearing cycle. Throughput on networks like Solana is high enough that internet-scale traffic — many small payments, many concurrent actions — is realistic instead of theoretical. For commerce, that means a rail can carry an agent-initiated purchase or a routine merchant settlement without the friction model that legacy rails impose.
2. Why stablecoin payments matter
Stablecoins denominate that programmable value in units that buyers and sellers already understand. A buyer does not have to reason about gas-token volatility before placing an order, and a merchant does not have to convert a speculative asset back to operating currency to balance their books. Stablecoins turn the rail into a payment instrument a real business can actually receive — which is the precondition for any meaningful commerce on-chain.
3. Why portable actions matter
Portable action standards let an interface anywhere on the web present a structured request — book this appointment, pay this invoice, confirm this order — that any compatible client can execute. The action travels with the business, not with a particular app. For commerce networks and AI agents, portable actions are how a Known Business exposes the things it is willing to fulfill in a form a reader can act on without bespoke integration.
4. Why merchant context is still missing
Rails, stablecoins, and portable actions are necessary but not sufficient. None of them describe which businesses exist, what they sell, where they operate, what they have proved, or which actions they are prepared to fulfill. Without that business context layer, a payment rail routes value to opaque counterparties, and an AI agent answers commerce questions from stale scraped data. The gap is not infrastructure — the gap is structured, owner-controlled merchant context.
5. Why Known Businesses matter
A Known Business is a business whose record is structured, current, and reviewable by systems — the kind of counterparty a payment rail, marketplace, or agent can route to with confidence. Known Businesses make the difference between a rail that technically works and a commerce network that participants will trust. RWC Guide explains the category; the Known Business Check on this site diagnoses readiness across Identity, Understanding, Proof, and Consistency.
6. Conceptual integration paths
Several integrations sit at the boundary of this page and live product. They are written here as concepts so builders can plan, not as live promises: wallet-connected claim flows, Solana Pay merchant readiness checks, Blinks for claim and proof actions, structured payment endpoint fields on a business record, on-chain attestations of credentials, and protocol-backed portability of the record itself. Each is marked conceptual or roadmap below until IdentityRecord ships it as live.
7. Live vs roadmap status
Anything not marked Live here is not live on this site. Conceptual items are integration patterns for builders to evaluate; Roadmap items will only be described as live once IdentityRecord ships them.
| Capability | Status | Notes |
|---|---|---|
| RWC Guide category pages and Known Business Check | Live | Public diagnostic and category narrative ship in the MVP. |
| Owned business record + AI Page on IdentityRecord | Live | Owners build and maintain the record on IdentityRecord today. |
| Wallet-connected claim flow | Conceptual | Concept for builders; no wallet is required on RWC Guide today. |
| Solana Pay merchant readiness checks | Roadmap | Educational only today; payments are not processed in the MVP. |
| Blinks for claim and proof actions | Conceptual | Conceptual builder pattern; no Blinks are wired to the diagnostic. |
| Structured payment endpoint fields on a business record | Roadmap | Roadmap on IdentityRecord; not described as live on RWC Guide. |
| On-chain attestations of credentials | Roadmap | Roadmap; blockchain-backed proof is not live anywhere on this site. |
| Protocol-backed portability of the record | Roadmap | Roadmap per the global compliance footer; do not treat as live. |
Run the Known Business Check
See how your business reads to AI systems and commerce networks across Identity, Understanding, Proof, and Consistency — no wallet involved.
Run the Known Business Check