Orca provides the infrastructure. Each asset’s terms and any eligibility requirements are defined by its servicer, not by Orca. General information only — not investment, legal, financial, or tax advice.
Why eligibility requirements exist
Regulated assets are issued under legal/regulatory frameworks that vary by asset and jurisdiction. Where they apply, the servicer is responsible for meeting them — including who may hold or trade the asset. They exist for compliance, not exclusivity; what’s required (e.g. identity verification, accreditation, jurisdiction limits) varies by asset.Permissioned pools
A permissioned pool only lets accounts the servicer has marked eligible hold or trade its token. Some regulated assets enforce eligibility this way — onchain, at the token level; others simply carry the label. For assets in a permissioned pool, eligibility is designed to be enforced onchain:- Frozen by default — token accounts start frozen (Solana’s Default Account State extension), so the asset is designed not to move unless your account is eligible.
- Live access control — an onchain layer syncs eligibility from the servicer’s platform, so the pool reflects the servicer’s latest data.
- Shown in the UI — Orca surfaces the servicer’s eligibility-status callouts (e.g. KYC, where required) before you trade.
Trading a regulated asset
- Meet the servicer’s requirements — these vary by asset, and may include identity verification or other steps.
- Trade on Orca — buy or sell against the available onchain liquidity. For permissioned-pool assets, Orca shows the eligibility status reported by the servicer’s platform before you trade.
FAQ
What if my eligibility changes? For permissioned-pool assets, access control syncs with the servicer’s platform, so losing eligibility is designed to stop you from transacting the asset.
How do I meet an asset’s requirements? Through the servicer — the process varies by asset. Any regulated asset you come across in Orca’s UI will have a link to the servicer.