Keyring Network

The reason RWAs haven't scaled yet? Settlement Risk Come find us this week in Cannes to discuss how we have solved the four major risks vectors: 1. Compliance Risk 2. Hack/ Exploit Risk 3. Governance Risk 4. Settlement Risk DM @huge_flood or @flipdazed for more info!

🚨 NEW: @flipdazed of @KeyringNetwork at Cointelegraph Connect: Cannes points to a core tension in DeFi. As soon as protocols resemble broker-dealers, regulatory pressure kicks in, making KYC far more complex.

Thanks! great explanation @TylerSherwin ! it's a bit more than this on the zk permissioning side - think if it like being able to do SSO with any website that has every KYCd you. We can get much of that aml/kyc decision result from them as part of the SSO that you can use to prove (to a dApp for example) that you have a legitimate check already done on you by a legitimate entity (and here is proof of that check). You can also share the information relating to that check to a degree that it is available to the user on their own browser session

@defyneric @KeyringNetwork User onboarding with portable KYC credentials. I liken it to an ecosystem of participants who’re willing to onboard a certain type of user. KYC once and gain access to subsequent platforms. At least that’s how I understood it from my conversations with the team.

whoever solves shared kyc across infra providers is going to make a lot of money right now, every time you add a new provider in your neobank stack, your users have to re kyc that’s a massive drop off point one unified kyc layer that can be reused across providers would remove a ton of friction whoever builds this is going to print

We did an atomic levered loop with @paretocredit , @centrifuge and @eulerfinance ✅ no external OTC liquidity ✅ async redemption ✅ async mint ✅ extendable to every DeFi protocol. Here's how the wind/unwind works: # WIND FLOW: opening a leveraged RWA position 💵 Stage 1: User funds the position The borrower deposits USDC equity and selects target leverage. That USDC transfers to the wind manager, not directly into the final RWA position. A per-request escrow is deployed to isolate this position from every other request, one escrow per request, no commingling. 🌉 Stage 2: Virtual collateral bridges the settlement gap The manager mints a pending settlement token (psToken) to the escrow. That token represents a confirmed dollar-denominated pending subscription and functions as virtual collateral during the settlement window. It bridges the gap between "capital has been committed" and "fund tokens have not arrived yet." 🏦 Stage 3: Temporary CDP opens on Euler The escrow deposits the psToken into a dedicated Euler vault as collateral. The escrow borrows USDC against that virtual collateral and sends the borrowed USDC back to the manager. This creates the temporary CDP: virtual collateral + real debt. 📦 Stage 4: Total capital enters the fund subscription path, fee is collected The manager now holds the borrower's original equity plus the newly borrowed USDC. The Keyring fee is excluded from the total sent to the fund. The total assets (minus fee) are sent through the Pareto adapter into the async subscription queue toward the RWA fund. The Keyring fee is then transferred to a separate fee collector. Multiple requests within the same epoch accumulate into a single batch. 📅 Stage 5: Issuer processes at NAV The fund administrator does not see or care about the psToken. The issuer processes subscriptions at the next NAV strike and determines how many real fund shares the subscribed capital buys. Standard off-chain fund logic, bridged back on-chain through the tokenisation layer. 🧾 Stage 6: Queue settles, shares are allocated Settlement runs opportunistically when users transact (new wind requests or finalisations) and can also be triggered directly via settleQueue. An off-chain operator ensures timely settlement when no user transactions occur. The adapter claims all tranche shares in one shot and streams them pro-rata across pending requests in FIFO order. At this point the request's share allocation is recorded, but the escrow still holds psToken as collateral. 🔁 Stage 7: Finalization swaps virtual collateral for real collateral A separate finalizeWind call is made by the operator. The escrow atomically swaps: psToken withdrawn and burned, real RWA collateral deposited into the Euler position. If any step fails, the entire transaction reverts. 🎯 Stage 8: Borrower holds the final leveraged position The completed CDP, now backed by real RWA collateral, transfers to the borrower's own Euler sub-account. What would normally require multiple looping transactions to build leverage happens in a single atomic action. The user holds the leveraged RWA position directly on the lending market. Wind TLDR - USDC equity to the manager - psToken minted to escrow - temporary CDP opened on Euler - borrowed USDC sent back to manager - total capital (minus fee) sent through Pareto into fund subscription - fee transferred to collector - issuer allocates fund tokens at NAV - queue settles, shares allocated to request - operator calls finalizeWind, psToken burns, real RWA collateral replaces it - final leveraged position transfers to borrower # UNWIND FLOW: closing a leveraged RWA position 🔒 Stage 1: User locks the existing position The borrower starts with a leveraged RWA CDP on Euler: real collateral (deACRDX) and USDC debt. They submit an unwind request. The system checks position health is below liquidation LTV minus a safety buffer. Positions already close to liquidation cannot enter the unwind flow. 🏦 Stage 2: Position moves into the unwind escrow A dedicated unwind escrow is deployed. Collateral shares transfer from the borrower's sub-account to the escrow first. Then the debt relationship is pulled into the escrow. The position is now isolated. 🪄 Stage 3: Virtual collateral replaces real collateral in one atomic step The manager mints psTokens to the escrow. In a single atomic batch, the escrow deposits psToken as Euler collateral and withdraws the real RWA collateral back to the manager. Same bridging logic as wind, running in reverse. The psToken keeps the Euler position healthy while the real asset enters the redemption queue. 📤 Stage 4: Real collateral enters the redemption path The manager sends the real RWA collateral through the Pareto adapter into the fund's redemption queue. The fund processes the redemption according to its normal notice period and dealing cycle. 🎟️ Stage 5: Receipt NFT is minted After all escrow setup, debt pulling, collateral swapping, and adapter submission is complete, the system mints an ERC-721 Receipt NFT to the borrower. An NFT because every exit has unique parameters: size, fee, and path. It tracks the request through its lifecycle. ⏳ Stage 6: Operator settles when proceeds are available Settlement liveness depends on an off-chain operator. When the fund settles and the adapter reports claimable assets, the operator calls settlement. The FIFO queue distributes proceeds in order: first request in gets settled first. Settlement correctness is enforced on-chain, but settlement liveness requires the operator call. 💸 Stage 7: Fees deducted, surplus distributed, debt repaid, virtual collateral removed The NFT holder or operator calls fulfilment. Fees are computed and paid first: Keyring fee to the fee recipient, adapter fee to the adapter's recipient. Any surplus after fees and debt is transferred to the borrower. The repay amount goes to the escrow. The escrow repays the Euler debt, withdraws psToken to the manager (which burns it), and transfers any remaining position to the caller's sub-account. 🚨 Stage 8: What happens if the escrow goes unhealthy during the wait The settlement window can last days to weeks. If debt accrues faster than psToken collateral can sustain, the escrow breaches Euler's liquidation LTV. A liquidation operator deploys a per-liquidation contract that executes Euler's native liquidation: seizes psToken collateral, settles debt, distributes surplus. The request is marked as liquidated and skipped during subsequent queue processing. Wind is configured to avoid this scenario. The unwind system includes a dedicated liquidation path for it. Unwind TLDR - health check passes - collateral to escrow, debt pulled in - psToken minted, real collateral swapped out atomically - real collateral sent through Pareto for redemption - Receipt NFT minted - issuer redeems at next settlement window - operator settles queue when proceeds arrive - fees deducted first - surplus transferred to borrower - escrow repays Euler debt, psToken burns - remaining position to caller's sub-account Why this is an innovation for RWAs The fund never sees the psToken. It settles subscriptions and redemptions the same way it always has. The psToken exists purely at the protocol layer. It keeps the Euler position collateralised while the real asset moves through the fund's settlement cycle. Virtual collateral that bridges DeFi's atomic execution with TradFi's async fund mechanics, then disappears. Winding in uses psTokens that are pegged 1:1 to the debt asset (USDC in this case), whereas unwinding uses psTokens that are pegged 1:1 to the RWA asset (pACRDX in this case). rwa [un]wind is coming.

@AlexKrasnow you're massive

This is massive.

1/ You're going to hear a lot about RWAs in 2026. Tokenised RWAs just crossed $26B on-chain, ($2 trillion still off-chain). But capital efficiency is broken, and until that's fixed, the market is stuck.

@KeyringNetwork just ran the first-ever levered loop of a non-atomically settled RWA on @eulerfinance without any external market marker or OTC liquidity, and using no additional capital. This is a huge step forwards for RWAs that do not settle atomically. Will share more shortly 😁

@Gideoomatic how it feels to finally close a trade in profit

The size of the cigar and badge is frying me LOOOOOOOOOL

@0xPhasma how much did polymarket pay you to post this?

found a wallet doing something illegal or at least it should be $731,964 balance trading every 0.3 seconds on 5-minute BTC markets +$2, +$8, +$15, +$22, +$5, +$11 non-stop the bot doesn't predict price movements it exploits order book imbalance microseconds before anyone else sees it 9ms latency via private RPC nodes scans 260k+ market feeds simultaneously finds 0.2-0.8¢ liquidity gaps and executes instantly while price bounces randomly, equity compounds mechanically no analysis, no sentiment, just surgical execution the wallet: @0x0eA574F3204C5c9C0cdEad90392ea0990F4D17e4?via=phasma" target="_blank" rel="nofollow noopener">polymarket.com/@0x0eA574F3204… printed $400+ in the time it took to write this humans physically can't compete with this speed

@RoundtableSpace has any of these claude gurus made any money besides selling courses on how to use claude?

OPENCLAW CAN NOW CREATE FULL ANIMATED VIDEOS WITH A SINGLE SKILL. PROMPT TO FINAL VIDEO WITH MUSIC IN 11 MINUTES - WORKS WITH CLAUDE CODE.

@AlgodTrading im still holding...

There will be a period this year when we look back and realise what a bunch of pussies we were by not bidding alts that were sold into the ground

@Cointelegraph housecoin coded

🚨 ALERT: Google searches for “can’t sell house” have reached an all-time high

@toly this post is cringe

We are going to go from — being cringe to — being based within 1 year.

@VitalikButerin plz stop selling

💛💙

Great article on RWA lending and how Keyring fits into the stack

@KeyringResearch Great read

@KeyringResearch top read