Privacy Version 2


Launch privacy v2


3 months

Key results:

  • Ship one-time address
  • Ship Multilayered Linkable Spontaneous Anonymous Group (MLSAG) Ring Signature
  • Ship Confidential Assets
  • Decrease transaction size by 20%-50%
  • Increase transaction throughout by 10%-20%

Detail Schedule:


  • Continue to integrate with pDEX (1 - 7 Jun)
  • Refactor and Optimized source code to decrease transaction size and increase transaction throughput (7 - 14 Jun)
  • Integrate with Portal (15-30 Jun)


  • Deploy Privacy ver 2 (without Confidential Asset) to Testnet (1-30 July)
  • Implement Confidential Asset (1-30 July)


  • Deploy Confidential Asset to Devnet (1 - 15 August)
  • Deploy Privacy ver 2 (with Confidential Asset) to Testnet (15- 30 August)



Hi guys, we are working hard on the test and debug phase. The main problem is the backward compatibility with the current version on Mainnet and Testnet.

The integration with Portal will be delayed until July. The performance report will be released before next Monday (Jun 29, 2020)


Hi all,

We are finishing the implementation phase for privacy version 2. The majority of crucial barriers have been resolved. We are doing an automation test on devnet.

The summary of finished tasks is as follows:

  • All transactions version 2 (PRV and pToken)
  • Conversion transaction from version 1 to version 2 (PRV and pToken).
  • Backward compatible with old data (syncing fullnode testnet)

The pending tasks are as follows:

  • Benchmark transaction size and throughput
  • Fix bugs from QC team.

Good :heart::heart::heart:


Hi all, here are the new updates for privacy version 2.

We have passed all test cases on Devnet. Now is the time to integrate with pDex version 2 and merge with the optimized syncker from the Consensus team before deploying on Testnet.

With privacy version 2, we reduce 35% in terms of transaction size with one input and two outputs, and 58% on average.

Transaction throughput is also improved by around 11%-21%. The detail is provided in here.

Compare token transaction size between version 1 and version 2

Compare normal transaction size between version 1 and version 2


Don’t we already have one-time addresses when shielding coins?

Update for August:

  • Integrated with pdex ver 2
  • Internal audit code for privacy ver 2

Plan for September:

  • Introduce a new viewing key to encrypt amount of output coins with the full-node.
  • Implement Confidential asset feature

It’s only available for 60 minute then it switches…

I know. Isn’t that exactly what a one-time address is?


Currently, shielding a crypto asset uses an address from a pool of rotating addresses. If you view a deposit address in a block explorer, you will see other transactions days, weeks before yours. As Jerry notes, these addresses are only available to a user for 60 minutes during a deposit transaction. Addresses are then reused after a certain amount of time has passed to ensure deposits are properly credited.

A one-time address is exactly as it sounds. A one-time (use) address. Every deposit transaction will receive its own address. The address will never be reused again. Not by the original depositor nor any other depositor. This will solve the time window issue, as the address will remain “available” until a deposit is made (or presumably canceled by the user).

1 Like

Right, so even though my COIN app can take 1-3 days I could then deposit it straight to incognito instead of going to KuCoin first, really cannot wait for that.