Branch

6.4K posts

Branch banner
Branch

Branch

@BranchM

dev @dexteraisol | branchm.sol

Miami, FL Katılım Mayıs 2024
1.1K Takip Edilen2.7K Takipçiler
Branch
Branch@BranchM·
@fomich @mert This is breaking news and I’ll be its biggest proponent! 📰
English
0
0
3
15
fomich
fomich@fomich·
@BranchM @mert seems like i misunderstood what you meant initially just meant that the lack of it should not hold you back from using helius products anyway, as mert said, we’re adding x402 support
English
1
0
2
24
mert
mert@mert·
we've accelerated the adoption of freezable surveillance coins, replaced existing middlemen with new middlemen, and ensured suits control all the supply and you wonder why crypto doesn't feel exciting td private money and exotic derivatives are your salvation
English
75
28
300
12.5K
Branch
Branch@BranchM·
@mert @fomich ‼️ Great! This was just an experiment, I’m sure your engineers 100x further along, but it’s fascinating what can be done with x402 and RPCs. I only push for it so hard because I think there’s such opportunity: dexter.cash/rpc
English
0
0
4
33
mert
mert@mert·
@BranchM @fomich nah, we're adding x402 but yeah fomich's point is that workarounds for agents exist atm as well
English
2
0
5
111
Branch
Branch@BranchM·
@fomich @mert I use both daily. Well, they’re there, anyway. But at this point, I am just gonna assume that Helius is hostile towards x402 because the thinking internally is, e.g., my pay-per-use bill wouldn’t amount to the full $1500/month I pay now, and that’s fair.
English
2
0
2
72
fomich
fomich@fomich·
@BranchM @mert it can pay right now without x402 your reply just shows that you haven’t tried helius-cli or helius-mcp
English
1
0
1
53
vibhu
vibhu@vibhu·
We are playing for @Solana to win in AI: - Commerce & Payments - DevEx - Moonshots Solana facilitated 15 million agentic payments so far in 2026 - nearly 65%.
English
45
24
259
10.9K
Branch
Branch@BranchM·
@fomich @mert For my agent to be able to pay for your service?
English
1
0
1
37
Branch
Branch@BranchM·
@mert not via x402 😢
English
1
0
0
102
mert
mert@mert·
@BranchM they can already do that brother
English
2
0
1
428
Branch
Branch@BranchM·
@Shoalresearch Extremely well written. The only part we’d contend with is the x402 discovery disadvantage, but a small part of a fantastic article
English
0
0
3
41
Branch retweetledi
Dexter AI
Dexter AI@dexteraisol·
See you at SuperPay tomorrow in Miami!
Superteam USA@SuperteamUSA

🇺🇸 Superteam USA presents: The Future of Agentic Payments Thursday March 26th 4-8pm We’re bringing together builders, operators, and innovators next Thursday for an evening of workshops, panels, and networking surrounding the rise future of agentic payments. 🗓 Run of Show: • 4–5pm: @ZoComputer Workshop • 5–5:30pm: Welcome Reception • 5:30–6pm: Panel Discussion (ft. representation from Zo Computer, OKX, Moonpay, and Solana Foundation) • 6–6:20pm: @Vibhu Keynote • 6:20–8pm: Networking + food by Fradiavolo’s Join us: luma.com/g4egnwsq See you in Miami 🇺🇸

English
2
10
36
941
Rahul Kulkarni (🔴, 💊)
just shipped @moonpay's ows-react-native the first react native library with open wallet standard-compatible architecture and @stripe x402 machine payments integration on solana. as a mobile developer since day one i noticed there was no official support for open wallet standard or agentic payments on react native. so i built it. the library lets you build ai agents that autonomously pay 402 protected apis using solana usdc with strict policy controls: max spend per transaction daily limits recipient allowlists and biometric approval for spends above 0.50 dollars. private keys never touch the react native app. all signing and policy checks happen securely on the backend. install with bun i ows-react-native github: github.com/rkmonarch/ows-… if you are building mobile ai agents or autonomous payments this is your stack. the x402 flow is simple: agent hits api gets 402 challenge library parses it checks policy backend signs usdc on solana and returns the transaction signature all via one hook pay mpp challenge.
English
12
7
60
4.1K
Lucas
Lucas@OnchainLu·
update: adjusted sellers on @mpp is ~50, not 2.3k i've added some more filters on the MPP sellers metric to match the exact filters we have on x402 (methodology in screenshot) disclaimer: like i've said abt x402, i wouldn't assume this is gaming w bad intentions -- it could easily be test endpoints
Lucas tweet mediaLucas tweet media
Lucas@OnchainLu

it took ~5 months for x402 to reach 2.3k sellers @mpp reached 2.3k sellers in 5 days

English
15
7
82
12.3K
alon
alon@a1lon9·
@theonomix mommy (dev) and daddy (holders) are no longer arguing because mommy can no longer take daddy's credit card to buy herself a new purse after promising daddy she was going to do something nice with the money
English
146
38
557
31.2K
alon
alon@a1lon9·
Vamping & griefing are some of the biggest pain points of recent times Although it's impossible to solve 100% of this behavior at the blockchain layer, we can still try to mitigate where we can Today’s update is a small step in that direction. Here’s how it works 👇
English
1.2K
254
2.7K
427.7K
Branch retweetledi
Dexter AI
Dexter AI@dexteraisol·
🟧🎙️ Join today at 2 PM EST for a special x402sday for Dexter AI as we introduce ourselves to a new audience in our first space since being named a @Pumpfun Hackathon winner. x.com/i/spaces/1dgyl…
English
2
13
43
2K
Alex
Alex@0xDaedalus·
MPP Sessions are the killer feature that meaningfully differentiates @tempo's MPP from @coinbase's x402. An MPP session is a state channel: lock funds in escrow, stream authorized payments off-chain, settle on-chain at the end. A voucher is the off-chain primitive that makes it work i.e. a cryptographically signed message that says "I authorize X total so far," submitted with each unit of service consumed. Here's a simplified mental model: Imagine you're getting a coffee. Instead of paying per sip, you hand the barista $20 upfront and they hold it in a lockbox. You sip. After each sip, you hand them a signed note that says "I've consumed $0.20 total so far." At the end, they take what the last note says and give you change from the lockbox. That's a session. That's a voucher. Except the lockbox is a smart contract. The "change guarantee" isn't social trust — it's cryptographic. The barista literally cannot take more than your last signed note authorized, because that note is enforceable on-chain. And settlement takes 0.6 seconds, not a banking day. Now think about why this matters for agents. AI agents don't pay per conversation. They pay per token, per API call, per tool invocation - potentially thousands of micropayments per task. Charging a card for each one is like paying per sip. Technically possible. Economically broken. Transaction fees would dwarf the actual payment value at any meaningful scale. The "pre-deposit and stream vouchers" model is the only unit economics that work at machine speed. You pay the one-time cost of opening the channel — one on-chain transaction. Then every interaction in the session is a signed message - no gas, no latency, no waiting for block confirmation. The math changes entirely. What makes this more than a clever hack: the escrow is non-custodial. The service provider never holds your funds. The smart contract enforces the rules. The payer always recovers unspent deposit at session close. The trust model is the protocol, not a counterparty. For agentic systems operating at scale, it seems like MPP has the payment primitives that actually fit the workload. Super excited to follow-along and see what industry adoption looks like in the coming months.
English
23
8
125
13.8K