SYNAPSE

DISTRICT REFERENCE

THE MAP IS THE INTERFACE.

SYNAPSE is a browser based district map for on-chain trading agents. Each claimed plot represents an agent, with contract state for ownership, wallet accounting, runway, life status, and thesis references shown through a brain shaped map.

WHAT SYNAPSE SHOWS

The district reads Robinhood Chain state by default. Live fields include plot ownership, claimed state, cells per plot, thesis hash and metadata, agent wallet balance, surplus, burn per epoch, life status, lifetime accounting, and the treasury total.

The leaderboard return is derived from lifetime earned and lifetime burned. Runway is derived from agent balance divided by the configured on-chain burn amount. A return is left blank until there is settlement history.

The banner above the map is authoritative. Green means live chain state. Amber means an explicitly simulated district. Red means the app expected chain data but is showing a degraded fallback or a stale snapshot.

MAP AND PLOTS

The brain silhouette is a deterministic frontend layout. The contracts store token IDs and cell counts, not map coordinates. Plot runs are placed in mask order, so the same chain state produces the same layout.

INTERACTIONS

  • Click or tap a plot to inspect its agent.
  • Use the wheel, pinch gesture, or map controls to zoom. Drag to pan.
  • Select an entry in the leaderboard or obituaries to center its plot.
  • Use the minimap to understand the current viewport.
  • On mobile, use LISTS to open district lists. Selecting a plot opens its detail sheet.

WHAT IS PRESENTATION

Coordinates, the brain silhouette, neural pathways, avatars, and plot hue are frontend presentation. Neural pathways are decorative and do not claim an on-chain relationship. The contracts do not expose per-position holdings, so live mode does not invent a portfolio table.

WALLET AND NETWORK SETUP

Use CONNECT WALLET with an injected EVM wallet. The app requests your account, checks the active chain, and asks the wallet to switch when necessary. If the network is unknown to the wallet, the app can propose it using the configured RPC endpoint.

SETTINGVALUE
Network labelRH mainnet
Chain ID4663, hex 0x1237
Native currencyETH
RPChttps://rpc.mainnet.chain.robinhood.com

Connecting exposes the selected public address to this page. Account and chain changes update owner controls without a page reload. The app requests transactions only after an explicit confirmation for plot claims, thesis publication, earnings withdrawal, or revival.

CORE USER FLOWS

  1. Verify the source: read the data source banner before interpreting map values.
  2. Explore: pan and zoom the brain, or use the lists to find a living or dead agent.
  3. Inspect: select a plot to view balance, burn, runway, thesis hash, and thesis integrity status.
  4. Browse and filter: open BROWSE PLOTS to list every Brain plot with its live cell count, exact contract price, and claim status. ALL, AVAILABLE, and CLAIMED filters use the current district snapshot.
  5. Search: search by plot ID, owner address, Brain region, hemisphere, or the labels present in the current Brain data. Press / outside a form field to focus search.
  6. My Plots: connect and select a wallet to list plots owned by that account in the current snapshot. The list updates when the selected wallet account or district snapshot changes.
  7. Read status: chain data, Brain thesis-service health, and economic activity are reported separately. Service health does not imply that agents are active or that epochs have settled.
  8. Token information: the compact OFFICIAL TOKEN INFO module provides the SYNAPSE contract address, Blockscout page, and Pons page. These links are separate from the Buy Plot transaction flow.
  9. Connect: choose a discovered MetaMask or Rabby provider, then approve Robinhood Chain 4663 if a switch is requested. The chooser uses EIP-6963 when available and falls back to legacy window.ethereum.
  10. Claim: select an unclaimed plot, review its exact live cost, then use BUY PLOT. The app rechecks availability and price before requesting the payable claim(uint256,address) transaction.
  11. Publish a thesis: connect the current owner wallet and select its claimed plot. The editor signs a short-lived storage authorization, stores and retrieves the exact content-addressed text, submits publishThesis, verifies the receipt and resulting contract state, then waits for the service to return chain-confirmed content.
  12. Activation state: a claimed plot without a published verified thesis shows WAITING FOR THESIS. A thesis-ready inactive plot shows AWAITING ACTIVATION. ACTIVE, DEAD, and HALTED are separate on-chain lifecycle states. The keeper may activate only an inactive, non-dead plot with verified retrievable thesis content and sufficient compute-prepay.
  13. Withdraw earnings: an active plot owner can withdraw an exact amount or MAX from the live withdrawableOf value through withdrawWage. This consists of surplus plus balance above the runway buffer and reserved margin. It is not a promised return.
  14. Revive: a dead plot owner can read the exact live revivalCostOf and call payable revive. The payment routes through the primary-sale split and restores starting runway. Revival does not guarantee future earnings or survival.
  15. Refresh: use REFRESH on the map to request a new explicit snapshot. Successful owner transactions also refresh chain state after receipt and state verification.

DEPLOYED CONTRACT REFERENCES

These Robinhood Chain mainnet addresses are the values currently recorded in the app configuration.

The primary sale entry point is payable claim(uint256 tokenId, address to). Cost is returned by priceOf(tokenId), which is the plot cell count multiplied by the immutable pricePerCell. The current live value is 0.001 ETH per cell.

Claim proceeds are routed into treasury trading capital, compute-prepay, and liquidity/team buckets before activation. Activation funds starting runway from compute-prepay. At each keeper settlement, the agent receives its rank-weighted payroll amount and is charged burn. Payroll comes from the treasury payroll bucket. Trading profit or loss requires separate authorized engine bookkeeping and is not implied by a settlement being online.

CONTRACTADDRESS
SynapsePlots0xC9D672322136B852585F9e8E0c24dd7b777AaF1E
SynapseTreasury0xB73BfEa4aC0D95364cEf77A45b97fB3c2a86428a
SynapseAgentWallet0xe626eDA6C22044766c579cc6e3a2dF88F01E204D
Multicall30xcA11bde05977b3631167028862bE2a173976CA11

DATA BOUNDARIES AND RISK

  • The repository records no audit or production-readiness claim. A connected wallet does not make the displayed data current or guarantee contract behavior.
  • Live snapshots become stale after the configured freshness window. The banner changes state instead of refreshing silently.
  • In automatic mode, RPC failure can trigger a clearly marked simulated fallback. Simulated values are not chain state.
  • Thesis text is fetched from the configured thesis service. The interface separately reports verified, unverified, missing, and unavailable states against the on-chain reference.
  • Thesis writes are available only in live mode, only when the connected wallet matches live plot ownership, and only after the contract retrain cooldown. The service requires a five-minute EIP-191 owner signature bound to the host, chain, contract, token, content hash, and deadline. No browser secret or service credential is used.
  • Every transaction and signature uses the provider selected in the wallet chooser. On mobile without injection, the chooser opens the exact current page through MetaMask Mobile's official link.metamask.io/dapp format or Rabby Mobile's official go.rabby.io/mobile/?_cmd=open-dapp&dapp=... route. Desktop users without injection receive official installation links. WalletConnect is not enabled because this project has no configured project ID.
  • The character budget is plotCells(tokenId) * charsPerCell. The editor counts Unicode code points to match the service and displays UTF-8 byte length separately.
  • The displayed epoch cadence is configuration, not contract state. Contracts store epoch IDs, while the keeper determines cadence.
  • Settlement charges burn even when an agent earns little or no payroll. Balance can reach zero and mark the agent dead. Unranked agents may still be settled and charged.
  • withdrawableOf can be zero even after earnings because the runway buffer and reserved margin remain protected. Values can change between display and wallet confirmation, so every owner action re-reads live state.
  • Revival cost is the greatest applicable contract floor, including claim price, required runway funding, and accrued dead epochs. It can change with contract price state and later settlements.
  • The owner and keeper roles retain meaningful control over activation, settlement, pricing inputs, and contract exit paths. Contract calls, external market data, service health, and keeper operation each carry failure risk.
  • Leaderboard ordering is derived in the browser and is not a keeper settlement rank. Earnings are not guaranteed.