Top web3 and AI developers delivering infra and apps on demand. Helping clients reach +$4B TVL
Distributed
Joined March 2019
- Tweets4.7K
- Following343
- Followers3.8K
- Likes6.5K
What happens after the trade?
A tokenized asset demo can make buying look simple. Then comes a split, redemption or distribution.
Your product needs to explain what the customer owns, what changed and which record is authoritative.
First Draft explores the lifecycle beyond the first trade, with an illustrative prototype.
Token rights depend on the issuer's terms. A token balance alone doesn't establish direct share ownership.
firstdraft.dorg.tech/edition…
A one-block reorg was enough because the deposit got credited before the re-check could confirm it was still on the canonical chain. Good on the solvency checker for halting swaps on its own
On October 31, THORChain halted trading on several blockchains.
An Ethereum block reorg caused THORChain to pay out 10 ETH that a vault never received. The automatic solvency checker caught the shortfall and halted ETH swaps. Within approximately two minutes, node operators halted ETH transaction signing, so no further ETH could leave the vaults.
Node operators then halted all chains as a precaution so core developers could investigate.
The 10 ETH has been returned by the user to make the vault solvent again.
Breakdown of what happened and next steps:
At 11:34 UTC Oct 31, Ethereum had a one-block reorg. A 10 ETH deposit to one of the vaults sat in the dropped block and never landed on the canonical chain.
THORChain had already observed and credited that deposit. The swap missed its price limit and was refunded, so the vault paid out 10 ETH it never received. The sender's real deposit was refunded as well.
Every node detected the reorg. But the re-check that should have removed the deposit could not get a clear answer in time, so it was finalized.
The solvency checker halted ETH swapping automatically, then three node votes halted all ETH outbound payments.
All chains were then halted by three node votes as a precaution. Now that this is public knowledge, every time there is a block re-org on an external chain, a malicious actor could perform a new transaction with the same nonce and would be paid funds by the THORChain vaults.
Note: Three node votes can trigger emergency halts to protect network solvency. However, that action can be reversed by four counter node votes, then five node votes can reverse the reversal, and so on, maintaining a balance between decentralization and rapid emergency intervention. Halting a chain does not give those nodes control of the assets.
Core developers have been working on the necessary fixes.
Nodes will decide to re-enable chains as they are deemed safe.
Trading blockchains: AVAX, BASE, RUNE, XRPL
Halted blockchains: ATOM, BCH, BSC, BTC, DOGE, ETH, LTC, SOL, TRON, ZEC
New chains will keep launching for a simple reason: for an institution coming onchain, launching its own chain is usually the best way to capture the value.
@ecdsafu from @squidrouter on why that makes connecting them the long-term problem.
Full episode👇
We ported @StarkWareLtd 's cryptographic libraries and key derivation algorithms to Java so @rhinofi trading on StarkEx could run inside @opera's native browser wallet.
One of three builds with StarkWare since 2021, and the one that meant coordinating teams at StarkWare, RhinoFi and Opera👇
Two roles. One person?
Your policy requires an operator and an independent approver. One person holds both roles.
Does the product still enforce separation of duties? Test the action, not just the settings screen, before shipping a custody integration.
Our First Draft turns custody permissions into release-test scenarios.
It's an illustrative design exercise, not a custody provider audit. The provider's actual configuration and identity model still need checking.
firstdraft.dorg.tech/edition…
Moving tokens to another chain used to mean a bridge, a wait, and hunting for gas on arrival. On @squidrouter, market makers bid to fill the swap, it settles in seconds, and nobody has to trust Squid with the funds.
@ecdsafu from @squidrouter explains how.
Full episode below this post👇
Can two workers spend one budget?
Both check the remaining allowance. Both see enough. Both send.
A written spending limit isn't an enforced limit. Stablecoin payment flows need a reservation step before concurrent requests can consume the same capacity.
Explore the fictional payment-control scenario in First Draft.
The prototype helps explain budgets, approvals and competing requests. It is not a live treasury system or evidence of a defect at a named provider.
firstdraft.dorg.tech/edition…
No system can distinguish a caller it never asked to identify itself...
SCOOP: Major U.S. banks are detecting unauthorized third-party AI agents inside customer accounts, including some attempting to take actions that appear to be independent of user instructions, sources told Axios.
The findings have alarmed banking executives, who are racing to restrict access to their systems as AI moves at a velocity faster than financial institutions can respond, multiple industry and bank executives told Axios.
Several banks are now preparing for worst-case and even “day after” scenarios, including how to rapidly secure or restore customer accounts if things go wrong, the people said.
Several bank executives told Axios they're struggling to distinguish between human users and AI agents. One executive said banks also struggle to determine whether agents are authorized by customers or potentially operating without their permission, more akin to rogue agent behavior.
Read my latest for Axios here: axios.com/2026/10/22/ai-agen…
We built the Zodiac Core SDK: TypeScript tooling that lets any developer encode, deploy and verify a Zodiac-compliant module without reading the contracts first.
Four years of building Zodiac with @gnosisguild, and the SDK is the part that made other people's work possible👇
dOrg retweeted
Most portfolios find out where the floor is after the drop. With MoonUp, you set it before: Conservative (70%), Balanced (50%) or Bold (30%).
Capital splits between a USDC reserve and tokenized stocks. Markets fall, more shifts to USDC. They rise, exposure grows. CPPI, onchain.
By the time the market reaches your floor you're already 100% in stablecoins. The algorithm starts deleveraging before it gets there, and leverages back up when the market turns.
@Yas_MoonUp from @getMoonUp on how the protection layer works.
Full ep on our Youtube channel
Paid twice. Or notified twice?
A payment provider sends the same notification again. Your application credits the customer again.
One transfer has become two balances. Reconciliation starts with durable identities and evidence, not a green success badge.
Our First Draft follows a fictional deposit across payment intent, provider record and ledger entry.
Try the reconciliation prototype and see why retries need an idempotent path. No real transfer is involved.
firstdraft.dorg.tech/edition…
