Architecture & Security

Roblade pairs a blockchain with a real-time game server, and each does the job it is best at. Ownership and settlement live on Robinhood Chain, where they are public and verifiable; moment-to-moment gameplay runs on a fast, authoritative game server, where it stays responsive. This page explains how the two layers fit together and how player accounts and sensitive actions are protected.

Design objective

Use the chain where ownership matters. Keep the game fast where experience matters.

Roblade does not attempt to put every animation, movement, or harvest on-chain. The split works like this:

• The chain handles: Land ownership, asset transfers, payment and settlement, public transaction history, and — over time — additional contract-controlled economic systems where public verification creates real value.
• The game server handles: movement and pathfinding, farming and ranching state, worker and build timers, inventory and XP, gold and materials, and anti-abuse checks.

This hybrid design gives players digital ownership without forcing a wallet prompt and a gas fee for every ordinary game action. Signing in, walking, planting, and harvesting never require a transaction. Blockchain interactions are reserved for the moments where they matter — buying Land, transferring it, and authorizing sensitive account actions.

The two layers stay synchronized: the game reads Land ownership from the chain, so when an NFT transfers, in-game control of the plot follows the new owner.

Built on Robinhood Chain

Roblade runs on Robinhood Chain, a permissionless Layer 2 built with Arbitrum technology. Robinhood announced the network’s public mainnet in July 2026.

• chainId: 4663
• Currency: native ETH
• Explorer: explorer.mainnet.chain.robinhood.com  (Blockscout)

The chain provides the settlement environment for Land purchases and a foundation for future public economic systems described in the Vision section. Roblade is an independent ecosystem project building on Robinhood Chain; references to the network do not imply that Roblade features are developed, operated, or guaranteed by Robinhood. For current network information, use Robinhood’s official Robinhood Chain page .

The game server

Everything that is not on-chain runs on an authoritative Rust game server backed by Postgres. “Authoritative” means the server — not the client — is the source of truth for the world:

• It maintains the real-time multiplayer world state that every connected player shares: positions, crops, animals, buildings, and timers.
• It validates every action server-side. The client is a view; if you attempt something your character cannot do — harvest a crop that isn’t ready, spend gold you don’t have, build past a limit — the server rejects it, regardless of what the client claims.
• Gold, materials, and other game resources are managed here, in the server’s database, not in a token contract. There is no ERC-20 token deployed today (see Tokenomics).

Server-side validation is also the first line of anti-abuse defense: modified clients and replayed requests fail the same checks as any other invalid action.

Wallet experience

Your wallet is your identity in Roblade. There is no password.

• Sign-in is SIWE (Sign-In With Ethereum): you sign a human-readable authentication message with your wallet, and the server issues a session JWT for the rest of your play session. Signing this message proves who you are — it never transfers funds or assets.
• Guest Mode exists for players who want to explore the world before connecting a wallet.
• During play, ordinary actions use your session — no wallet prompts while you farm, build, and play.

Two habits keep every wallet safe, in Roblade or anywhere else:

• Read what you sign. Roblade’s prompts state what action is being performed; a sign-in message and a Land purchase transaction look nothing alike.
• Never share your private key or recovery phrase — not with Roblade staff, not with community members, not with anyone. Roblade is non-custodial and cannot recover a lost key, so securing your wallet is in your hands.

The same address can be used across different compatible wallet applications, and wallet behavior can differ between desktop, mobile, and in-wallet browsers; known issues are communicated through official channels. For first-time setup, see How to Play.

EIP-712 protected actions

A session token is convenient, but convenience should never be able to destroy value. Roblade therefore requires a second, stronger factor for sensitive game actions:

• renaming,
• shop purchases,
• demolishing buildings.

These require an EIP-712 typed-data signature from your wallet, combined with a single-use nonce issued by the server. EIP-712 signatures are structured and human-readable — your wallet shows exactly which action you are approving — and because each nonce works exactly once, a captured signature cannot be replayed.

The security consequence is simple: even if someone stole your session token, they could play as you but could not rename, purchase, or demolish anything. Destructive and high-value actions always come back to the wallet only you control. High-frequency, low-stakes actions stay on the fast session path, so the game remains smooth.

Security & transparency practices

Security is an ongoing process, not a one-time claim. Roblade’s working principles:

• Verified, public contracts. The Land contract source is verified on the Blockscout explorer , and its address is published in The Land Contract. Anyone can read the code and audit every mint and transfer.
• Minimal, documented privileges. Owner powers on the contract are limited to upgrades and configuration (price, pause, metadata URI, treasury), and the pause switch gates minting only — never transfers.
• Event logging. Purchases and transfers emit standard events, so the asset’s full history is publicly reconstructable.
• Scoped, readable signatures. Authentication and EIP-712 prompts describe the action being approved rather than asking for blind approval.
• Server-side enforcement. Game-state protection does not rely on trusting the client.
• Incident communication. If a meaningful issue affects players, the project’s job is to say what is known, which systems are affected, what precautions apply, and when it is resolved.

No blockchain, contract, wallet, or application can honestly be called risk-free. Verify official links through Official Links, confirm contract addresses on the explorer, and protect your keys.