Betanet Analisys Group Reports

As announced in the blogpost here, we have a small group of professional validators running their nodes on the new NEAR Betanet. These nodes require additional attention such as frequent updates and reboots - generally speaking, a lot more maintenance.
This activity is valuable for the entire community, as the NEAR Core team can test the nightly releases in a “real-world scenario” and build a more reliable nearcore.

The thread below will be used by the Betanet Analisys Group to report (on a monthly basis) their activities. Every reply will follow a template, which is still very basic and open to improvements, that will be forwarded to NEAR Foundation for the token allocation.

Every reply should contain:

  • the timeframe (start and end) of the activity (e.g. November 16th - December 31st 2020)
  • the name of the betanet staking pool (e.g. pool1.nearkat.near)
  • a list (not mandatory) of the additional measures that were requested, such as hard forks or manual nearcore updates

We will process token allocations in batches (similar to the Stake Wars) so expect a few days to pass between the report submission and the tokens transfer.
The compensation for this activity is $500 in NEAR Tokens per month.

As of today this group is full, and we don’t plan to add other validators to it in the foreseeable future

Reach out to me directly via chat or email if you have any questions!

1 Like

• November 16th - December 31st 2020
• pool.appload.near
• everything has been requested in the Slack channel

Our validator is running from the start of betanet with all neccesary updates, details below:

• November 16th - December 31st 2020
• infinite.lux.near
• completed in time all neccesary updates

  • November 16 - December 31 2020
  • c1.inotel.near
  • completed all the tasks from the slack channel and kept the node up and running all the time.
  • November 16 - December 31 2020
  • pool.jazza-betanet.near
  • completed all necessary nearcore updates and kept the node up and running.
  • November 16 - December 31 2020
  • pool.zavodilbetanet.near
  • completed all the tasks from the slack channel and kept the node up and running all the time.
  • November 16th - December 31st 2020
  • pool.projecttent.near
  • completed all tasks described in the Slack channel
  • November 16th - December 31st 2020
  • pool.48.near
  • completed all tasks proposed in the Slack channel in a timely manner

November 16 - December 31, 2020

poolv1.majlovesreg.near

Did all the requirements and maintained the node studiously. :slightly_smiling_face:

• Jan 1 - Feb 14, 2021
• pool.appload.near
• completed all the tasks have been requested in the Slack channel, kept the node running

• Jan 1 - Feb 14, 2021
• c1.inotel.near
• completed all the tasks have been requested in the Slack channel, kept the node running

  • January 1st 2021 - February 14th 2021
  • pool.48.near
  • completed all tasks proposed in the Slack channel in a timely manner, and reported minor bugs encountered while running the node.
  • January 1st 2021 - February 14th 2021
  • pool.jazza-betanet.near
  • completed all the tasks have been requested in the Slack channel and kept the node up and running.
  • Jan 1st - Feb 14th 2021
  • pool.projecttent.near
  • completed all tasks described in the Slack channel and kept node running
  • January 1st 2021 - February 14th 2021
  • pool.zavodilbetanet.near
  • completed all the tasks have been requested in the Slack channel and kept the node up and running.
  • January 1st 2021 - February 14th 2021
  • infinite.lux.near
  • completed in time all neccesary updates.

January 1st 2021 - February 14th 2021
majlovesreg.poolv1.near
completed all the tasks have been requested in the Slack channel and kept the node up and running.