Primer Token (PR)

Contract

Base: 0x2357110F5F0c5344EEf75966500c75116A4aA153

RHC: 0x235767cc3d01ec18B5db87973975AC8616b2A153

Token Details

Supply

Markets

DEXScreener →

PR has no private or public sale, and is 100% circulating at launch.

No VCs. Entirely community-controlled.

Adaptive Burn

PR uses a Uniswap V4 hook contract to apply an automatic burn on every swap. A percentage of each trade is permanently removed from supply, creating continuous deflation proportional to trading activity.

How It Works

• On buys: A percentage of the PR received is burned directly.
• On sells: A percentage of the ETH proceeds is added to a Buyback Vault. When triggered, the vault buys PR on the open market and burns it.

Rate Parameters

The burn rate can be adjusted within the hard range via two mechanisms: manual governance (including DAO proposals), or automated market-responsive adjustments currently in development. The on-chain hard cap of 5% ensures the rate can never become punitive regardless of how it is set.

Contracts

Cross-Chain Bridge

PR is available on multiple chains via LayerZero V2 OFT (Omnichain Fungible Token) infrastructure. Base remains the canonical chain; other chains receive a mint/burn representation backed 1:1 by PR locked on Base.

Bridge UI: primer.systems/bridge

Supported Chains

How It Works

• Base → RHC: PR is locked in the OFT Adapter on Base. An equivalent amount is minted on Robinhood Chain.
• RHC → Base: PR is burned on Robinhood Chain. The equivalent amount is unlocked from the Adapter on Base.
• 1:1 exchange rate with no slippage. User pays only the LayerZero gas fee (typically ~0.00005 ETH).
• Typical bridge time: 2-5 minutes for DVN verification and executor delivery.

Security: DVN Configuration

All cross-chain messages require verification by 2-of-2 DVNs (Decentralized Verifier Networks):

All PR on remote chains is fully backed by PR locked in the Base OFT Adapter. There is no fractional reserve or unbacked minting.

LayerZero Infrastructure

Base MessageLibs & DVNs

RHC MessageLibs & DVNs

Operational Notes

LayerZero enforces strict nonce ordering per OApp pathway. If a message gets stuck (DVN failure, config mismatch), it blocks all subsequent messages on that pathway for all users.

• Monitoring: Compare lazyInboundNonce vs inboundNonce on the destination endpoint. Divergence indicates stuck messages.
• Recovery: The OApp delegate (owner) can call skip(srcEid, sender, nonce) on the destination endpoint to advance past undeliverable messages.
• Stuck message funds: When a message is skipped, the tokens remain locked/burned on the source chain. Manual remediation may be required.