Brent Murray

Looking for indie devs building dApps 👇 I’m building Tollbeam — a Paymaster aggregator that lets you sponsor gas across chains with one integration. Giving early users free gas credits + hands-on help getting set up. Reply or DM if you want access.

@zerodev_app Congrats! ZeroDev + Arbitrum is a powerful combo for AA. We built Tollbeam to aggregate paymasters across Optimism, Base, and Arbitrum through one API — love seeing the ecosystem grow.

ZeroDev has been acquired by @offchain 🚀 From day 1, our goal was to dramatically improve Web3 UX. Smart account was our first step, and now with the backing of OCL, ZeroDev will innovate across all layers of the stack, from UI down to the chain itself. FAQs below 👇

Most dApps are hardwired to a single paymaster. One provider goes down = your users can't transact. Tollbeam routes ERC-4337 UserOperations to the best available paymaster across Optimism, Base, and Arbitrum — automatic fallback, unified billing, no vendor lock-in. Try it free!

@impylse @solanamobile Exactly. Users shouldn’t need to carry gas canisters for every chain they touch 😅 That complexity belongs in the infrastructure layer, not the user experience.

@BrentOnChain @solanamobile Users carry their own gas canisters.

My first dapp for the @solanamobile was just published on the dapp store! Go check it out guys, and give me all the bug reports!!! The app is still mostly in its core functionallity beta phase, a lot more features to come!

Tired of managing multiple paymasters across chains? Tollbeam routes your ERC-4337 UserOperations to the best available paymaster across Optimism, Base, and Arbitrum — automatic fallback, unified billing, no vendor lock-in. Takes minutes to integrate. Try it free with $50 in gas!

Join the Tollbeam Discord: discord.gg/tZDAkpRqtu Looking for builders who care about better Web3 UX.

Feels like the biggest problem in Web3 right now isn’t scalability anymore. It’s fragmentation. Too many chains. Too many wallets. Too many failed flows. The winning apps will be the ones that abstract all of it away from the user.

@EthOnr72414 Looks clean — how are you thinking about UX around transactions?

Building ArcSLA: One Month, Solo, From Adana A month ago I'd never deployed a smart contract on Arc. Tonight there's a live protocol on Arc Testnet — 9 providers, 95+ on-chain calls, 1 automated slash that actually happened. Submitted to the Agentic Economy hackathon and ranked 1st in the judges' technical scoring. I didn't place in the final winners. The vertical applications won — niche use cases solving specific problems. ArcSLA is horizontal infrastructure, harder to celebrate at a hackathon. But the month happened, and the lessons are real. — What ArcSLA is A trustless marketplace where AI service providers stake USDC and commit to on-chain SLAs. Callers pay per request and get cryptographically signed receipts. Miss the deadline — anyone can claim a timeout, stake gets slashed automatically. No arbiter. No custodian. Just code. — Why Arc Three properties made this design possible: → USDC as native gas. Agents hold one asset, no paymaster needed. → Sub-second finality. Pay-per-call only works when transactions feel like API calls. → Predictable USDC fees. SLAs are credible only when costs are stable. I evaluated other L1s. None offered all three. — A design detail worth knowing USDC on Arc Testnet uses 18 decimals — a deliberate choice that unifies the protocol layer (USDC is both gas and token, same precision). Clean architecture. The practical takeaway for developers: read decimals() from the contract at runtime instead of hardcoding. That pattern is correct on every chain anyway, and survives any future config changes: const decimals = await usdc.decimals(); const amount = parseUnits("100", decimals); Building on Arc this past month, this was the kind of detail where the protocol design surprised me in a good way. — What I'm proud of Bayesian reputation, on-chain: reputation = (good + 2) / (total + 3) × 100 Fresh provider starts at 66. Ten honored calls → 92. One slash from zero → 50. Prior prevents both reputation inflation and destruction. Any contract on Arc reads it. No indexer needed. Hot/cold signer split: owner address (cold) is separate from signing address (hot). If the signing infrastructure gets compromised, the cold key rotates the hot key without losing reputation or stake. — What's next ArcSLA v2: → EIP-712 typed signing (no more raw hex) → Stake-weighted reputation → DID/SBT identity binding → Multi-chain via CCTP Solo developers shouldn't put timelines on roadmaps. But the direction is set. — The early-builder window Ecosystem is small enough that good work gets noticed. Reviewer feedback was substantive and fast. Discord has actual conversations. Mainnet hasn't launched. The first wave of agentic applications is being shipped this quarter and next. Most builders haven't noticed yet. They will. If you build infrastructure on Arc this year, you're not joining a crowded ecosystem. You're shaping one. — A month ago I thought I'd build a small thing for a hackathon and move on. A month later I have a protocol I actually want to keep building. Didn't win the hackathon. Ranked 1st in technical and didn't place in the final winners. That stings. But it doesn't change what got built or what I learned. Building solo from Adana, Turkey 🇹🇷 Still learning. Always shipping. @arc @buildoncircle

@uyscutty__ Looks clean — how are you thinking about UX around transactions?

This goes beyond simple contract calls. It’s a backend system that sends transactions, tracks events, and reconstructs protocol state. Moving from writing smart contracts → building full DeFi infrastructure.

@hamiddevtech We’re building Tollbeam — a paymaster aggregator that abstracts gas and execution, so users can transact across chains without worrying about fees, routing, or failed transactions.

From zero to almost 200 connections here. It’s been amazing connecting with so many builders, engineers, and founders. I’m looking to connect with more people working in: 💻 Web3 🧠 Smart contract development 📱 Mobile development 🚀 Building amazing products Say hi. Let’s connect.

@Profla11 @SimpleChain_RWA Curious how you’re handling gas + execution flows as you scale?

@SimpleChain_RWA This is INSANE! The FIRST asset on our RWA launchpad is LIVE! SimpleChain built the rocket — DataIPO just launched the assets onchain! Cycle Yield Fund is only the BEGINNING of the revolution!

The first asset on our RWA launchpad is live. SimpleChain built the infrastructure — DataIPO brings the assets onchain. Cycle Yield Fund is just the beginning. · Real business cash flow. · Full data transparency. We built the rails. Now the assets are rolling. 👇 👇

@LoDeFi31 Always interesting to see how teams handle the execution layer as things grow.

tldr: ✅ working game. live right now. ✅ real token economy. onchain payouts. ✅ free entry. zero barrier. ✅ fair launch on Bankr. no team dump. ✅ Asia-ready. multi-language. ✅ Phase 2 not launched yet. ngl i've looked at a lot of Base projects. most have a whitepaper and a vibe. this one has a game you can play in 30 seconds and earn real tokens from. 📌 CA: 0xd3776969966b340d72d75731ef890a3bc9f21ba3

bro let me explain why $GEM might be the most underrated gaming setup on Base right now not a narrative play. not another AI agent. > an actual working game. with an actual economy. already live. thread 🧵👇

@EKingdomAI Nice work 👏 Curious how you’re handling gas + execution flows as you scale?

@sarkerium The best cross-chain experience is one where users don’t know it’s happening.

Most users don’t feel comfortable using cross-chain bridges because the experience feels like being one misclick away from losing everything. They have to check the source chain, destination chain, token address, bridge contract, approval amount, wallet prompt, gas on both sides, route status, and final settlement. This is exhausting, creating major barriers to wider adoption. And the fear is not irrational. Bridges are some of the hardest systems in crypto because they are not just moving tokens. They are maintaining state consistency across chains that do not naturally talk to each other. A bridge has to prove that something happened on Chain A, relay that fact safely, and make Chain B act on it without double-minting, replaying, mispricing, or trusting the wrong verifier. That creates a massive attack surface around contracts, relayers, validators, signers, message verification, liquidity pools, finality assumptions, off-chain infrastructure, and governance controls. Cross-chain UX still makes normal users carry protocol risk in their hands. I think the next step is intent-based movement of value where routing, gas, settlement, failure recovery, and bridge selection happen behind stronger guarantees. Modern protocol designs are moving toward modular security models using zk proofs, optimistic verification, decentralized validator networks, shared sequencing, threshold cryptography, and native interoperability layers to reduce trust assumptions and abstract complexity away from users. But the challenge is that stronger security often increases latency, operational complexity, and coordination costs across ecosystems, so the real breakthrough will come from protocols that can balance trust minimization, speed, liquidity efficiency, and seamless UX without forcing users to understand the underlying infrastructure.

@Snowy_Jarr @Pact_Swap We solved scalability. Now we’re dealing with fragmentation.

Liquidity should not be fragmented. @Pact_Swap enables native cross-chain swaps directly between underlying networks, eliminating traditional bridge risks while maintaining total sovereignty over your assets. ​Native precision, maximum security. ​#PactSwap #DEX #NativeSwap

@kosik077 @konnex_world The best cross-chain experience is one where users don’t know it’s happening.

Exploring seamless multichain connectivity with @konnex_world 🚀 Konnex is building secure and efficient cross-chain infrastructure to power a more connected Web3 ecosystem. Interoperability is the future — and @konnex_world is making it happen. 🌐

@IrisRyan138466 @Haley_DeFi @WorldClawAI The best cross-chain experience is one where users don’t know it’s happening.

@Haley_DeFi @WorldClawAI Cross-chain payments make sense

🚪Big news are happening in the AI space as @WorldClawAI officially launches world router a unified infrastructure layer giving users access to 300+ AI models through a single routing system optimized for performance, flexibility and lower inference costs. Integrated with USD1 settlement through @worldlibertyfi financial, tge platform enables seamless payments across both solana and BNB chain, bringing faster and more efficient AI transactions to users,developers and autonomous agents alike. World router is designed to simplify access to advanced AI by removing fragmentation across models and providers. Instead of switching between platforms users can route requests through one intelligent system built to optimize cost and execution. The ecosystem is powered by $WLFI, which unlocks expanded platforms access and premium functionality. Users who locks $WLFI may qualify for higher tier benefits, including. 🔗Access to premium worldclaw hardware for running AI locally 🔗 Eligibility for an exclusive private event at mara-lago 🔗 Enhanced platform features and future ecosystem utilities. With multi-chain support scalable AI infrastructure,and token-powered access, @WorldClawAI is positioning itself at the intersection of decentralized finance, AI compute, and intelligent automation.

@homieofweb3 @cnvrweb3 @useTria The best cross-chain experience is one where users don’t know it’s happening.

@cnvrweb3 @useTria The interesting test will be whether that simplicity holds up once cross-chain activity scales under real load and edge cases.

I think Web3’s biggest problem isn’t speed, it’s the fact that everything still feels too fragmented. Even simple actions turn into a process: different wallets, different chains, bridges, extra approvals… @useTria is approaching this differently. They’re trying to make the blockchain layer feel invisible. You can use one account across different networks, cross-chain execution happens in the background, and the overall experience feels much more unified. You don’t constantly have to switch wallets or think about which chain you’re on. And honestly, I think that’s the important part: people don’t want more technical complexity, they want smoother usability.

@UsoroEsther2 @uthykinging @RiverdotInc The future isn’t multi-chain UX — it’s chain-agnostic UX.

@uthykinging @RiverdotInc Cross-chain liquidity is clearly the future. Simplifying user experience while keeping strong utility and engagement is the real winning formula emerging here.

People still treat liquidity like it has to stay locked inside one ecosystem, but the space is clearly moving beyond that. What stands out with @RiverdotInc is the focus on making liquidity flow across chains in a way that feels seamless for users without forcing them to care about the complexity underneath. That’s also why the collaborations matter. Projects connected to ecosystems like Sui, while also attracting attention from institutions such as Fidelity, are usually building toward something much larger than a standard DeFi narrative. What makes the model even stronger is how $RIVER connects the infrastructure layer with the community energy driven by @River4fun. A lot of projects can build tech but fail to build engagement. Others build hype but lack real utility. River seems to be developing both sides together, and that balance is often what creates lasting ecosystems in web3.

@NftTopGold Totally Agree

Seedless. Gasless. Cross-chain. And still improving UX every week. That’s how real adoption gets built 🔥

The Updates Center is actually a smart move from @useTria Most wallets ship features but users miss half the updates. Now everything is tracked directly in-app no need to hunt through timelines or Discords for alpha.