DarkPoolFi

The first sealed-order dark pool for tokenized stocks on @robinhoodapp chain.

[DarkPoolFi @DarkPoolFi]

We just launched the first sealed-order execution layer for Stock Tokens on @Robinhoodapp Chain.

CA: 0x073407b2ba247e88a3183849ec2817512171d7ef

Fund a private note. Seal your order. At each 5-min close, eligible flow crosses at the Chainlink reference price.

No public book. No queue. Private results. Delayed tape. STAY $DARK.

[DarkPoolFi @DarkPoolFi]

The interesting ZK problem is not proving one transaction.

It is proving that an entire window settled correctly: fills, refunds, rollovers, fees, and backstop flow, all under one set of rules.

[DarkPoolFi @DarkPoolFi]

Good morning $DARK fam

Another day of cooking, main dev (me) is going to get some coffee I’ll be back in a few minutes and I’ll start cooking more partnerships, tech updates and answer any question on TG.

Stay $DARK

[DarkPoolFi @DarkPoolFi]

Tech update: $DARK

Privacy has a boundary, and we say where it is.

ETH uses a separate private transfer path. Stock tokens move directly to and from the vault, visibly onchain.

No vague claims. Just the exact model users are getting.

[DarkPoolFi @DarkPoolFi]

Tech update:

A price limit on DarkpoolFi is a guardrail, not a promised fill.

The cross uses the external reference at execution. If it is inside your limit, your order is eligible. If the reference is unreliable, the window does not force a trade.

stay $DARK

[DarkPoolFi @DarkPoolFi]

Private execution needs more than encrypted-looking data.

It needs a proof that the state change is valid before the contract accepts it. That is what the Noir layer is there for.

[DarkPoolFi @DarkPoolFi]

Tech update:

The public tape is built to show the window, not the trader.

Your orders and results stay private. Once the window closes, aggregate volume is published on a labeled delay.

Private execution. Public accountability.

[DarkPoolFi @DarkPoolFi]

The threshold committee designed to remove the operator’s current ability to open sealed orders is implemented and tested, but not active yet.

We will keep separating what is live, what is tested, and what is still being moved out of trust.

https://t.co/Y2YGUxV0es

[DarkPoolFi @DarkPoolFi]

Private orders are not enough if somebody still has to open them to run the match.

The direction we are building toward is moving from operator-run settlement to proof-verified settlement inside the shielded pool. Full thread🧵

[DarkPoolFi @DarkPoolFi]

The goal is simple:

The operator can help keep the venue live, but should not be the party you trust to decide whether your fill was calculated correctly.

Correctness belongs in the rules and the proof.

[DarkPoolFi @DarkPoolFi]

This is why we made the repository public.

Privacy is not one circuit or a landing-page claim. It is the full chain of notes, commitments, proofs, relaying, verification, and clear trust boundaries.

https://t.co/Y2YGUxV0es

[DarkPoolFi @DarkPoolFi]

When we built DarkpoolFi, the hard part was never just hiding an order.

It was making sure privacy held across funding, proving, relaying, crossing, and settlement.

That full path is what we put in the repo.

Thread 🧵

[DarkPoolFi @DarkPoolFi]

The current boundary matters. Today, the operator runs the crossing engine and can see orders once a window is sealed.

The next stage settles windows inside the shielded pool with ZK proofs, removing that trust from the operator.