Incognito Performance

hieutran · 23 July 2020 08:56

Sending Cryptocurrencies Confidentially: Ring Signature, Homomorphic Commitment, and Zero-Knowledge Range Proofs ▸

Privacy at Scale with Dynamic Sharding ▸

Consensus: A Combination of iPoS, Multiview-pBFT, and BLS ▸

Multiview PBFT ▸

Incognito Software Stack: Navigating the Incognito Source Code ▸

Incognito Performance ▾

We evaluate the performance of Incognito based on its real workload on the mainnet, as well as on simulated workloads.

In evaluating the performance of the Incognito network, we focus on the privacy transaction throughput, more specifically the metric of transactions per second (TPS). Note that Incognito uses a UTXO based ledger. In most cases, fewer than 32 existing UTXOs are used as inputs and 2 new UTXOs are produced as outputs.

Figure 1. Transactions per second based on the number of inputs per transaction on a shard

In Figure 1, we show the TPS metric of one shard and two fixed outputs. In the best case, we have 6.5 TPS and only one input, and in the worst case, approximately 2.5 TPS and 32 inputs. From March 2020, we introduce the batch verification feature to verify transactions in a batch [Bunz et al., 2018]. This feature improves transaction throughput by twofold. Specifically, Incognito archives 12.5 TPS and 5 TPS for one input and 32 inputs, respectively.

Figure 2. Transactions per second based on number of shards

Figure 3. TPS comparison among Incognito, Monero, Zcash, Grin, and Beam

Transaction throughput scales out linearly with the number of shards. Currently, with 8 shards active, Incognito is able to handle 90-100 TPS in the most common case (two inputs and two outputs per transaction). We are working on a new network topology to scale to 64 shards. With this, Incognito will achieve 800 TPS, a significantly higher number than that of other privacy blockchains. For example, 4 TPS for Monero¹, 6 TPS for Zcash², 10 TPS for Grin³ and 17 TPS for Beam⁴. Details are shown in Figures 2 and 3.

Network Incentive: Privacy (PRV) ▸

User-Created Privacy Coins ▸

Use Cases: Privacy Stablecoins, Privacy DEX, Confidential Crypto Payroll, and more ▸

Future Work: Smart Contracts, Confidential Assets, Confidential IP, and more ▸

Conclusions, Acknowledgments, and References ▸

0x123 · 14 February 2020 10:48

How is sharding going to affect Incognito’s performance? Is it a linear relationship between TPS and number of shards? Are there any penalties from cross-shard interactions?

If there are, I think each shard should strive to be “stand-alone”, meaning a dapp should reside on only 1 shard to lower the amount of cross-shard interactions.

jason · 14 February 2020 13:36

Number of in-shard transaction per second increases linearly with the number of shards. While the delay or the number of cross-shard transaction won’t be effected when we increase the number of shards.

Absolute.