Bitcoin Forum
May 28, 2024, 04:45:20 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Creating nonsense fork in blockchain  (Read 557 times)
Gustavotonini (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 30, 2017, 01:16:11 AM
 #1

It is just a stupid question. Imagine if I start mining over an old block which already has many subsequent blocks, find a new block and submit to the network. Will they accept it and create a nonsense fork?

I know it is the longest chain that really matters, but would the network accept my block, creating the new fork or simply reject it?
os2sam
Legendary
*
Offline Offline

Activity: 3578
Merit: 1091


Think for yourself


View Profile
August 30, 2017, 10:23:53 AM
 #2

It is just a stupid question. Imagine if I start mining over an old block which already has many subsequent blocks, find a new block and submit to the network. Will they accept it and create a nonsense fork?

I know it is the longest chain that really matters, but would the network accept my block, creating the new fork or simply reject it?

Only work for the current block is sent out.  If you submit a hash for a past block it will be rejected, probably as stale or not meeting current difficulty.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
reee
Sr. Member
****
Offline Offline

Activity: 439
Merit: 252


Get Paid to Play your Media on Current


View Profile
August 30, 2017, 09:28:58 PM
 #3

That block will be simply orphaned.
To do a fork you need to make your own client with its specific rules, and distribute it to people who will use it.

.
▄████████████████████████▄
██████████████████████████
██████████████████████████
██████████████████████████
▀█████████████████████████
   ▀██████████████████████
█▄▄   ▀███████████████████
████▄▄   ▀████████████████
███████▄▄   ▀█████████████
██████████    ▀██████████
███████▀▀        ▀███████
████▀▀              ▀████
█▀▀                    ▀█
..   █
█  █
█  █
█  █
█  █
█  █
█  █
   █
   Just Press Play
Spotify
YouTube
Soundcloud


8Tracks
Radio
Podcast

█  █
█  █
█  █
█  █
█  █
█  █
.
.
GET IN TOUCH
Telegram
.
ANN Thread
.
Gustavotonini (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
August 31, 2017, 12:58:13 AM
 #4

Yeah I understand the block would become orphaned. But would the other nodes add it to their databases or reject it?
os2sam
Legendary
*
Offline Offline

Activity: 3578
Merit: 1091


Think for yourself


View Profile
August 31, 2017, 01:40:23 AM
 #5

Yeah I understand the block would become orphaned. But would the other nodes add it to their databases or reject it?

It would not be orphaned.  Work for old blocks is no longer sent.  Only work for the current block is sent.  So hashes for past blocks would be rejected.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!