Pinned Tweet
Hey, this is dOrg, d-Org🕵️ (from decentralized organization).
We accelerate your web3 development needs, here’s how:
Thread Alert!⬇️
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…
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
At 200ms the chain stops being the slow part of most applications.
An RPC polled on a fixed interval, an indexer that batches before it serves, a frontend built to show a pending state for a second or two: none of that gets faster because the block did.
The work to feel 200ms is in the stack above it.
Anyone publishing their alpha on X isn't running it with their own money...
@Yas_MoonUp from @getMoonUp on why that's the tell.
Full episode below👇
Five banking flows, each a browser prototype with fictional data.
Start with the payroll one. A supplier is due today, payroll is due tomorrow, and the cash is split across currencies. Choosing what to pay is the easy part. Proving the agent was allowed to is where the work is.
Link in the reply👇
Subscribe!
firstdraft.dorg.tech/edition…









