Stage 2 — Expansion

For background:

• What is ACR
• What is AMT

In Stage 1, we validated that:

• Worlds can be created, persisted, and loaded again
• Block- and contract-based interactions work within gameplay flows
• We can operate an initial community test within a limited scope

Stage 2 builds on that foundation to validate whether we can actually scale on-chain functionality and user creation.

Timeline (Planned)

• Stage 2 — Expansion (Testnet Beta)
  2026.Q2

Stage 2 runs on the official Testnet. We validate expanded functionality in a production-like environment while still keeping room for experimentation and iteration.

Dates are targets and may change depending on Stage 1 validation results and system stability.

Goals

Key questions in Stage 2:

• Can user-driven on-chain interaction scale in practice?
• Can contract blocks and custom blocks be reused repeatedly?
• Is ACR-based contribution recording systemically stable?
• Does feature expansion avoid exploding operational complexity?

In short:

“Can Akkadia’s core philosophy be expanded into real structures and real usage flows?”

This stage validates whether Akkadia’s core philosophy can be expanded into real structures and usage flows.

Scope

In Scope

• Apply the official Testnet environment
• Release Testnet Beta
• Expand user contract block creation
• Validate contract block deployment and reuse flows
• Apply the ACR token system
• Test quest-based ACR earning logic
• Validate ACR accumulation and recording structures
• Validate operational stability under user growth

Out of Scope

Not required in Stage 2:

• Issuing AMT (Main Token)
• Finalizing Mainnet tokenomics/economy
• Operating large-scale event worlds
• Completing long-term balancing and growth design

Stage 2 focuses on expansion and validation.

Expansion Validation Checklist

Contract & Custom Block Expansion

• Users can create contract blocks
• Created contract blocks can be placed in worlds
• The same contract block can be reused by multiple users
• Contract execution does not break gameplay flow
• World state remains safe on failures/errors

ACR System Validation

ACR is a contribution record token applied for the first time in Stage 2. For the concept and design intent:

See What is ACR.

• ACR is applied correctly on Testnet
• Play/contribution-based ACR accumulation is recorded accurately
• ACR payouts work when quest conditions are met
• ACR data is managed without loss/duplication
• UX helps users recognize ACR as “contribution record,” not “reward”

Gameplay & UX Expansion

• Expanded features do not break existing gameplay flow
• System feedback is clear based on user actions
• Users can still operate and understand the system as complexity increases
• Major UX confusion points are identified and improvement directions are defined

Operational Scalability

• Server stability holds as user count increases
• Performance degradation is controllable as on-chain calls increase
• A response strategy is defined for rising operational complexity
• Testnet operating costs remain within a predictable range

What We Learn in Stage 2

What matters most in Stage 2 is not “results,” but data and decision rationale.

We clarify:

• Which on-chain features are actually used
• Which features are too complex or burdensome
• When/where user creation becomes meaningful
• Which core features must be carried into Stage 3 (Mainnet)

Exit Criteria — Ready for Stage 3

We move to Stage 3 — Launch & Operation when:

• User contract/custom block flows are stable
• ACR can be accumulated and managed continuously
• Expanded features are within an operable scope
• Key structures to validate on Mainnet are clear (What is AMT)
• Stage 3 operational scope and risks are defined

Notes

Stage 2 does not aim for unlimited expansion. Every feature is evaluated by whether it can be operated in Stage 3. The outputs of Stage 2 become core inputs for AMT design and the Mainnet transition strategy.

Stage 2 is the turning point where Akkadia moves from a “working world” to an expandable on-chain world.