Humanity Ledger (@humanityledger) header
Humanity Ledger (@humanityledger) profile picture

private state and messaging protocol only possible on @aztecnetwork

Joined October 2026
Photo by Humanity Ledger (@humanityledger)Photo by Humanity Ledger (@humanityledger)Photo by Humanity Ledger (@humanityledger)Photo by Humanity Ledger (@humanityledger)Photo by Humanity Ledger (@humanityledger)Photo by Humanity Ledger (@humanityledger)Photo by Humanity Ledger (@humanityledger)
Humanity Ledger retweeted
Congratulations to @aztecnetwork for reaching 1st place this week. aztec.network now sits above Base, Starknet and Optimism on AXBeat.
1
1
2
10
794
Humanity Ledger retweeted
Another day, another breach. There is NO reason that home addresses, phone numbers, and dates of birth need to be shared with TFL.
2
2
2
18
952
There is no operational requirement for Transport for London to hold home addresses, telephone numbers or dates of birth. Eligibility can be proven by selective disclosure. The raw personal data need never be shared.
Another day, another breach. There is NO reason that home addresses, phone numbers, and dates of birth need to be shared with TFL.
1
5
160
Humanity Ledger retweeted
As a reminder, private money on Aztec is reachable from wherever your funds already sit. @zk_money accounts fund from any EVM chain, stay private in between, and withdraw back to any of them. Plus, there's even more to love about @zk_money, read more below! ⬇️
Fund your zk.money account from multiple EVM chains. Withdraw privately to any of them. Any chain in. Private in between. Any chain out. Powered by @AcrossProtocol
6
8
1
53
4,946
Humanity Ledger retweeted
Aztec didn't go down yesterday. Unstoppable, decentralized private financial rails are going to be more important than ever as traditional financial rails fall to pieces under AI assaults. Now is a great time to start using @zk_money
Yesterday's bank outages, and today a Fed governor says the bank monopoly on payments is breaking down. Every day there's another reason to move onchain.
5
6
2
73
2,736
Built on Aztec v6: in Ledger Chat, your device is the client. Keys are derived there. Proofs are made there. New: passkeys that open the same private account, payee proofs bound to the network, and an Ethereum portal whose Aztec side is written in aztec-nr.
4
13
409
Humanity Ledger retweeted
AXBeat · 16 Nov @aztecnetwork is now top of the AXBeat leaderboard. 18th two weeks ago. 3rd last week. 1st today. 8 more fixes on aztec.network this week: ➔ Link headers ➔ API catalog ➔ MCP server card ➔ Agent Skills index ➔ WebMCP tools ➔ DNS for AI discovery ➔ Agent resource manifest ➔ Personal Agent Protocol Aztec now is 4/5 on Cloudflare’s agent-readiness scan, meaning @build_on_bob drops to 2nd and @base falls to 3rd place.
2
6
6
26
5,180
Messages encrypted on your device. Payments proven on your device. In the same conversation. This is Ledger Chat: XMTP (MLS) for chat, a private wallet whose PXE runs in your browser, private HLC payments on @aztecnetwork, settled on @ethereum. Live on Aztec Alpha. ledgerchat.org
3
8
266
The five plates are one diagram of a client on Aztec Alpha. The line from the left is what is already true before a payment exists. The person holds an Ethereum account on the device. Private execution runs in Aztec’s Private Execution Environment, in the browser, where the UltraHonk proof is constructed and the private inputs are not transmitted. The message is separate from that proof: it is an XMTP version 3 session under Messaging Layer Security, IETF RFC 9420, which this client does not implement. Before the payment is constructed, a domain-separated Schnorr signature over the Grumpkin curve binds that inbox to the Aztec account. The binding is trust on first use, and it is not a proof of control of the nullifier key. The line from the right is the settlement, and it ends in the same plate. The payment is a private note, and the nullifier that spends it is Aztec’s. The account pays the fee in Fee Juice. That balance is public, because Aztec must be able to see that a transaction can pay for itself, while the transaction itself stays private. The application does not sponsor the fee. Aztec Alpha settles the note, and the sequencer posts the block to Ethereum. The third plate is only where those two lines meet. Ledger Chat operates neither the sequencer, nor a relayer, nor a remote prover. The last plate states the limit of the drawing. Keyed instances of the escrow and of the payment stream exist on the testnet, they are not deployed on Alpha, and there is no external audit.
1
1
7
594
How non-custodial onboarding works on @aztecnetwork Alpha without centralized relayers: Aztec Alpha shifts away from testnet subsidized fee payers toward credible neutrality: accounts are sovereign smart contracts that fund and execute their own state transitions. To onboard a user holding zero AZTEC without introducing a custodial relayer, Ledger Chat implements peer-to-peer fee delegation using Aztec's native FeeJuicePaymentMethodWithClaim (breakdown of the diagram below): Phase 1. Ephemeral Secret Generation The recipient derives an ephemeral claimSecret locally in-browser from their signing key. Only the recipient Aztec address and secretHash are shared with the counterparty. Phase 2. Cross-Chain Message Ingress The counterparty calls depositToAztecPublic on Ethereum L1 FeeJuicePortal, locking AZTEC collateral and emitting an L1→L2 message into the rollup inbox (provable on L2 after ~2 blocks). Phase 3. Account Initialization & Fee Settlement The recipient dispatches FeeJuicePaymentMethodWithClaim. Inside the transaction setup phase, claim_and_end_setup consumes the message with the claimSecret, credits Fee Juice to public storage, deploys the account contract instance, and settles the execution fee. Why this architecture matters: • Zero centralized gas pool vulnerable to Sybil drainage. • No privileged relayer sitting between user and sequencer. • Recipient privacy is preserved on L1 (the portal only sees the secretHash). • True peer-to-peer onboarding: economic friction is settled directly between counterparties. Programmable privacy requires programmable, non-custodial fee mechanics. Runbook and verification receipts: github.com/humanityledger/Hu… @aztecnetwork @AztecLabs_ @Zac_Aztec @jaosef
1
6
16
730
How a private payment moves through Ledger Chat, end to end: 1. You agree on it inside an XMTP direct message encrypted with MLS (IETF RFC 9420). The message content never leaves the devices of the two participants. 2. Before any value moves, the app verifies a domain-separated Schnorr signature over the Grumpkin curve (G7 peer binding). This signature binds the recipient’s XMTP inbox to their Aztec account, so the payment can only go to the person you are actually talking to. The binding is checked on the client before the transaction is built. 3. Your browser runs Aztec’s Private Execution Environment (PXE) as WebAssembly and generates the UltraHonk zero-knowledge proof locally. Private keys, note amounts and other sensitive inputs never leave the device. Only the proof and encrypted outputs are sent. 4. @aztecnetwork Alpha settles the transaction. On chain an observer sees note commitments and nullifiers, but not the sender, recipient or amount. Fees are paid in Fee Juice from the sender’s own account (no sponsor). Today we sent a second private payment from the normal wallet screen in the web app. It was checkpointed in L2 block 29771. Earlier today the first payment (0.10 HLC) was settled in L2 block 29012: 0x1eb2bb76ae52d876e0ef8e107bf9de5b83ce9cb42850a1a1a938cae3c24040a5 (verifiable on Aztecscan). Still open, in this order: 
• External audit of the Aztec contracts (payments remain capped until then)
• Real-world G7 testing between two different people across browsers
• Zero-cost onboarding so new accounts do not need Fee Juice to start Code and tests: github.com/humanityledger/Hu… @aztecFND @Arnaudschenk @jaosef @Zac_Aztec
1
3
13
267
On-chain privacy without private communication still leaves the social graph exposed. Ledger Chat settles private value on @aztecnetwork Alpha. Its 1:1 direct messages run on @xmtp_ v3, which implements Messaging Layer Security (IETF RFC 9420). Joining the two layers opens a specific risk: substituting the address a private payment is sent to. We built and open-sourced two primitives to close it. 1. G7 peer binding (lib/aztec/peer-binding.ts) Each XMTP inbox is bound to its Aztec account by a domain-separated Schnorr signature over Grumpkin: σ = Schnorr_sk(H("hl/aztec-binding/v1 | address | signerInboxId | dm:recipientInboxId")) The client recomputes the account address from the signing key and verifies σ before any private payment is authorised. Because the recipient inbox is signed, a binding cannot be replayed into another conversation. 2. Encrypted local storage (lib/xmtp/db-key.ts) The in-browser message database is encrypted at rest. Its key is derived on demand with HKDF-SHA256 from a deterministic EIP-191 wallet signature. It is never stored in plaintext and never leaves the device. Private messaging and private settlement now share one verified identity. Both primitives ship with unit tests. The contracts are not yet audited, and we welcome review from the research community. Architecture and security notes: ledgerchat.org Code and G7 tests: github.com/humanityledger/Hu…
3
7
169
Ledger Chat is live on Aztec Alpha. On 14 November, a private payment sent from the Ledger Chat web app settled on Aztec Alpha, the privacy L2 secured by Ethereum. The proof was made in the browser. The keys never left the device. The network verified it, and L2 block 29012 recorded it. Why it matters: • Proved where you are. Aztec's PXE runs inside the browser (WebAssembly). No remote prover sees the inputs or holds the keys. • Pays its own way. Network fees are paid in Fee Juice from the sender's own account. No sponsored fee payer. • Your chat knows who it is paying. Ledger Chat binds an XMTP identity (MLS, RFC 9420) to an Aztec address with a domain-separated Schnorr signature, so value only moves to an address its owner signed for. • On chain, checkable. Transfer 0x1eb2bb76ae52d876e0ef8e107bf9de5b83ce9cb42850a1a1a938cae3c24040a5, checkpointed in L2 block 29012. Confirmed by our public CI. Encrypted messages and private payments in one place, from a browser tab. The contracts are not audited yet, and payments on Alpha are capped. Everything we claim is in the repo. ledgerchat.org Code and dossier → github.com/humanityledger/Hu… @AztecLabs_ @Zac_Aztec @aztecnetwork @Zac_Aztec @jaosef @xmtp_
2
6
21
724
Humanity Ledger retweeted
Do you understand now how big the vision is? And that some of the biggest gigabrain devs in the space are bringing it to life?
14
5
5
79
6,649