Repository navigation
Releases
v5.0.0-rc11
Release candidate 11. A test release: the CVN Testnet has not started, and coins on any CVN test network have no value and carry over to nothing.
This release changes no rule. It agrees with release candidates 9 and 10 about every block, so machines on any of the three can share a network, and a development-network (devnet) chain carries on unchanged. Nothing needs deleting: update and start again.
One setting of the CVN Testnet changes before it starts: its first block's difficulty is 2,500,000 (was 1,000,000), chosen for a publicly announced start. The difficulty rule takes over from the second block either way.
For someone joining a network
- A new node no longer starts a chain of its own by mistake. A mining node that was given seeds asks them for their first block before anything else. If none answers and it has no blocks, it says NOT MINING YET, mines nothing, and carries on by itself as soon as one answers. If they answer and are on a different chain, it stops and says DIFFERENT CHAIN, with what to check. Earlier releases began mining alone without a word. Whoever means to mine a network's very first blocks before its other machines are up adds
--start-alone. - A seed address that cannot be read stops the program and is named. An address written with a port number, a space or
http://used to be left out silently. - The download at start shows its progress bar as the blocks arrive. It was drawn only between passes, and a whole chain usually arrives in one, so it was never seen.
- The installation guide's Windows section is rewritten as two ways, A and B, of which you do one. It says where the download is on the releases page, and has the one command for joining the development network (section 7).
For miners
- The built-in miner no longer slows down on top of a full block. To see whether the newest block had changed, it re-read that whole block on every hash. For an ordinary block that costs nothing; for a full one it cost more time than the mining. It now asks for the block's identifier alone. The fast miner was not affected.
- The private key is not shown as you type or paste it in the text wallet on Windows. The prompt already said so, and it was true only on Linux.
For anyone running a node
- Backups of the chain. Two minutes after it starts, and then once a day, a node saves a copy of its chain into a
backupsfolder beside the program, checks the copy (every block present and linked, each block matching its identifier, the first block this network's, and coins plus vault equal to what was issued), and keeps the newest seven.--check-backup FILEchecks one by hand;--restore-backup FILEputs one back, with the node stopped, and keeps the file it replaced.--backup-hours N,--backup-keep Nand--no-backupschange the schedule. Section 10 ofInstallation_Guide.md. - A block that arrives while the node is catching up is fetched as soon as the catch-up ends. It used to be dropped and not asked for again for up to thirty seconds, which on a 45-second network left the node a block behind for a whole interval.
- Races are counted. A node counts the heights at which it saw two valid blocks compete, logs each as
[RACE]with the share of blocks so far, and reports the count with its newest block (races,races_blocks,races_sincein the reply to/block). The count starts from zero when the node starts. Nothing about which block is kept has changed.
Tested since the last release
- Several real nodes on one machine. A new set of tests starts the program several times over, each copy at its own address, and takes them through seeds, miners, a late joiner, a transfer, a seed that is killed and comes back, and a miner that returns from being cut off. At the end every node must hold the same block, the same work, the same vault and the same coins.
go test -tags multinode -run MultiNode -timeout 30m ./node/. The network these run on exists only in a program built with that tag; this release does not contain it. - Full blocks. The block size limit is 300,000 bytes. On the development network, across six seeds on three continents, five blocks of about 296,700 bytes (76 transfers of 50 outputs each) and six of about 286,000 bytes (16 transfers of 200 inputs each) reached every seed within 5 seconds of being mined, against a block interval of 45.
Checking a download
Every file in this release is signed by GitHub as built by this project's build recipe from this repository at this tag: gh attestation verify cvn_node_windows.zip --repo kalashnikovski/cvn_node. SHA256SUMS_windows.txt and SHA256SUMS_linux.txt list the SHA-256 of each package and of each program inside it, and anyone can rebuild the programs from the tag and compare. Section 11 of Installation_Guide.md says how.
Updating
- Stop the miner or seed.
- Replace the programs with this release's (a seed:
bash /opt/cvn_node/deploy/update_seed.sh). - Start again exactly as before. Keep the chain files and, on a development network started from a Bitcoin block, the same height.
The fast miner itself is unchanged: cvn-6.26.0-2 from https://github.com/kalashnikovski/cvn-xmrig/releases still works.
Everything in this release was made after the last outside review and has not been reviewed by anyone but its authors.
v5.0.0-rc10
Release candidate 10. A test release: the CVN Testnet has not started, and coins on any CVN test network have no value and carry over to nothing.
This release changes no rule. It agrees with release candidate 9 about every block, so machines on the two can share a network, and a development-network (devnet) chain made with release candidate 9 carries on unchanged. Nothing needs deleting: update and start again.
For your wallet
- Recovery words. A private key is now also shown as 24 ordinary English words, which are the same key written another way, with a check built in. A misspelt, missing or misplaced word is refused at once. Wherever a wallet asks for the private key, the 24 words work too. A wallet made with an earlier release has its words as well: in the text wallet, choose "Recovery words and saved key". The word list is the one Bitcoin wallets use (BIP39).
- A saved key. The text wallet can keep your key on your computer in
wallet_key.json, locked with a password. After that, either wallet takes the password where it asks for the key, so the key need not be pasted for every transfer. The file is a convenience and not a backup: keep the 24 words on paper.
Section 4 of Installation_Guide.md explains both.
For miners
- The miner window says what the node is doing. A STATUS line in the heading reads UP TO DATE, CATCHING UP (with the block it has reached, a bar and a percentage) or WAITING. While catching up or waiting, the reason is shown on a line of its own, and the regular line says "Not mining yet" in place of "Mining at 0 H/s". The download at start-up shows the same bar.
- A 60-second average hashrate heads the averages, above 15 minutes, 60 minutes and 24 hours.
- The heading stays on screen however fast lines arrive, and the fast miner's "stale job" lines are no longer shown. They are not faults: they are answers to work the chain had already moved past.
- The fast miner's repeated "not ready" errors while the node is catching up are no longer shown either. A connection lost at any other time still is.
For anyone running a node
- A node no longer treats itself as a peer. A seed given the list of all the seeds, itself among them, used to ping itself, send itself every block, and log every minute or two that it had closed an idle connection to its own address.
- That log line now says what it means: nothing was heard from a node for 90 seconds, so nothing is sent to it until it is heard from again. Nodes do not hold connections open to each other.
- A second copy of a block already held, arriving after the chain has moved on, is no longer reported as a rejected block.
Checking a download
- New: every file in this release is signed by GitHub as built by this project's build recipe from this repository at this tag. With GitHub's command-line tool:
gh attestation verify cvn_node_windows.zip --repo kalashnikovski/cvn_node. - As before,
SHA256SUMS_windows.txtandSHA256SUMS_linux.txtlist the SHA-256 of each package and of each program inside it, and anyone can rebuild the programs from the tag and compare. Section 10 ofInstallation_Guide.mdsays how.
Updating
- Stop the miner or seed.
- Replace the programs with this release's (a seed:
bash /opt/cvn_node/deploy/update_seed.sh). - Start again exactly as before. Keep the chain files and, on a development network started from a Bitcoin block, the same height.
The fast miner itself is unchanged: cvn-6.26.0-2 from https://github.com/kalashnikovski/cvn-xmrig/releases still works.
The recovery words, the saved key and the changes to the miner window were made after the last review and have not been reviewed by anyone but their authors.
v5.0.0-rc9
Release candidate 9. A test release: the CVN Testnet has not started, and coins on any CVN test network have no value and carry over to nothing.
This replaces release candidates 7 and 8, which should not be used. It does not agree with either about every block, so a network must run one release, and it should be this one.
This release changes rules every node enforces. It cannot follow a development-network (devnet) chain made by an earlier release, and it can no longer follow the first test network (testnet-1) at all. Every machine on devnet must move to this release together and start from an empty chain.
Rule changes
- Relief for a late block is no longer inherited. A block dated six minutes or more after its parent is still mined at a halved difficulty, but the next block is worked out from the difficulty its parent would have had without that. Before, one long gap left dozens of nearly free blocks for whoever held the most mining power.
- Difficulty steps are applied as e^x, rounded to the nearest whole number. Before, a miner holding most of the mining power could gain up to 13% by choosing the dates of its blocks. The same patterns now gain nothing. The arithmetic is done in whole numbers, so every node gets the same result.
- The seven-year sweep leaves the smallest coins alone. A coin so small that a fifth could not be taken without leaving less than the smallest coin allowed used to be taken entirely. It is now left as it is. The sweep takes a fifth from a coin or nothing; it never takes a coin whole.
- Plain names inside a block. The fixed texts in a block's reward transaction, and the first block's fields, said things like "immutable consensus valid" and named a "steward assembly" that does not exist. They now say what they are: a reward with no key and no signature, and a first block that pays nothing to nobody. This changes every block's identifier.
- The first test network is retired.
--network testnet-1is refused, and every rule that existed only for it is gone from the program: the first difficulty rule, decimal amounts, the looser block format, addresses without a check, and the uncle share. Two networks remain,cvn_testnet(the default) anddevnet, on the same rules.
How the difficulty changes were found and checked is in audit/FINDINGS_ROUND_4.md and audit/FINDINGS_ROUND_5.md. The sweep change and the names were made after the last review and have not been reviewed by anyone but their authors.
Other changes
- Miners reach the six-minute halving at the same moment. A block may be dated up to two minutes ahead of the clock, so a miner who dated ahead reached the halving before those who did not, and took about 1% more than its share. The program's miner now dates a block ahead for that purpose alone, so nobody has a head start.
- Renew my coins, in both wallets: one step gives the coins that are within a year of their seven-year date a new seven-year count.
- The miner window has colour and plain wording: the heading and figures in green; in the log the
[MINING]tag in purple and[SUCCESS]in green. It says "mining address" and "recent activity" where it said "rig identity" and "live streaming consensus and hardware action regions". Set the environment variableNO_COLORto switch the colour off. - The desktop wallet uses plain wording too: "balance", "your address", "newest block", "send CVN".
- The CVN Testnet is the network the program runs on when none is named. It cannot start until its Bitcoin block is announced; wallets still open.
- The fast miner (the CVN edition of XMRig) is used whenever its
xmrig-cvnfolder is beside the program. No setting is needed. - The miner window shows whether the fast miner's processor tuning was applied.
MINING_GUIDE.mdsection 3 explains the tuning, what it needs and what it costs. - A
miner_config.jsonthat cannot be read is refused, with the line at fault. - The built-in miner checks its own block as it would anyone else's before keeping it.
- The program no longer builds for 32-bit computers, where difficulty would one day stop fitting.
- Two log lines that read as faults and were not no longer appear.
Moving a devnet machine to this release
- Stop the miner or seed.
- Update to this release.
- Delete the development network's files from the CVN folder:
cvn_devnet.db,genesis_anchor_devnet.txtandpeers_devnet.json. Your wallet (miner_config.json) is not touched and your address does not change. - Start again as before, with the Bitcoin height agreed for the restart.
The fast miner itself is unchanged: cvn-6.26.0-2 from https://github.com/kalashnikovski/cvn-xmrig/releases still works.
Checking a download
SHA256SUMS_windows.txt and SHA256SUMS_linux.txt list the SHA-256 of each package and of each program inside it. Section 10 of Installation_Guide.md says how to check them, and how to rebuild the programs yourself and compare.
v5.0.0-rc6
Desktop wallet no longer says MAINNET Three labels on the wallet screen named a mainnet. There is none: the screen now says what each thing is. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
v5.0.0-rc5
v5.0.0-rc5: trial build; batch files in the Windows package have Wind…
v5.0.0-rc2
v5.0.0-rc2: trial build; Windows programs built so they can be rebuil…
v5.0.0-rc1
v5.0.0-rc1: trial build of the packages for the launch rules
v4.3.0
Official Release of the Hardened 1MB Block-Gate v4.3.0 Mainnet Node
v4.2.0
Official Release of the Safe-Sync Hardened v4.2.0 Mainnet Node
v4.1.0
Official Release of the Hardened v4.1.0 Cryptographic Firewall Node