We have created the fastest DeFi on ICP

We have created the fastest #DeFi on #ICP!

:white_check_mark:0.15s

:white_check_mark:0 gas

:white_check_mark:fully on-chain

Try it:

7 Likes

Congrats, that’s impressive! :fire: Sub-second swaps with zero gas fully on-chain is a big deal. Do you have a whitepaper or technical docs where we can dive deeper into the architecture?

3 Likes

Yes, here is Litepaper:

Investor deck:

2 Likes

Hey @SSS thank you for sharing.
As you are very well aware of, there is very little interest and even less engagement here on the forum regarding DeFi, as seen in :
Part1, Part2 and Part3.
With that said we will take a look and provide some feedback. Having some open sourced code would help.

3 Likes

Thank you, there is no opensource yet, as we are developing V3, with multiple tokens and unstablecoin pools.

Feedback is important for us.

Investor recommendations would be greatly appreciated.

2 Likes

The “0.15s” metric: how does this differ from the standard ICP canister update call response? As far as I understand, any canister on ICP returns a response to the caller before block finalization. Wouldn’t any well-built DEX on ICP be able to report a similar “optimistic” response time? What specifically makes SSS’s approach different at the architecture level?


On verifiability: the litepaper emphasizes “audit-grade” tracing and recomputable receipts, which is a strong claim. Is the canister source code open-source, and is the deployed WASM hash verified against published source? Without that, the audit trail is only as trustworthy as the team behind it, which somewhat undermines the “DEX trust” positioning.


On the user experience during failures: if a trade receives an Optimistic ACK at ~150ms but then fails to finalize, what exactly does the user see? Is the balance silently reverted? Is there a notification or error state? How long could a user be in a position where they believe a trade has succeeded when it hasn’t yet settled?

3 Likes

Thanks for the very professional questions.

(1) On the “0.15s / 150ms” metric: this is not ICP update-call finality. It’s our Optimistic ACK = acceptance into a traceable pending state, while we separately report Finalized settlement.

This “fast acceptance vs later finality” is also common elsewhere:

  • Solana has processed/confirmed/finalized style commitments;

  • Ethereum has submitted/pending → confirmations → stronger finality.

You’re right that any dapp can show “submitted” quickly — the difference is whether the system provides a traceable state machine path from “click → pending → finalized/failed” with retry-safe semantics.

So the differentiator is not “showing submitted quickly”, but whether the ACK is meaningful and recoverable. In SSS, it’s backed by:

  • a unified internal ledger (CEX-style account model) so swaps are state-machine accounting (deposits/withdrawals touch ICRC transfers), and

  • idempotency via Tx Hash( Explorer Page) so retries don’t double-execute, and the pending state is traceable end-to-end.


1 Like

(2) On “audit-grade verifiability”: fair point. V2 is not fully open-sourced yet, so we agree the strongest form of “trust-minimized auditability” needs:

  • open-source code,

  • reproducible builds, and

  • verification that the deployed WASM hash matches the published build.

The core of V2 lies in validating the end-to-end functionality of SSS systematic architecture and establishing a complete closed-loop system. It primarily serves to attract investor attention and engage interested developers.

Our plan for V3 is to do this properly: security audit → open-source → reproducible build + hash verification → SNS DAO deployment.

If you (or anyone) can help with introductions to investors / funding support, it directly accelerates this path. Our goal is to build the strongest on-chain trading system on ICP, and we will make the “DEX Trust” claim to be backed by public verification.

1 Like

(3) On failures after an Optimistic ACK: the UI does not treat ACK as success. The user sees:

  • Pending immediately (traceable via SwapEvent.id(Swap Page) ), then

  • Success or Failed when finalization completes.

If finalization fails, any optimistic balance delta is reverted and the swap log shows an explicit error/timeout (we cap the pending window rather than leaving users stuck).

Best way to verify: do a small swap, check the SwapEvent.id and Tx Hash , and check the Optimistic ACK and Finalization trail.

We also have a short demo video showing the exact flow (ACK → finalized):

2 Likes

Has anyone been rethinking this as ICP keeps sliding: doubling down on DeFi might be the most direct way for ICP to break out of its price black hole?

3 Likes

Thats why we are building @DoxaFoundation

3 Likes

Stablecoin. Looks great!

yes, its a game changer on #ICP

Yeah, we can collaborate, list on SSS trading system.

That would be game changing dusd<>sss patnership