Updates & Forks - Discussion

Blockchain and Bitcoin 101
#711

Hi everyone,

I have a question unrelated to the topic. Could anyone please explain why Ivan and Filip use the term “upend” when talking about blocks being added to the network? The definition that I have in my Mac dictionary:

upend | ʌpˈɛnd |
verb [with object]
set or turn (something) on its end or upside down: she upended a can of soup over the portions.
• [no object] (of a swimming duck or other waterbird) submerge the head and foreparts in order to feed, so that the tail is raised in the air: a pair of swans were feeding by upending.

Is there something that I don’t understand or is it used incorrectly? :smiley:

#712

I think you misheard them, they say append not upend, meaning attach or add to the end.

1 Like
#713

Oh, it makes total sense now. I definitely misheard them. That’s what happens when non-English speaker listens to non-English speakers. :smiley: Thanks, Maki! :raised_hand:

#714

Thank you Filip, now it is all clear! I had heard of hard and soft works but did not fully understood what there is pretty much behind.

#715

Thanks for asking this question. Was wondering the same thing

1 Like
#716

Hard forks: let’s say 90% of the network nodes are now running on the new (updated) protocol which allows for a greater block size. In the “Hard Forks” video we learn that it will indeed create a new fork as some of the nodes (10% in this case) are still running on the old protocol, hence they’ll reject all blocks that are greater than the old size allowance. As the size of the blockchain running on the new protocol will increase in its PoW much faster than the blockchain on the old protocol (due to the 90-10 ratio of computing power), I am not seeing why there is not an eventual merge of the blockchain running on old protocol into the blockchain running on new protocol once the remaining 10% of nodes also receive the updated protocol’s allowance for block size. Please clarify.

#717

Those 10% nodes must be updated to work by the new rules unless both the old and new blockchains exist side by side.

#718

Thx Maki. Does that mean that each node owner has the choice to update or not, just like in the case of other software applications on personal computers?

#719

Yes, they can only update the software if they are happy/agree with the change.

#720

Thx Maki for clarification.

1 Like
#721

Could you please clarify that pre -hard fork invalid blocks that were not accepted onto the chain can not become valid blocks after the fork. They have been returned to the mempool. It is only the new blocks with the new set of rules after the fork that can be accepted by the nodes. Is this correct???

#722

Hello Filip and community,
but when we talk about updates for the hard fork, what exactly do we mean? how come all the nodes do not update? is it a matter of them not doing it in time, or is it a matter of them not accepting new updates? sorry, but i am not clear on this point.

thx for the explanation!

1 Like
#723

Correct, the updated nodes will accept new blocks with new set of rules.

#724

Yes, it is a matter of them not accepting new updates, they can only update the software if they are happy/agree with the change.

1 Like
#725

thx for the explanation !

#726

It is very likely that transactions in each block are the same tx tho no? thus even if a block with your tx is removed, if your tx was in the other block as well it would be valid either way right?

#727

If I understand correctly, even in a split situation, It is very likely that transactions in each block have the same tx no? thus even if a block with your tx is removed, if your tx was in the other block as well it would be valid either way right?

#728

Hi Filip,

For how long the invalid block can wait to be valid?, I assume that that it should be returned to the mempool immediately.

#729
  • Clients will ignore invalid blocks when determining which chain is difficultywise-longest.
  • Mining clients will not build on top of invalid blocks.
  • Clients will not propagate invalid blocks (or invalid transactions).

The invalid block will be rejected and drop out from the mempool once it has been marked has invalid.

The transaction will be sent back to the client who made it. ( not exactly sent back, the node that propose the transaction will marked it has rejected, it could send it again to the mempool but it will be rejected again)

Carlos Z

1 Like
#730

Thank you Calos, appreciate your help

2 Likes