Releases: cairnchain/cairn
Release list
v0.11.1
chore: 0.11.1, for what changed since v0.11.0
1 commits since v0.11.0:
1 fix
What is different in the programs:
fix: cairn-wallet new prints the new key's address, not the key, on the line that says address (#269)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
SHA256SUMS, published beside the archives, is signed the same way. Once it
has passed the same check, it vouches for every archive it lists:
gh attestation verify SHA256SUMS --repo cairnchain/cairn
shasum -a 256 -c SHA256SUMS --ignore-missing
Comparing hashes without the first line shows only that a download arrived
whole: whoever could replace an archive could replace the list beside it.
This is a test network
testnet-7 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.11.0
feat: testnet-7, because a place in the hot set was free to a miner, a block did not commit to its signatures, and an address showed its key (#268)
Testnet-7, released as 0.11.0. The test network starts over, because a place in the hot set was free to a miner, a block did not commit to its signatures, an address showed its key, and two hash domains were told apart only by length. Every block of testnet-6 is invalid under these rules; nothing carries over but keys.
What changes for everyone
- A place in the hot set has a price. Every new place a transfer takes burns 6 000 pebbles (0.00006 CAIRN) that no coinbase can claim, so a miner stuffing its own blocks pays like anyone. Emptying the hot set now costs about 7.8 CAIRN destroyed. The price is a fee paid once, when a payment is made, by whoever takes the place: a note is never destroyed, expired or charged rent. An ordinary payment's floor is 8 230 pebbles, of which 6 000 are burned; the wallet says so before paying, and the explorer shows what each block burned.
- An address is the hash of a key, written as Bech32m text:
tcairn1...on the test network,dcairn1...on devnet,cairn1...later. A mistyped character or two swapped neighbours are refused, where one typo in sixteen used to be some other valid address. The key appears on the chain when a note paid to an address is first spent; the wallet keeps one address, so its change then sits behind that key (a fresh key per payment is a decision tracked in the open questions, not started). Old 64-hex keys given to--mineare converted, andinstall.shwrites the address back into the unit. - A block commits to every byte of its body. A copy of a block with another signature, key or proof no longer matches its header and is refused at the door rather than held and tried; some such copies used to be valid.
- Hash domains are told apart by name, for the sampling draw and the empty leaf of the cold set.
- Protocol version 10. The handshake loses the tip nothing read (76 bytes), and a peer on another version is dropped on its version, never read as a broken frame or held against its address.
- Devnet moves to a new marker, and the old one is named devnet-1, so an old devnet node or directory is told plainly where it is.
Networks
testnet-7: marker0x4341525A, first block0000000cd9f098b5467d2cfa0c70b3c2a874fde9d436e6fc92bc26002ddc15bb, minted 30 September 2026 at 20:40:58 UTC.devnet: marker0x43415245.
A 0.10 or older node meets testnet-7 as another network and is refused without its address being held against it; 0.10.0 already names testnet-7. A 0.11 node on a testnet-6 or devnet-1 directory refuses it and names it; install.sh and explorer.sh set the old chain aside. Wallet history.dat and pending.dat files from before the address format are set aside, not read; key files carry over.
How it was made
Four units (#259, #261, #263, #267) on the integration branch consensus/testnet-7, each with tests that failed first and targeted mutation, then an enumerating audit in three parts (2026-09-30-consensus/: 323 items, no critical finding, one high, three medium) whose findings are fixed in #265 and #266, and main's own fixes brought in by #264. The price was measured on a devnet flood harness (cargo run --release -p cairn-chain --example flood): a cold witness adds 596 bytes, 6 000 pebbles at the floor rate.
Local gate on this branch: cargo fmt --all -- --check 0, RUSTFLAGS="-D warnings" cargo clippy --workspace --all-targets --locked 0, cargo test --workspace --locked 0.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
SHA256SUMS, published beside the archives, is signed the same way. Once it
has passed the same check, it vouches for every archive it lists:
gh attestation verify SHA256SUMS --repo cairnchain/cairn
shasum -a 256 -c SHA256SUMS --ignore-missing
Comparing hashes without the first line shows only that a download arrived
whole: whoever could replace an archive could replace the list beside it.
This is a test network
testnet-7 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.10.0
chore: 0.10.0, for what changed since v0.9.4
4 commits since v0.9.4:
2 test
1 fix
1 feat
What is different in the programs:
feat: testnet-7 is named before it starts, so a node left on testnet-6 says where its peers went (#260)
fix: a node counts only introduced peers, makes room for a visitor once it has spoken, and catches up without waiting a patience a window (#256)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
SHA256SUMS, published beside the archives, is signed the same way. Once it
has passed the same check, it vouches for every archive it lists:
gh attestation verify SHA256SUMS --repo cairnchain/cairn
shasum -a 256 -c SHA256SUMS --ignore-missing
Comparing hashes without the first line shows only that a download arrived
whole: whoever could replace an archive could replace the list beside it.
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.9.4
chore: 0.9.4, for what changed since v0.9.3
19 commits since v0.9.3:
13 fix
3 ci
2 test
1 docs
What is different in the programs:
fix: a newcomer holds the tip to the hardest header of its run, so a fresh draw of the sampled questions costs work again (#255)
fix: a payment is followed until nothing can undo it, never called unpaid on blocks unread, and a restored account survives a node catching up (#254)
fix: an archivist keeps its blocks, a start keeps what it cannot trust, and what a peer volunteers renews nothing (#253)
fix: a heavier branch that weighs more than one window is fetched a window at a time, and where the fix branches met in sync says what is true (#251)
fix: a node spreads its connections across neighbourhoods and blames a host for what it did (#243)
fix: a node that falls off the tip notices, asks for the branch that won, and says why when it cannot (#240)
fix: a wallet's node tells a stranger nothing about whose money it follows, and the documents say what the network learns (#249)
fix: the HTTP server refuses what it cannot read as one request, a batch removal folds each path once, and a slow refusal costs a dial wave, not a round (#247)
fix: work a peer asks of this node is paid for before it is done (#242)
fix: the wallet's account undoes only what a reorganisation took, and says which way the money went (#248)
fix: a newcomer on a real network is handed a ledger, and a forged copy of a side block keeps no node off the heavier branch (#244)
fix: a peer counts as having answered only together with the paths its answer brought (#241)
fix: a payment the wallet sends is written down and followed until the chain settles it (#238)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
SHA256SUMS, published beside the archives, is signed the same way. Once it
has passed the same check, it vouches for every archive it lists:
gh attestation verify SHA256SUMS --repo cairnchain/cairn
shasum -a 256 -c SHA256SUMS --ignore-missing
Comparing hashes without the first line shows only that a download arrived
whole: whoever could replace an archive could replace the list beside it.
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.9.3
chore: 0.9.3, for what changed since v0.9.2
8 commits since v0.9.2:
7 fix
1 chore
What is different in the programs:
fix: a start stops on what it cannot read instead of deleting it, and says what it did with the disk (#236)
fix: a timestamp may run ten blocks ahead, and a handover is held to the history its headers commit to (#237)
fix: an update keeps every setting, a release builds the commit it tags, and a miner does not mine alone (#235)
fix: the explorer says why something on the chain is not here, and stops when its node stops (#234)
fix: a wallet's backup is its key and its account, and neither file is written over or through (#233)
fix: every constant read at two places asks one question, in four places it did not (#231)
fix: a failure the programs turned into an ordinary answer is said, in thirteen places (#230)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
SHA256SUMS, published beside the archives, is signed the same way. Once it
has passed the same check, it vouches for every archive it lists:
gh attestation verify SHA256SUMS --repo cairnchain/cairn
shasum -a 256 -c SHA256SUMS --ignore-missing
Comparing hashes without the first line shows only that a download arrived
whole: whoever could replace an archive could replace the list beside it.
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.9.2
chore: 0.9.2, for what changed since v0.9.1
95 commits since v0.9.1:
64 test
23 fix
7 docs
1 chore
What is different in the programs:
fix: the account writes down where the winning branch put a note (#227)
fix: a shard past its deadline is run again (#214)
fix: a hanging mutant costs one suite's time, not five (#211)
fix: a clock step back asks nothing before it pulls the moments back (#207)
fix: the full-disk audits run somewhere (#204)
fix: a mutant that allocates without end is a failed test, not a dead runner (#200)
fix: a count in roman figures cannot run past its end (#195)
fix: the weekly mutation run finishes, and says when it has not (#193)
fix: a length that will not read does not buy the record beside it a pass (#188)
fix: a loop that spins on the branch that cannot happen (#174)
fix: a maximum written as a branch on the wrong pair, and a stale reason on a guard (#145)
fix: a sweep test that raced its own patience (#150)
fix: a join that never read the first block (#149)
fix: a verdict list one test short, and two paragraphs out of order (#148)
fix: the one price table in the allowance that had a default (#143)
fix: an address walked twice under the chain lock, and two statuses sent as "Error" (#146)
fix: an amount error for an amount nobody sent (#141)
fix: a guard in the header log that could not fire, and two sentences about the store (#140)
fix: the refusal queue that lost its last callers, forty places in (#137)
fix: one DNS answer could fill the address book with seeds nothing displaces (#139)
fix: a catch-up discount a peer re-armed with its own blocks (#138)
fix: a depth guarantee held against a limit no network is promised to run (#136)
fix: a full refusal table that refused nobody (#133)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
Or compare hashes against SHA256SUMS, published beside the archives:
shasum -a 256 <the archive>
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.9.1
chore: 0.9.1, for what changed since v0.9.0
19 commits since v0.9.0:
11 fix
4 test
3 docs
1 chore
What is different in the programs:
fix: a 405 naming the methods this server stopped refusing (#132)
fix: eight shards, measured, is too few for the weekly run to finish (#130)
fix: two shipped texts showing a status line this node stopped writing (#128)
fix: a rescue from a retired network that handed back a retired network (#129)
fix: a gate that checked a target nobody ships and missed two that are shipped (#126)
fix: a rule the list was written to justify, not applied inside the list (#125)
fix: an eighth of the mutants was never tested, behind a job that looked red (#124)
fix: a default port whose doc named two readers and had none (#123)
fix: an address read two ways, and the error written for it built nowhere (#121)
fix: three fallbacks that cannot fire, and one that was not a fallback at all (#115)
fix: a pool ceiling that measured the wire, and a field asked two questions (#114)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
Or compare hashes against SHA256SUMS, published beside the archives:
shasum -a 256 <the archive>
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.9.0
chore: 0.9.0, for what changed since v0.8.1
14 commits since v0.8.1:
7 fix
4 test
1 perf
1 feat
1 docs
What is different in the programs:
fix: three numbers copied where five places derive them (#111)
fix: a length that was asked one question of two (#110)
fix: a third way in that consulted neither, then one of the two (#109)
feat: how long this build has, read off its own rules (#108)
fix: an attack surface understated by its own header, and held to the code now (#105)
fix: a list that stops short about money, and says nothing (#104)
fix: a fact kept twice, and the copy nobody read (#102)
fix: a ceiling that waited on a bigger one, and a walk that hashed for its key (#98)
perf: signatures checked again under the chain lock, twice a minute (#100)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
Or compare hashes against SHA256SUMS, published beside the archives:
shasum -a 256 <the archive>
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.8.1
chore: 0.8.1, for what changed since v0.8.0
8 commits since v0.8.0:
5 fix
3 test
What is different in the programs:
fix: three limits read after the thing they limit (#96)
fix: a pool that takes what no block can carry, for free and for good (#95)
fix: one reader of an address, and a cross-check that asked half the question (#94)
fix: a replay that carried on past the one error it exists to find (#91)
fix: the other door into awaiting, which my own repair did not reach (#90)
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
Or compare hashes against SHA256SUMS, published beside the archives:
shasum -a 256 <the archive>
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.
v0.8.0
chore: 0.8.0, for what changed since v0.7.1
14 commits since v0.7.1:
11 fix
1 perf
1 feat
1 docs
What is different in the programs:
fix: half the grace window's rule, asked as though it were the whole (#87)
fix: a branch that got shorter, agreed with at every height (#86)
fix: a proxy this server called a stranger (#85)
fix: a megabyte from somebody who had not said who they were (#84)
fix: an address nobody holds, taken as an address (#83)
fix: what a node was told, and what it told back (#82)
fix: five ways the wallet answered a question nobody asked (#80)
fix: three checks that were written and not reached (#81)
feat: a chain nobody could watch moving (#79)
fix: a usage text for a resolver that was asleep (#78)
perf: a pass over the whole archive, once for every note on a page
fix: a mark armed on one condition and cleared on another
fix: eleven bits that still emptied the log
Which file to take
| Your machine | File |
|---|---|
| Mac, 2020 or later | cairn-macos-apple-silicon.tar.gz |
| Mac, older | cairn-macos-intel.tar.gz |
| Linux, ordinary server or desktop | cairn-linux-x86_64.tar.gz |
| Linux, ARM server or Raspberry Pi | cairn-linux-arm64.tar.gz |
| Windows | cairn-windows-x86_64.zip |
Each archive holds a node, a wallet, the explorer that serves the website,
both licences, a VERSION file, and a README.txt that says what to do with
them. The names carry no version on purpose, so a link to the newest release
never has to be rewritten:
https://github.com/cairnchain/cairn/releases/latest/download/cairn-linux-x86_64.tar.gz
This release keeps its own copy of every file under its own tag, so it stays
reachable after a newer one arrives.
Checking what you downloaded
Your operating system will warn you about these programs. It is right to:
they carry no certificate, because a certificate is something bought rather
than earned. Here is the check that is actually worth something.
gh attestation verify <the archive> --repo cairnchain/cairn
That asks GitHub which commit and which workflow produced the file, and
GitHub answers from its own records rather than from anything we control.
The build ran in the open and its log is on this repository.
Or compare hashes against SHA256SUMS, published beside the archives:
shasum -a 256 <the archive>
This is a test network
testnet-6 money is worth nothing, is meant to be worth nothing, and the
network will be reset. Nothing on it carries over.