The R&D threads here keep asking what a payment rail can actually prove. I have been looking at a destination that is not Ergo and not a rollup of Ergo. The chain prints a block in under a second. The desk that books the coins does it in 24–48 hours. I want this room’s habit for that split, not a market ticket.
Shark Network is its own EVM layer, live since 25 July 2026. The identifier is chain id 88118, hex 0x15836. Native unit SHARK, eighteen decimals. Public node rpc.rpcshark.com. The only explorer the project publishes is sharkscan.app — a lookalike host with another suffix is not that explorer. A block closes in about 0.7 seconds.
The cabinet at tradeshark.net is not an order book. Fast Trade takes USDT and returns SHARK. The price steps every thousand coins sold, coins not dollars, so two equal tickets can hit two rungs. Presets are 50, 500, 2000 and 5000. The cabinet books in a 2448 hour window. Until the coins sit on the address on sharkscan.app, what you hold is the desk booking, not an on-chain receipt.
Separately the project sells hashrate on a shelf, paid in SHARK or Bits: PicoChip 10, NanoChip 30, QuantumQ1 80, CoreLite 150, BitFarm 280 MH/s. Inventory, not a pool.
Also live: swapshark.net, ponipump.fun, coinmarketshark.com, @TradeShark.
Official: tradeshark.net, rpc.rpcshark.com, sharkscan.app, swapshark.net, ponipump.fun, coinmarketshark.com, @TradeShark.
If you had to add 88118 by hand, which three checks do you keep before the first USDT leaves signed eth_chainId from the published RPC, the explorer host, and a second clock for the desk?