OPEN: New Wallet: New features, upgrades, and maintance

1. Socket Overview

This socket is by Decentralized Authority to enable feature adds, upgrades, and maintenance of a new POKT wallet, which was commissioned by PNF. To account for PNF’s intial budget, we started the wallet initiative with the lowest possible cost. However, there are features and future development that we would like to pursue, hence why we are started a socket for this wallet.

Potential future features:

  • Import Seed Phrases from other wallets (ex. POKT Wallets using a MataMask Seed Phrase)
  • EVM Support (hold wPOKT from Ethereum, in the same wallet with all the Standard Wallet Functionality
  • Recipient Address Book
  • Stake, unstake, and unjail nodes (custodial and non-custodial)
  • Professional UX Design
  • Automated Testing
  • Updates, maintenance, and support

2. Type of Socket

  • Experiment: $3K, paid and reviewed monthly, for the life of the experiment.

3. Commitment to “Default to open”

We will work in the open and self-report monthly.

4. Link to Work

Github Repo

5. Wallet



This socket is now opened. We look forward to seeing what other valuable features you build into the wallet :saluting_face:


September update:

Development of the POP features are almost complete. The wallet will be code complete by next week, in time for wPOKT.

Regarding the extra features in this Socket:

  1. Groundwork has been laid for EVM support. With this wallet being built with new code from the ground up, this month we built a plugin structure that allows the wallet to scale to other chains and network in the future. POKT’s plugin has been created, and we now have the groundwork for EVM support.

  2. Professional UX Design: While the initial release of the wallet will be a simpler UX, this is the design we plan to implement in the coming weeks. It is multi-chain ready as shown in the example below, giving each chain/token a distinct color design.

Be on the lookout for an announcement next week for the beta release :wink:


Sweeet,looking great…


Updates and features for the month of October:

  • Added NodeWallet to the Chrome Store
  • Wallet naming functionality
  • Added menu and settings paged for user defined options
  • Added “Select Account” screen when using wPOKT Bridge
  • Added auto retry to account for RPC errors
  • Other budge fixes

When is coming to firefox…


Unfortunately, Firefox does not support the required features for Manifest v3, so not much we can do right now. It’s expected they will fully support Manifest v3 in the future, so we’ll need to wait until they do.

1 Like

This month we addressed bug fixes and created a new POKT wallet API, pokt_signMessage, to support PNF’s future governance initiatives. This API was added to the wallet and also to the POKT Wallet Integration Tester to serve as a reference implementation for applications.

This feature has not been pushed to the Chrome Store, but folks can download a dev version for testing here.


Ayoo @shane can we see a couple feature requests?

  1. Remove a wallet once it has been added to the NodeWallet interface - some sort of management here would be nice
  2. Could we integrate with something like CoinStats? Unsure of the difficulty of this one compared to the previous ask but would be such a nice feature add.

I don’t believe that #1 should be a huge issue. Will discuss with Amish :+1:

#2 not familiar with CoinStats, so will look into it.

Thanks for dropping some suggestions!


Our code for December was a mix of small fixes and also significant changes to prepare for an new SDK for POKT wallets that we are making in collaboration with PNF. These changes don’t effect user of the wallet directly, but will make it easier for app developers to create services that integrate with NodeWallet.

A new version of NodeWallet will likely be pushed to the Chrome Store in January with these changes, along with others.


This socket remains open for January.

Appreciate the updates Shane - let us know if you need any additional support.

You’re already in attendance, but for completeness - I’m asking all open Sockets to join us next Thursday for the Builders All-hands. I’d like to encourage people getting paid via the DAO to know what’s going on with the protocol, and have a forum to ask questions and cross pollinate. Matteo will run the first half w/ developers & protocol, and then I’d take the second half to review sockets work. The goal here being more cross-pollination and collaboration, so looking forward to you showing up and sharing on Thursday!


Our code for January added in-wallet staking and fully integrating the NodeWallet SDK and the NodeWallet React SDK.

With both the staking functionality and the NodeWallet SDK fully supported, node providers can easily add staking buttons to their websites. Providers can use the SDK to pre-generate a staking TX, which the user can choose to accept or deny via a popup modal. Staking with providers can have the same experience as interfacing with the POKT Bridge.

The NodeWallet React SDK comes with default button which can be used and styled by providers.


Users can create their own staking transaction directly from the wallet :point_down:

All of these features and updates have already been pushed and accepted by the Chrome Store.

@h5law we will be adding wallet removal in our next release :+1:


@shane this is great - very excited to see this continuing to be supported and add new features. Y’all remain open for February.

Could you update the logo to match the new POKT logo in the next release? It’ll make it feel more official and legit. (press kit is on the website)

I think we should also discuss updating our docs + next steps here.

My personal opinion is that we should be ‘recommending’ a wallet and the POKT wallet no longer seems to be getting additional features or upgrades, so pushing this narrative in our docs will most likely be good for our community + new comers.


It’s great seeing this feature available ,I was hoping to comment on the same,is there a way we could have a feature that allows a user to stake with third party node runners ?


That is already possible with the update last month.

Node providers however have to enable it on their websites, but all the groundwork is there.


What about if we had a way a user you could have the option of choosing which 3rd party node runner to stake with maybe also have a way of reporting avg rewards see for example when choosing…