8 months and 1 day later, I've created a PR that adds a job to produce an ARM binary from the CI. However, seeing as eth2.0-deposit-cli seems unmaintained now (no updates or accepted PRs or even comments on issues since April), I'm worried my PR will be ignored.

I leave the following instructions for those who still want ARM binaries. This post ended up being very long, but considering this tool generates your staking seeds/keys, you better be sure you know what you are doing; please read carefully.

Also, I TAKE NO RESPONSIBILITY FOR THIS SOFTWARE. THIS POST IS PURELY EDUCATIONAL AND THE ARTIFACTS PRODUCED BY THE CI PURELY FOR DEMONSTRATION.

You can see the build-linux-arm job for the commit in my PR here.
You can (and should) verify that indeed the "PR / Commit" matches the PR 224 referenced above, and commit c4d5b1c. The "❌" next to the commit is just due to the MacOS build not running in the free tier.
You can (and should) verify that the history of my repo matches the official repo: my commit history. I have two commits as described by the PR.
Even if you don't know how to code, you should review my changes in the PR/2 commits visible here. I didn't change any of the actual code; just updated the dependencies and added the ARM CI job (again, verify that I didn't pull a fast one on you; the commit hashes should be the same).
Then you should be safe (as far as I can think of; if someone notices additional steps which should be taken please post); you can download the artifacts generated by the CI here (verify that this link is the same job as above with the same commit/history).

If you are more paranoid, you could fork the project and make your own CI build. But as far as I can think of, conceptually that doesn't give you any more safety than verifying that I didn't change the history of the repo, and that the two (small) commits I made are not malicious.

If one doesn't trust Circle CI, one could build the binaries themselves using a second, online ARM machine, or an ARM emulator such as QEMU. To be clear, when connected to the internet, one can clone the repository/download the source as is, install the dependencies locally, and run eth2.0-deposit-cli locally just fine. I ran into two issues building the portable binary (to copy over to the offline machine via USB or some other means):

The build requires additional dependencies, and in particular the current version of PyInstaller used in the official repo (3.6) doesn't compile on an up-to-date machine. My [second and last commit (c4d5b1c as above) simply updates the build dependencies so they should compile on an up-to-date ARM machine (tested on Fedora 35 by me, and Ubuntu 20.04 by the CI).
I also had issues where Fedora 35 has Python 3.10 installed, which also failed to build some of the dependencies because stuff got deprecated between Python 3.7 (the minimum/recommended version for eth2.0-deposit-cli). I don't remember what exactly failed, because this was actually the first issue I encountered, but I worked around it by manually compiling Python 3.7.5 (the version used by the CI config - but I'd guess most users wouldn't be familiar with compiling their own Python). Ubuntu seems to only provide ARM ISOs until (and including) 18.04 Bionic (releases), and the Python in Bionic seems to be 3.6 (which does not meet the minimum version required).

As someone who tried to (and did successfully) use a QEMU emulated ARM machine, I am happy to provide instructions (of which I had trouble finding), but I will say it is relatively slow to emulate a different architecture on your presumably x86_64 main machine.

ARM binary #82

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions