Fede Blockchain 🇦🇷

The Protocol Roundtable, Ep. 7: When Autonomous AI Agents Go Onchain xitter.cf/i/broadcasts/1PKqrNval…

Hola Madrid! 🇪🇸 Our Head of Growth, Ale Losa, is at @mmerge_io Madrid until tomorrow to talk about the infrastructure behind institutional onchain finance: stablecoins, tokenization and payments. If you’re a bank, CASP, fintech or asset manager in town and want to compare notes on building and running these systems, get in touch.

"Be comfortable that things will break." Emma Landriault on what production on public chains asks of a bank: teams ready to fix what goes wrong, and monitoring for risks they aren't used to watching. Blueprint BP-18 maps out that response under DORA: protofire.io/blueprints/risk…

Protocol Roundtable Ep. 6: Stablecoins Go Mainstream xitter.cf/i/broadcasts/1qJDzWqOZ…

Protofire turns 10 this year. 10 years, built together. A look back at some of the partners, protocols, and ecosystems we’ve helped build with since 2016. Grateful to everyone who has trusted us to build meaningful infrastructure.

What turns an onchain finance pilot into dependable market infrastructure? Episode 5 of The Protocol Roundtable brings together: - Emma Laundriault, Global Head of Kinexys Labs and JPM Coin, J.P. Morgan Payments - Martin Quensel, Co-Founder of @centrifuge and Founder of @anemoycapital - Ryan Zega, Head of Structured Finance at @AptosLabs - Rado Patus, Lead Product Manager at @protofire Hosted by Andrei Yurkevich, Co-Founder of Protofire. 📅 1 Oct ⏰ 1 PM UTC 📍 Live on X, LinkedIn and YouTube

TradFi is moving onchain. But who’s actually building the systems it will run on? Protocol Roundtable, Episode 4: TradFi Goes Onchain With leaders from @Circle, @0xPolygon, @ADI_Foundation, and @Protofire. Friday, Sept 18 · 1 PM UTC

The Protofire team will be in Warsaw on September 9–10, and we’re opening a few slots for B2B meetings while we’re in town. If you’re a bank, CASP, asset manager, fintech, Web3 protocol, or infrastructure team building around DeFi, tokenization, RWA, stablecoins, or onchain finance more broadly, we'd like to hear what you're working on. We're setting aside 30-minute architecture fit meetings: what you're building, where the technical and infrastructure pressure actually sits, and whether Protofire is the right partner to design, build, or run the systems behind it. We've delivered 250+ projects since 2016, so most of these conversations start from something we've already shipped. In Warsaw on September 9–10? Send us a message to set up a meeting.

A prediction market lives or dies on the quiet weeks between events. Volume shows up for an election or a title fight, then the book thins out and the next visitor finds a market with nothing moving. Marketing spend does not fix that. Baseline activity between events is an engineering problem, and it lives in the infrastructure. By some counts, more than a third of Polymarket wallets are now run by autonomous agents. The category has already worked out how the quiet weeks get filled. The open question for every other venue is whether that activity runs on a layer the operator actually controls. Protofire has built that layer. The operator keeps authority over it, and every action stays on the record for a compliance review. The mechanics stay off this post on purpose. What are prediction-market teams doing today to keep a book alive between the big events?

Every mechanism you ship becomes something you have to run. The contract goes live, liquidity arrives, and from that point the question is no longer whether the design is elegant. It is who answers when something moves against you at 3am. Diego Torres, our Field CTO, made a design point: "Keep it simple before you make it powerful. Over-engineering incentives too early means expensive audits, more attack vectors, and a confusing user experience." The phrase worth sitting with is "more attack vectors." Simplicity lowers the operational burden of what you ship. It never lowers it to zero. Validators, RPC, indexers, oracle feeds, keepers, liquidation bots: each is a surface that stays live long after launch, with no rollback on a bad upgrade and counterparties actively looking for the gap. Detection tooling tells you something is wrong. That is where the work starts. The harder question is operational: who is authorized to act, and in what order, before the incident widens. That authority needs to be agreed in advance, and the team owning the product keeps the funds and the regulatory perimeter throughout. This is the layer we spend most of our time on at Protofire. Launch is day one.

"Tokenizing an illiquid asset doesn't suddenly create demand for it." @alanchiu breaks down why tokenization strategy has to be asset-specific — not one-size-fits-all. From our Protocol Roundtable - Episode 2 👇

Less than an hour to go till we hit the stage in Miami ⌛️ Two conversations on the table: ​RWA Yield vs Liquidity vs Maturity — the tradeoffs that define how tokenized credit instruments actually perform on-chain. ​Allocating To & Deals From Emerging vs. Established Issuers — where the real risk-adjusted opportunity sits, and what due diligence looks like when the issuer landscape is still taking shape. ​Private credit fund managers, DeFi protocol teams, institutional LPs, one room. ​See you soon.

Trillions in assets on-chain. Secondary markets that wouldn't fill a kiddie pool. We sat down with @pharos_network , @centrifuge , @bobanetwork , @base, and @DIAdata_org to unpack the RWA liquidity crisis and what the industry has to build in the next 24 months to fix it. We gathered our takeaways and recap in our latest blog post 👇

Safe Wallet is now live on @LitVM’s LiteForge Testnet. @dewpointlabs, our R&D unit, handled the deployment. Contracts verified. Infrastructure ready. Testnet is open. Mainnet follows in mid-2026!

1/ Latest situation on @aave: $169M in liquidity on @BNBCHAIN. Most of it sitting idle or underpaid: $151M in BTC and BNB combined, producing nothing. Same-chain way to push it to 10–15% APY 🧵