November BetaNet Compensation Applet Instructions

This applet will allow you to sign the contract to receive 4,000xx in compensation for running your node in the first half of November 2021. Only nodes with > 60% uptime between ProtoNet and MainNet are eligible. If you are eligible you will receive an email.

MainNet Nodes

Per the November Payments announcement, you need to register a new wallet to receive your November payments in

Next week, the process for operators to move their nodes over to the new wallet will be done. You will be moving your node to this new wallet, which will free your current wallet to nominate any node while maintaining the Team Multiplier – thereby ensuring your coins can take the most advantage of nominating on the xx network.

Step 1 – Generate a new wallet

Please use the Quantum Ready Wallet Generator to make a new wallet. Make sure to keep it safe, this will be the wallet your node will be validating from.

Step 2 – Sign the contract for the new wallet

Using the November Payment Applet (download below) use your BetaNet Keys to sign the contract and commit to your new wallet.

You will need to use this wallet with the new MainNet Transition Program Commitment applet next week.

That is it. The team will get your coins over the next week and start the next phase of the process soon.

CanaryNet Nodes

Instructions for receiving November BetaNet compensation for nodes not in the MainNet Transition Program.

Per the November Payments announcement, you need to register a wallet to receive your November payment.

It can either be a new wallet or an existing wallet. If you want to use a new wallet, please use the Quantum Ready Wallet Generator to make a new wallet.

With your selected wallet, download the November Payment Applet (download below) and use your BetaNet Keys to sign the contract and commit to your wallet.

That is it. The team will get your coins over the next week.

Download the correct file for your operating system. You can use the provided SHA256 checksums to verify the integrity of your download.

Download

macOS (Intel and M1)
Checksum: 9b6ab0a974999aefe03c5f1c8551464ac5f8f71cbdcd7fd09f19de3436a023a5
Windows
Checksum: bc4278c2e8e382ef6c1bef85700766ad6e42551945c18fd9a88f1e4c52386a21
Linux
Checksum: 09808e3a8cc9bdeca7ce9e1c2ef561b17c04bf74af0cc6a73605f210158cece9
Source: november-commitments branch in the elixxir/mainnet-commitments repository
GUI Source: novemberCompensationForm branch in the elixxir/mainnet-commitments-ui repository

Instructions

Set-Up

macOS

Download the zip file for macOS above. The same file will work on both M1 and Intel Macs.
Double click the zip file. The app will extract to the same location.
Right-click on the app and select “Open”.
A warning will appear saying the app cannot be verified. Click the “Open” button to continue.

Windows

Download the binary for Windows above.
Double click the downloaded executable to install the app (note that the installer extracts the app and its assets to your temporary file directory).
Once the installer opens, click the “Install” button to install the app into your temporary files (or select an alternate location).
Once the installer completes, click the “Close” button, and the app will automatically launch.

If you close the app and need to relaunch it, you can either reinstall it via the downloaded installer or navigate to %LocalAppData%\Temp\novemberCompensationForm and launch nw.exe.

Linux

Download the zip file for Linux.

Extract the contents of the zip file.

$ unzip november-compensation-linux-x64.zip

Enter the extracted directory.
```
$ cd nwjs-*
```
Run the nw executable.
```
$ ./nw
```

Using the Form

To fill out this form, you need the credentials for your BetaNet node (key, public certificate, and IDF). Per previous instructions, the team expects node operators to have these in a secure location. To find these, refer to Finding Betanet Node Credentials on the wiki. If you do not have them already, download them to the machine from which you are running the app.

First, select your Node’s public certificate. It will be a .crt or .cert file.
Select your Node’s private key. It will be a .key file.
Select your Node’s identity file (IDF). It will be a .json file.
Enter the wallet to receive payment. If you are a MainNet node, this will be a new wallet. If you are a CanaryNet node, this will be an existing or new wallet.
Review the contract and press the checkmark to accept the conditions. Note that you can view the entire contract on a separate page or print it for your records.
Press the “Submit” button and wait for the confirmation message. This may take a few moments.

If you do not have your BetaNet Keys, the team cannot help you.

Cookie	Duration	Description
_ga	2 years	The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gat_UA-130126130-8	1 minute	A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to.
_gid	1 day	Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
CONSENT	2 years	YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.

Cookie	Duration	Description
__cf_bm	30 minutes	This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
__hssc	30 minutes	HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
__hssrc	session	This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.
__hstc	1 year 24 days	This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
aka_debug	session	Vimeo sets this cookie which is essential for the website to play video functionality.
guest_id	2 years	This cookie is set by Twitter to identify and track the website visitor.
guest_id_ads	2 years	This cookie is set by Twitter to identify and track the website visitor.
guest_id_marketing	2 years	This cookie is set by Twitter to identify and track the website visitor.
hubspotutk	1 year 24 days	HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.
mbox	2 years	This cookie is for marketing on developer.twitter.com
muc_ads	2 years	Twitter sets this cookie for tracking and targeting purposes.
personalization_id	2 years	Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting.
player	1 year	Vimeo uses this cookie to save the user's preferences when playing embedded videos from Vimeo.
sync_active	never	This cookie is set by Vimeo and contains data on the visitor's video-content preferences, so that the website remembers parameters such as preferred volume or video quality.
vuid	2 years	Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.