Engineering · Tokenomics

AERE pays developers, Fee Monetization live

By AERE Network May 31, 2026 5 min read

On May 31, 2026 AERE Network deployed AereFeeMonetization, a contract that pays developers AERE for every transaction that touches their registered contracts. The dev-share right is an ERC-721 NFT: transferable, fractionalisable, collateralisable. Plus a fixed 5% of every gas fee on AERE flows to the AERE Foundation treasury, separately. On AERE, developers actually get paid for the work their code does.

What this means: a popular dApp on AERE, say a games library, a DeFi protocol, or an NFT marketplace alternative, earns continuous AERE revenue from gas fees. A popular contract can earn meaningful, continuous AERE revenue from the gas its users generate. No grant application, no token launch, no surcharge on users. You build, users use it, AERE flows to your wallet.

The contract

Contract	Address	What it does
AereFeeMonetizationV2	0xb560bdFB8b8B918012e6481e3bcF473c79c2a850	ERC-721 NFT registry + per-NFT pending balance + Foundation treasury slice. Developers call `register(contractAddr, payoutAddr)` and receive NFT tokenId. The off-chain distributor (Foundation-operated) parses block traces, attributes gas to top-level called contracts, looks up registered tokenIds, and calls `distribute(tokenIds, amounts, treasuryAmount)` per cycle. NFT owners call `claim(tokenId)` to withdraw their accumulated AERE.

The fee distribution per gas fee

After all session tiers ship, the gas-fee economic flow on AERE is:

Slice	Rate	Recipient	Source
Burn	37.5%	AereFeeBurnVault (permanent destruction)	Tier 1.8
Developer share	20%	Registered NFT owner (or validator if unregistered)	Tier 1.10 (this)
Foundation treasury	5%	AERE Foundation (always)	Tier 1.10 (this)
Validator	37.5%	Block validator coinbase	Tier 1.0 baseline

(All four rates are Foundation-tunable within hard caps: burn ≤ 50%, dev-share ≤ 30%, treasury ≤ 15%. Validator slice is the residual.)

How a developer registers

// One transaction. ~80k gas. Permissionless.
AereFeeMonetizationV2 fm = AereFeeMonetizationV2(0xb560bdFB8b8B918012e6481e3bcF473c79c2a850);
uint256 myTokenId = fm.register(MY_CONTRACT_ADDR, MY_WALLET);

// Done. Now you earn 20% of all gas fees users pay to MY_CONTRACT_ADDR.
// Check your balance any time:
uint256 pending = fm.pendingRewards(myTokenId);

// Withdraw when you want:
fm.claim(myTokenId);  // sends AERE to whoever currently owns the NFT

Foundation pre-registered 37 contracts on deploy

Every Foundation-deployed contract from this session, AereSwapRouter, AereYieldFarm, AereSettlement, AereMessenger, AereNFTMarketplace, all 5 paymasters, AerePyth, AereRandomnessBeacon, AereCoinbaseSplitter, and 27 more, is pre-registered with AERE Foundation as the NFT owner. Their fee-share flows back to Foundation automatically.

External developers register their own contracts permissionlessly. There is no allowlist for the register() function; anyone can call it for any contract they want to earn from. (Yes, anyone could try to front-run a developer by registering their contract first. Honest answer: this is a known minor griefing surface. Phase 2 adds contract-owner verification via EIP-7201 storage or AdminRoles ABI introspection. For Phase 1, devs should register immediately on deploy, same tx, same block, to lock the NFT.)

Why this matters strategically

For users: nothing changes. Same gas costs, same UX.

For developers: AERE becomes one of very few chains where building is financially rewarded. The economics work for indie devs: a contract doing 10k transactions/day at AERE gas levels, when gas pricing becomes meaningful, generates a steady AERE income stream. The NFT can be sold for a lump-sum if the developer wants to exit; or held for the recurring revenue.

For AERE token economics: every Tier-1 feature shipped this session generates gas → 37.5% gets burned forever (price-supportive), 5% flows to Foundation treasury (operational sustainability), 20% creates a flywheel attracting more developers (more dApps → more gas → more burn). Three economic loops, all activated by ordinary transactions.

For AERE Foundation specifically

The 5% treasury slice + dev-share on the 37 pre-registered Foundation contracts means Foundation receives meaningful gas-fee revenue automatically as the chain grows. Combined with the existing Foundation revenue streams (validator coinbase, paymaster spreads, NFT marketplace fees, mining subscriptions, locked-staking penalties), AERE Foundation operates on a sustainable on-chain revenue model, without requiring grants, donations, or token sales.

What's still pending

Deploy aere-fm-distributor Docker container on aere-infra (next to coinbase-forwarder). Parses block traces, attributes gas per top-level called contract, batches calls to distribute(...).
developer-revenue.html page documenting the pattern for builders.
Phase 2: contract-ownership verification. Today, anyone can register any contract. Phase 2 introduces optional dispute window where the contract owner can challenge wrongly-registered NFTs.

What's next

Tier 1.11 tunes sub-second block times. Tier 1.12 adds Symbiotic-secured bridge economics. Beyond that the work moves to consumer-app launches, MiCA EMT partnership, and the dApp ecosystem the Tier-1 stack is designed to support.

The economic engine is complete: burn flow + dev share + treasury slice + MEV-resistant DEX + intent bridging + Pyth oracle + drand randomness + 5-paymaster gasless stack, all live, all on chain, all permissionless.

← Back to all posts