Rewards Queue

Today marks the launch of the rewards queue. Previously, a single Chainpoint Node that passed all audits was randomly selected and issued a reward. This model has ended. Here’s how the new model works:

  • Public Chainpoint Nodes are placed in a queue and given an audit score.
  • Nodes that pass audits get a +1 to their audit score.
  • Nodes that fail an audit get a -1 to their audit score.
  • For each reward period, a single node is randomly selected from the top 100 nodes in the rewards queue and issued a reward.

The Chainpoint Wiki on Github has a full description of the Chainpoint Network Reward Queue Rules.

What’s The Benefit of the Rewards Queue?

The rewards queue should improve network reliability and distribute rewards more evenly. Node operators are incentivized to keep nodes online and passing audits. The launch of the rewards queue is the latest in an upcoming series of changes that will allow nodes to join the Chainpoint Network at any time.

Additional Network Growth

On April 5th at 10:00am PT (17:00 UTC) an additional 500 nodes joined the Chainpoint Network. This brings the total number of public Chainpoint Nodes that have successfully registered to 7,500.

Those keeping track of the size of the Chainpoint Network might notice this number is slightly higher than expected. High demand and technical problems in February and March led to an unintended overage in the number of nodes that registered. These problems have been resolved. The April 5th registration went smoothly.

As of this writing, the total number of public Chainpoint Nodes passing audits is 6,057. This number is different from the total nodes that have successfully registered for the following reasons:

  • The number of Nodes passing audits fluctuates
  • Every node that has ever registered is not active
  • Some nodes have not upgraded to the latest software version

The difference between the number of nodes that have ever registered, and the number of active nodes that are passing audits will continue to grow over time. For this reason, we will be periodically making the count of active nodes that pass audits publicly available. More information will be coming in a future update.

Upgrade Registration Process

Node operators should upgrade to version 1.3.7 as soon as possible. The command ‘make upgrade’ will upgrade and restart a Chainpoint Node.

IMPORTANT: Nodes must upgrade to 1.3.7 to be eligible for rewards.

Chainpoint API Tutorial

Want to build something with Chainpoint? Our team created a guide that shows how to use a Chainpoint Node’s API to create a Chainpoint proof. You can use any programming language that supports HTTP calls.

Chainpoint Javascript Client

This javascript client can be used in both Browser and Node.js based Javascript applications using callback functions, Promises (using .then.catch), or Promises (using async/await) functional styles.

chainpoint/chainpoint-client-js chainpoint-client-js — A full featured Chainpoint client. Can be used in Node.js or the browser, using Callbacks or

We’ve created a live code notebook on Runkit that demonstrates how to use the client. Developers are encouraged to submit any issues to the Chainpoint Client Github repo.


We’re Hiring

Tierion has several openings for experienced developers to join our team in San Francisco. Our toolchain is based on Node.js, CockroachDB, PostgreSQL, RabbitMQ, Redis, and Consul. Everything is glued together with Docker, Docker Compose, and Kubernetes.

View full job descriptions

Follow Chainpoint development on Github. Keep up to date by following Tierion on Twitter.