Architecture
Not live yet
Stratus is not live yet. This page describes features that will be available when the app launches.
Stratus has three layers:
- The Stratus app: the web interface. It reads the chains, prepares transactions and asks your wallet to sign them. It holds no funds and has no special authority over any contract.
- SkyBridge: Airfox's crosschain bridge. It moves value between chains and keeps the registry of multichain tokens. See SkyBridge architecture.
- The Stratus contracts: the token factory and token standard, and the pool module that creates and locks Uniswap V4 liquidity.
The contracts are open infrastructure: anyone can call the factories directly, and the app is one way to do it.
Your wallet
├─► Stratus app (reads, builds, asks you to sign)
│
├─► SkyBridge EntryPoint ──► Diamond (bridge logic + multichain registry) bridging
│
├─► SKY20 token factory ──► SKY20 token (same address on every chain) launching
│ └─► registers the token in the SkyBridge registry
│
└─► PoolFactory ──► Uniswap V4 pool + LiquidityLockPool (+ your position) pool at launch
The contracts at a glance
| Contract | Role |
|---|---|
| SKY20 | The token. An ERC-20 with a fixed global supply. The full supply is minted once, on the launch chain. After that, only the SkyBridge Diamond can mint or burn it, as tokens move between chains. It has no owner. |
| SKY20 token factory | Launches SKY20 tokens and deploys them on more chains. It sits at the same address on every chain, and it places each token at an address derived from the creator and the token's configuration, so a token has the same address everywhere. |
| PoolFactory | Creates a Uniswap V4 pool, mints the creator's liquidity position straight into a new lock pool, and binds it, in one transaction. One per chain. |
| LiquidityLockPool | One per locked pool. Holds the V4 position, splits its trading fees, and returns the position to the creator when the lock ends. No owner, no upgrade. |
| LockFeeSchedule | The table that prices a lock: lock length in, platform share out. |
| HookRegistry | The per-chain list of V4 hooks a pool may use. |
| StratusTaxHook | The hook that charges a Taxed token's buy and sell rates inside its pool. |
Details, functions and events: Contracts.
How a launch works end to end
A token launch with a trading pool, as the app runs it:
- Predict. The app picks a random
userSaltfor the draft and asks the token factory for the token's address withpredict(creator, userSalt, cfg). The address depends on the creator's wallet, the salt and the full token configuration (name, symbol, decimals, global supply, launch chain, mint recipient, profile and native chains). With a pool, it also asks the PoolFactory for the lock pool's address withpredictLockPool(...). Both appear at Review, before anything is signed. - Check. Before each transaction the app reads the live contracts (the pool factory, the hook registry, the minimum lock, the pair token) and simulates the call. Anything that would revert is shown as a plain message instead of a transaction.
- Launch. On the launch chain, the creator calls
launch(userSalt, cfg, buyTaxBps, sellTaxBps, treasury). The factory deploys the SKY20 at the predicted address, which mints the global supply to the mint recipient, and registers the token in the SkyBridge registry with its native chains as the set of chains it may bridge between. The factory emitsLaunched. - Approve. The creator approves the PoolFactory to take the token deposit, and the pair token too if the pair is not ETH.
- Create the pool. The creator calls
launchLockPool(userSalt, cfg, lp, sCfg). In one transaction the PoolFactory deploys the LiquidityLockPool at its predicted address, initializes the V4 pool, mints the position to the lock pool, binds it, and refunds any unused deposit. It emitsLaunchedLockPool. - Expand (optional). For each other native chain the creator chose to deploy now, the app switches network and calls
expandToChain(...). The token appears at the same address with zero supply and emitsExpanded.
A launch without a pool is steps 1, 2, 3 and 6.
How a Stratus token moves between chains
- Bridging goes through SkyBridge's Chainlink CCIP route.
- The registry marks a Stratus token as native multichain, so on arrival SkyBridge mints on the token's existing contract at the same address, instead of creating a separate wrapped token.
- On a chain where the token is not native, its name is shown as
SkyBridge NAMEand its symbol assSYMBOL. - A token can only bridge between chains in its allowed set, which starts as its native chains.
- The token must already be deployed on the destination. The app checks this before a bridge and shows Expand token first when it is not.
- No chain's supply can ever exceed the token's global supply.
Where the app gets its data
| Data | Source |
|---|---|
| Balances, allowances, contract state | Direct reads from Ethereum and Robinhood Chain |
| Launched tokens in My tokens | The token factory's Launched events, filtered by creator, plus launches recorded in the browser |
| Bridge history in Activity | SkyBridge's API, merged with the session's own records |
| USD values | Chainlink price feeds on Ethereum |
| NFTs | An NFT data provider on Ethereum; recent Transfer events on Robinhood Chain |