Integrations & asset support
How Uniswap, price sources, external launch platforms and data providers fit the system.
On this page
Integration map
| Integration | Role |
|---|---|
| Robinhood Chain | Execution network, canonical stock-token contract identities and underlying chain finality. |
| Uniswap v4 | PoolManager, hook callbacks, flash accounting and canonical Sinjoh pools. |
| Universal Router / Permit2 | Direct SDK swaps, explicit spending approvals and supported atomic multi-hop execution. |
| Uniswap API / 0x | Hosted user-trade quote/transaction routing; separate from automated Settings paths. |
| Chainlink feeds | Configured USD valuations with freshness requirements. |
| Pons / Long | Approved factory/pool source rules for qualifying backing and discovery; a bonding-curve-only token is not automatically pool-supported. |
| Pools.trade / Flap.sh / CASHCAT | Portfolio discovery/validated source coverage; visibility does not automatically grant protocol backing eligibility. |
| Privy / Supabase | Account authentication and embedded wallets / persistent public profiles and avatar storage. |
| Alchemy | Indexed wallet candidate discovery; on-chain balances and validated price sources determine displayed holdings. |
| Envio / IPFS providers | Indexed protocol history / reproducible content-addressed reward and metadata publications. |
Support has several levels
Distinguish discovered, priced, backing-eligible, path-registered, sized-quote-executable and live-transaction-verified. An integration can satisfy one level without satisfying all the others. For example, accepting a stock directly as market backing does not require or prove that an ETH-to-stock prize conversion can fill a particular amount.
Provider deployment lists and token labels are starting points. Compatible hook behavior, exact trade types, source freshness, transfer restrictions, actual reserves and full-route execution must be checked in the intended chain/deployment.
Underlying protocol references
- Robinhood canonical contracts
- Uniswap v4 architecture and references
- Chainlink Data Feeds
- Safe documentation
These references describe the underlying projects. Sinjoh-specific fees, authority, source precedence, market accounting and supported integrations are defined in the relevant guides here.
Skip to documentation