Pinned Tweet
One design, six chains. We're building downside protection wherever people invest.
Holders keep the upside. Paid providers carry the downside, with the backing reserved on-chain before anyone commits.
What each testnet adds 🧵
On @BNBCHAIN testnet: claim free test tokens, trade them, then protect them through a synthetic price shock and see exactly who absorbs the loss.
No real money involved:
bnb.yieldshield.ai
YieldShield is live on @FlareNetworks Coston2 testnet ☀️
Protect test FLR against a fixed backing claim, valued at entry by FTSOv2, the oracle built into Flare, and reserved at 150% by separate providers.
Valueless test tokens, open source:
flare.yieldshield.ai
One testnet position, start to finish:
1. Protect 0.1 AVAX at 25 → backing claim of 2.5
2. Price hits 35 → exit half as AVAX, paying 12% of its gain
3. Exit the rest to the backing → 1.25, whatever AVAX does next
Synthetic test price, all on-chain:
github.com/YieldShield/yield…
Flare Coston2: a built-in oracle.
FLR markets priced by FTSOv2, the price feed Flare provides at the protocol level. Our newest testnet.
flare.yieldshield.ai
Why so many chains? People invest across all of them, and the risk follows them. AI-assisted development lets a small team build natively on each.
Test tokens only, unaudited. Tell us where you invest 👇
yieldshield.ai/testnets
Tokenized stocks sold off this weekend while Wall Street was closed.
24/7 markets mean 24/7 downside. So who carries the drop until Monday?
On Base Sepolia we're testing one answer: a fixed backing claim per position, reserved on-chain by paid providers. Test tokens only.
Every protected position has two sides.
Holders keep the asset and its upside, minus a share of gains.
Providers supply first-loss backing, earn those fees, and take the loss if a holder exits to the backing after a drop.
Both see the same on-chain reserves.
A design choice that matters:
On Avalanche Fuji, protection uses Chainlink AVAX/USD. If that price is stale (20+ min old) or the round is incomplete, the contract rejects it. No fallback to a guessed price.
Backing exits don't need a price at all: your claim is fixed at entry.
YieldShield now runs natively on @StellarOrg Soroban ✨
Protect vault receipts with first-loss backing reserved on-chain. Two exits: keep the receipts and share part of the gain, or take the fixed backing.
Testnet demo, MIT-licensed code:
stellar.yieldshield.ai
Before you protect anything, the market shows its terms:
• Backing reserved at 150% of your claim
• Fees only on gains: 10% providers, 1% creator, 1% protocol
• A fixed maturity. Exit before it to keep your upside
Live on Avalanche Fuji testnet 👇
avalanche.yieldshield.ai
Yield-bearing assets like staked ETH, savings stablecoins and vault shares pay you to hold them. But that yield comes with risks most holders never price in.
Why protection belongs next to yield 🧵
It isn't free insurance:
• Cover is limited to the backing actually reserved
• Positions run for a fixed term
• You give up part of your gains
In return, you can see your downside on-chain before you commit.
We're testing this on five testnets (Base, Monad, BNB, Avalanche, Stellar) with valueless tokens. It's unaudited, so feedback is the point.
Try protecting and exiting a position, then tell us what was unclear 👇
avalanche.yieldshield.ai







