Pinned Tweet
How I submitted evidence, created a digital asset, and sent another digital asset using the @GeeqOfficial wallet on the IGNITE chain
“The primary users of the Internet are no longer human. They’re AI agents.”
Olivia Moore’s post from @a16z has become a defining observation of the tech landscape in late 2026.
Agents already account for the majority of web traffic, write more than half of new articles published online, and generate most of the code pushed to production.
Agents are moving from answering questions to completing tasks — choosing products, signing up for services, and *spending money* on behalf of users.
Moore calls this the “B2A (Business to Agents)” economy and argues that companies that treat agents as first-class customers will capture the next wave of growth. She also highlights the need for “agent infrastructure” — the underlying layers for payments, identity, communication, and more.
bull.family $BULL sits at the forefront of that infrastructure.
@bulldotfam_ily is building “The Modular Settlement Layer powering the Agentic Economy” — a layer where agents settle deals with each other as code.
Agents compose the terms as modular blocks.
The contract holds the funds.
When every condition resolves true, settlement is atomic. If the conditions are never met, the funds are automatically returned. It is fully non-custodial: no owner key, no admin key, and no one can touch the funds.
The modular conditions include:
- Time passing
- Confirmation (attest) from a specific agent or arbiter
- Onchain balances or prices crossing a threshold
- Another Bull deal having settled (deal chaining)
- Automatic settlement after a window unless someone objects
- Panel voting (k-of-n)
and more to come.
This allows complex agent-to-agent agreements — for example, “Pay 500 USDG only after C confirms delivery and B’s token balance has increased, unless D objects within 48 hours” — to be expressed entirely in code.
An MCP server is already live, so Claude and other MCP-compatible agents can connect directly to create RFQs, run private OTC trades, or set up programmable agreements. No accounts or API keys are required — just a wallet signature.
In the world Moore describes — where agents choose products, subscribe to services, and move money — a foundation for *trustless settlement* becomes essential "which ai agents already claiming in public!!"
To sum it up,
Agents are already dominating and coming to onchain sooner than we think. Start betting on early movers on each layers, "credit" "account" "trading" "settlement" etc.
Agents now make up the majority of web traffic, write more than half of new articles published online, and generate most of the code pushed to production.
This is what the early stage of a platform shift looks like: adoption is measurable, but the business models it enables mostly aren’t visible yet.
Welcome to the agent economy.
a16z.news/p/welcome-to-the-b…
Golden retweeted
The real problem isn’t payments. It’s verifiable, revocable authority.
We open-sourced the control layer for institutional wallets:
->Approvals locked to the exact transaction bytes.
->Approvers and signers verify independently.
->Pending payments count against shared limits.
->Approval is not signing is not settlement.
EVM + Solana. Fail-closed. Runs locally.
What’s still missing for institutions to actually trust this?
Golden retweeted
AI companies aren't just asking for faster payments. They're asking who gave the agent permission.
@cc_crowley on what that means for founders entering the agentic economy. 👇
Golden retweeted
Replying to @cc_crowley
Very helpful go-to-market advice, @cc_crowley.
Proving current authority for a specific task,
within a specific workflow,
on a specific asset,
while cross-checking that it doesn't violate policy and other binding constraints
is exactly why we've built Evidence Rails.
Authority requires new crypto-primitives. I'd dispute the notion that traditional identity and access management does that well, see any recent headline... although inertia is real. At least it will become costly.
Transactions and liability must account for the third-party risk of incorporating agents, see: @Mubaraqkhan.
THEN we hope we'll be ready to return to payments at scale.
For now, let's work on keeping the castles from falling.
Golden retweeted
Can we defend ourselves based on the records
we recovered?
When the services resume, are you still liable for the uncertainty?
That's the question I want to solve for all of us.
Let's build to take anxiety down a notch or two. Or ten.
Cloud services have had a bad week. It could get worse.
Restoring cloud services won't necessarily restore confidence in your records.
Can you independently verify the evidence behind a payment, approval, or report?
We build evidence rails to preserve proofs, so you are not purely dependent on your cloud provider.
Golden retweeted
Synthesizing out loud:
- Merchant
- Customer
- Agent
- Payment provider
Each has separate incentives and requirements.
At present, we only have a muddy view of authority.
Each wishes to exercise some authority; however,
those views may overlap and conflict.
@Mubaraqkhan is correct: sorting these out requires pre-execution checks at the edge. Starting with API calls defines the problem for organizations well and is measurable.
@cc_crowley is correct: the problem becomes harder when an agent works across companies - or across any boundary, as we see daily. Controls haven't caught up.
That's not something that companies can be expected to solve on a case-by-case basis.
That's friction that should be alleviated by infrastructure. That's the opportunity.
The most important take-away, for me, was:
"who owns the work-around"?
How much would they pay?
Who else has concluded that this is an infrastructure problem? One that requires shared state on authority across payment rails, chains, and applications?
I'd like to speak with them.
Has your email been down for days?
You can still send a message through Geeq. ❤️
Let someone know you're thinking about them.
ignite.geeqsearch.io
Golden retweeted
Exactly this. Knowing who an AI agent is isn't the same as knowing what it's authorized to do. And a mandate is only useful if it can be enforced at the moment of action.
TrustLogic is building that missing layer: assets and payments that can carry and enforce their rules.
Who's really behind the login? AI agents are forcing a rethink techradar.com/pro/whos-reall…
Golden retweeted
Completely agree with this analysis. A payment without verifiable control is a massive liability for any enterprise.
This is exactly why we have to secure the execution edge. The x402 protocol provides that cryptographic receipt at T=0, and seeing how this could plug into @ComplicatedIsOK's Settlement Infrastructure is incredibly exciting. It feels like the key to giving merchants total control.
Golden retweeted
A hardware wallet is one chip you trust blindly. Tamper with the supply chain and the seed was never yours.
The fix isn't a better box. Split the key so no single device ever holds all of it.
Why is self-custody still sold as a single point of failure? nitter.cf/Cointelegraph/status/2…
🇦🇪 LATEST: Ledger’s hardware tampering saga has spread to Dubai, where two owners report losing $604,000 in crypto from wallets they say they bought at an authorized Virgin Megastore.
ct.com/news/ledger-hardware-…
Golden retweeted
Highly relevant, @GoldenGeeq.
The immediate operational aftermath gets all the attention.
I hope they get their records back.
I hope the records are unaltered and current.
I hope the can detect any anomalies.
However, legal and risk management may not be comfortable with putting too much stock on hope.
Let us help. Evidence rails can speed up the effort and remove some uncertainty. They certainly can't hurt.
Golden retweeted
Right now, accepting automated agent traffic without verifying cryptographic intent is like handing over a rental car without checking a driver's license.
If a misconfigured bot goes rogue, the merchant absorbs 100% of the liability. We have to secure the execution edge before agentic commerce can truly scale.
Golden retweeted
Current systems make you highly dependent on a few cloud providers for both availability and the trustworthiness of your records.
Evidence Rails reduce that single-point dependency by making key proofs independently checkable and portable.
Relevant?
@syrupsid @joe_defi @maplefinance
@carlosdomingo @Securitize
@DeutscheBank
@ComplicatedIsOK
Cloud services have had a bad week. It could get worse.
Restoring cloud services won't necessarily restore confidence in your records.
Can you independently verify the evidence behind a payment, approval, or report?
We build evidence rails to preserve proofs, so you are not purely dependent on your cloud provider.
























