Chainpoint Node 1.5.4 is now available on Github. This release adds optional HTTPS support and improves retries for failed submissions to Core. Chainpoint Nodes must upgrade to 1.5.4 by January 2nd at 12:00 PST (20:00 UTC) to be eligible for rewards.
How To Upgrade a Chainpoint Node
There is a special upgrade command for Chainpoint Node 1.5.4.
curl -sSL https://chainpoint-node.storage.googleapis.com/upgrade.sh | bash
This special command is necessary to remove all unused references to PostgreSQL and Redis and finalize the migration to RocksDB. Future upgrades will use the usual
make upgrade command.
Chainpoint 1.5.4 Release Notes
- Upgraded Node.js base Docker image to Node.js
- Removed deprecated
make backup-auth-keysMakefile target. Use
- Removed all references to PostgreSQL, which is no longer used, from
- Removed all references to Redis, which is no longer used, from
- Optional experimental TLS/HTTPS support and self-signed certificate generation. Requires port 443 open for use. Port 80 will continue to operate the same as before.
- Retry mechanism on failure to submit an aggregated Merkle Root to Core.
/verifyendpoint as a convenience when verifying a proof
- Community provided Korean translation of the
Build Something With Chainpoint
Want to build something with Chainpoint? Here’s 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.
callback functions, Promises (using
.catch), or Promises (using
await) functional styles.
Follow Chainpoint development on Github. Anyone can submit an issue or pull request. Keep up to date by following Chainpoint on Twitter. The Discord Community is one of the best places learn about Chainpoint and get answers to your questions.