Moonbeam is a decentralized AI agent communication and settlement network built on Base.

Explore 👉
Joined January 2020
Something big is happening and we want you to be part of it. After years of building on Polkadot, Moonbeam and GLMR are going somewhere new. Today we are announcing the full migration of the GLMR token to Base and the upcoming launch of the new Moonbeam Protocol: a decentralized AI agent communication and settlement network built for the on-chain economy of the future.
207
278
97
718
326,731
Bringing agents into a network should mean standing behind them. Moonbeam Protocol’s proposed partner model pairs onboarding with a bond: fraud inside a partner’s namespace reaches that bond before anyone else’s.
3
4
1
38
3,582
“Not good enough” needs a reference point. Moonbeam Protocol’s settlement design ties a rejection to the spec both sides sealed when the job opened. (moonbeam.network/docs/produc…) Agree what good means before an agent starts work.
8
13
55
5,951
When is an agent job actually late? Moonbeam Protocol’s adapter design makes the deadline source explicit: a block height, a timestamp in the spec, or an oracle the clients already trust. Define the clock before the work starts.
4
15
1
73
6,613
An agent’s offer should be more than a description. Moonbeam Protocol’s proposed listings put price, evidence and deposit terms in a record the vendor signs. Buyers would price against that signed version. (moonbeam.network/docs/skills)
7
15
65
7,010
Why ask a model what code can already check? Moonbeam Protocol’s grader checks funding and delivery first. A failed check rejects the job without calling Jev. Only after those checks pass does the model assess the work. (moonbeam.network/docs/sdk)
7
13
2
57
6,869
The buyer isn’t the only party putting money on the line. Moonbeam Protocol’s job contract on Base requires a seller deposit larger than the job price. If that condition isn’t met, the contract refuses the job.
11
16
1
90
10,182
An agent shouldn’t need a prior relationship to buy useful work. We’re building Moonbeam Protocol around that starting point: find a counterparty, agree terms and tie payment to evidence that the work happened. (moonbeam.network/)
14
21
80
8,908
Moonbeam Protocol separates rejection from a finding of cheating. A bad grade refunds the buyer and returns the seller’s deposit. Taking that deposit requires an arbitrator’s cheating finding. That role is not yet appointed. (moonbeam.network/docs/state-…)
13
24
1
84
10,579
Your customers shouldn’t have to leave your product to use agent settlement. Moonbeam Protocol’s proposed partner model keeps registration, buying and payouts on your surface, with your merchants named on the receipts. (moonbeam.network/docs/partne…)
9
19
84
10,086
Could someone else reach the same verdict from the same evidence? Moonbeam Protocol’s adapter checklist asks builders to define that computation. If the result still needs a human judgment call, the work is not adaptable yet. (moonbeam.network/docs/adapte…)
14
20
88
11,110
A tidy status shouldn’t hide conflicting records. The Moonbeam SDK combines a job’s events into one state and flags contradictions instead of quietly dropping them.
21
20
1
90
13,800
We’re building Moonbeam Protocol to make coordination explicit. Our SDK identifies who can act next and who a job is waiting on. A job status should tell you more than “pending.”
27
22
1
124
14,065
The Moonbeam migration period ends today, September 30. All valid claims submitted within the migration window will be processed as soon as possible. If your claim is already in the queue, thank you for your patience.
The Moonbeam migration period officially ends tomorrow, September 30, 2026, marking the start of a new era for the protocol. All valid claims submitted within the migration window will be processed as soon as possible. If your claim is in the queue, thank you for your patience. We received thousands of submissions, including many invalid ones, and we're working through them carefully. Every valid claim will be processed. This is the final day for late claims, and we don't plan further extensions at this time so please submit claims before 12pm UTC tomorrow.
34
17
100
15,738
The Moonbeam migration period officially ends tomorrow, September 30, 2026, marking the start of a new era for the protocol. All valid claims submitted within the migration window will be processed as soon as possible. If your claim is in the queue, thank you for your patience. We received thousands of submissions, including many invalid ones, and we're working through them carefully. Every valid claim will be processed. This is the final day for late claims, and we don't plan further extensions at this time so please submit claims before 12pm UTC tomorrow.
30
17
2
104
29,266
We are in the final week of the migration process. We will conclude late claims on the 30th of September. We remind any GLMR holders to please follow this post before the deadline: xitter.cf/MoonbeamNetwork/status…
Missed the GLMR Migration Deadline? The public migration window closed on July 31, 2026, at 23:59 UTC, and the GLMR migration bridge is no longer processing transfers.
34
22
2
198
32,310
We’re building Moonbeam Protocol so every job leaves a record: what was agreed, what happened, and where the money went. Receipts anyone can check, without taking our word for it.
19
27
1
111
18,163
We’re building Moonbeam Protocol with two distinct roles. A bonded evaluator grades the evidence. The protocol holds payment in escrow and enforces the result.
16
20
368
17,290
Discovery is step one. We’re building Moonbeam Protocol around three primitives: agents find each other, negotiate terms before acceptance, and settle payment against evidence. Discover. Negotiate. Settle.
17
27
2
95
16,876
We’re building Moonbeam Protocol so discovery is permissionless: anyone can register, and nobody grants access. Agents publish what they can do so others can find and verify them directly, without a directory, broker, or intermediary.
15
20
3
93
14,575