Announcing the xNAV testing bounty program: How to try the new privacy in NavCoin’s Testnet and get rewarded.
After years of development and refinement, the brand new self developed privacy protocol blsCT has finally made it to testnet, the final step before official release. You can have a sneak peek into how it works before the final launch. We want to invite everyone to be part of the testing process and reward users for their participation, as this part of the process is critical to ensure the final release and mainnet deployment are smooth and free of issues.
In this article we will explain how to download and test the beta version of NavCoin Core 6.0, which features support for the new private token xNAV.
Downloading the binaries
The first step is to download the right binaries depending on your system:
Once you’ve downloaded the corresponding file, you will need to unpack it. Inside of the bin folder, you will find a binary with the name navcoin-qt.
After running it, the wallet will start automatically to synchronize with the testnet, where xNAV is already enabled. This can take a few minutes depending on your system specifications and your internet speed.
Filling your wallet with test coins
Your wallet will be initially empty with no coins. In order to get some, you are invited to come over to our Discord and share your receiving address where one of our community members will gladly send you some test coins. You can see your receiving address clicking in the “Receive” tab in the menu on the left.
Above the QR code you can find a combo box, where you can select whether to see an address to receive public NAVs or private xNAVs. Copy this address to your clipboard and share it in our Discord!
The new home screen has a few changes.
The balance is shown split between NAV (1) and xNAV (2). This is a great way to have always control of the amount of coins your wallet holds.
There’s also a new button to swap between NAV and xNAV (3). This is the easiest way to transform your legacy NAV into the new privacy-enabled xNAV.
Once the transaction is sent and confirmed by the network, you will see the balance updated.
The “Send” tab has also been slightly updated to allow the sending of private tokens:
You will only need to select in the combo box which kind of coin you want to send. Depending on the type of coins (NAV or xNAV) you are sending, and the address type of the destination, there are four different types of transactions:
- From NAV to NAV. Both the sender, recipient and amount are public and can be seen by anyone.
- From NAV to xNAV. The recipient of the transaction remains anonymous, while the sender and amount are public.
- From xNAV to xNAV. Every detail of the transaction (sender, recipient and amount) stays private.
- From xNAV to NAV. The source of the transaction is hidden, while the amount and the recipient are public.
When a transaction is sent, it is shown on the transaction list in the “History” section.
You will be able to copy the transaction ID and look for it in the testnet version of NavExplorer, which already supports xNAV, to see how a private transaction looks like! We challenge you to guess the amount, source and destination of the transaction. Hint: You will not be able!
Found a bug? Have a suggestion?
The final intention of making this beta version available is to test the binaries in a different set of scenarios to track possible bugs or mistakes in the implementation.
Feel free to play with this beta release. Send coins around, look at the explorer. If you find anything that does not work as expected, have any question or just want to provide your feedback, feel free to get in our Discord. Our community members are very helpful and will assist you in the process. We’ve set up a bounty program so those who find issues can get rewarded based on the severity of the finding:
- Visual glitches -> 100NAV for reporting 200NAV if a fix is delivered
- Minor UX issues -> 300NAV for reporting 500NAV if a fix is delivered
- Major UX issues -> 600NAV for reporting 1,000NAV if a fix is delivered
- Local client crashes -> 1,000NAV for reporting 2,000NAV if a fix is delivered
- DoS/Network isolation attacks -> 4,000NAV for reporting 7,5000NAV if a fix is delivered
- Consensus model (POS) vulnerabilities -> 5,000NAV for reporting 10,000NAV if a fix is delivered
- Generation of coins out of thin air -> 10,000NAV for reporting 15,000NAV if a fix is delivered
- Theft of funds, remote code execution -> 15,000NAV for reporting 20,000NAV if a fix is delivered
In addition to the bug bounties, we also want to reward users for merely participating in the testing of xNAV. You can claim 10NAV for free by sending any amount to the following private address:
- xNU54ErfsN4v78cgHLzSCRzb9HpBMhGQAxZ7grD4Cy5iWtyKGdfC2S7YhRURFnSafZiBX7GPbKBW8EETs1NK2pc3fp2zefaoBrsz1AuQahiYEv8UdQAdtUpmXBWeZXK6Kgee7DWqcPs
You will only need to add your Discord username in the encrypted message field and one of our community members will get in touch with you to send you the bounty. Additionally until the 30th of November, you can claim other 10 NAV by tweeting about xNAV and adding the hashtags #blsct $NAV #privacy. Remember to show your tweet to our community member when he reaches you!
