Vojtěch Strnad
@vostrnad
Followers
655
Following
56K
Media
38
Statuses
1K
Inscriptions were possible before Taproot | Make crypto cryptography again
Joined December 2012
Last week I made a special Bitcoin transaction. Today I'll tell you all about it:
stacker.news
If you've been on Twitter or Stacker News last week, you may have seen this strange Bitcoin transaction: https://mempool.space/tx/b10c0000004da5a9d1d9b4ae32e09f0b3e62d21a5cce5428d4ad714fb444eb5d It...
26
74
231
The Bitcoin Core development process and distribution model actually makes it somewhat harder to fix security issues, compared to other serious software distributors. Take Google Chrome as an example. The CVE fixing happy path is to develop and review a fix in private, push that
github.com
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
@adam3us They can always push security fixes in v29 like any serious software distributor does, not forcing anyone to upgrade to unwanted/unprepared for functional changes… and I should know I work for a software editor for 15+ years
27
73
275
GM. There's no way a change to Bitcoin Core's default relay policy could have a snowball's chance in hell of killing Bitcoin. (This will be even more true if/when we activate the consensus cleanup soft fork.)
3
1
9
Merged PR from instagibbs: policy uncap datacarrier by default
0
0
1
Merged PR from instagibbs: policy uncap datacarrier by default
github.com
Retains the -datacarrier* args, marks them as deprecated, and does not require another startup argument for multiple OP_RETURN outputs. If a user has set -datacarriersize the value is "bud...
94
27
190
A statement on Bitcoin Core development and transaction relay policy -
bitcoincore.org
Bitcoin Core development and transaction relay policy
411
179
691
Some updates on OP_CHECKCONTRACTVERIFY: - BIP draft: https://t.co/kv6jb7iiqA - bitcoin-core concept implementation: https://t.co/O6sYUCfDGC - Delving post:
1
19
50
Compiling a list of filming locations, this one did take a solid two minutes to find. @peterktodd 50°08'45.6"N 14°12'05.9"E
1
0
4
Merged PR from 1440000bytes: policy enable fullrbf by default
github.com
This pull request enables full rbf (mempool policy) by default. #28132 was closed recently with this comment. Rationale: Full RBF config option was added in July 2022: Add a -mempoolfullrbf node...
9
20
73
Referral to the Crown Prosecution Service "In these circumstances, as set out in the whole of my Main COPA Judgment, I have no doubt that I should refer the relevant papers in this case to the CPS for consideration of whether a prosecution should be commenced against Dr Wright
1
14
106
My node still has a few peers running 0.20.1 or earlier. I expect these to disappear from the network within a few days as they are either speedily updated or remotely crashed. Don't run unmaintained software people.
Today we announce the new disclosure policy the Bitcoin Core will adopt for most reported vulnerabilities. We also publicly disclose 10 vulnerabilities affecting Bitcoin Core versions lower than 0.21.0. https://t.co/yRa4QrNXTT
https://t.co/fbRnnzHp5Q
0
0
6
Okay. Let's go! Feed me all the Easter eggs you can find in this transaction. I agree there's art here.
The nLockTime epoch timestamp is the genesis block timestamp 🤌 This transaction should be framed in a museum.
3
3
16
BIP 101 was proposed in June 2015 for activation in January 2016. Under its rules, the blocksize now would be 154MB.
16
41
199
Thanks to @pwuille, whose witness statement was "the most significant document in this Trial" and "used to devastating effect"
21
38
237