MasayumeDocs
Open app
How it works

How Masayume fits together

The app, the markets and the services behind each action.

Reviewed 2026-09-07

Masayume brings several ways to use the same price markets into one app. A normal call, a copied trade and a duel pick all depend on a real market Window. Each feature adds its own rules around that market.

Interactive system map

One app, several clear boundaries

Market reads, authorized trades and server features take different routes.

Masayume

Explore each part and its connections. Expand to use more of your screen.

Follow an arrow to explore a connected part.

Selected part · 1 of 11You + your wallet

Choose a call or a feature

What this part does

The browser shows quotes, records your choices and asks for the signatures the selected route needs. Reading a market does not require spending permission.

Control & permission Your wallet authorizes funds and grants. The app does not own your wallet.

Outgoing connections

  • From You + your walletreadsRead or display
  • From You + your walletapprovesAction or record
  • From You + your walletfeature requestAction or record
  • From You + your walletgame socketRead or display
Inside the boxYou + your wallet

The browser shows quotes, records your choices and asks for the signatures the selected route needs. Reading a market does not require spending permission.

Control & permission Your wallet authorizes funds and grants. The app does not own your wallet.

Solid arrows show actions or recorded data; dashed arrows show reads and display updates. The map describes implementation paths, not a claim that every operator is online.
Read the map as text
  1. You + your wallet Shared market reader: reads.
  2. Shared market reader Market data: public facts.
  3. You + your wallet Wallet or bounded key: approves.
  4. Wallet or bounded key Checked order lane: signed intent.
  5. Checked order lane DreamDEX venue: direct order.
  6. Checked order lane Masayume contracts: vault route.
  7. Masayume contracts DreamDEX venue: venue call.
  8. You + your wallet Next server routes: feature request.
  9. You + your wallet Long-running operators: game socket.
  10. Next server routes Configured AI provider: model request.
  11. Next server routes Postgres records: stored records.
  12. Long-running operators Masayume contracts: bounded calls.
  13. Long-running operators Postgres records: decisions + match history.
  14. Long-running operators Configured AI provider: agent read.

One app, several clear boundaries

Masayume

Select a part to see what it does and who controls it. The map adapts to the space available.

Follow an arrow to explore a connected part.

Selected part · 1 of 11You + your wallet

Choose a call or a feature

What this part does

The browser shows quotes, records your choices and asks for the signatures the selected route needs. Reading a market does not require spending permission.

Control & permission Your wallet authorizes funds and grants. The app does not own your wallet.

Outgoing connections

  • From You + your walletreadsRead or display
  • From You + your walletapprovesAction or record
  • From You + your walletfeature requestAction or record
  • From You + your walletgame socketRead or display
Inside the boxYou + your wallet

The browser shows quotes, records your choices and asks for the signatures the selected route needs. Reading a market does not require spending permission.

Control & permission Your wallet authorizes funds and grants. The app does not own your wallet.

Solid arrows show actions or recorded data; dashed arrows show reads and display updates. The map describes implementation paths, not a claim that every operator is online.

Read the map as text
  1. You + your wallet Shared market reader: reads.
  2. Shared market reader Market data: public facts.
  3. You + your wallet Wallet or bounded key: approves.
  4. Wallet or bounded key Checked order lane: signed intent.
  5. Checked order lane DreamDEX venue: direct order.
  6. Checked order lane Masayume contracts: vault route.
  7. Masayume contracts DreamDEX venue: venue call.
  8. You + your wallet Next server routes: feature request.
  9. You + your wallet Long-running operators: game socket.
  10. Next server routes Configured AI provider: model request.
  11. Next server routes Postgres records: stored records.
  12. Long-running operators Masayume contracts: bounded calls.
  13. Long-running operators Postgres records: decisions + match history.
  14. Long-running operators Configured AI provider: agent read.

The four parts

PartWhat it does for you
The appShows prices, explains tickets, connects your wallet and displays your receipts.
DreamDEX on SomniaSupplies the market contracts, live orders, fills and settlement.
Masayume contractsHold trading balances, enforce spending permissions and manage specialist tickets, reserve shares and duels.
Masayume servicesFind opponents, run strategies, read X mentions, provide AI answers and keep useful history.

The checked-in app configuration points to Somnia Shannon testnet, chain 50312. Test collateral and STT for transaction fees have different jobs. A displayed test balance is not a claim about real-money value.

Reading is separate from signing

The market reader has no account or signing key. It reads the indexer, price feed and chain. Every signer gets a separate session, bound to one account and one role.

Your wallet signs ordinary transactions. A browser key can sign under permission you granted. A strategy runner or X executor acts under its own bounded grant. Sharing a market data connection does not make those signers share a wallet.

What decides the result?

The browser does not declare a winning trade. Market contracts and oracle answers determine settlement; receipts record actual fills. Masayume's contracts apply the rules for their ticket type.

Server responsibilities vary. Private mode relies on a desk to connect a claim back to its owner. Season prizes use an admin-controlled payout. Arcade scores are checked by replay on a server. These distinctions are explained on the relevant pages.

Choose a deeper view

For the current deployment, use Status. A contract address in the source is a deployment record; it does not establish that every connected service is running today.

Source notes

This guide follows the application code reviewed on 2026-09-07. Links point to that reviewed commit and require repository access. GitHub may show 404 if you are signed out or do not have access.

On this page