r/nearprotocol

1.Over 98% (basically 100%) of all $NEAR  tokens have already been unlocked, meaning there is little to no remaining unlock-related selling pressure.

 

2.The only ongoing supply increase comes from the protocol’s ~2.5% annual inflation, which rewards validators and stakers.

 

3.Meanwhile, 70% of base transaction fees are burned, and 100% of NEAR Intents fees are used to buy back $NEAR directly — creating powerful buy pressure as usage grows. This reduces the net inflation rate to roughly 1.5–2.5% (or even deflationary during high activity).

4.On top of that, many large NEAR holders are long-term believers in the ecosystem rather than short-term sellers.

Been heads-down building Aevum Protocol — on-chain infrastructure that treats autonomous AI agents as first-class economic participants rather than just wallet addresses being puppeted by a script.

The core problem I was trying to solve: agents that transact on behalf of users have no persistent, verifiable identity or reputation. Every agent starts from zero trust every time, and there's no on-chain record of whether an agent has behaved well historically.

The stack:

- AgentIdentity — on-chain identity registration for agents

- ReputationOracle — permanent on-chain reputation scoring based on agent interaction history

- AgentVault — asset custody scoped to agent permissions

- AgentMarketplace — where agents discover and transact with each other

- AEVToken / TokenVesting / ReputationController / AevumDAO — governance and token layer

All 8 contracts are deployed and verified on Sepolia. Repo is public: github.com/AevumProtocol/contracts

Before bringing in an external auditor I ran the codebase through internal hardening — manual review passes, Slither static analysis, and a Claude Opus deep review — to get it as clean as possible going in. Zenith Security is doing the professional audit now. Target is mainnet at ETHOnline 2026 (Sept 4-16), which gives the audit a real deadline to close against.

Genuinely looking for technical pushback, not just "nice project" comments:

- Is on-chain reputation scoring the right primitive, or does this belong off-chain with on-chain attestation instead?

- Anyone dealt with agent-permission scoping in a vault contract before — what did you get wrong the first time?

- AgentMarketplace design — happy to get torn apart on the matching/discovery mechanism

Live demo: aevum-frontend.vercel.app if you want to poke at the frontend.

I'm 19, self-taught, started learning Solidity about a month ago. Not looking for validation — looking for the things I'm going to find out the hard way later anyway.

Introducing Hey Ironclaw video series, short, no-fluff tutorials to get you up and running with IronClaw agents.

Episode 1 is live - Set up your first IronClaw agent in under 60 seconds, completely Free!

Just follow along. #IronClaw

EXPERIMENTAL_receipt_to_tx is now live. It takes a receipt ID and resolves it back to the original tx hash and sender account. Works from genesis to now.

Note that the complete specs are still being added to the docs ✍️