Finance District

185 posts

Finance District banner
Finance District

Finance District

@FD_XYZ

Infrastructure for the agent economy Start: https://t.co/7CAhUQtH2A | Docs: https://t.co/DSIgErJw70 Built by @FirstDigitalHQ

Katılım Eylül 2025
6 Takip Edilen895 Takipçiler
Finance District
Finance District@FD_XYZ·
Most businesses running AI agents have no audit trail for what those agents spend. They're running them on shared wallets or prepaid cards and reconciling manually after the fact. That setup holds up when you have two agents. It doesn't hold up at twenty, and it won't survive a legal review. The question their finance teams are actually asking isn't "can it do the task?" It's whether they can see what it spent and why. The compliance question always catches up to the deployment question.
Finance District tweet media
English
0
0
0
58
Finance District
Finance District@FD_XYZ·
@0xJeff One edge case as you add providers: tools that accept different tokens or chains. A single-asset wallet bounces on whatever you're not holding. Multi-asset balances avoid it.
English
0
0
0
104
Finance District
Finance District@FD_XYZ·
The financial system was designed around one assumption: a human is always in the loop. Not to authorize every transaction or approve every payment, but simply to exist as an accountable party. AI agents are the first buyers, sellers, and intermediaries who do not meet that assumption. The rails need rebuilding, not patching
Finance District tweet media
English
0
0
0
167
Finance District
Finance District@FD_XYZ·
Every payment protocol before x402 added a layer on top of the web. x402 puts payment inside the request itself. → A server returns a 402 with the payment details. → The agent pays on-chain. → It retries with proof in the header. → The server verifies and returns the resource. No SDK. No API key. No checkout flow. No redirect. Any server that supports x402 is now a storefront your agent can buy from.
Finance District tweet media
English
1
0
0
117
Fireblocks
Fireblocks@FireblocksHQ·
Humans used to initiate every payment. These days? Think again, AI agents are here. Today we're launching the Fireblocks Agentic Payments Suite and joining the @x402Foundation. Buckle up. It's going to be a wild (but secure) ride. Here's the full stack 🧵
English
13
13
71
12K
Finance District
Finance District@FD_XYZ·
@catena_labs Congrats on the round. Agents safely using money splits two ways: bank custody with governance, or non-custodial with hardware-isolated keys. Operators will pick based on their threat model.
English
0
0
0
65
Catena
Catena@catena_labs·
Your agents can ship code, draft contracts, and triage your inbox. What they can't do is safely use money. The financial system has no framework for software acting on someone else's behalf.
English
21
13
100
19K
Finance District
Finance District@FD_XYZ·
@Nick_Prince12 We love no API keys. The worst hour of any agent project is signing up for 5 accounts, juggling 5 secrets, and finding which one is throttling you this week
English
0
0
0
71
Nick Prince🛡
Nick Prince🛡@Nick_Prince12·
my agent ran my morning briefing today for $0.02 (world, ai, crypto, top deep dive) 5 APIs, zero API keys shipped this as a bundle in agentic(.)market. market research and talent market scanner live too. what bundle do you want next?
English
40
11
100
9.3K
Finance District
Finance District@FD_XYZ·
@circle @jerallaire The change is happening: payments live inside HTTP itself. No portal, no signup, no API key. Sign and go 🤝
English
0
0
0
210
Circle
Circle@circle·
If software is going to transact, costs have to disappear. @jerallaire on why nanopayments matter and what becomes possible when moving money costs almost nothing.
English
23
33
249
664.5K
Finance District
Finance District@FD_XYZ·
@CoinbaseDev @Jnix2007 Spend caps are the natural pair to scoped signing. Per-tx, per-day, per-token limits enforced by the smart account itself. Scoped signer stops the wrong action. Spend caps bound the right action when instructions go sideways.
English
0
0
0
43
Coinbase Developer Platform🛡️
Most AI agents don't need access to the whole wallet. Account-scoped delegated signing is now available on Coinbase non-custodial wallets, letting users grant agents permission for one account only. Demo + docs from @jnix2007
jnix.base.eth@Jnix2007

🚀Introducing Account-Scoped Delegated Signing in @CoinbaseDev Wallets You can now scope delegations to a specific account, enabling flows like the one shown in this demo app, with a user granting an agent narrower permissions:

English
6
7
23
3.5K
Finance District
Finance District@FD_XYZ·
@jerallaire Pay-per-request only works if the agent can pay on whatever chain the merchant takes. ERC-3009 makes the payer gasless. Most x402 deployments still pin you to one chain and one stablecoin. That's where the wallet has to do the work.
English
0
0
0
31
Finance District
Finance District@FD_XYZ·
@brian_armstrong The wallet on the agent's side is where it breaks. ERC-3009 makes the payer gasless. The harder part is letting that wallet pick the chain from what the merchant accepts, not the other way around.
English
0
0
0
490
Finance District
Finance District@FD_XYZ·
Giving an agent access to your wallet is not the same as giving an agent a wallet. One borrows a human permission model. The other has its own: spend limits, session keys, revocable permissions, audit trails a human can actually read. When your agent has its own wallet, you are not trusting it. You are governing it.
Finance District tweet media
English
0
0
1
79
Finance District
Finance District@FD_XYZ·
The most important thing in any payment network was never the currency. It was the infrastructure that moved it. That was true for Visa in 1958. True for SWIFT in 1973. The token is easy to copy. The rails take years to build and decades to earn trust. Stablecoins are the money layer of the agentic economy. But what's actually scarce isn't a stable token, there are dozens. What's scarce is the infrastructure that moves value between agents, APIs, and services without human intervention. Own the rails, not just the token.
English
0
0
4
106
Finance District
Finance District@FD_XYZ·
@jessepollak 'no API keys' is where 'integrate with us' stops being a sales call and starts being an HTTP request.
English
0
0
0
22
jesse.base.eth
jesse.base.eth@jessepollak·
x402 now supports batched settlement this unlocks many many tiny tiny payments (<$0.0001) which is perfect for paying for just in time resources like compute and inference
jnix.base.eth@Jnix2007

🚀x402 now supports batch settlement: Transact at extremely low latency and fractions of a cent Agents can now escrow funds once, then pay with off-chain vouchers. x402 sellers can settle a batch of payments in a single transaction, instead of settling every request

English
85
76
599
78.7K
Finance District
Finance District@FD_XYZ·
@circle The access vs control framing resonates with us as progressive architecture. Layer in session keys and spend caps when agent autonomy needs them. Balance ends up being the primary control.
English
0
0
0
83
Circle
Circle@circle·
Agents need access to funds. Users need control. Agent Wallets give agents a way to hold and move USDC under human-defined policies, including: → Time-bound spending limits → Transfer and x402 service controls → Allowlists and blocklists → Wallet-layer policy enforcement Built for agentic payments with guardrails.
Circle tweet media
English
53
69
296
14.7K
Finance District
Finance District@FD_XYZ·
@base This makes us wonder whether the next wave comes from new agents on the same merchants, or new merchants opening up to agent traffic for the first time 👀
English
0
0
0
295
Base
Base@base·
Over $50M has now been spent on services by agents using x402 More than 85% of it happened on Base
Base tweet media
English
132
118
717
159.6K
Finance District
Finance District@FD_XYZ·
Stablecoins have had four distinct eras. 1.0 — Trading. Getting in and out of crypto without touching a bank. The original use case, dating back to 2013. 2.0 — DeFi. Liquidity, lending, yield. The protocol era that made stablecoins load-bearing infrastructure for decentralised finance. 3.0 — Payments. Cross-border transfers, merchant settlements, payroll. What most people today think stablecoins are for. 4.0 — Agentic. Agents don't use payment links. They don't have billing accounts. They hold stablecoins, pay in seconds, and settle without human approval. The builders who design for 4.0 now, while most of the market is still building for 3.0, are the ones who will own the infrastructure when agents become the dominant economic actor. Most of what's being built today will need to be rebuilt. The ones who build for 4.0 first won't have to.
Finance District tweet media
English
1
0
2
135
Finance District
Finance District@FD_XYZ·
By 2030, AI agents are expected to mediate $3-5 trillion in global commerce. The institutions in that room were not debating the number. They were working out what it means for how they need to be positioned. Most of what they'll need doesn't exist yet. That's the window.
First Digital@FirstDigitalHQ

What a great day in Seoul yesterday! 🇰🇷 Our CEO @vchok took the stage at the Institutional Web3 Forum to share his perspective on stablecoin innovation and Asia market strategy. Great to see the conversation around institutional Web3 moving this fast.

English
0
0
2
106
Finance District
Finance District@FD_XYZ·
@CoinbaseDev Batch settlement changes the wallet design calculus. Gas overhead per request disappears and you're working with a single fixed session budget. This follows our Agent Wallet philosophy: fund the agent exactly what it needs, no more.
English
0
0
1
150
Coinbase Developer Platform🛡️
New for agentic payments on x402: Batch settlement lets AI agents fire off API calls without settling each one individually onchain. Off-chain vouchers. One final settlement. Gasless for both sides (if facilitator-sponsored). Learn more ↓
jnix.base.eth@Jnix2007

🚀x402 now supports batch settlement: Transact at extremely low latency and fractions of a cent Agents can now escrow funds once, then pay with off-chain vouchers. x402 sellers can settle a batch of payments in a single transaction, instead of settling every request

English
18
9
66
10.3K