Polkassembly Logo

Create Pencil IconCreate
OpenGov

Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more

View All Medium Spender

Private Transfers of DOT

inMedium Spender
2 years ago
Executed

This is a retroactive treasury spend proposal by Integritee AG

We ask the treasury for 87'377 USD = 11'655 DOT

Work done:

  • Implement Incognitee Sidechain which can transfer a relaychain native token privately by shielding it to L2 and eventually unshielding it back to the relay chain without linkability
  • Demo Video where we shield DOT from a local Asset Hub to Incognitee and back
  • We are now able to transfer ROC privately (on public Rococo testnet)

Next Steps:

  • launch a public test campaign and bug bounty on our Rococo testnet which we launched in Dec 2023
  • Support for Asset Hub and its fungible assets, i.e. USDC/USDT
  • Support for ANY substrate based chain and its assets

Some History:

  • Initial Blog outlining the Vision
  • Previous attempt Referendum 17 for treasury funding (was also retro-active, but deemed to be too early for retro-active by commentors):  

Full Proposal Document

edit:

You can now test our tech on our Rococo testnet

Comments (9)

2 years ago

First off I want to say it's great that the dotsama ecosystem gets more privacy friendly ways to store and send dot.

Questions:

  • Manta is another player in the privacy field here. With mantas zkassets coming to dot, allowing what I interpret as achieving the same outcome where a users can not find source and destination. What are the main differences in your approach Vs manta?

  • What are the pros and cons compared to what your suggesting?

Thanks
~ flipchan

2 years ago

@Rust Syndicate Manta and Integritee chose different technical approaches to the same problem. Manta applies zero-knowledge cryptography while Integritee applies trusted execution environments. We believe privacy is an underserved topic in Polkadot and we should welcome a plurality of approaches

From a user experience perspective:

Manta (Calamari today)

  1. obtain KMA tokens
  2. bring tokens you want to protect to Calamari parachain via XCM (still a tricky endeavour, unfortunately, and only few tokens supported)
  3. shield token to zkAddress
  4. sync chain in browser extension to lookup your balance privately
  5. transfer privately (12s block time)

Incognitee

  1. send your DOT to vault address (no XCM needed) 
  2. transfer DOT privately on Incognitee (1s blocktime)

Notes:

  • Users don't need TEER tokens in the process (which is one of the reasons we think Incognitee will mainly boost DOT valuation and why we think the treasury should contribute to its development)
  • Any parachain could deploy Incognitee on their chain to get privacy for their tokens (another reason why this tech is a common good)
  • In the future, Incognitee can host EVM/WASM private smart contracts (see our PoC) Please remember: Manta promotes zkEVM but that is not about privacy its only about succincness/scalability
  • Incognitee is an L2 to every substrate based chain (even without the consent/support of the underlying L1)
  • Incognitee has a good chance for regulatory compliance because with TEE it can tune selective law enforcement access based on decentrlaized governance. ZK can't do that
  • In order to use Manta for privacy, you need to use their custom wallet UI (or browser extension). Incognitee, on the other hand, can be supported by any substrate-compatible wallet UI easily because it just uses secure websocket RPC.

2 years ago

This is one of the teams with the greatest potential. Excellent work by Alain and his team.

Load more comments
PleaseLogin to comment

Requested

DOT
11.65K DOT

Proposal Passed

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2026

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy