By making high quality magic states much cheaper to produce, quantum computers don’t need to be nearly as huge just to support these special operations. This is a concrete step toward building smaller, more practical, error-corrected quantum computers that can actually run useful programs instead of mostly just manufacturing their own fuel.

123Carbon is still cooking! 🔥

Google is among the buyers backing 63 Tesla Semis in Texas starting in 2027, expected to avoid ~92,000 tonnes of CO2e over four years.

GMA selected 123Carbon to issue and track environmental certificates on Algorand, making claims traceable and helping prevent double counting

https://www.123carbon.com/123carbon-selected-as-registry-by-center-for-green-market-activation-for-zero-emission-trucking-pilot/

Lute 2.0 is live 🎉

Lute 2.0 is now rolling out for the web app and the browser extension. At a glance:

• UI: a full redesign with Dark, Light and Gold themes, a sidebar on wide screens, a better mobile layout and reorganized Settings.
• Security: every key stored in your browser (HD seeds, Algo25 and Falcon accounts) now lives in one keystore, protected by a single wallet password. You can export mnemonics from the account menu. Your keys still never leave your device.
• Swap: swap assets right from your wallet, with Haystack Router by TxnLab finding the best price across Algorand DEXes.

Swapping in Lute

Open an account and go to the new Swap tab, or start a swap from any asset in your list. Pick what you're swap from and to, and Lute gets a quote routed across Algorand DEXes. Before you sign, you see:

• Price impact, with a warning when it's high
• Slippage, set to 0.5%, 1% or 2%

Swapping is only available on MainNet.

Your accounts carry over

Most of the upgrade happens automatically. The first time you enter your password in 2.0, Lute moves your 1.x seeds into the new keystore. They keep signing exactly as before. Ledger and passkey accounts are unchanged.

Exporting mnemonics

New in 2.0: Export mnemonic in the account menu shows an account's mnemonic after you enter your password.

1.x stored a one-way form of each key, so accounts added in 1.x need a one-time step before they can be exported. A banner on the home screen tells you how many accounts this applies to. For each one:

1. Open the account's menu and choose Upgrade account.
2. Re-enter its mnemonic. Lute checks it against the account's address, so you don't need anything else.

You don't have to do this. You can upgrade accounts one at a time whenever you like, and they work fine without it.

Don't have the mnemonic for an account added in 1.x? Lute keeps signing with it, but can't show its mnemonic to you. Consider moving those funds to a new account and writing down the new account's mnemonic.

Passwords

• No password set? Your wallet still works, but anyone with access to that browser profile can sign with your accounts. Lute shows a warning until you set one in Settings → Security. Setting one also turns on the Lock after inactivity option.
• Forgot your password? Use Forgot in Settings to set a new one. Seeds stored under the old password stay locked until you either enter the old password or upgrade each account by re-entering its mnemonic.

Other changes worth knowing

• Web app + extension: use Settings → Sync to Extension (from the web app) or Sync to Web App (from the extension) to copy accounts between them in the same browser. The receiving side asks you to confirm and only adds accounts it doesn't already have.
• Passkey seeds: you can't register new ones, but existing ones still work and can be recovered.
• Removing an Algo25 or Falcon account deletes its key from the browser, so keep the mnemonic. Removing an HD account leaves the seed in place, so you can derive the account again.

Links

• Web app: https://lute.app
• Extension: https://chromewebstore.google.com/detail/lute/kiaoohollfkjhikdifohdckeidckokjh
• Full release notes: https://github.com/GalaxyPay/lute/pull/24
• Bugs and questions: https://github.com/GalaxyPay/lute/issues

https://allo.info/account/2MX44ABLHTAJ2KX6M57QIWGMAITJC7H35FJJA336KCZC5WROGJC2N5XMKA

Hi all,

We have made the application quite a bit snappier. It was not loading some of the larger holding wallets in a reasonable amount of time so we have sped things up. Hopefully you like the update. Come track everything from node rewards, to PnL on your holdings updated real time to tax information / transactions. The page is also fully customizable so if you don't like something, simply remove it. Hope you guys like it! More to come!

European banking giant UniCredit is advising on how water credits recorded on Algorand could reach capital markets.

Hypercube has mandated the bank for the launch of a European Water Credit Sandbox.

Each of its water credits is one verified cubic metre of water.

Read more: https://www.hypercube.eco/archive/338

"While many L1 and L2 networks plan to become fully quantum-resilient L1 networks, these are just plans.

Algorand has been putting in the work since 2022.

The first major L1 to protect its chain history with Falcon-secured State Proofs.

The first major L1 to execute a post-quantum transaction on mainnet.

Native Falcon-1024 accounts, and now over 1.5 million PQ-signed transactions.

Our plans aren't just plans; they're already live on-chain, and in 2027, Algorand will be quantum-resilient.

Talk is cheap; Algorand delivers."

https://x.com/Algorand/status/2109705783088976123

Every token that bonds through hayapp Launch week will be eligible to stake their tokens (single or LP) to earn ALGO & POW

Please update your nodes to v5.0.3 as soon as possible. Release notes are available at https://github.com/algorand/go-algorand/releases/tag/v5.0.3-stable. 

This patch fixes an issue with DNSSEC validation that prevents nodes from bootstrapping into the network when started or restarted. The issue affects all types of nodes.

Nodes that are currently connected to the network are functioning properly, but a new start or restart with versions less than 5.0.3 will not be able to validate DNSSEC signatures, which are required by default. This would result in the node being unable to connect to the network.

If you have any questions about upgrading your nodes, please reach out to us in the node-runners channel of the Algorand Discord server.

One of the most consistent pieces of feedback we've gotten about Sprout is that crowdfunding, on its own, is a one-shot process: you launch a campaign, it succeeds or fails, and then there’s no real reason to hang around. A few builders pointed out that what the ecosystem might actually need isn’t just a funding tool, but a persistent environment where projects can be discovered and followed, whether or not they’re raising money right now. That resonates with our vision for Sprout, so we built it.

Sprout now has a free project directory. Any Algorand project can list itself at no cost. You don’t need to run a campaign to be there. The idea is simple: give people one place to come and see what’s actually being built on Algorand, and give builders a way to be visible even when they’re not raising funds. Crowdfunding is still there when a project needs it, but it’s now one feature of a broader home for the ecosystem rather than the whole point.

The big reason we're doing this is that there are genuinely good projects being built on Algorand that almost nobody hears about. They ship into silence. A directory won’t fix that overnight, but it’s a start. I hope the community embraces this as a shared, no-barrier environment to surface the work of our excellent builders and let the community find the projects worth following. If being discovered leads some of them to eventually run a campaign, great! If it just means a good project gets a few more eyes, that’s a win too.

If you’re building on Algorand at any stage, campaign or no campaign, we would genuinely love to have you listed. And if you want to help, just come browse what’s there and share the projects that catch your eye. The whole thing only works if the community actually uses it. Happy to answer any questions below.

www.sproutalgo.com/directory

I think he is not okey with algorand becoming EVM compatible

https://x.com/bmartins_/status/2108577435587330345

The new CEO talks about delivering post quantum security as a product to sell to the private industry, it has me thinking . I looked at companies that this could be beneficial for and thought about DocuSign. A company that stores documents and creates e signatures that need to stand the test of time so I built post-quantum signed proofs for DocuSign envelopes, anchored on Algorand mainnet

I've been built a PQ Verifiable Archive, a small open-source service that gives a signed document a proof anyone can check independently, decades from now, without trusting a middleman

**What it does**

1. A DocuSign envelope is completed. DocuSign Connect sends a webhook (HMAC-verified).

2. The service downloads the final PDF, archives that exact copy, and takes its SHA-256 hash.

3. It anchors the hash in an Algorand mainnet transaction. Finality is a few seconds and the fee is ~0.001 ALGO.

4. It issues a proof bundle signed with ML-DSA-65 (NIST FIPS-204, post-quantum).

5. Anyone can verify it in the browser or with an open-source offline CLI. Change one byte of the PDF and verification fails. A backdated capture time also fails.

The time from envelope completion to anchored proof was 23–26 seconds.

**What it doesn't claim**

The Algorand transaction is signed with Ed25519, so that part isn't post-quantum. The post-quantum guarantee comes from the ML-DSA-65 signature on the bundle. I don't verify Algorand state proofs yet.

**Try it (free, no wallet or account needed)**

- Sign a real DocuSign sandbox envelope and watch the proof get created: https://pq-verifiable-archive.vercel.app/try

- Example of a completed, verified envelope: https://pq-verifiable-archive.vercel.app/d/iblWu6Og5jJy2oFXCxsXhEAEUOb3WCc55SFZlOLKgCY

- Its anchor transaction on mainnet: https://allo.info/tx/VSQLJMHAWDPMI66MWBXGJ5RFBA3VVPH5F7IMBU3CKMARCT223FUA

**Code and write-ups**

- GitHub (code, offline verifier CLI, roadmap): https://github.com/m-reynaldo35/pq-verifiable-archive

- Step-by-step live test write-up: https://github.com/m-reynaldo35/pq-verifiable-archive/blob/main/docs/live-tests.md

- My idea post on the DocuSign community: https://community.docusign.com/ideas/i-ve-been-building-a-post-quantum-hashing-certificates-for-docusign-envelopes-using-algorand-27810

I'd really value feedback from Algorand devs, especially on verifying state proofs, alternatives to the note-field anchoring,

New piece by Algorand CSMO Marc Vanlerberghe in The AI Journal: https://aijourn.com/agentic-commerce-doesnt-have-to-kill-the-customer-relationship/

Hi all,

I build Fizzl, a set of services for AI agents that pay for things themselves (the x402 standard: an API answers "402 Payment Required" and the agent pays per call in stablecoins).

This week we added Algorand:

- Paid APIs in USDC on Algorand (ASA 31566704), settled through GoPlausible's public x402 facilitator:
- x402 Doctor: checks whether a paid x402 endpoint is safe to pay before your agent does (also free web checks at x402-doctor.fizzl.eu)
- presign-guard: a green/orange/red verdict on a transaction, approval or token before an agent signs
- Ichimoku Signal: crypto trend signals
- Fizzl Agent Wallet (wallet.fizzl.eu): spending limits and approvals for your agents' wallets. You can now sign in with Pera (QR code or the app, a free signature, no transaction) and pay for Pro in USDC on Algorand straight from Pera.

Payments go directly to our own Algorand address; nothing is custodied.

- Agents can now pay in USDC on Algorand themselves: the Fizzl wallet MCP server (npm presign-guard-wallet-mcp, with ALGORAND_MNEMONIC) and x402-safe-fetch pay x402 APIs from the agent's own Algorand account, within your limits.
- A free daily status page of x402 on Algorand: https://x402-doctor.fizzl.eu/algorand. It shows 2,392 endpoints from 134 sellers, each checked the way a paying agent would, including whether the seller's payout account is opted in to USDC (without the opt-in, every payment fails).

Feedback welcome, especially from people building agents on Algorand. What would you want an agent wallet to check before it pays?

fizzl.eu