Skip to content

Instantly share code, notes, and snippets.

View newtonick's full-sized avatar

Nick Klockenga newtonick

View GitHub Profile
@newtonick
newtonick / SeedSigner-0.8.0-rc1-testing.md
Last active August 16, 2024 01:36
SeedSigner 0.8.0-rc1 testing

SeedSigner Release Testing Checklist

Software Versions Used

SeedSigner Release Version Number: 0.8.0-rc1

Image sha256 hash: 8e687702b6dffbbcdc51639f3428aabe9bb2509c3ed6932d26119182225accf2 seedsigner_os.100a974.pi0.img

Coordinators and versions used in testing

@newtonick
newtonick / seedsigner-os-reproducible-build-steps.md
Last active July 19, 2023 03:10
SeedSigner OS Reproducible Build PR Testing

SeedSigner OS Reproducible Build PR 51 Testing

SeedSigner/seedsigner-os#51

SeedSigner OS reproducible build allows creation of the image to be compiled and assembled deterministically. This makes it possible for multiple people to compile the same source code into identical binaries. This also means SeedSigner the person (or any other SeedSigner contributors) don't need to be solely trusted for the image that most people run on thier SeedSigner. This trust can be distributed through others attesting they too can produce the same image byte for byte. Also for those who compile the image themselves, they have a way to verify the image produced is identical to the one released.

Steps to create a reproducible SeedSigner image

Clone the SeedSigner OS repo from github. Do this with a recursive clone to pull the buildroot submodule at the same time. By default this will create a directory in the current working directory named seedsigner-os.

### Keybase proof
I hereby claim:
* I am newtonick on github.
* I am newtonick (https://keybase.io/newtonick) on keybase.
* I have a public key whose fingerprint is 0849 D32D 79EC 01A4 EE87 FEF5 8521 D9A0 D54E 7D50
To claim this, I am signing this object: