dOrg

Top web3 and AI developers delivering infra and apps on demand.

Helping clients reach +$4B TVL

[dOrg @dOrg_tech]

Hey, this is dOrg, d-Org🕵️ (from decentralized organization).

We accelerate your web3 development needs, here’s how:

Thread Alert!⬇️

[MoonUp @getMoonUp]

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.

[dOrg @dOrg_tech]

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.

https://t.co/wMgSuf4fXm

[dOrg @dOrg_tech]

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.

[dOrg @dOrg_tech]

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

[Ethereum Institutional @ethereuminsti]

Ethereum is the home of onchain finance.

[dOrg @dOrg_tech]

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.

[jesse.base.eth @jessepollak]

200ms blocks live on testnet, mainnet soon

[dOrg @dOrg_tech]

@PsyProtocol Giving the agent its own budget makes sense. First thing I'd poke at is what happens when it hits the limit halfway through a checkout.

[dOrg @dOrg_tech]

@zksecurityXYZ Crypto code is where generic scanners struggle most, so a tool built just for that makes sense. Does it cover circuits too or mainly native implementations?

[dOrg @dOrg_tech]

@0xenzo_eth @solana_devs That's how a lot of auditors get their start. Congrats on presenting the first one.

[dOrg @dOrg_tech]

@0xdoug The cost curve is what flips it. Once writing the spec is cheaper than writing the tests, it stops being niche.

[dOrg @dOrg_tech]

@xrpl_commons @angell_denis @XRPLF Three days hands-on in core protocol code is how you actually grow a dev base. Have a good one in NYC.

[dOrg @dOrg_tech]

@CetusProtocol Sui's object model feels like a good fit for this. You can scope an agent to specific objects instead of handing it a whole wallet.

[dOrg @dOrg_tech]

@QMSNetwork Listing the known differences upfront saves people hours. PREVRANDAO returning 0 will catch anyone porting a contract that leans on it.

[dOrg @dOrg_tech]

@SuccinctJT Fair point on the double standard. Planning for upgrades no matter which primitive you pick seems like the only honest position.

[dOrg @dOrg_tech]

@Nethermind @etheconomiczone Multiple prover clients from the start is a good call. The client diversity lessons from L1 carry over pretty directly.

[dOrg @dOrg_tech]

@Concordium @XDCNetwork Agents spending money is the easy part to build. Who's on the hook when one misbehaves is what regulators will ask about first.

[dOrg @dOrg_tech]

@CoinbaseDev @Mastercard @Cloudflare Mastercard + Cloudflare is a strong sign x402 is past the demo stage. Merchants barely needing a new integration is the part that makes it stick.

[dOrg @dOrg_tech]

@decentrek The gif helps a lot. What I'd want to understand next is latency: how many aggregation rounds before the builder gets its single proof?

[dOrg @dOrg_tech]

@StarkWareLtd Native AA plus privacy at the wallet level is a nice combo. Curious how shielded balances show up for dapps that need to read them.

[dOrg @dOrg_tech]

@StellarOrg Starting PQ signature work alongside smart accounts makes sense. Much easier to build signature agility into the account layer from day one than to retrofit it.