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 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.

[DarkPoolFi @DarkPoolFi]

New on DarkpoolFi: settlement pings on Telegram.

Seal an order, tap "Ping me on Telegram", and @DarkPoolFi_bot messages you when your window settles.

We learn only which window you're waiting on. Never your market, side, size or wallet.

[DarkPoolFi @DarkPoolFi]

New for DarkpoolFi liquidity providers: your full position history.

Every deposit and withdrawal in the backstop vault, with its value at the time and a link to the transaction, next to your PnL and spread earned.

Our servers never see which wallet is asking.

[DarkPoolFi @DarkPoolFi]

Faster settlement on DarkpoolFi

Every 5 minutes, each market's crossing window closes. Its sealed orders are priced at the Chainlink reference and settled with a zero-knowledge proof.

Until now, our settlement engine handled one step for one window per minute, across all markets. With every market busy, it would slowly fall behind.

Now:
- Every finished window, in every market, is handled in the same run
- A window is sealed and settled together, not a minute apart
- No proof is repeated while a settlement is still being confirmed
- Each market settles in order, so the backstop's liquidity is never promised twice

In a simulated day with all 5 markets busy, the old engine missed 792 windows. The new one missed none, and every fill settled within a minute of its window closing.

Same sealed orders, same privacy. Your fills just arrive sooner.

[DarkPoolFi @DarkPoolFi]

Faster private trading on DarkpoolFi

Every private action on DarkpoolFi (an order, a withdrawal, a private send) needs a zero-knowledge proof built in your browser. That proof needs your note's place in the pool's Merkle tree.

Before, your browser rebuilt the entire tree from scratch several times for every proof. The bigger the pool, the slower it got.

Now:
-The tree is kept between syncs, and only new notes get hashed
-With 4,096 notes, preparing a proof takes about 4 ms, down from half a second
-Proof preparation stays fast as the pool grows
-Our servers read the note list from a proper index, not by scanning history every minute

Nothing about privacy changed. Your Merkle paths are still built on your device, so nobody learns which note you're spending.