Networks and addresses
Brila DAT launched on HyperEVM mainnet (chain 999) on 2026-06-19. The protocol contract addresses below are the live deployment recorded across
deployments/999.json, package configuration, and contract role reads verified on 2026-07-23. TheDATtoken address is the one to add to wallets, explorers, and DEX listings.
Networks
HyperEVM mainnet
999
https://rpc.hyperliquid.xyz/evm
https://hyperevmscan.io
HyperEVM testnet
998
https://rpc.hyperliquid-testnet.xyz/evm
https://testnet.purrsec.com
Standing infrastructure (HyperEVM mainnet)
Chain-level addresses shared by every HyperEVM deployment — the same for Brila DAT.
WHYPE (reserve token)
0x5555555555555555555555555555555555555555
Project X — Uniswap V2 factory
0xb0D032B6cC82e37488497781338f359cE8CC40e0
Multicall3
0xcA11bde05977b3631167028862bE2a173976CA11
Protocol contracts (HyperEVM mainnet, chain 999)
The
DATtoken (the ERC-1967 proxy) is the canonical contract address. The implementation lives behind the proxy and is replaced on upgrades; the proxy address never changes.
DAT token CA (mainnet): 0x9C45701620d8cE4eBd5213FAa2B4BF725fe2BD9c
DAT token (ERC-1967 proxy)
0x9C45701620d8cE4eBd5213FAa2B4BF725fe2BD9c
DAT implementation
0x0f5175FC7dc72cB8D72b80a506dAD4C714c01d29
BrilaDATRebaser
0xF2E417252FFc6d9355BC2d90EFcdD53c057844Ee
BrilaDATIncentivizer (LP staking farm)
0x3e9E18f5944B2d95571d68b9e74627aa9dAb2cc0
BrilaDATZap
0xD3661eAb84fF93d3e2D9cFdDc6Bd74f231488AE6
DAT/WHYPE Uniswap V2 pair
0x3E0B18bD621304Df40485428eCd20765cF692432
The
BrilaDATIncentivizeris live: it stakes the DAT/WHYPE LP token and emits DAT rewards on a fixed schedule (the launch emission period runs through 2026-09-18).
Verify on the explorer: DAT token · BrilaDATRebaser · BrilaDATIncentivizer · BrilaDATZap · DAT/WHYPE pair
Ownership & treasuries
Owner (token, rebaser, incentivizer)
0x2f8771644015447D9b2946f580f76f9fd5C2C75D
The deployer EOA at the time of writing. The token and rebaser use two-step ownership (Ownable2Step); the incentivizer uses single-step Ownable. Transfer to a governance multisig is the intended launch hand-off — see Governance & security.
Rebase treasury (rebase-skim recipient)
0xF6D4E0365c910b7225502ABD485C88e52B9dcB49
A 2-of-3 Safe; receives the WHYPE proceeds and any DAT minted by positive-rebase mint-and-sell.
Launch treasury / LP custody
0x367a0316302D609A5C2408386f1E7675fF79cFE2
Holds the 5% launch DAT allocation and custody of the seeded LP; distinct from the rebase treasury.
Launch helper
BrilaDATPairSeeder
0x32373ff1b1994d7A4a79cd3Bfed61f15e0Bafe15
This helper created and seeded the pair. It is not required for ongoing protocol operation.
Contract without a recorded deployment
BrilaDATDistributionPool
Source only; no mainnet address recorded
LPTokenWrapper and UniswapV2OracleLibrary are inherited/embedded code and do not have standalone deployment addresses.
USD-mode oracle feeds (HyperEVM mainnet)
USD mode requires two independent reserve→USD (WHYPE/USD) feeds. The launch ships two HyperCoreOracleAdapters, each wrapping a native HyperCore price precompile. The precompiles, indices, and scale exponents are protocol constants (they match script/brila-launch-params.sh).
Primary reserveUsdOracle
HyperCoreOracleAdapter
Perp oracle 0x0000000000000000000000000000000000000807 (HYPE perp index 159, scale exp 4)
0x97Cbf8AB394c7BaB4E26883E9Fc1791b8D9Ab999
Secondary secondaryReserveUsdOracle
HyperCoreOracleAdapter
Spot 0x0000000000000000000000000000000000000808 (HYPE/USDC pair @107, scale exp 2)
0x366338122acE94a3835511b81387A2C807172e95
The rebaser is in USD-peg mode (
usdPegMode = true,targetRate = 1e18= $1.00 per DAT).
Testnet (998)
No Brila DAT testnet deployment is recorded here, so contract addresses and peg mode are not specified.
Last updated
Was this helpful?