Cross-chain payments are interesting. Cross-chain actions that settle real financial obligations are even more interesting.
That's what we're exploring with @clearline_usdc on @0xReactive Omni.
One reactive contract. Two chains. No off-chain orchestration.
Let's see how far we can push this. ⚡
Introducing Clearline, our entry to the @0xReactive Omni Buildathon.
USDC between Base and Unichain in about two(2) seconds, with one reactive contract in between and nothing off-chain.
The same two(2) seconds can save a loan: money on one chain repays a loan on another
Jerry Musaga retweeted
Introducing Clearline, our entry to the @0xReactive Omni Buildathon.
USDC between Base and Unichain in about two(2) seconds, with one reactive contract in between and nothing off-chain.
The same two(2) seconds can save a loan: money on one chain repays a loan on another
On @HyperliquidX , your position and liquidation risk can be publicly observed.
@RipcordOnNear gives traders a private defence: a hidden reserve, secured on NEAR, that automatically reaches their margin before liquidation.
Live on mainnet: margin funded, rescue executed in 26 seconds
Built at NEAR HACKATHON @NEARProtocol #NEARHackathon
@NearLegion @NearBuilders
🧵
2
5
267
Who watches the guards?
Anyone can run a Ripcord keeper.
Keepers monitor active guards without seeing their private trigger levels.
When a keeper's check fires a rescue, it earns a bounty on the keeper market (live on NEAR testnet, mainnet next)
An open network protecting positions without exposing the strategies behind them.
1
9
Your liquidation risk shouldn't be public.
Your defence shouldn't be either.
Every rescue leaves an onchain record on NEAR, using hashes rather than exposing your trading address.
github.com/Musaga-Technology…
Traders: how much of your liquidation defence would you trust to an autonomous system?
5
Jerry Musaga retweeted
New to Flare or need a quick refresher?
The Flare Explainers playlist covers FXRP, FAssets, enshrined oracles, rewards, and why Flare is built for data, all through short videos that get straight to the point.
youtube.com/watch?v=NPIL1LDk…
Jerry Musaga retweeted
A useful piece of Flare infrastructure to understand is the Flare Systems Protocol (FSP).
FTSO and FDC rely on FSP for a shared coordination and finalization layer.
Data providers independently compute protocol results and sign candidate Merkle roots. Once signatures representing more than 50% of the active voting weight agree, the result can be finalized through the Relay contract.
That finalized root can then be used by smart contracts to verify individual pieces of data with a Merkle proof.
FSP also coordinates signing policies, validator uptime voting, reward calculation and network randomness.
So when you use an FTSO price or verify FDC data, there is a broader protocol running underneath to coordinate who participates, how much weight they have, how results reach consensus, and how they become verifiable onchain.
Worth understanding if you’re building deeper into the Flare stack. 🧑💻
Jerry Musaga retweeted
It's a great Sunday to build on @FlareNetworks☀️
Jerry Musaga retweeted
I’d recommend keeping an eye on these builders.
Some are already making real progress, and there’s a lot we can do as an ecosystem to help them grow!
I want to make sure I’m seeing all the active projects coming out of Flare Summer Signal.
Sometimes people tag me and X simply doesn’t surface the notification.
If you’re still building and want more visibility, drop your project below. And if there’s a project you think deserves more attention, feel free to shout it out too. 🙏
Jerry Musaga retweeted
What the Flare Confidential Compute TEE keypair actually is:
Public key — publish. Verify, or encrypt to the machine. That is the TEE id.
Private key — generated at boot, stays in the enclave. Sign and decrypt. If it leaks, anyone can impersonate the machine.
ECDSA stamps (does not hide). ECIES locks (hides).
More on docs: dev.flare.network/fcc/overvi…
Jerry Musaga retweeted
Flare Systems Deployment v1.7.0 is out.
If you run the stack, there’s no urgent upgrade deadline, but a couple of things are worth knowing before you update:
• The C-chain indexer now starts much faster and keeps a shorter rolling history.
• Run ./populate_config.sh after upgrading, as the indexer configuration changed.
• Don’t delete the old Docker volumes during the upgrade if you want to preserve your rollback path.
• If you run FDC2 verifiers on Songbird, keep using the dedicated indexer from fdc-suite-deployment.
Release:
github.com/flare-foundation/…
Changelog:
github.com/flare-foundation/…
Jerry Musaga retweeted
In the last Flare Builders workshop, we explored how to build paid AI APIs with x402 & Flare Confidential Compute.
We explored how to combine:
💳 x402 for API payments
🔐 Flare Confidential Compute for secure execution
🤖 AI APIs and agents
Thanks to everyone who joined and built along with us!
Here is a small recap video of the materials, and the code is here: github.com/flare-foundation/…
Flare Builder Online Workshops - Session 23: Building Paid AI APIs with x402 & Flare Confidential Compute xitter.gq/i/broadcasts/1jxXgBajE…
Jerry Musaga retweeted
Flare Builder Online Workshops - Session 23: Building Paid AI APIs with x402 & Flare Confidential Compute xitter.gq/i/broadcasts/1jxXgBajE…
We live 🔥🔥
Flare Builder Online Workshops - Session 23: Building Paid AI APIs with x402 & Flare Confidential Compute xitter.gq/i/broadcasts/1jxXgBajE…
2
59
Jerry Musaga retweeted
⚡️ Next Flare workshop with @fassko tomorrow.
Hands-on: wire x402 payments into an AI API endpoint, run the sensitive bits (prompts, model logic, keys, private data) inside Flare Confidential Compute TEEs, and ship a complete flow that settles on Flare.












