Incognito Core Dev 2020 Live Roadmap

7 key initiatives

Incognito launched its mainnet in November 2019. We believe that at this foundational stage, implementing the following 7 initiatives will provide the most value to the community.

These foundational building blocks will enable a thriving community of users, validators, and developers to build many new privacy-first products for this new world of cryptonetworks.

Initiative 1: Bring incognito mode to every cryptoasset

As crypto is eating the world, it is not far fetched to estimate that cryptoassets will increasingly compose an individual’s net worth or a company’s balance sheet. Incognito hopes to give these new assets and their owners - both now and in the future - the option to claim their right to privacy.

We’re focused on building as many trustless bridges as possible, so that people can confidentially send and receive cryptoassets like BTC, ETH, DAI, and USDT.

Objective 1.1: Build trustless bridges Date Status
Trustless bridge with Ethereum Nov 2019 Shipped
Trustless bridge with Bitcoin and Binance Chain (Phase 1: Incognito Bond Contract) 1 May 2020 Shipped
Trustless bridge with Bitcoin and Binance Chain (Phase 2: Ethereum Bond Contract) Nov 2020 Building
Trustless bridge with Cosmos TBD

As it takes time to design and build trustless bridges the right way, a pragmatic solution is to provide temporary trusted bridges while trustless bridges are built out.

Objective 1.2: Build trusted bridges Date Status
Trusted bridges with Bitcoin, Binance Chain, Ziliqa, and Tomo Chain Nov 2019 Shipped
Trusted bridges with Monero Feb 2020 Shipped
Trusted bridges with Ontology, Ripple, NEO, Cosmos, and EOS Apr 2020 Delayed

1 The development of the trustless bridge between Binance Chain and Incognito is funded by Binance.

Initiative 2: Bring incognito mode to every crypto activity

Right now, thousands of developers all over the world are programming smart contracts to build decentralized applications (commonly known as “dapps”). Arguably, privacy concerns play a part in discouraging adoption beyond the crypto niche, as traditional investors hesitate to expose how much they trade on a trading dapp like Uniswap, or how often they invest & borrow on a lending dapp like Compound.

We’re focused on building incognito mode for existing smart contracts on other cryptonetworks.

Objective 2.2: Incognito mode for existing dapps Date Status
pKyber June 2020 Shipped
pUniswap, p0x Aug 2020 Shipped
pCompound Sep 2020 Building
pMakerDAO TBD Delayed
Smart Contract SDK TBD

In parallel, we also identify unique dapps and build them natively on Incognito.

Objective 2.1: Build useful dapps Date Status
Issue your own privacy coin Nov 2019 Shipped
pDEX Nov 2019 Shipped

Initiative 3: Build the largest proof-of-stake network with 20,000 nodes

By design, Incognito is powered by a very large group of small validators, while other PoS networks are often controlled by a small group of large validators.

Our hardware strategy is focused on designing and making simple, beautiful, plug & play physical nodes for every home.

Objective 3.1: A Node in every home Date Status
Node Nov 2019 Shipped
Node Tree Oct 2020 Building
Node Pro Cancelled

For more technical validators, a host-it-yourself option is available.

Objective 3.2: Host-it-yourself Date Status
Node Virtual Nov 2019 Shipped
Node Virtual Desktop App Nov 2019 Shipped

Initiative 4: Bring the best privacy research results to production

Instead of reinventing the wheel, our strategy is to bring the best privacy research results to production. The Incognito privacy stack borrows heavily from the research work of CryptoNote (RingCT), Dan Boneh (BLS), and Benedikt Bunz (Bulletproofs).

Objective 4.1: Bring the best research to production Date Status
Ring signatures Oct 2019 Shipped
CT (in RingCT) Oct 2019 Shipped
Upgrade range proof to Bulletproofs Nov 2019 Shipped
BLS Nov 2019 Shipped
Batch verification Mar 2020 Shipped
One-time address Apr 2021 Building
Upgrade Ring signature to “Multilayer Linkable Spontaneous Anonymous Group (Mu-LSAG) signatures” Oct 2020 Building
Confidential IP

We’re also focused on solving privacy problems that are unique to Incognito, such as Confidential Assets.

Objective 4.2: Solve Incognito’s unique problems Date Status
ZKP on Mobile Nov 2019 Shipped
Confidential Assets Nov 2020 Building

Initiative 5: Be the highest-performance privacy cryptonetwork.

To deliver privacy at scale, we implement sharding on privacy transactions and a new consensus based on proof-of-stake, pBFT, and BLS. Transaction throughput scales out linearly with the number of shards.

Objective 5.1: The highest-performance privacy network Date Status
Mainnet v0 with 8 shards Nov 2019 Shipped
Highway v1 to scale from 1K nodes to 5K nodes Feb 2020 Shipped
Highway v2 to scale from 5k nodes to 10K nodes Mar 2020 Shipped
Storage reduction Mar 2020 Shipped
Consensus v2(with slashing) Nov 2020 Building
Reduce committee size dynamically June 2021 Building
Randomness v2 TBD

The network began with partial-decentralization and iterates steadily towards full decentralization over time.

Objective 5.2: As decentralized as possible Date Status
Remove fixed producers 2 Nov 2020 Building
Remove fixed nodes 3 Apr 2021 Building
Stake for Beacon TBD
Highway PoS TBD

2 Will be shipped as part of Consensus v2.

3 We originally anticipated that we could remove the fixed nodes within 3-6 months of minimum viable mainnet launch. This is now delayed until April 2021. The main dependencies are Consensus v2 (Nov 2020), Dynamic Committee Size (Dec 2020), and Randomness v2 (Apr 2021). Without these components in place, there is a huge risk to network stability.

Initiative 6: Build a universal privacy wallet

We’re focused on building a universal privacy wallet that is safe (innovative key backup solutions), smart (seamless integration with different cryptoservices), and private – of course.

Objective 6.1: Incognito Mobile Wallet Date Status
Wallet v1 Nov 2019 Shipped
Wallet v2 Mar 2020 Shipped
Biometric Authentication Mar 2020 Shipped
Keyless + Multisig Apr 2021
Incognito mode for dapps like Uniswap and Compound Aug 2020 Shipped
Notifications Mar 2020 Shipped
PRV Staking Pool Apr 2020 Shipped
Node Self-staking Mar 2020 Shipped
Batch payment June 2020 Delayed
Internal Tools v2 Apr 2020 Shipped
Devops (CI/CD, monitor web, app-apis, autoscale) Apr 2020 Shipped
Invest & Borrow anonymously TBD

In parallel, we also develop a Wallet SDK that allows developers to build “micro apps” inside the wallet.

Objective 6.2: Wallet SDK Date Status
Wallet SDK v1 Dec 2019 Shipped
Wallet SDK v2 April 2020 Shipped

The next objective is to make Wallet available on other platforms.

Objective 6.3: Be on as many platforms as possible Date Status
Web Wallet Jun 2020 Delayed
Desktop Wallet TBD

The final objective for Wallet is to bring incognito mode to every other wallet out there.

Objective 6.3: Incognito SDK Date Status
Incognito SDK for mobile wallets Mar 2020 Shipped
Incognito SDK for web wallets Mar 2020 Shipped

Initiative 7: Community

Incognito is a community of privacy-minded builders. The long-term goal is to make the community autonomous by achieving 3 main goals: self-funding, self-incentivizing, and self-organizing.

Self-funding ensures that the community is sustainable both in the short and long term.

Objective 7.1: Self-funding Date Status
Block reward split Nov 2019 Shipped
Core team donation TBD

Self-incentivizing ensures that there is an in-built incentive mechanism to facilitate long-lasting, large-scale collaboration among community members.

Objective 7.2: Self-incentivizing Date Status
Block rewards Nov 2019 Shipped
Community rewards Mar 2020 Shipped
Liquidity rewards Apr 2020 Shipped
Custodian rewards TBD

Self-organizing ensures that the community adopts a bottom-up approach. Its members self-organize based on common goals and take necessary actions without requiring permission.

Objective 7.2: Self-organizing Date Status
Community Crowdfunding Mar 2020 Shipped
DAO Mar 2021


This 2020 roadmap is a small sampling of all the possibilities available to those who want to explore Incognito’s potential and help build out the network. The core dev team chose these initiatives to give Incognito its best shot at providing privacy that is not just technically robust, but also open-minded, inclusive, and far-reaching. Privacy that anyone, any currency, and any application can have. Join us in building this choice for the world.

Next page: Incognito's 2021 privacy roadmap for the world


Hi @duy please add this proposal link Privacy Version 2 for Incognito into “Initiative 4”, both “One-time address” and “Upgrade Ring signature …”, please


To my experience while introducing Incognito to someone, the lack of two features in the wallet really makes the novice users surprised:
1- Not able to see receiving TXs
2- If the app is uninstalled somehow, she cannot access her previous transactions after she reinstalls it.

Related to 2, another feature restricting the users is that she cannot use readonly key via incognito explorer. I think if they cannot be implemented simultaneously because of workload, one of this or 2 should be implemented. Please remember that we call blockchain as distributed “ledger” frequently. Currently, ledger function is not easily accessible for Incognito users.


Hi Abduraman,

We plan to improve these features at the end of April, 2020. Let’s wait for it.


Hi Tech Team -

Can we get an update on how many current total Nodes there are in the network?

And is there a new plan on when the new validator slots will be opening? How many and when will that be?



According the committee page on the mainnet explorer, there are about ~915 (waiting + preparing + 80 community slots) non-Incognito team nodes. This does not include any nodes that are online but not staked or nodes that are otherwise offline.


Hi Mike Despo,

Let’s check out the explorer to see the total Nodes in the network:
As the objective 5.2, I see that it is delayed till April 2021.

Thanks Mike Wagner for a clear explanation.


When will the source code of pNode be open to public? I think this is essential for a decentralized network and should be put into the roadmap. @duy @Peter


There are no plans to open source the pNode code.

The pNode is the Incognito implementation of a vNode device.
Everyone can bring their own version of a pNode, with their own logic, own staking mechanism, to the market. The pNode is just one way of doing it. Would be exciting to see what others come up with.


Not a good idea but anyway I will not be long. The closed source of pNode may hurt the reputation of Incognito. Everything is a tradeoff. So, I’m sure the team already thought this.


hey @abduraman… just want to make sure i understand exactly what you’re asking… what exactly (which components) of node are you asking to be open-source? the main part is already open-sourced, as node is basically a… computer running a full node just like how you’re running it on your vps.


hey @duy . As of now, I have no concern on this issue (otherwise I wouldn’t apply for Incognito Rebel position :slight_smile:) but some people will have. Why? Nobody can know whether a random node is vnode or pnode. What if pnodes have 2/3 of the network? In that case, how will people be sure whether the company of pnodes doesn’t go rouge? Of course, you may open some code as the source code of pNode but in truth, you may install a different node software not built upon the open source code. Anyway, in short, my question was just a suggestion, not a concern. Best.


hi @abduraman do you ever run a pNode ?
if you run a pNode, you will see your pNode running by your validator key from your wallet.
and it like a vNode.


Where on the explorer do you find this information?



@abduraman you asked, we listened. the core team is working on open-sourcing the Node (pNode) source code. most likely the source code will be released on github next week.

in general, the source code inside Node is still pretty 80% the same code that you’re using to run Node Virtual (vNode). the other 20% is considered like “firmware logic”.

  • updating the latest version of the chain
  • communication with the mobile app
  • wifi setup
  • in-memory validator key mechanism
  • and a few other minor things that i can’t remember now

cc @binh @Jamie @Peter @annie


Any plan to progressively open source the hardware used for the pnode?

Probably can’t be done all at once because the only decent processor options out there are currently proprietary, but that’s slowly changing with the introduction of RISC-V.


It is happening :slight_smile:

I asked for the same as you, not sure if they will release only the code or the hardware itself.


Releasing the code is super awesome. :heart_eyes:

Open sourcing the hardware would take a lot of logistical work, but would help to increase security.


@annie COOL!!! :heart: :orange_heart: :yellow_heart: :green_heart: :black_heart: Thank you!