v1.11: the first binaries that call the unit VARVAlso in this post: the swap toolkit published as v1.10, which never had an
announcement of its own, and a second place to read the sourceThis project was renamed from BigCoin to Varve on 20 November, and the source
has said Varve ever since. No compiled program did. v1.10 added a toolkit and
rebuilt nothing, so every binary published before this one labels amounts BIG.
These are the first that do not.
That is the whole of the release.
No consensus rule, no network rule, no
default and no RPC method changed. Every release from v1.7 onward accepts
exactly the same blocks and sits on the same network, and all of them stay
published. If your wallet saying BIG does not bother you, there is nothing here
you have to install.
Links and digests are at the foot of this post, as always.
What is in it, and what is notWallet amounts BIG -> VARV, mBIG -> mVARV the visible change
bigcoin-cli -version Varve Core RPC client version v31.1.11
Node user agent /Satoshi:31.1.11/ was /Satoshi:31.1.9/
Documentation English only; three translations in doc/ are gone
Everything else unchanged
There is no new feature here and no fix anybody is waiting on. The diff from
v1.10 is 43 files, and with one exception every line of it is text a human
reads: comments, log messages, the help in the two mining scripts, the readme,
three deleted translation files, and a screenshot retaken from this build. The
exception is the string that names the unit, which is one line of code:
-const std::string CURRENCY_UNIT = "BIG";
+const std::string CURRENCY_UNIT = "VARV";
That string is what the wallet prints next to an amount, and what some RPC
help text and error messages spell out. No RPC method, argument or result
changed shape, and no amount anywhere is a different number.
Upgrading without resyncingWorth spelling out, because the folder is named differently now and the easy
mistake costs you a full resync.
The release archives unpack into
Varve-win64 and
varve, where
v1.9's unpacked into BigCoin-win64 and bigcoin. The bundled mining scripts
keep the chain and the wallet in a
data folder next to themselves, so a
fresh folder means a fresh empty chain:
Windows stop the node first: bigcoin-cli.exe -datadir=data stop
then copy the .exe and .dll files out of Varve-win64\ into the
folder you are already running, keeping your existing data\
(or unpack the zip and move your data\ folder into Varve-win64\)
Linux stop the node, then the same thing: the binaries are new, the
data directory is yours and does not move
Your wallet file is in data\wallets. Nothing in this release touches it
and nothing reads it differently. There is no migration step, no reindex and no
database change: the same data directory works under v1.9 and v1.11, in both
directions.
The label is the only thing about your coins that changed, and it changed
nothingBalances, transaction history, addresses, the data directory and bitcoin.conf
are untouched. No coin moved when the name on the amount changed.
Addresses are still big1... and B... and they are staying that way.
Renaming an address prefix would make every address already written down, in
every file and every message, unusable. That is not a trade worth making for
tidiness, and I am not making it.
What was said in advanceWhen I announced the rename I wrote that if the unit label ever moved, the old
one would keep being accepted indefinitely and it would be announced before it
shipped rather than after. The first half is kept exactly, and more simply than
I expected: no part of this software has ever taken a unit name as input. RPC
amounts are numbers, addresses did not change, and the label exists only where
the wallet prints it. There is nothing that could stop accepting anything.
The second half, honestly: the specifications table on the site has said since
20 November that the label changes in the next release, and the build landed on
the 21st, so the notice was published before the binaries were -- but not here
first, and it should have been. None of this is a consensus matter. The
30-day promise is about changes a node validates; it still stands, and
this is not one.
Three strings keep the old name, permanentlyNetwork magic BIGC
Genesis coinbase text BigCoin genesis 21/Oct/2026
yespower pers string BigCoin/yespower1.0
These are deliberately outside the rename and will stay outside it. The first
is how a node recognises its own network, the second is inside the block that
every node hashes and checks, and the third is an input to the proof-of-work
function itself -- it is hashed into every block from the activation height
onward, so editing it would reject the entire chain rather than relabel it. The
source says so where the string is defined, in a comment put there to stop a
future tidy-up: it is not prose, and a rename must never touch it.
The file names on the downloads page follow the same rule in the other
direction: BigCoin-win64-v1.9.zip and the rest keep their names and their
digests forever, because those digests are printed in this thread next to
those names, and renaming a published file invalidates every check anyone has
already made against it.
One consequence of that rule is worth stating before somebody hits it. The
standalone mine-bigcoin-v1.8.cmd on the downloads page is unchanged and keeps
its digest. The copy of that script inside the v1.11 zip is not the same bytes
any more: it prints Varve and VARV where the standalone one prints BigCoin and
BIG. Nothing else about it differs, and I would rather say so than publish a
fifth standalone file for a difference nobody has to care about.
There was never a 31.1.10: v1.10 published no program, and the release number
and the program version have been the same number since v1.7, so the gap stays
unused rather than breaking that.
English only from hereThe three Japanese translations in doc/ and the Japanese page on the website
are gone. A translation that quietly disagrees with the English it was made
from is worse than no translation, and those had started to drift. The readme's
wallet screenshot was retaken from this build, so the window in the picture
says VARV like the one you will be looking at.
v1.10: swapping coins for BTC with nobody holding either sideThis went up on 20 November and never got a post of its own. It is seven Python
files, it adds no node and no consensus rule, and it is inside the v1.11 source
archives at contrib/bigcoin/swap/ -- there is no separate download and nothing
to install twice. The two v1.10 archives stay published, with the digests at
the foot of this post.
Ground rules first, because they matter more here than in any other release:
nothing is for sale. There is no market in this thread, no price, no
rate and no price talk, I am not a counterparty, and every amount in the
documentation is a placeholder. No exchange listings are sought.
What it does. Each side pays into one output on their own chain, and
that output can be spent two ways:
claim whoever knows a 32-byte secret, and holds the claim key
refund the person who funded it, but not before a deadline
Both chains use the
same secret, so the moment one side claims, the
secret is sitting in a public block and the other side can claim too. If
anybody walks away, both deadlines pass and both sides recover their own coins.
At no point does either party hold the other's money, and there is nobody to
run off with it, because there is no third party in the protocol at all. The
contract is one miniscript descriptor:
wsh(or_i(and_v(v:pk(CLAIM),sha256(H)),and_v(v:pk(REFUND),after(T))))
That is a plain P2WSH output. Your counterparty does not have to trust this
program's description of what they are paying into -- the script is visible on
a block explorer, including one that is not mine. No consensus change was
needed: CHECKLOCKTIMEVERIFY and CHECKSEQUENCEVERIFY have been buried since
height 1 and segwit has been active from height 0.
No wallet passphrase, ever. Swap keys are generated locally and live
only in your swap file. Signing goes through descriptorprocesspsbt, which takes
a private key inline in the descriptor, so your wallet is never unlocked and
nothing is imported. The flip side, stated plainly:
the swap file is a
bearer secret. Between funding and settling, whoever has that file can move
the money. Back it up somewhere you control, and delete it when you are done.
What you need: Python 3.8 or newer, standard library only; a Varve node
and a Bitcoin Core node, both with -txindex=1. That flag is not optional -- the
tool fills in each input's witness_utxo from the node, and once an output has
been spent the UTXO set no longer knows anything about it.
Verify it before you use it. Every module checks itself when you run it
directly, against published test vectors and the BIP380 checksum vector. Then
there is an end-to-end rehearsal that starts two throwaway private chains, runs
a complete swap through both the claim path and the refund path, and checks 28
things about it -- including that a party without the secret cannot claim, that
a swap file with an address edited into it is refused rather than funded, and
that a refund is refused before its deadline and succeeds after it. It uses its
own temporary data directories and ports and touches nothing of yours:
python keys.py
python htlc.py
python psbtfield.py
python varveswap.py selftest
python rehearse.py --bigcoind /path/to/bigcoind
The Bitcoin half was tested against a stock Bitcoin Core. Both chains in
the rehearsal are Varve regtest chains, so that script alone cannot answer the
question this release rests on: does an unmodified Bitcoin Core sign and
finalise our contract? It was tested separately against a released Bitcoin Core
32.1 binary -- unmodified, signature-verified, reporting /Satoshi:32.1.0/ --
with Varve regtest on one side and Bitcoin regtest on the other:
45 checks,
both the claim path and the refund path. Core parses the descriptor and
reports it solvable, derives the same address the swap file recorded, signs and
finalises the claim from the preimage carried in the PSBT with no patch and no
custom build, and refuses the time-locked refund before the deadline while
citing the chain's median time.
Every spend in that run also had to cross a P2P connection and be accepted by a
second node that holds no wallet and has never seen the descriptor. That is
worth more than the broadcasting node's opinion of its own transaction, because
-acceptnonstdtxn defaults to 0 in Bitcoin Core 32.1 on
every chain,
regtest included: the node passing judgment is applying mainnet's relay policy.
What is still untested: mainnet, on either chain, and one thing no test
network can supply -- a live fee market. Fees in the rehearsals come from
-fallbackfee, so nothing here has paid a fee anyone competed for.
Treat your first mainnet swap as the experiment it is, and make it a small
one.Put Varve on the initiator's leg. Either direction works and the tool
asks each node what chain it is on rather than assuming, but the six-hour gap
between the two deadlines is checked once against the wall clock, while the
deadlines themselves are enforced by each chain's median time past, which
trails the wall clock by roughly five and a half block intervals. Measured on
20 November, Varve's median time past was 1h43m behind the wall clock where
Bitcoin's sits near an hour, and Varve's difficulty takes days to answer a fall
in hashrate -- the ASERT half-life is two days -- so intervals stay long and
the lag stays wide. At an average interval above about 65 minutes the whole six
hours is gone. Put Varve on the initiator's leg and that lag works for the
responder instead of against them. It is also the only arrangement the
rehearsal tests.
Risk, stated plainly. A reorganisation deeper than the confirmations you
waited for breaks this, and on a chain this size that is cheap to buy. One
ordinary 8-core desktop does about 7,000 H/s, and this network has never run at
more than a few multiples of that. Three or four machines like that outrun
everything else on it combined, which is a few hours of rented cloud CPU. So
waiting for confirmations here buys you exactly that much and no more: six
confirmations is not six confirmations' worth of security, it is about an hour
of somebody's rental bill. Size what you trade to what you would tolerate
losing outright. That is a property of a young proof-of-work chain and not
something a tool can fix, and it works in your favour on the Bitcoin leg and
not at all on the Varve leg -- whoever is receiving coins on this chain carries
it.
The other things that can go wrong:
-
You miss your own claim deadline. Then the counterparty refunds and
you do not. Claim early; do not leave it to the last block.
-
You lose the swap file between funding and settling. The money is then
unspendable by anyone, forever.
-
You fund before checking the fingerprint. Both sides print the same
fingerprint of the agreement before anyone pays; if the two differ, stop. Do
not fund. One changed character changes the fingerprint.
-
Either node is not fully synced. A node behind the chain reports a
healthy-looking depth for a transaction the rest of the network has not seen.
-
This coin has no promised value and no market. There is no exchange,
no market maker and no buyer of last resort. If you acquire some and later
want out, your only exit is another private trade with someone who wants in,
and there may not be one. Anything you pay could be a total loss, and nobody
needs to buy any: mining is open to everyone.
And what the toolkit is not:
not a service no server, no website, no API, no operator
not custody no key generated here ever leaves your machine
not anonymous both legs are ordinary on-chain transactions, and the claim
publishes the secret that links the two
One detail for anyone reading the files at tag v1.11: they are the v1.10 files
with one change, the readme's examples now spelling the unit VARV where they
said BIG. The tool's own help still shows BIG. Both work -- a leg label is a
short name you choose when the swap is proposed, and the tool takes either.
Source, and a second place to read itgit clone https://varve.mine.bz/git/bigcoin.git
cd bigcoin
git diff --stat v1.10 v1.11
That prints the whole of this release: 43 files changed. To review the fork
against Bitcoin Core rather than just this release, the comparison from the
earlier posts, with the tag moved on:
git remote add upstream https://github.com/bitcoin/bitcoin.git
git fetch --depth=1 upstream tag v31.1
git diff --ignore-cr-at-eol --stat v31.1 v1.11
59 files. The flag matters because the source archives are packed on Windows,
so 14 files that upstream keeps as CRLF are LF in this repository; without it
the same command says 73 and the extra 14 differ by nothing but line endings.
VERIFYING.md inside the archives spells that out.
Tag v1.11 holds exactly the published archives, file for file. Its history
continues from the v1.10 commit, so no published history moved and every tag
this repository has already served still resolves to the object it always did.
The source now has a second home, because one host is one host:
https://codeberg.org/takamoto/varve
It is a mirror and not a second source of truth. The repository above, on the
same server as the downloads, is the one I push from; the mirror never pushes
back, and the clone URL that has always been published is unchanged and is not
going away. The reason it exists is simple enough: if that one server is down,
unreachable from where you are, or filtered by something between you and it,
the source is still readable somewhere.
A mirror you cannot check is worth very little, so here is how to check this
one. A commit id pins the entire tree, so two lines settle it:
git ls-remote https://codeberg.org/takamoto/varve.git refs/heads/main refs/tags/v1.11
6ac9e40b9140cd04e06fe03db70b1599854bd15b refs/heads/main
1d118d0b9bc1a4e6ccbf0a8fe22f20faabf4502f refs/tags/v1.11
If those match what is printed here, the mirror is this repository, down to the
byte. If they ever do not, believe this post and the digests below -- they are
on a forum I do not host, which is the whole point of printing them here.
On the softwareAny future consensus change still gets at least 30 days between the notice and
the activation height, and the height goes in the release notes and in this
thread. This release is not one: it changes nothing a node validates.
The coin has no promised value. The only way to get it is to mine it.
Links and digestsBlock explorer https://varve.mine.bz/
Downloads https://varve.mine.bz/downloads
Mining status https://varve.mine.bz/mining/status
Faucet https://varve.mine.bz/faucet
Running a node https://varve.mine.bz/node
Source git clone https://varve.mine.bz/git/bigcoin.git
Source (mirror) https://codeberg.org/takamoto/varve
The same things by IP, unchanged and permanent:
http://133.242.139.204/
http://133.242.139.204/downloads
http://133.242.139.204/mining/status
http://133.242.139.204/faucet
http://133.242.139.204/node
git clone http://133.242.139.204/git/bigcoin.git
Seed node 133.242.139.204:8338
Seed node (Tor) rjxywola2kupk4rp67qzidqiuxwvr76xmri5zimt6ecrvhx4xv5t7wyd.onion:8338
ANN thread https://bitcointalk.org/index.php?topic=5598514
Mining guide https://bitcointalk.org/index.php?topic=5599204
yespower thread https://bitcointalk.org/index.php?topic=5600188
v1.11, published 21 November 2026:
347a8f51d7b1770e8d2d82b8e99d80f82e432f3258ff159b7f8595719e589788 Varve-win64-v1.11.zip
40c90c692431ec0fb45d62a102340dd23501ee4219c446b6753479e7482ccae1 varve-linux-x64-v1.11.tar.gz
4b76899fb8be633e60d4621917b9c82a2112a92e96343c21865216bf99cbdd8c varve-source-v1.11.zip
0f705a4eec25b49919ab98f8f422adaf724fd7d3ddbb07a177abd1a5689af5d2 varve-source-v1.11-unix.tar.gz
v1.10, the swap toolkit, published 20 November 2026:
6bd8fa23735f799ad2444aebf9224bafa90b48f09073922b318fabc04a304641 varve-swap-v1.10.zip
c31d74e4637e940d0df6fabe0a495f4823c14a200392936ab504c13745de1f72 varve-swap-v1.10.tar.gz
v1.9, still published at the same URLs with the same digests:
f3999cc9d6da8a032a4ba8d2023a098e18dfeabe90e0369693b451415c5fd5cb BigCoin-win64-v1.9.zip
cf85ed4f4b158e3c8c292052025252182c8f80d037a8419f5ef6bea5540b5ba8 bigcoin-linux-x64-v1.9.tar.gz
d287776d917d0d22c063ffbc6c6ed91bba3fe96b8c9f385a594a2de1caf790bb bigcoin-source-v1.9.zip
d44066c8bf5d70404b66d21d6689af4d99a13695b1bbf047816c47cc6b99c693 bigcoin-source-v1.9-unix.tar.gz
b4973f0c5c6a6f59c276f899a21a7453a60e35e3b916d222e55fa27647c4bf26 mine-bigcoin-v1.8.cmd
67d55214e84a5571358c09d2c875f0b49d94a08307ac32e93e79cc56fec574dd mine-bigcoin-v1.8.sh
These digests are published here as well as on the downloads page on purpose:
this thread is not hosted on my server, so if that server were ever compromised
the attacker could rewrite an archive and the hash page together, but not this
post. Nothing published has been replaced, and the rename did not replace
anything either.
- Masashi Takamoto