https://xitter.cf/t.co/kUkqXycBcQ 🇿🇦 || 🟦

Joined January 2014
Cash on the internet. No auto-updates.
7
9
433
ReproducibilityMatters retweeted
A new release candidate of Bitcoin Core, v32.0rc4, is available for testing. This is a new major release, and follows v31.1. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
12
22
1
83
7,318
ReproducibilityMatters retweeted
A new release candidate of Bitcoin Core, v32.0rc3, is available for testing. This is a new major release, and follows v31.1. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
12
26
4
116
12,303
ReproducibilityMatters retweeted
A new release candidate of Bitcoin Core, v32.0rc2, is available for testing. This is a new major release, and follows v31.1. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
36
40
12
138
16,923
32.0rc2 testing binaries are now available bitcoincore.org/bin/bitcoin-… Includes the new getopenrpcinfo RPC (shoutout @willcl_ark). It returns a machine-readable OpenRPC spec of the entire RPC API, useful for generating client code and docs or diffing between releases.
2
12
31
1,119
Cash on the internet. No auto-updates.
6
141
ReproducibilityMatters retweeted
BIP54 would make it so Bitcoin's PoW actually provides tight bounds on worst case resource usage. Read Pieter's latest post on Delving.
5
16
3
75
16,782
ReproducibilityMatters retweeted
I wrote a blog post on the recent exploits in the Bitcoin ecosystem, how Bitcoin Core is holding up, and how I think the community can get ahead of the models: dergoegge.de/blog/somethings…
4
45
9
153
61,020
ReproducibilityMatters retweeted
More progress being made by @remix7531 on the libsecp256k1 Schnorr Signature (BIP 340) formal verification front: github.com/bitcoin-core/secp….
4
12
38
2,321
ReproducibilityMatters retweeted
Hopefully it’ll only take one round of trying closed source “security through obscurity”, to convince everyone that this is (certainly nowadays) mostly pointless/confusing, and undermines the whole “don’t trust, verify” ethos. The way forward is writing robust, open source code.
1
7
1
39
5,726
Reproducible builds give you a source code -> binary mapping. Without this, any open source project needs to pick a single “trusted” person to produce binaries; where no one else can even double check that person compiled the source code they claimed to have compiled (given no reproducibility). So even if you don’t trust the contents of a binary, reproducible builds still solve the problem of a project deciding which binary to make available to end users, given its source code.
1
6
28
1,468
Cash on the internet. No auto-updates.
2
6
2
21
4,121
Would be great to get some more testing on more diverse x86_64 and aarch64 systems here. Already run this on some of my hardware. Solving linux platform portability has been a long standing goal and one of the things that kept me interested in bitcoin development.
I’ve pushed up a new round of -static-pie Bitcoin Core binaries that I’d like to get more testing of! More details on the mailing list: groups.google.com/g/bitcoind…
6
17
1,007
ReproducibilityMatters retweeted
I’ve pushed up a new round of -static-pie Bitcoin Core binaries that I’d like to get more testing of! More details on the mailing list: groups.google.com/g/bitcoind…
5
10
2
44
8,714
If you have any coldcard device, I would recommend against updating. Just get your funds out.
3
5
29
1,155
ReproducibilityMatters retweeted
Bitcoin Optech newsletter #416 is here: - warns about a severe vulnerability affecting wallets generated by COLDCARD signing devices - summarizes the disclosure of two denial-of-service vulnerabilities in Core Lightning - describes a proof of concept for a zero-knowledge proof of reserves - summarizes popular Q&A from Stack Exchange - Optech Newsletter #416 Podcast
7
15
1,438