Weekly Privacy Newsletter - 3.28.22

Hello Privacy Protectors :prv:,

Welcome to spring, the weather is not the only thing changing, Incognito is bringing some exciting changes this week and next. Along with app improvements we have easier Un-Shielding, CSV Export, :fantom: Fantom Bridge, Incognito Pay, and much much more.

Recent Developments

Incognito App :iphone: (Android & IOS)

We have submitted the next app update to the app stores and are awaiting their approval. After the approval process is complete, the app will be available to end-users. This update will include the following new features as well as some minor bug fixes:

  • Export Transaction History - The CSV export feature will give users the ability to record past transaction data for record keeping/tax purposes. As requested previously by the community: How do I export my trades, Tracking history, Do we have a way to export CSV's?, etc.

  • pCoin Un-shielding Fee - App users can pay the un-shielding fee with the same coin that is being un-shielded. PRV will no longer be needed to un-shield. This prevents a scenario where users do not have enough PRV to un-shield without first swapping some into PRV. Read the official announcement: App Version 5.2.0 - Unshielding Fees Changes

Privacy apps

  • Fantom Bridge - As mentioned in our last weekly update, we have finished coding, testing, and deploying the :fantom: Fantom bridge.


Upcoming Developments

Incognito wallet extension

  • The dev team was working on another option for Incognito users to interact with Incognito network alongside Incognito app - a wallet extension on browser. This will be a building block for possible use-cases in the future such as Incognito exchange web version and Incognito pay. The more details will be revealed in coming weeks.

Privacy apps

  • pUnified Tokens - Gives the ability for all tokens, no matter the network (BSC, Ethereum, Polygon, etc), to be used as the same coin. For example, USDC (ERC-20) will act the same as USDC (BSC) and vice versa. Currently, the UI/UX flow is being developed. Once this is finished, we will publish all documents on the forum for the community to review and feedback.


  • Benchmark Node - The dev team is reviewing various network aspects such as data size, vote stat, blocktime, transactions per block, etc to find out improvement rooms like increasing network throughput and reducing transaction latency.

Growth Efforts

  • As previously mentioned, we have submitted an entry for the :solana: Solana RipTide Contest. We need our communities help to get Incognito recognized for our efforts to bring privacy to the Solana network. Everyone can cast their vote by going to this link and clicking upvote (a Twitter account is required). Please share the word and let’s pump :incognito: Incognito <> :solana: Solana! :partying_face:

Stay Connected:
:twitter: Twitter: https://twitter.com/IncognitoChain
:telegram: Telegram: https://t.me/incognitochain

As always, if anyone has any questions, comments, or concerns feel free to leave them in the comments section below.


I really like these weekly newsletters. It highlights that a lot is happening, really fast (at least in my opinion).

Keep up the good work! :heart:


Is there any way for us mere mortals to know when this happens? My nodes are still getting >10 PRV rewards and then >50 epoch pending queues, so I take it the feature has not been enabled yet.

But the RPC command getfeaturestats seems to only list the Validator size for each shard. The ValidatorStat and ProposeStat lists are empty. I’m not able to get the stat node feature list on my own node or the mainnet.incognito.org/fullnode?

Hi @fredlee,
Yes, you are correct, the committee size is still 32 now. As stated in the newsletter, this feature will be enabled once 98% nodes in the network running the update. Currently, according to our stats, only about 70% of nodes did it. The stats is calculated from messages exchanged in the network and will be exposed on the node monitor in the near future.
This is an important change and we wanted as many nodes to be updated as possible (aka less nodes will be stalled and slashed), that’s why we set the 98% threshold for the feature to be effective. But yeah, we may have to wait forever if the requirement is never satisfied so will need to have a deadline for this: we planned to make it happen next week.


That’s a fairly high threshold. If there’s ~2150 nodes only need ~45 to not be running the most recent update. Most of us are proactive but I’m sure there’s still a significant contingent that aren’t, (i.e. that 30%!) especially if they are only running one node.

Yes, what do you guys think if we decrease that to a more reasonable number, maybe 85%?


That sounds like a more appropriate number while still being a sufficient hurdle.

1 Like

That would be great.

From your own experience, how fast are new versions adopted? Apparently around 30% of all nodes do not use auto-updating scripts (or have scheduled them to update less frequently than 7 days). I guess a lot of them won’t update unless needed (stalled or slashed). If that is the case, to even reach 85%, we need to put up another 2150 auto-updating nodes. :flushed:

Personally I want the feature as soon as possible, but losing 30% of the nodes is a bit extreme. Maybe give it a 2-4 week deadline and see how high natural adoption we can reach in that time?

Yeah, we are still monitoring the percent, let’s see how this will change next week. We will definitely make head ups for the new deadline then.


REMINDER: Come on everyone, we need to Up-Vote the Solana Privacy Layer project by going to this page - https://solana.com/riptide/voting/the-privacy-layer-for-solana

I was upvote #30

Let’s all get behind this and see how many votes we can get.

The team did a great demo video ( https://www.youtube.com/watch?v=JPaM-L7y9Cg ) and it’s a super easy privacy solution for Solana that deserves more recognition.