In just one year, engineers have gone from writing code to entrusting AI to write the vast majority of it. The pace is exciting yet nerve-wracking because as developers put more faith in AI, the systems underneath need to actually work. Payments and crypto cannot be built on a house of cards.

Two things feel like common sense to me as AI usage continues to increase.

1. Software must become more modular - Lego pieces that AI can pick up & use.

2. The probabilism of AI must be balanced with deterministic systems that deliver reliable, consistent outcomes.

That last point is worth unpacking.

AI generates outputs based on likelihood, not certainty. Ask an AI agent the same question a hundred times and you'll get a hundred different responses. That's useful for reasoning, drafting, and analysis. It's not useful for executing a trade, moving funds, or triggering a workflow that needs to fire the same way every time. Those systems need to be deterministic: same input, same output, every time.

The good news is that while AI itself is probabilistic, the tools AI uses - software, APIs, execution layers - can be designed to be reliable and predictable. An AI agent can reason about what to do; a deterministic system ensures it gets done correctly.

The problem is that blockchains, in their current form, are not reliable tools. They're difficult for AIs (and businesses) to interact with at scale. Execution on decentralized networks means dealing with:

• RPC failures

• Chain reorgs + updates

• Indexing and data access

• Gas spikes

• Fragmented data interfaces and protocols

We learned this firsthand at B3 Labs, building an ecosystem of horizontally scaled chains with over a dozen consumer products. As builders who worked with enterprises - both at Coinbase and now with major external partners - we realized there was a gap we needed to fill.

A lot of effort is going into building better reasoning models and better AI. There's a growing need on the other side, providing these AIs with reliable, trigger-based ways to actually execute things. As demand grows for AI agents, demand for deterministic automation grows with it. They're opposite sides of the same coin, and I don't think most people understand that yet.

ServiceNow CEO Bill McDermott put it well on their Q4 2025 earnings call:

"AI doesn't replace enterprise orchestration. It depends on it."

The fundamental promise of crypto is building on a shared compute layer with a publicly accessible ledger. The trade-off is complexity: wallets, key management, gas, constant signing, RPCs, competing for execution on gas markets. Every onchain action requires stitching together multiple steps - and if any one fails, the whole thing breaks.

B3OS abstracts that complexity into composable blocks. Each block does one job reliably: land a transaction, listen for an event, connect to a protocol, manage a wallet. You snap them together to build workflows - the same way you'd connect nodes in Zapier, except these blocks understand crypto natively. A trigger fires, an action executes onchain, a connector pipes the result to Slack. The pieces are modular, the execution is deterministic, and the infrastructure underneath handles the mess so you don't have to.

Here's what those blocks look like:

Triggers: The starting point. Fire on a schedule, on a block, or on specific contract events - Polymarket trades, new markets, LP pools, and more.

Actions: The things that happen. Production-tested, composable blocks for executing onchain: placing trades, fetching data, bridging assets. Instant support for any x402 endpoint, indexed automatically.

Connectors: The bridges. Onchain protocols like Polymarket and Neynar, plus 2,000+ Web2 connectors for Slack, Telegram, Google, and more.

Execution Engine: The layer underneath. Lands transactions consistently across multiple chains with low latency. Handles gas, RPC failures, reorgs, and auto-retries so individual blocks don't have to.

Managed Wallets: Shared or solo wallets with organizational structure. Export your private keys anytime. Full audit trail and permissions.

AI Agent: Caddie, our specialized LLM, who works with you to build, connect, modify, and debug all of these pieces.

Building onchain should be as simple as connecting blocks - a unified API and MCP layer where agents can provision wallets and set up complex workflows without friction. Whether you're powering DeFi apps, stablecoin operations, or agentic commerce, B3OS is the execution layer underneath - the missing link builders, traders, & teams have been searching for..

- @seangeng CTO of B3

In just one year, engineers have gone from writing code to entrusting AI to write the vast majority of it. The pace is exciting yet nerve-wracking because as developers put more faith in AI, the systems underneath need to actually work. Payments and crypto cannot be built on a house of cards.

Two things feel like common sense to me as AI usage continues to increase.

1. Software must become more modular - Lego pieces that AI can pick up & use.

2. The probabilism of AI must be balanced with deterministic systems that deliver reliable, consistent outcomes.

That last point is worth unpacking.

AI generates outputs based on likelihood, not certainty. Ask an AI agent the same question a hundred times and you'll get a hundred different responses. That's useful for reasoning, drafting, and analysis. It's not useful for executing a trade, moving funds, or triggering a workflow that needs to fire the same way every time. Those systems need to be deterministic: same input, same output, every time.

The good news is that while AI itself is probabilistic, the tools AI uses - software, APIs, execution layers - can be designed to be reliable and predictable. An AI agent can reason about what to do; a deterministic system ensures it gets done correctly.

The problem is that blockchains, in their current form, are not reliable tools. They're difficult for AIs (and businesses) to interact with at scale. Execution on decentralized networks means dealing with:

• RPC failures

• Chain reorgs + updates

• Indexing and data access

• Gas spikes

• Fragmented data interfaces and protocols

We learned this firsthand at B3 Labs, building an ecosystem of horizontally scaled chains with over a dozen consumer products. As builders who worked with enterprises - both at Coinbase and now with major external partners - we realized there was a gap we needed to fill.

A lot of effort is going into building better reasoning models and better AI. There's a growing need on the other side, providing these AIs with reliable, trigger-based ways to actually execute things. As demand grows for AI agents, demand for deterministic automation grows with it. They're opposite sides of the same coin, and I don't think most people understand that yet.

ServiceNow CEO Bill McDermott put it well on their Q4 2025 earnings call:

"AI doesn't replace enterprise orchestration. It depends on it."

The fundamental promise of crypto is building on a shared compute layer with a publicly accessible ledger. The trade-off is complexity: wallets, key management, gas, constant signing, RPCs, competing for execution on gas markets. Every onchain action requires stitching together multiple steps - and if any one fails, the whole thing breaks.

B3OS abstracts that complexity into composable blocks. Each block does one job reliably: land a transaction, listen for an event, connect to a protocol, manage a wallet. You snap them together to build workflows - the same way you'd connect nodes in Zapier, except these blocks understand crypto natively. A trigger fires, an action executes onchain, a connector pipes the result to Slack. The pieces are modular, the execution is deterministic, and the infrastructure underneath handles the mess so you don't have to.

Here's what those blocks look like:

Triggers: The starting point. Fire on a schedule, on a block, or on specific contract events - Polymarket trades, new markets, LP pools, and more.

Actions: The things that happen. Production-tested, composable blocks for executing onchain: placing trades, fetching data, bridging assets. Instant support for any x402 endpoint, indexed automatically.

Connectors: The bridges. Onchain protocols like Polymarket and Neynar, plus 2,000+ Web2 connectors for Slack, Telegram, Google, and more.

Execution Engine: The layer underneath. Lands transactions consistently across multiple chains with low latency. Handles gas, RPC failures, reorgs, and auto-retries so individual blocks don't have to.

Managed Wallets: Shared or solo wallets with organizational structure. Export your private keys anytime. Full audit trail and permissions.

AI Agent: Caddie, our specialized LLM, who works with you to build, connect, modify, and debug all of these pieces.

Building onchain should be as simple as connecting blocks - a unified API and MCP layer where agents can provision wallets and set up complex workflows without friction. Whether you're powering DeFi apps, stablecoin operations, or agentic commerce, B3OS is the execution layer underneath - the missing link builders, traders, & teams have been searching for..

- @seangeng CTO of B3