Blockchain

Ethereum Glamsterdam Upgrade: ePBS, BALs, Every EIP and Operational Changes

Ethereum Glamsterdam Upgrade: ePBS, BALs, Every EIP and Operational Changes

Glamsterdam aims to expand Ethereum L1 capacity by changing both how blocks are built and how receiving nodes validate them. Enshrined proposer-builder separation (ePBS) brings commitments, payload reveals and proposer payments into the protocol. Block-level access lists (BALs) carry actual state accesses and post-transaction changes so receiving nodes can parallelize reads and validation. Gas repricing and networking changes support that effort. These changes do not guarantee lower fees for every transaction or a particular TPS figure. EIP-7773 defines the scope; EIP-7732 and EIP-7928 define the two central mechanisms.

Read More
Transferring Tokens with Canton Daml: State and Authorization Compared with Solidity

Transferring Tokens with Canton Daml: State and Authorization Compared with Solidity

When Alice sends all 100 token units to Bob, Bob becomes the person who can spend them next. The Solidity example updates balances by address; the Daml example for Canton consumes Alice’s holding contract and creates Bob’s. They express the same transfer outcome with different units of state and different authorization checks.

Read More
Understanding Besu: From Ethereum Execution to Bank Token Payments

Understanding Besu: From Ethereum Execution to Bank Token Payments

Besu is a Java Ethereum client that executes smart contracts and verifies and stores their results. Banks can use it to build a ledger that handles deposit tokens alongside interbank settlement assets. It also serves as an execution client on Ethereum mainnet. These deployments share execution technology, while the issuers of money and the parties that finalize the ledger depend on the network. Besu documentation

Read More
Understanding Canton Network: Financial Privacy, Atomic Settlement, and Institutional Adoption

Understanding Canton Network: Financial Privacy, Atomic Settlement, and Institutional Adoption

Buying a security changes records in several places. A trading venue records the execution, a custodian records the securities position, and a bank maintains the cash ledger. Each institution has its own account of the transaction. Reconciliation checks that amounts, rights, and processing states agree. A single public database might appear to simplify the problem, but institutions cannot publish their customers’ balances and trading strategies to everyone operating the infrastructure.

Read More
Glamsterdam's New Gas Model: EIP-8037 State Gas, EIP-8038 Access Costs, EIP-2780 Intrinsic Gas

Glamsterdam's New Gas Model: EIP-8037 State Gas, EIP-8038 Access Costs, EIP-2780 Intrinsic Gas

Glamsterdam’s three gas proposals make new persistent state more expensive and raise the cost of updating existing state, while lowering the base cost of some transactions that do less work. A fresh cold storage write has specified components of 12,100 execution gas plus 97,920 state gas; the first cold change away from an existing slot’s nonzero transaction-start value costs 12,100 execution gas and no state gas. Both still draw on the transaction’s single gasLimit, but gasleft() does not report the separate state-gas reservoir. These are specification costs, not measured Solidity function totals or an announcement that the rules are active on mainnet. EIP-8037, EIP-8038 and EIP-2780 define the changes together.

Read More
Know Your Agent (KYA): AI Agent Identity, the Standards Race, and What Is Actually On-Chain

Know Your Agent (KYA): AI Agent Identity, the Standards Race, and What Is Actually On-Chain

An identity credential or an on-chain registration number is insufficient grounds to let an AI agent spend money or access data. Identifying the agent, authenticating the requester, checking its authority for this action, and deciding how much to trust past feedback are separate checks. Know Your Agent (KYA) groups these concerns under one name. ERC-8004 supplies identifiers and public trust signals; Visa TAP and identity-verification vendors offer other ways to check requests, organizations or people. The service receiving the request still decides whether to grant access. The ERC-8004 specification and Trulioo’s product description both limit what registration or verification establishes.

Read More
The A2A (Agent-to-Agent) Protocol: How Agents Delegate to Each Other, and Where Payments Plug In

The A2A (Agent-to-Agent) Protocol: How Agents Delegate to Each Other, and Where Payments Plug In

A2A (Agent2Agent) standardizes how to delegate work to an independently operated agent and receive progress and results. A client reads an Agent Card for capabilities, endpoints and authentication requirements, then tracks longer work as a Task. MCP connects each agent to tools and data; separate protocols such as AP2 and x402 handle purchase authorization and payment settlement. Collaborating over A2A requires neither a blockchain nor a wallet. A2A specification, division of responsibilities with MCP

Read More
Bitcoin, Ethereum, and the Quantum Computing Question

Bitcoin, Ethereum, and the Quantum Computing Question

Quantum computers are a long-term threat to the signatures that protect Bitcoin and Ethereum. The public research checked on October 16, 2026 (KST), however, estimates resources for future error-corrected machines; it does not demonstrate recovery of a real secp256k1 private key on quantum hardware. Risk depends on how long a public key is exposed, how long an attack takes, and whether authentication and authority can migrate first. Bitcoin’s defenses remain proposals, while Ethereum is working on a transition across accounts, consensus, and data. Resource-estimation paper, BIP-360, Ethereum Foundation transition plan

Read More
Apify x402 and Coinbase Wallets, in Depth: How Agents Buy Web Automation Tools Directly

Apify x402 and Coinbase Wallets, in Depth: How Agents Buy Web Automation Tools Directly

Apify, the web scraping platform, announced x402 support: AI agents can now run more than 20,000 Apify Actors by paying with USDC on Base, with no Apify account and no API key. Apify frames the prior x402 ecosystem as roughly 2,000 endpoints, so by its own count this integration expanded the paid-tool surface by about 10x.

Read More
AI Agent Commerce and Coordination: ERC-8183, ERC-8226, ERC-8001, ERC-8041

AI Agent Commerce and Coordination: ERC-8183, ERC-8226, ERC-8001, ERC-8041

The ERC-8004/8126/8196 trust stack defines three layers: agent identity, security verification, and policy-constrained execution. It identifies an agent, scores its risk, and keeps it acting within the limits an owner has set. All of that answers one question: can I trust this agent to act on my behalf?

Read More
Chainlink CCIP EVM Contracts: Architecture from Source Code

Chainlink CCIP EVM Contracts: Architecture from Source Code

EVM chains are isolated by design. A contract on Arbitrum has no native way to call a contract on Base, and sending USDC from Ethereum Mainnet to Polygon is not a built-in operation. Cross-chain bridges filled that gap for years, but the category has seen repeated security incidents that highlight how wide the attack surface is.

Read More
Circle CCTP V2 EVM Contracts: A Source-Code Walkthrough

Circle CCTP V2 EVM Contracts: A Source-Code Walkthrough

Bridge designs for moving USDC between chains come down to two families. Lock-and-mint parks the original token in a contract on the source chain and issues a wrapped version on the destination. Burn-and-mint destroys the token on the source chain outright and issues the same amount fresh on the destination. Circle’s CCTP (Cross-Chain Transfer Protocol) is the second kind.

Read More
ERC-8004 Agent Reputation: On-Chain Registration and Lookup

ERC-8004 Agent Reputation: On-Chain Registration and Lookup

A prior post on this blog covered the ERC-8004/8126/8196 trust stack: three Ethereum registries that handle agent identity, reputation, and validation. If you want the conceptual overview first, start there. This post is about something narrower: how feedback actually gets written to the Reputation Registry, how to read it back, and what services are available today to browse and index that data.

Read More
Agentic Payments in June 2026: x402, UCP, and MPP Implementation Progress

Agentic Payments in June 2026: x402, UCP, and MPP Implementation Progress

Agentic payments in June 2026 moved from “can an agent pay” toward “who authorized the payment, how is it verified, and how is it traced.” The major open protocols (x402, UCP, MPP/pay.sh, and ACP) each had meaningful implementation changes. All figures and commit details below come from GitHub API, PyPI, and npm registry checks.

Read More
AI x Blockchain in 2026: Bittensor, DePIN, and Agent Finance

AI x Blockchain in 2026: Bittensor, DePIN, and Agent Finance

“AI plus blockchain” spent most of the early 2020s as a marketing phrase. By mid-2026, it has organized into four distinct layers, each with its own competitive dynamics. Which projects have staying power, and what are the actual evaluation criteria at this point?

Read More
Figure: From HELOC Lender to Blockchain-Native Capital Markets

Figure: From HELOC Lender to Blockchain-Native Capital Markets

Two companies go by the name Figure. One is Figure AI, the humanoid robotics company. The other is Figure Technology Solutions, which is what this post is about. They are unrelated.

Read More
Lighter: A ZK-SNARK Orderbook DEX on Ethereum

Lighter: A ZK-SNARK Orderbook DEX on Ethereum

Decentralized exchanges come in two main forms. AMMs (Automated Market Makers) like Uniswap set prices algorithmically from pool ratios and work as permissionless swap venues. Orderbook DEXes match individual buy and sell orders by price and time priority, the same way centralized exchanges like Binance or Coinbase operate. Orderbooks enable limit orders, tighter spreads with active market-making, and more precise price discovery. AMMs do not.

Read More
The AI Agent Trust Stack: ERC-8004, ERC-8126, and ERC-8196

The AI Agent Trust Stack: ERC-8004, ERC-8126, and ERC-8196

When an AI agent acts on behalf of a user (spending funds, calling contracts, accessing paid APIs), the obvious question is: how do you know this agent is safe? The Ethereum community has three standards that address different layers of that question. They don’t solve the whole problem, but they’re building toward a coherent stack.

Read More
Secret Voting Architecture with FHE, SP1, and Groth16

Secret Voting Architecture with FHE, SP1, and Groth16

On-chain secret voting creates three tensions at once. Votes must stay hidden while still being tallied. Off-chain computation cannot be trusted without proof, yet results need to land on-chain. And the EVM cannot run heavy cryptographic operations natively, but it still needs to verify them. FHE (Fully Homomorphic Encryption), SP1 zkVM, and Groth16 each take on one of these.

Read More
Categories
Tags