Skip to content

Deployment Addresses

The meme/off-chain deployment uses a BSC platform meme Bridge and Openfish ledger trading. The current production path is:

BSC platform meme token -> Bridge -> Openfish CLOB ledger -> app/API trading

ServiceURLPurpose
Apphttps://openfish.mePublic market UI
CLOB APIhttps://api.openfish.meOrders, balances, market data, waitlist, agent APIs
Gamma APIhttps://gamma.openfish.meEvents, markets, metadata, comments
Data APIhttps://data.openfish.mePositions, value, leaderboard, analytics
Bridge APIhttps://bridge.openfish.meBSC platform meme deposits and withdrawals
Docshttps://docs.openfish.meDeveloper and product docs
Adminhttps://luna.openfish.meInternal administration UI

WebSocket endpoints:

ChannelURL
Marketwss://api.openfish.me/ws/market
Userwss://api.openfish.me/ws/user
RTDSwss://api.openfish.me/ws/rtds
Sportswss://api.openfish.me/ws/sports
Commentswss://gamma.openfish.me/ws/comments

The Bridge supports one configured BSC platform meme token.

FieldCurrent default
ChainBSC
Chain ID56
Token address0xaE71fd8baCc2f17C43a01C3F4aFF6dEEbc194444
Token nameagentic money
Token symbolagentic money
Decimals18

The token address and display metadata are deployment configuration. Admins can update the Bridge asset configuration when changing the platform meme token.


The current branch separates wallet purposes:

WalletPurpose
Platform / Fee ReceiverReceives platform fees, protocol revenue, and configured platform ledger accounting flows
Gas FunderHot wallet used by Bridge withdrawals and gas-funded BSC token transfers
User deposit addressesDeterministically derived from the master seed for each Openfish user wallet

Production should derive system wallets from the configured master seed whenever possible, so private keys can be recovered from controlled seed material.