Verify a Token or Lock Pool
Stratus is not live yet. This page describes features that will be available when the app launches.
Anyone can deploy a contract with any name. These checks tell you whether a token or a lock pool was really created by the Stratus contracts, and what its fixed rules are. They are the same reads the Stratus app relies on.
The factories are permissionless: anyone can launch a token, with or without the Stratus app. A token that passes these checks was created by the Stratus contracts and follows their rules. It says nothing about the project behind it.
Official factory addresses
These are the Stratus factories deployed on mainnet. A token or lock pool created by Stratus traces back to one of them.
| Contract | Chain | Address |
|---|---|---|
| Token factory | Ethereum | 0x6f2198d19932d1eA402464f8Cd1F41B26e5e5f3F |
| Token factory | Robinhood Chain | 0x6f2198d19932d1eA402464f8Cd1F41B26e5e5f3F |
| PoolFactory | Ethereum | 0x42809129575B1342221Ea22Cdaa8368445E7ED19 |
| PoolFactory | Robinhood Chain | 0x23A8D163dafEfDB614228641425Af917653ca88c |
The token factory has the same address on every chain. Each chain has its own PoolFactory. Both are upgradeable proxies, so these addresses stay the same across upgrades.
Check a token
1. Ask the SkyBridge registry
Every token the factory launches is registered in the SkyBridge registry, which lives on the SkyBridge Diamond. The Diamond addresses are listed on Official Addresses, and Robinhood Chain has its own Diamond address.
On the Diamond for the chain you are checking, call:
| Read | What to expect |
|---|---|
isNativeMultichainToken(token) | true for a registered multichain token |
getAllowedChains(token) | The CCIP chain selectors the token may bridge between (its native chains, unless SkyBridge has widened them) |
getTaxParams(token) | (buyBps, sellBps, treasury): zero and address(0) for a Clean token |
The SKY factories (the token factory and its NFT counterpart) are the only holders of the registry's registrar role, so true means the token was registered by the token factory. The Stratus app makes the same isNativeMultichainToken read before it bridges a token or uses one as a pool pair.
2. Read the token itself
On the token contract:
BRIDGE()should equal the SkyBridge Diamond for that chain.LAUNCH_CHAIN()names the chain where the supply was minted.GLOBAL_SUPPLY()is the total supply across every chain.
3. Find its launch event
On the launch chain, the token factory emitted Launched(token, creator, salt) when the token was created. Look for that event with your token's address as token, and check that it came from the token factory's address. It tells you the creator and the launch transaction. Each later deployment to another chain emitted Expanded(token, chainId, salt) on that chain.
This is how the Stratus app builds the My tokens list: it filters Launched by creator on each chain.
4. Check the same address on other chains
A Stratus token has the same address on every chain it is deployed to. On another chain, code at that address plus isNativeMultichainToken(token) == true on that chain's Diamond means the token is deployed there. Before every bridge, the app checks that the token is registered on the source chain's Diamond, that the destination is in getAllowedChains(token), and that there is code at the same address on the destination: no code there means the token has not been expanded there yet.
Check a lock pool
1. Find its creation event
The chain's PoolFactory emitted LaunchedLockPool(pool, distributor, creator, destination) in the transaction that created the pool. Check that the event came from the PoolFactory's address for that chain. For a token launched in the Stratus app, that transaction is the Create the pool step, right after the token launch.
2. Read the pool's rules
On the lock pool contract:
| Read | What it tells you |
|---|---|
FACTORY() | The PoolFactory that created it. It should match the PoolFactory address for that chain. |
TOKEN() | The project token. It should be your token. |
PAIR() | The other side: address(0) for ETH, or the stablecoin or token |
CREATOR() | Who receives the pair-side fees and gets the position back at expiry |
DESTINATION(), DESTINATION_TARGET() | Where token-side fees go (1 treasury, 2 burn) |
bound(), tokenId() | Whether a V4 position is locked, and which one |
unlockTime() | When the creator can withdraw the position |
lockSchedule(i), segmentCount() | Each lock segment's end time and platform share |
activePlatformBps() | The platform's share applied to the next collection |
3. Check the locked position
The position is a Uniswap V4 position NFT. Its owner on the V4 PositionManager should be the lock pool, and its pool key should match CURRENCY0(), CURRENCY1(), FEE(), TICK_SPACING() and HOOKS(). The lock pool already checks this when the position is bound, and refuses a position from any other pool.
4. If the pool uses a hook
HOOKS() is address(0) for no hook. Otherwise, the chain's HookRegistry (read it from the PoolFactory's hookRegistry()) reported the hook as active when the pool was created. For the tax hook, taxOf(poolId) returns the rates and treasury fixed for that pool.