Pieter,
You are correct.
And also, I did prove what I set out to prove. The code provided privately
to the security team will in fact consume 99% of the CPU, which means it
does have an effect on the electorate. It is true the node still
stubbornly passes messages, but I would argue that this is
Very interesting,
Block mixing did not resolve the selfish mining that is currently observed
on the network. This mitigation was only intended to limit the maximum
impact of waiting for a 2nd block to be produced.
Rebalancing the selfish-mining incentives with FPNC and a faster block
creation ti
Hello all,
By the way, is this FPNC is similar to the way the current (or recent) code of
Ethereum that is selecting branches based on the difficulty of the crypto
puzzles solved to obtain the blocks of this branch without comparing the sizes
of the subtrees?
Any ideas?
Best,
Önder
> On 8
Good morning all,
>
> Below is a novel discussion on block-withholding attacks and FPNC. These are
> two very simple changes being proposed here that will dramatically impact the
> network for the better.
>
> But first of all, I'd like to say that the idea for FPNC came out of a
> conversation
On Wednesday, October 7, 2020 1:31 PM, Mike Brooks via bitcoin-dev
wrote:
> But first of all, I'd like to say that the idea for FPNC came out of a
> conversation with ZmnSCPxj's in regards to re-org stability. When I had
> proposed blockchain pointers with the PubRef opcode, he took the time t
Hello Everyone,
Below is a novel discussion on block-withholding attacks and FPNC. These
are two very simple changes being proposed here that will
dramatically impact the network for the better.
But first of all, I'd like to say that the idea for FPNC came out of a
conversation with ZmnSCPxj's in
