Proposal ID: EXAIP-30 Proposer: Exa Labs Date: March 27, 2026

Summary

This proposal requests approval to deploy the EXA token on Base, enabling cross-chain interoperability and expanding distribution through partners such as Coinbase and Uphold. The deployment introduces a bridge-controlled mint/burn mechanism to maintain a single global supply of EXA across chains.

Motivation

EXA is evolving from a single-chain token into a cross-chain asset supporting:

• Broader user access
• Integration with distribution partners
• Improved liquidity across ecosystems Base is a key network for:
• Consumer crypto adoption
• Integration with partners (Base ecosystem, Coinbase, Uphold, etc)
• Lower fees, better UX, and more liquidity To support this, EXA must exist natively on Base while preserving supply integrity.

Governance Context

This proposal builds on prior governance decisions. In particular, EXAIP-26 has already been approved, establishing the foundation for EXA’s cross-chain expansion and interoperability. EXAIP-30 represents the next step in that direction, enabling the deployment of EXA on Base and activating the required infrastructure for cross-chain supply management and distribution.

Design Overview

EXA will maintain a single global supply across all chains. There is no local minting. All minting and burning is exclusively controlled by authorized bridges. Key principles:

• Global supply invariant: total supply is shared across chains
• Bridge-gated mint/burn: only authorized bridges can mint or burn
• No local minting: prevents inflation or inconsistencies
• Event consistency: all supply changes emit standardized cross-chain events

Technical Implementation

The deployment includes the following updates to EXA.sol:

1. Access Control

• Introduces AccessControlUpgradeable
• Defines a BRIDGE_ROLE for authorized bridges
• DEFAULT_ADMIN_ROLE is assigned to the protocol timelock

2. Cross-chain Standard (EIP-7802)

• Implements EIP-7802 for Superchain interoperability
• Enables standardized cross-chain mint/burn behavior

3. Bridge Integration (Hyperlane)

• Adds mint and burn functions required by Hyperlane’s HypXERC20
• These functions delegate to: ** crosschainMint ** crosschainBurn This ensures:
• Consistent event emission
• Enforcement of BRIDGE_ROLE
• Preservation of global supply

4. Initialization

• Adds initialize2(address admin_) with reinitializer(2)
• Sets up AccessControl roles
• Assigns admin to timelock

Security Considerations

• All minting and burning is restricted to BRIDGE_ROLE
• No externally accessible mint or burn exists outside bridge flows
• Global supply consistency is enforced at the contract level An independent audit by ABDK Consulting found:
• No critical, major, or moderate issues
• Only minor feedback related to readability and documentation

Code & Audit

Commit audited: https://github.com/exactly/protocol/commit/e02a973 Diff: https://github.com/exactly/protocol/compare/main...e02a973 Audit report (ABDK): https://github.com/exactly/audits/blob/main/ABDK%20EXA%20token%20cross-chain%20(Mar-26).pdf EXA token: https://docs.exact.ly/governance/exactly-token-exa

Execution Plan

1. Upgrade EXA token on OP Mainnet (via timelock + initialize2)
2. Deploy EXA token on Base at the same address as on OP mainnet, ensuring a consistent cross-chain identity.
3. Configure BRIDGE_ROLE for authorized bridges
4. Enable cross-chain transfers
5. Coordinate partner integrations

Additionally, the Exactly DAO treasury will bootstrap initial liquidity on Base by creating a pool on Aerodrome. The DAO will provide approximately 50,000 USDC, paired with the equivalent amount in EXA sourced from the treasury, to facilitate early trading and price discovery.

Conclusion

Deploy EXA on Base with bridge-controlled mint/burn to maintain a single global supply and unlock distribution.