As for every release please find here the free to download binaries for 1.34.1 on ARM architecture (aarch64).
GHC used is version 8.10.7 from last august (no more update on v8 since then)
As usual it still needs libsodium, unchanged if you were already using it, but available here if you are new to this. (check my other posts for more details).
Sorry guys, please donât hesitate to ping me if you want binaries updates.
My pool is in sleep right now as I was sick and not impressed with the way the rewards are distributed to technically useless influencers while the really working peeps got to share the crumps of delegations. When that changes I might come back in the game.
In the meantime I keep the binary service up and will proceed to distribute it again no problem. Again, mention me and/or post here for updates.
I have made available both ARM64 and AMD64 pre-compiled binaries of cardano-node as deb packages.
If you want to trust my compilation and just install the binary cardano-node deb then follow the instructions here: https://terminadapool.github.io/deb/
Then it is as simple as:
apt install cardano-node
If you do this on an ARM64 machine then the apt package manager will get the arm64 deb automatically. Likewise on AMD64 machine you will get the amd64 deb.
Note: These deb packages will install binaries in /usr/bin, configuration files in /etc/cardano, and put the blockchain database in /var/lib/cardano, In other words, files will be put in standard filesystem locations like a good package manager should.
The package manager will clean up after itself too. So if you do an âapt upgradeâ when the next version of cardano-node comes out, the package manager will take care of removing the old version, installing the new, and restarting your cardano-node systemd service. If you later want to remove everything then just do âapt purge cardano-nodeâ and the package manager will take care of removing the installed files.
However, I do recommend that you build the deb packages yourself. After all, we are running a decentralised, trustless, secure cryptocurrency system so you shouldnât just trust my compiled debs, you should build your own. So, here is how to do that:
Would maybe be an idea to get the pre-compiled binaries from IOâs build servers to save a bit on CPU, RAM, time, and complexity. (Not an alternative for ARM, though, I fear.)
If you do not audit the source code, there is not much gain in compiling yourself compared to getting pre-compiled binaries from the same source.
Yes, but⌠At least with the source code being publicly viewable you have the benefit of the communityâs many eyes. But with binaries, even if compiled by IOG, there was ultimately one person who compiled them, and maybe he could be evil, and the binary nature would hide this.
But, I guess if IOG documented all compile options / switches used then the haskell compiler will produce an identical binary so then anyone could compile with same options and check the sha256 hash to confirm there were no changes.
We would probably need a bit more work than âjustâ rigorously documented build environment to achieve that, but it would be very beneficial. Just a few independent, trustworthy builders publishing and signing their results and everybody could just install binaries from any source and check a few hashes to be sure.
Iâm a huge fan of open source and a lot of open source projects, but itâs one of my pet peeves to point out if things are oversold, even if they are things I like. The âmany eyesâ making sure that nothing slips through in open source software are often disappointingly few â and cardano-node being a very sparsely documented project in a language very obscure to most people doesnât exactly grow the number of potential eyes.
On the other hand, I hope that more than one person looks at IOâs build server configuration. (That they use build servers and not just upload what one of their developers has compiled on their own development machine â from exactly that specific tag of sources with exactly those requirements in place (pinky swear!) â already makes it a bit better, a bit more secure.)
I believe my debian build system switches on some address space layout randomisation when I pass âDEB_BUILD_MAINT_OPTIONS = hardening=+allâ. But if I recompile I do seem to get the exact same haskell binary.
I am trying to learn. I think I am starting to like Haskell but I am never going to be good enough to audit code like Cardanoâs.
I studied computer science at a university that put a huge emphasis on the functional paradigm (though not using Haskell, but their own home-grown functional language at the time). Iâve written a dissertation using loads of category theory â which inspired a lot of Haskellâs design.
Is still canât stand it. There are so many design choices making it hard to read for me, so many implicit things you just have to know, ⌠And itâs obviously still possible to over-engineer with it, to scatter the code over hundreds of source files through a huge directory tree, where only the resident devs still have an overview, what is where and why (if there even is a why), âŚ
Maybe one day Haskell will win the place of second language I really want to know against Scheme, but until then Iâll stay with Python if I have a choice.
Hi, Captain.
Can we no longer receive your new version file (ARM64 complied binaries)?
Everyone is waiting for you.
Be strong, Captain.
You are our hero.
We will wait for you.
But understand that you are trusting that I didnât modify the code in a nefarious manner when building these binaries. (Which I didnât do.)
Also note that these deb packages will place the binaries, configs, and chain data in standard filesystem layout which might be different to what you expect if you are following certain community guides.
You can build the deb packages yourself by following the directions here:
Is it possible to import the ARM64 deb from a normal Ubuntu environment rather than an ARM64 machine?
I simply need only ARM64 compiled cardano-cli and node files
