Go to your app store to get release 3.10.0

Hey all you protectors of privacy!

There’s an app update today! Actually, there are two. Here’s a closer look at how to get them, and the new features and bug squashes that comprise them.

Note: some transactions may turn up unsuccessful on previous versions, so we recommend you make the update at your earliest convenience.


This first update can be initiated from your app store. It’s got a slew of changes that will make your app more convenient. You can click the topics in the list below to expand an explanation about it.

UTXO consolidation tool

Are your transactions are slowing or getting stuck? UTXOs accumulate in heavily used keychains (especially for those that send and receive many small amounts, such as Node operators and Provide users). With this release, there’s a tool to help you keep things tidy.

Here’s how to consolidate your UTXOs >

In-app update reminder

Ever wonder if you have the latest app version, but don’t feel like checking your settings?

Procrastinate no more! Whenever there is an update that is pushed through the app store, there will now be an update prompt at the bottom of your app’s home screen that will take you straight to the app store for the update.

Clarity for shield/unshield statuses

Until now, your shield and unshield transactions have only been classified as pending or complete. In this update, we’ve clarified “pending” to include a “processing” stage, and updated the details of what’s happening in each stage.

For example, the shield stages are as follows:

Old Stage Descriptor Updated Stage Descriptor Explanation
Pending [0] Pending Transaction pending receipt of funds.
Pending [1] Processing [1] Funds received. Turning your public coins into privacy coins…
Pending [2] Processing [2] Funds received. Turning your public coins into privacy coins…
Complete Complete Your balance may take a few minutes to update.
Shield time and text

Ever wished you could have just a little bit longer to shield your coins? Now, your one-time shielding address lasts for two hours! This makes it easier to deal with people who are slow to send you funds, and to protect against the time delays that some crypto wallets experience.

There’s also some updated text on the shield screen, reminding you to be wary of withdrawal times from certain crypto exchanges.

If you want privacy but your exchange takes too long, you may want to withdraw to a non-private wallet first, and then shield your coins.

Auto-remove special characters

When you scan an address that includes special text, your app will now automatically edit it to a usable format. For example, when your scan results in “address ±—@”, it will remove the “±—@” and ensure the address is correct.

Chain privacy maintenance update

Privacy is our first priority. We conducted a routine chain update, some “spring cleaning” in the Fall, to ensure the privacy you get with Incognito remains top-notch.


Once you have 3.10.0 and open the app, you’ll be prompted to do an in-app update for 3.10.1. This one’s for the validators in the crowd:

Notifications for all your Nodes

With this latest update, you can now get notifications for all your Nodes when they earn! If for any reason you do not want notifications to show - simply go to your device settings to toggle off notifications for the Incognito app.

Fixed incorrect Node status

Some have experienced an incorrect Node status with the new Node UI. You may have been told your Node was offline while it was actually waiting or even earning.

Now your app accurately represents the status of all your Nodes.

"Fixed “cannot buy Node" error

Have you bought a Node in the app, only to be told you “cannot buy Node”? We’ve fixed the messages we’re sending you about whether or not you can buy a Node (hint: you can).

And that’s the gist! Let us know your thoughts below, and feel free to join in other conversations around here at we.incognito.org.


Were unsheilding fees raised again? Gas has been pretty consistently low but I’m getting higher pricing than a few days ago. Do you have any tips/advice for capturing low gas fees when the network is not congested?

@aaron FYI… with the new update my pNode shows to be “offline”, but it is connected and earning, and the Incognito Tool is able to connect and query its status… so not sure if that is just a bug, or something more… but since it is called out specifically as a fix in this update, I thought I would let you know.


I am try to send my prv on old version the transaction was failed then update my app not works good.

1 Like

Use new update app on play store.


I think the gas/ fee depends on the previous tx at the time you make the transaction. If you see the fee is higher than the actual gas, let’s wait patiently.

I believe the other team members will be happy to share a tip/ advice for capturing low gas fees as well.

Thanks @doc . We are checking on this. However, have you followed the instruction when the app shows that your Node is offline? Does it show the green light again after that?

What do you mean, @Shobhan?

1 Like

I have not power cycled the pNode, will do that today… but everything else was done on the instructions.

1 Like

Keep us posted with the power cycle!

Power cycle fixed app connection

1 Like

@Peter When i am update my app on play store then app automatic closed problem show me then i am restart my phone now app work fine :+1:


@aaron @Peter. I am not sure if this is the expected behavior, but my pNode still goes gray several times. Since I first reported here in this thread, I have had to power cycle 3 times to get it back to green. So at least once a week.

I do have vNodes also running on the same network, and they have not had any connectivity issues within the app. I know with the current committee and selection process, this really isn’t an issue with earnings, but I do worry about this with the new updates being made, for instance I posted a comment here on this topic about a week ago:

Another concern around this Is that I am planning on hosting future NodeTree’s in remote locations where I will not have direct access to them for power cycling on the regular. And I dont want the new slashing rules to limit the selection process of nodes with the already increasingly lower probability of selections that happens as the network grows.

So, I am not sure if this is still an app UI desync, or if this is an actual problem with network not being able to tunnel in to the pNodes… any clarification on this would be helpful.

1 Like

If you won’t have access for power cycling, consider using an IP PDU to grant remote power cycling.

https://dlidirect.com/products/new-pro-switch (Amazon link)
https://www.synaccess-net.com/np-02b (Amazon link)
http://dataprobe.com/iboot-g2/ (Amazon link)

For the above options you should use a secured jumpbox or VPN to access the web frontend of these devices, rather than port-forwarding through your network’s edge device (router, firewall, etc). You could port-forward; it’s just perhaps not the best choice from a netsec perspective.

If that’s too much (cost, hassle) you could use any one of the app-enabled, “smart” power strips or power plugs available on Amazon as a low cost, pseudo-PDU with more-or-less “secure”-ish remote access.

For example –

1 Like

Thanks for these suggestions @Mike_Wagner, I am sure a connected power strip like you are suggestions could fit the bill, but I would also argue that if a pNode is losing connection with the network on a weekly basis, the devices themselves could power cycle after a period of time without connection to Highway/network… which seems like a much better solution than me having to look and check on the device to see it is not responding, and then making sure to cycle before the pNode gets hit with the slashing rules that will be upcoming.

I just think a solution on app (or pNode itself) is a better solution for the pNode, than requiring an additional device that could require extra configuration… especially since the pNode is supposed to be a super user friendly, plug and forget it type of device.

The Auto-Ping feature on the DLI PDU can do that for you. You would configure the Auto-Ping system to monitor the LAN IP of the Node. If the Node drops offline, the PDU will power-cycle the Node for you. You can configure how often the Node is checked (pinged), how long it needs to be offline to power-cycle, retries, etc.

Any of the first three devices will have that option.

The Amazon “smart” power strips/plugs … won’t.

Ahh, I see what you are saying… but the issue is the pNode is still online via the LAN… it is just not being see by Incognito…

I can still query the device RPC and get its information, the app is just not showing it can connect to it, which I assume is 1 of 2 things:

  1. NAT punch through has failed and needs to be updated for connection back to Incognito
  2. It is actually all good, and it is some sort of desync with just the app.
1 Like

Got it. I just wanted to give you some dev independent options.

1 Like

Thanks, I appreciate the input and insights… always good to get as much input as possible.

Maybe this is super silly but how about one of those cheap cheap timers designed to turn on/off lights when you wanting. Just set it to do a weekly poweroff. The key would be what’s the minimum time it can be off…the cheap one I have here looks to be like 1 hour (which is probably too long).

1 Like