r/AlgorandOfficial

With the announcement of its Agent Payments Protocol last year, Google signaled that autonomous agents transacting on our behalf is no longer a thought experiment. It’s infrastructure being built right now. It’s estimated that agentic commerce could influence trillions in global commerce by 2030. The question is no longer whether machines will pay each other, but which rails they'll do it on. Algorand has quietly put itself in a strong position to be one of those rails, and the reason it can win isn't just tech, it's the builders.

The technical case is real and has been discussed extensively. Agentic payment traffic under the x402 standard is high-frequency, low-value, and synchronous. An agent requests a resource, gets a payment request, attaches a payment, and expects immediate settlement. That pattern punishes chains with variable fees, probabilistic finality, or congestion-dependent performance. Algorand's instant deterministic finality means an agent never has to wait or write congestion-aware logic. Its fees make fractional-cent micropayments economically viable. Native atomic transaction grouping lets payment, authorization, and usage logic settle together without intermediate states. This matters enormously when an agent is composing a multi-step transaction that must either fully succeed or fully unwind. Add stablecoin support for predictable pricing and a track record of zero downtime, and you have a settlement layer genuinely suited to machine-speed commerce.

But here's the part that matters most, and the part I'd argue Algorand should lean into hardest. Infrastructure alone doesn't win- a builder community does. The chains that own agentic commerce five years from now will be the ones where a developer with an idea on Monday can have a working, paid agent endpoint live by Friday. After Algorand's recent hackathon, with more than 20 x402 endpoints launched in under four hours, it’s clear that the tooling has reached the point where builders can move fast. The Global x402 Challenge, with its $100K and 500K ALGO prize pool opening in mid-July, is a smart escalation of that energy.

The strategic gap to close is what happens after those endpoints get built. A hackathon produces a working prototype; it doesn't produce a sustainable project. If Algorand wants to be the home for agentic commerce rather than just the host of impressive demos, the ecosystem needs to treat the path from prototype to funded, maintained product as a first-class problem. That means visible showcases for agentic projects, funding paths that don't require pre-existing traction, and a culture that keeps builders engaged after the prize money is handed out. The chains that convert one-weekend hackathon energy into standing infrastructure will be the ones that win. Algorand has the settlement layer, the partnerships, and increasingly the builder velocity. The opportunity now is to make sure the builders who show up to prove what's possible have a reason and the resources to stay and build the real thing.

Come check us out at our new page!

• The King Safety Paper is being shared with the Ecosystem Advisory Council this month. This is the next step in a consultative process to refine our approach before the EAC shares it more broadly with the community.

• The Foundation is committing to extending its support for bonus staking rewards for another year (until January 2028) to allow the process to run its course and get to the best possible outcome for everyone.

• Now that the protocol is under Foundation control, we are making significant protocol changes to give us far more flexibility in how transactions are priced, from a bundled fixed 0.001 ALGO price to a decoupled model where pricing can depend more closely on resources being consumed and/or the type of transaction being executed.

• While the Foundation can propose changes to improve sustainability, any decision will need to be implemented through a consensus upgrade, which will require the support of 90+% of staked Algo.

Source: https://x.com/AlgoFoundation/status/2072412886002229694

https://preview.redd.it/mt7q2qnncfah1.png?width=1080&format=png&auto=webp&s=784a5984d5990798f166c44507efbbe07b1300c9

https://preview.redd.it/onigbap4v7ah1.jpg?width=2880&format=pjpg&auto=webp&s=5f757e3ca812b18b491d121455160d00ae562286

Hi everyone, and welcome to this Algorand Community AMA on Reddit!

Starting tomorrow (Tuesday, June 30), four members of the Algorand Foundation's leadership team will be answering your questions throughout the day, relayed here as their responses come in:

• Marc Vanlerberghe / CSMO
• Camilo Molano / Head of Developer Marketing
• Alexa Carr / VP of Marketing
• Will Beaumont / CPO

I'm publishing the thread a little early, so feel free to start posting your questions now.

If your question is intended for a specific team member, please mention who it's for.
I'll post the team's replies directly under your comments as they come in.

Looking forward to your questions! 🔥

A digital-first broadcast that brings the entire industry under one roof to anchor conversations for a global audience of founders, builders, institutions, enterprises, capital allocators and decision-makers—with no travel required.

​Premiering on Wednesday, August 5th, this high-signal, high-production news-style broadcast delivers the same quality conversations you expect on stage at our IRL events, now produced for a digital audience.

TLDR: There is no need to worry it is awful.

Quantum Resistant Ledger is a layer one that was created using only post-quantum cryptography. That sounds good! Quantum security since day one. Unfortunately it's not that simple.

The PQC signature scheme they choose is XMSS, this generates signatures 10k bytes long, Falcon signatures of similar security are 660 bytes long a far better choice for blockchains that are network traffic constrained and blockspace is expensive.

QRL do use some tricks to limit public key sizes as these must be written to the blockchain which limits public keys to 2.1kb However both Falcon implementations will have smaller keys.

>Falcon-512 public key ~897 bytes
Falcon-1024 public key ~1,793 bytes

The consequence of this is that QRL is very slow, it has 60 second blocktimes and approx 15tps. (I did have some trouble getting solid stats on this so if someone has a reputible source please share)

So could they migrate to better schemes? Yes but even if they adopted Falcon. It would make a small difference because they haven't done the other tricks Algorand does with cryptographic sortition so the various committees involved in consensus are limited in size which then limits network traffic while still being randomly selected so they cannot be distributed denial-of-service (DDoS) attacked.

Summary

QRL is a one-trick-pony and that trick is PQC and even then they have made poor choices.

Algorand's sensible migration plan will limit the performance impact and deliver results in a timescale similar to the timescales nations (like France) expect critical infrastructure to migrate to PQC.