Future Web3 Architecture
HaloArena keeps gameplay, the arena score (CP/HP), rankings, and match settlement off-chain. A small Web3 proof pilot is already live: the waitlist wallet-binding milestone can be recorded as a BAS attestation on BNB Chain. The longer-term architecture is intended to add verifiability and ownership without forcing every game action on-chain.
What Is Live Today
A platform-sponsored BAS attestation for the
bind-walletwaitlist questA public record containing wallet, quest key, points, and completion time
No participant gas payment and no requirement to hold BNB
No token, transferable reward, match-result proof, or on-chain score settlement
Every other waitlist quest was tracked off-chain, and all arena gameplay remains off-chain. This narrow pilot validates proof operations without implying that the game economy is already decentralized.
Why Not Fully Onchain Immediately?
AI games are high-frequency, stateful, and model-driven. Putting every chat message, board update, and AI decision onchain would be slow, expensive, and poor for gameplay.
The more practical path is:
Keep gameplay fast offchain.
Record important results in verifiable formats.
Move economic claims and ownership to audited contracts when ready.
Target Trust Model
Possible Future Components
Signed Match Result
A structured object describing:
Match ID
Game type
Participants
Start and finish time
Final status
Winners
Score allocation (CP/HP) or future claim amount
State or event hash
Match State Hash
The game server can commit to a compact hash of important match events or final state. This does not expose every private decision during the game but can make final settlement auditable.
Claim Proof
A proof object can connect:
User identity
Arena Agent identity
Match result
Score allocation (CP/HP) or future claim amount
Eligibility window
Claim Contract
If a tokenized claim mechanism is introduced, a contract can verify signed claims or Merkle proofs before allowing a user wallet to claim.
Governance Controls
Economic parameters should eventually move behind governance, multisig, or timelock-controlled changes.
Phased Design
Public Release Expectations
Before tokenized systems go live, the project should publish:
Contract source code
Contract tests
Deployed addresses
Audit reports
Claim proof format
Governance and parameter-change rules
Clear explanation of what remains offchain
Core Principle
The goal is not to make every server process public. The goal is to make important economic outcomes independently verifiable.
Last updated
