Eclipse

Dark Mode built around Uniswap v4 Hooks. Private execution for public liquidity on Robinhood Chain.

[Eclipse @eclipsehook]

Eclipse is exploring an expansion to @Enter_Elysium .

Elysium combines high performance EVM execution with a path to HyperCore liquidity, making it a natural fit for Eclipse:

Privately batch and match orders first, then route only the remaining imbalance to public markets.

[Eclipse @eclipsehook]

Privacy is not a single feature. It is a sequence of verifiable properties. 🌘

Eclipse now presents its privacy model layer by layer, showing what remains visible, what becomes hidden and where trust assumptions still exist.

The roadmap progresses through:

• Batch Actions
Individual swaps are combined inside a Dark Wave, reducing isolated public execution.

• Encrypted Orders
Order direction and limits remain hidden from the public before the wave trades.

• ZK Validity Proofs
The batch can be proven correct without requiring users to trust the operator’s reported result.

• Shielded Settlements
Designed to reduce the visible link between deposits, execution and payouts.

The information-leakage simulator demonstrates why each layer matters. A standard public swap may expose the trader, direction and minimum output before execution. Eclipse instead commits the order onchain while keeping sensitive parameters hidden until the wave locks.

The simulator illustrates the intended privacy architecture, not a claim that every layer is already live.

Privacy should not be implied.
It should be defined, measured and verified.

[Eclipse @eclipsehook]

@Larpcheckbot @Dhanuw97 @Uniswap https://t.co/63GKWJy8KJ

Check again @Larpcheckbot

[Eclipse @eclipsehook]

Everything is live and verifiable onchain. 🌘

Network
• Chain ID: 4663
• Consensus state: Synchronized
• Core contract bytecode: Active

Protocol deployments
• EclipseOrderRegistry
0x160A84e238Fa34f050630b37f55c2137A40b630f

• EclipseBatchVerifier
0x072E0ac3795C67D4C6cC17dCBB3865Fb115a1E0d

• Uniswap v4 PoolManager
0x8366a39cc670b4001a1121b8f6a443a643e40951

• Net Residual Routing Hook
0x47c68C343C422790F998e9F777865554732560c4

Verification checks passed
• Merkle commitment-root inclusion
• Order collision and replay prevention
• Internal-crossing conservation
• Minimum-output and slippage consistency
• Pre-cutoff cancellation logic
• RISC Zero zkVM batch-proof evaluation

Deployment proofs
• OrderRegistry
https://t.co/6yhIePy1G4

• BatchVerifier
https://t.co/UUBWOZEN4z

Private execution. Verifiable settlement. Public liquidity.

[Eclipse @eclipsehook]

Eclipse is now live on Robinhood Chain Mainnet. 🌘

CA: 0x935e693a6ce2beae85e4a85b79486f4fd6b3df9c

The deployment introduces a private execution layer built around @Uniswap v4 Hooks.

Protocol flow:
• Orders are submitted into time-bounded Dark Waves
• Compatible buy and sell flow is netted internally
• Uniform clearing logic is applied across each wave
• Only the net residual is routed to Uniswap v4 liquidity
• Final settlement and state transitions are recorded onchain

It coordinates execution around existing public liquidity, reducing unnecessary order-flow exposure without fragmenting liquidity.

[Eclipse @eclipsehook]

Different markets require different liquidity routes.

They should not require different execution guarantees. 🌘

The Eclipse market layer currently demonstrates three execution environments:
• WETH/USDG through the Uniswap v4 EclipseHook
• NVDA/USDG through a 24/7 tokenized-equity route
• PONS/USDG through the graduated-token executor route

Each market operates through the same protocol framework:
• 30–60 second Dark Waves
• Internal midpoint clearing
• Batch netting before public routing
• zkVM invariant verification
• Nullifier-based replay protection
• Merkle inclusion for settlement claims
• Only the net residual routed to public liquidity

Crypto, tokenized equities and ecosystem assets.

Different markets. One private execution layer.

[Eclipse @eclipsehook]

Everything is live and verifiable onchain. 🌘

Network
• Chain ID: 4663
• Consensus state: Synchronized
• Core contract bytecode: Active

Protocol deployments
• EclipseOrderRegistry
0x160A84e238Fa34f050630b37f55c2137A40b630f

• EclipseBatchVerifier
0x072E0ac3795C67D4C6cC17dCBB3865Fb115a1E0d

• Uniswap v4 PoolManager
0x8366a39cc670b4001a1121b8f6a443a643e40951

• Net Residual Routing Hook
0x47c68C343C422790F998e9F777865554732560c4

Verification checks passed
• Merkle commitment-root inclusion
• Order collision and replay prevention
• Internal-crossing conservation
• Minimum-output and slippage consistency
• Pre-cutoff cancellation logic
• RISC Zero zkVM batch-proof evaluation

Deployment proofs
• OrderRegistry
https://t.co/6yhIePy1G4

• BatchVerifier
https://t.co/UUBWOZEN4z

Private execution. Verifiable settlement. Public liquidity.

[Eclipse @eclipsehook]

Eclipse is now live on Robinhood Chain Mainnet. 🌘

CA: 0x935e693a6ce2beae85e4a85b79486f4fd6b3df9c

The deployment introduces a private execution layer built around @Uniswap v4 Hooks.

Protocol flow:
• Orders are submitted into time-bounded Dark Waves
• Compatible buy and sell flow is netted internally
• Uniform clearing logic is applied across each wave
• Only the net residual is routed to Uniswap v4 liquidity
• Final settlement and state transitions are recorded onchain

It coordinates execution around existing public liquidity, reducing unnecessary order-flow exposure without fragmenting liquidity.

[Eclipse @eclipsehook]

@yydsbubble 好的，谢谢你的建议。

[Eclipse @eclipsehook]

Dark Waves are running on the Eclipse.

Every 30 seconds, Eclipse collects orders into a single wave.

Inside each wave:
• Compatible buy and sell orders are matched internally
• A uniform clearing price is calculated
• Only the remaining imbalance is routed through the Uniswap v4 Hook
• The completed wave is settled onchain

The onchain-synced dashboard displays:
• Accumulated volume
• Netting efficiency
• Residual liquidity
• Settlement status
• Estimated gas savings

[Eclipse @eclipsehook]

@yydsbubble 查看最新发布的内容

[Eclipse @eclipsehook]

Silent build mode. 🌘

Eclipse is preparing for Robinhood Chain mainnet.

The final systems are moving into place:
• Mainnet contract configuration
• Uniswap v4 Hook integration
• Dark Wave settlement flow
• Zero-knowledge proof pipeline
• Deployment and monitoring checks

Just focused execution behind the scenes.

Private execution for public liquidity is getting closer.

[Eclipse @eclipsehook]

@yydsbubble 是的，我们将继续进行下去。

[Eclipse @eclipsehook]

Privacy should be explained, not implied. 🌘

Eclipse shows exactly what becomes visible at every stage of the protocol.

A standard public DEX swap can reveal:
• The trader’s wallet
• Token direction
• Order size
• Minimum output
• Information that searchers may use before execution

Eclipse Dark Mode is designed to progressively reduce that exposure through:
• Batched order execution
• Salted onchain commitments
• Encrypted order parameters
• Zero-knowledge validity proofs
• Shielded settlement research

Orders can be combined inside a Dark Wave and settled at a uniform clearing price, while only the remaining imbalance reaches public liquidity through Uniswap v4.

Each privacy layer will only be marked live once it is deployed and verifiable.

Privacy, stated plainly.

[Eclipse @eclipsehook]

The goal: prove that the wave followed the protocol’s rules without exposing every individual order publicly.

Private execution. Verifiable settlement. Public liquidity.

[Eclipse @eclipsehook]

Eclipse’s zero-knowledge circuit prover is running. 🌘

The Rust zkVM verifies each Dark Wave before settlement:
• No duplicate order IDs
• Order deadlines remain valid
• Private orders are included in the commitment root
• Internal crossing uses the correct clearing price
• Gross volume equals matched volume plus the residual

In this test:
• 12,000 USDG gross buy volume
• 8,000 USDG gross sell volume
• 8,000 USDG matched internally
• Only the 4,000 USDG imbalance routed through the Uniswap v4 Hook

[Eclipse @eclipsehook]

Eclipse’s zero-knowledge circuit prover is running. 🌘

The Rust zkVM verifies each Dark Wave before settlement:
• No duplicate order IDs
• Order deadlines remain valid
• Private orders are included in the commitment root
• Internal crossing uses the correct clearing price
• Gross volume equals matched volume plus the residual

In this test:
• 12,000 USDG gross buy volume
• 8,000 USDG gross sell volume
• 8,000 USDG matched internally
• Only the 4,000 USDG imbalance routed through the Uniswap v4 Hook

[Eclipse @eclipsehook]

Why does it matter?

• Less individual order-flow exposure
• Internal matching can reduce volume hitting the public pool
• Lower potential market impact
• Existing Uniswap v4 liquidity remains accessible
• Minimum-received and slippage protection
• Onchain status and transaction records

Private execution does not require isolated liquidity.
This shows the WETH/USDG flow running on Robinhood Chain.

[Eclipse @eclipsehook]

What happens when you choose Dark Mode on Eclipse? 🌘

Instead of executing as a separate public swap, your order is escrowed onchain and joins the next 30–60 second Eclipse Wave.

Inside the wave:
• Compatible buy and sell orders are matched
• Only the remaining imbalance reaches Uniswap v4
• The result is settled back to each trader

[Eclipse @eclipsehook]

What happens when you choose Dark Mode on Eclipse? 🌘

Instead of executing as a separate public swap, your order is escrowed onchain and joins the next 30–60 second Eclipse Wave.

Inside the wave:
• Compatible buy and sell orders are matched
• Only the remaining imbalance reaches Uniswap v4
• The result is settled back to each trader

[Eclipse @eclipsehook]

Exactly. That end-to-end path is where the protocol either holds together or breaks. Seeing it pass is an important checkpoint.

Now we keep testing the edge cases and strengthening every layer around it. Appreciate you recognizing that 🤝

[Eclipse @eclipsehook]

Eclipse smart contract test suite is passing. 🌘

The suite covers the core execution path from private order submission to final settlement:

• Orders escrow funds on submission
• Zero-value and expired orders are rejected
• Commitments hide order direction and limits
• Unauthorized and tampered reveals revert
• Cancelled orders return escrowed funds
• Full and partial internal matches settle correctly
• Slippage violations and token mismatches revert
• Settlement pays the intended order owner
• Dark swaps require the authorized executor
• Wave ID and execution amount must match
• Unregistered pools are rejected
• A wave cannot be executed twice
• Tampered batch-proof inputs revert
• Private payouts prevent double spending
• Specter shielded intents route into Eclipse escrow
• Public swaps continue through the Uniswap v4 Hook

This is an engineering checkpoint, The valid paths passed, and every tested invalid path reverted as expected.

[Eclipse @eclipsehook]

The official Eclipse contract address has now been added to our website. 🌘

Always verify from the official source before interacting.

One more step toward clearer, verifiable infrastructure on Robinhood Chain.

[Eclipse @eclipsehook]

The blue check is here. Eclipse is now verified on X. 🌘

Dark Mode built around Uniswap v4 Hooks. Private execution for public liquidity on Robinhood Chain.

[Eclipse @eclipsehook]

While we wait for our X verification badge, explore Dark Mode built around Uniswap v4 Hooks on Robinhood Chain.