LI.FI Composer: One Transaction for Every DeFi Action
Bridge. Swap. Stake. Deposit. Five transactions compressed into one. Here is how LI.FI Composer works, what it enables, and why it changes what is buildable in DeFi.
LI.FI Composer: One Transaction for Every DeFi Action
Bridge. Swap. Stake. Deposit. Five transactions compressed into one. Here is how LI.FI Composer works, what it enables, and why it changes what is buildable in DeFi.
Salvage: recovering what the EVM left behind
A non-custodial protocol for tokens stranded in smart contracts — and a real recovery to prove it works.
Salvage: recovering what the EVM left behind
A non-custodial protocol for tokens stranded in smart contracts — and a real recovery to prove it works.
Jumper vs. The Competition: A Real Comparison of Cross-Chain Aggregators
Before comparing, get the categories right. Stargate and Across are bridges. Jumper, Socket, and Squid are aggregators. Different layers, different jobs. Here is how the aggregators actually stack up. One of the most common confusions in cross-chain DeFi is treating bridges and aggregators as if they are the same category. They are not. A bridge is the underlying protocol that moves assets between chains — Stargate, Across, Hop, Connext, Relay, CCTP. An aggregator is the routing layer that si...
Jumper vs. The Competition: A Real Comparison of Cross-Chain Aggregators
Before comparing, get the categories right. Stargate and Across are bridges. Jumper, Socket, and Squid are aggregators. Different layers, different jobs. Here is how the aggregators actually stack up. One of the most common confusions in cross-chain DeFi is treating bridges and aggregators as if they are the same category. They are not. A bridge is the underlying protocol that moves assets between chains — Stargate, Across, Hop, Connext, Relay, CCTP. An aggregator is the routing layer that si...
Week 4 on Arc — what the data reveals, and what we shipped to make the intelligence layer trustless
By Abu Olumi — Edition 3 of Building on Arc Six weeks ago, ArcSense launched on Arc Testnet with a simple premise: scan every block in real time, detect failing transactions, and sell that intelligence through a gated API. An autonomous agent would be the first customer. Every payment would be on-chain. Every decision would be logged. The numbers since then: 400,000+ blocks scanned, $500+ USDC spent autonomously by the agent, a peak failure rate of 8.9%, and three full data resets from Railwa...
Week 4 on Arc — what the data reveals, and what we shipped to make the intelligence layer trustless
By Abu Olumi — Edition 3 of Building on Arc Six weeks ago, ArcSense launched on Arc Testnet with a simple premise: scan every block in real time, detect failing transactions, and sell that intelligence through a gated API. An autonomous agent would be the first customer. Every payment would be on-chain. Every decision would be logged. The numbers since then: 400,000+ blocks scanned, $500+ USDC spent autonomously by the agent, a peak failure rate of 8.9%, and three full data resets from Railwa...
Solvers, Intents, and the OIF: How LI.FI Rebuilt Cross-Chain Execution
You describe the outcome. Solvers compete to deliver it. Here is how intent-based execution works, what LI.FI Intents is, and why the Open Intents Framework matters.
Solvers, Intents, and the OIF: How LI.FI Rebuilt Cross-Chain Execution
You describe the outcome. Solvers compete to deliver it. Here is how intent-based execution works, what LI.FI Intents is, and why the Open Intents Framework matters.
