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…
Moving proving client-side keeps that work offchain, but apps still have to generate the proofs.
Making that practical on phones is a big part of what makes this approach interesting.
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable.
Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread.
Instead, the correct solution is... EIP-8288 maximalism.
If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation.
This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
Would your agent protect payroll?
A supplier needs paying. Payroll is tomorrow. Cash is split across currencies.
An agentic banking flow needs more than a payment button: obligations, permissions, settlement evidence and limits all have to agree.
Explore five proposed AI + Web3 banking integrations, each with a browser prototype you can challenge.
Fictional data and deterministic rules, not live banking or investment advice. Which failure would you test first?
firstdraft.dorg.tech/edition…
We were live with @ecdsafu from @squidrouter this week
We'll upload the recording to our Youtube channel soon!👀
dOrg Hot Seat ft. Fig from Squid xitter.cf/i/broadcasts/1dGYlawQl…
Right amount. Wrong recipient?
An agent matches an invoice and checks the budget. Then someone changes the destination.
Valid arithmetic isn't a valid payment. Our First Draft explores what belongs onchain and what the application must still verify.
Inspired by Vitalik's cryptographic world computer essay, we built an illustrative payment-boundary demo.
Change the inputs and inspect the failure. No live payment, blockchain or AI model is connected.
firstdraft.dorg.tech/edition…
dOrg Hot Seat ft. Fig from Squid xitter.cf/i/broadcasts/1dGYlawQl…
Join us TODAY at 11:30AM CET🙌
Let's chat with @squidrouter! hosted by @Pol_Lanski
Hot Seat with @ecdsafu from @squidrouter is up for tomorrow, 11:30AM CET / 5:30PM Taipei / 4:30PM Bangkok
Set a reminder👇
xitter.cf/i/broadcasts/1dGYlawQl…
Hot Seat with @ecdsafu from @squidrouter is up for tomorrow, 11:30AM CET / 5:30PM Taipei / 4:30PM Bangkok
Set a reminder👇
xitter.cf/i/broadcasts/1dGYlawQl…
