Bitcoin Knots version 21.2.knots20210629 is now available from:
https://bitcoinknots.org/files/21.x/21.2.knots20210629/
This Long Term Support (LTS) "Steel Rope" release is based on the unchanged
Bitcoin Knots feature set from 2021 June 29th, with only bug fixes and updated
translations.
Pleas
I know NFTs are controversial, but here's my take on them in Sapio:
https://rubin.io/bitcoin/2021/12/16/advent-19/
If you don't like NFTs, don't worry: the results and techniques are
entirely generalizable here and can apply to many other types of things
that aren't stupid JPGs.
E.g.,
- If you
high level response:
including a small number of block headers (10?) directly as op_return
metadata (or something) doesn't have that high overhead necessarily, but
could be super effective at helping miners participate with lower hashrate.
the reason to include this as on-chain data is so that the
@Jeremy
> for top-level pool participants there is never any central custody.
I definitely see that. That was actually what I meant when I said the goals
aren't the same as benefits. While your idea definitely satisfies all your
goals in a modular way, the fact that it relies on pools means that
> The missing piece here would be an ordering of weak blocks to make the window
> possible. Or at least a way to determine what blocks should definitely be
> part of a particular block's pay out. I could see this being done by a
> separate ephemeral blockchain (which starts fresh after each Bitc
