Hybrid On-Chain and Off-Chain Architecture
To deliver a seamless, scalable, and secure Web3 gaming experience, Quip Rabbit implements a hybrid on-chain and off-chain architecture that combines the speed and flexibility of traditional cloud services with the trust and transparency of blockchain.
The system is designed to:
Ensure the security and transparency of token-based transactions
Reduce gas fees and unnecessary on-chain activity
Provide real-time responses to game interactions (e.g., payments, validation)
Scale efficiently to serve millions of mobile and PC players globally
Unity Game Client (Front-End)
Players access Quip Rabbit through mobile devices or PCs built with Unity. When players initiate blockchain-related actions (e.g., participating in Play-to-Earn (P2E) tournaments, staking, etc.), the system first detects whether a wallet is connected.
MagicBlock + Phantom Wallet (Wallet Integration)
The game uses MagicBlock to detect connected wallets and automatically redirect users to the Phantom Wallet. Players are required to sign and securely connect their wallets, which enables game functions such as Play-to-Earn (P2E) rewarding, staking, map governance voting, purchasing game items in the in-game shop, and more. This connection is non-custodial and completely secure.
Off-Chain Services for Speed and Control
To maximize performance and responsiveness, Quip Rabbit handles core logic off-chain using enterprise-grade infrastructure:
Raydium API: Fetches real-time QUIP/USDC pair prices to determine fair token prices for in-game actions, including staking on prep day, voting for map governance, and purchasing in-game items using QUIP tokens (in the shop).
Microsoft Azure PlayFab + Microsoft Azure Cosmos DB: Validates player data, initiates CloudScript events, and sends various critical Calls to Action (CTAs) such as Play-to-Earn (P2E) tournament entries via USDC payments, QUIP token staking, map governance payments via USDC, such as voting, map creation, proposal creation, sending QUIP token rewards to players, purchasing in-game items using QUIP tokens (in the shop), and paying via USDC to top up your play quota with friends (in party and rooms), to Cloudflare.
Cloudflare Workers: Serves as a finalizer with a secure validation layer. It retrieves the txhash or TxID data from Helius and confirms the authenticity of the transaction before authorizing any action or reward.
In-game Calls to Action (CTAs) that directly involve MagicBlock and the Phantom wallet include:
Participate in Play-to-Earn (P2E) tournaments by paying $0.75 USDC.
Staking QUIP tokens: You send QUIP tokens to the developer's wallet address, which are locked for 13 days, for a total of 1 month (26 days across two rounds).
Participate in map governance (such as map voting ($0.1 USDC), proposal voting ($0.1 USDC), map creation ($2 USDC), and proposal creation ($5 USDC)) by paying in USDC. Map creators will also receive rewards in QUIP tokens.
Purchase game items in the in-game shop with QUIP tokens, whose prices change every 3 minutes based on the QUIP/USDC market price, sourced from the Raydium API.
Increase your game quota to play with friends (in party and rooms) by paying $0.18 USDC.
Helius + Solana Blockchain (On-Chain Finalization)
The final transaction data retrieval execution occurs on-chain, specifically on the Solana network:
Helius is used to retrieve information from the associated transaction result (such as the TxHash or TxID), providing real-time data retrieval speeds with ~1 second latency.
The Solana blockchain returns information from the associated transaction result (such as the TxHash or TxID) and waits for the transaction to be validated by Cloudflare.
Cloudflare uses this verified blockchain data to determine whether an action is approved, the transaction result is successful, confirmation and validation will be carried out whether the response transaction information results are correct and appropriate such as transaction results, time, recipient wallet address, sender wallet address, and the number of tokens all information obtained from Solana Blockchain (On-Chain) is forwarded to Helius, if correct and appropriate then it will be forwarded again to Cloudflare to be followed up whether everything is valid such as: providing Play-to-Earn (P2E) rewards to players, distributing QUIP token staking to players, receiving USDC payment fees from player transactions in Play-to-Earn (P2E), map governance, map governance by sending QUIP token rewards to players, confirming purchases of items in the game store paid for via QUIP tokens by players, adding playing quotas with friends via USDC payments from players.
Validated On-Chain Actions:
The following table summarizes all in-game interactions that require on-chain validation on the Solana blockchain. These actions are critical to maintaining transparency, trust, and security in all tokenized transactions and reward systems within the Quip Rabbit ecosystem.
1
Validate USDC payments for tournament entry
Validate QUIP token staking transactions
Validate USDC payments for map creation
Validate QUIP token payments for in-game items
Validate USDC payments to increase match quota in party or room play
2
Grant P2E rewards to winners
Distribute staking returns to players
Validate map voting submissions
Confirm successful purchases
-
3
-
-
Validate proposal voting submissions
-
-
Each action is executed off-chain for speed, then finalized and verified on-chain via Solana with transaction retrieval through Helius and validation through Cloudflare Workers.
Below is a flowchart of Hybrid On-Chain and Off-Chain Architecture, zoom in or click on the image for a larger and clearer view:
Last updated