Assets and markets

The native gas token of Midas Chain. Every wallet on chain 64327 shows it without being asked, because it is not a contract. Nothing to import.

The collateral and quote token of every Pactol market. Test money with a public faucet, never real funds. Deposits into the perp and options vault, and every spot quote leg, are denominated in this token. The v5 re-genesis on 2026-09-16 rebuilt this chain from a fresh genesis, so every pre-v5 address now holds no code at all. This entry named the pre-v5 token 0x057ef64E until 2026-09-18, which is the address the live gateway's only spot pair does NOT quote against: the terminal rendered that pair as "WMIDS/Unknown token 0x8198…FbB7" because the quote leg it was served could not be resolved here. Address verified by eth_getCode on 2026-09-18 and against POST /info spotPairs.

Deployed 2026-09-07 via CREATE2 (Arachnid deployer, salt pactol-wmids-v1); eth_getCode and symbol() verified on chain 64327.

Deployed on the pre-v5 chain at 0x261D8c5e9742e6f7f1076Fa1F560894524e19cad and NOT redeployed. The v5 re-genesis on 2026-09-16 rebuilt this chain from a fresh genesis, so that address holds no code (eth_getCode, 2026-09-18). The address is dropped rather than kept beside a retired status, because rule 2 of registry/README.md is about exactly this: a stale address does not fail, it resolves and gets copied into a config. Both spot pairs it was a leg of are retired with it.

The canonical bridge representation of Circle's Sepolia USDC, minted by the OptimismMintableERC20 factory. The contract exists and its remoteToken is the L1 USDC below; total supply is still zero because nobody has bridged yet. Shown as USDC.e because its on-chain symbol is the same string as the faucet token, and two different tokens reading USDC in one wallet is how a deposit goes to the wrong address. The L2 sweeper converts it 1:1 into Testnet USDC through the CollateralAdapter before it becomes tradable collateral.

The only token a Pactol deposit address accepts on Ethereum Sepolia. Anything else sent to a deposit address is not swept and not credited.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

Listed on the pre-v5 engine and NOT re-listed after the 2026-09-16 re-genesis: POST /info meta answers with 22 perps (read 2026-09-18) and this is not one of them. The asset id is dropped rather than kept, because the engine renumbers on each listing round and a stale id is what put another market's name on a live row.

The options engine, the gateway actions and the trading screen all exist and are wired end to end. Zero series are configured on chain 64327, so the venue lists nothing to trade yet.

Hidden at the gateway since 2026-09-06. Both token addresses are Arbitrum Sepolia contracts carried over from before the 2026-09-04 move and eth_getCode returns 0x for both on chain 64327, so no balance can exist on it and no order can settle. The ENGINE STILL LISTS IT and always will: there is no delist command, so the listing is in the WAL for good. What changed is that the gateway now masks it (ML_GATEWAY_SPOT_HIDDEN_PAIRS), which drops it from spotPairs, refuses spotBook, and refuses a new order with SPOT_PAIR_HIDDEN before the command reaches the engine. Cancel and withdraw are deliberately not masked, so nothing already resting or already held on it is trapped.

The reverse-orientation pair, listed on the pre-v5 engine. The live gateway lists only WMIDS/USDC (read 2026-09-18), and this entry's base leg was the pre-v5 USDC, which holds no code. The v5 re-genesis on 2026-09-16 rebuilt this chain from a fresh genesis, so every pre-v5 address now holds no code at all.

Listed on the pre-v5 engine 2026-09-07 (seq 2114139). Both legs named pre-v5 tokens and the live gateway does not list the pair (read 2026-09-18). The v5 re-genesis on 2026-09-16 rebuilt this chain from a fresh genesis, so every pre-v5 address now holds no code at all.

Listed on the pre-v5 engine 2026-09-13. Its base leg is the pre-v5 USDT, which holds no code after the 2026-09-16 re-genesis, and the live gateway lists only WMIDS/USDC (POST /info spotPairs, read 2026-09-18).

The one spot pair the live gateway lists (POST /info spotPairs, read 2026-09-18). Its quote leg is the v5 TestnetUSDC; this entry named the pre-v5 token until 2026-09-18.

Retired with its vault. MLPVault was deployed on the pre-v5 chain and not redeployed on 64327, so a share is a claim on a contract that is not there: the /assets page must not advertise one while the /vaults page cannot read a balance. Earlier note: Shares in the backstop vault at 0x807D3b63765693169D67393D979AF2E72de0abb0. NOT an ERC-20: a mapping inside the vault, so it cannot be imported into a wallet.

Shares in a copy-trading vault created by a leader through the CopyVaultFactory at 0x44f2EDBD66A5E6fCc21815C30160f395e015EAb4. NOT an ERC-20: a mapping inside the vault that holds it, so it cannot be imported into a wallet, and a child vault has no fixed address - the factory registry is the discovery mechanism.