Bitcoin Forum
May 04, 2024, 01:54:12 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How PoS Blockchains prevent miner from sending different block  (Read 164 times)
flow_ (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 25, 2018, 12:43:19 AM
 #1

Hello everyone,
I'm quite new to the world of crypto and have been wondering, how different blockchains prevent miners/forgers from breaking it.
As far as I know, (in PoS, for instance) a forger get's selected to validate a block of transactions.
But theoretically speaking, he could create different versions of the new block he is validating.

Example:
The miner/forger received 100 transactions and is including all of them in his block A.
Also, he creates a block B that only holds 95 of the transcations.
Now, he broadcasts block A to 50% of the network and block B to the rest.
Both blocks are valid and are signed by him -> he created two different blockchains.


What am I missing / how are do blockchain projects adressing this issue?
Thanks.
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714787652
Hero Member
*
Offline Offline

Posts: 1714787652

View Profile Personal Message (Offline)

Ignore
1714787652
Reply with quote  #2

1714787652
Report to moderator
joniboini
Legendary
*
Offline Offline

Activity: 2184
Merit: 1789



View Profile WWW
November 25, 2018, 03:47:06 AM
 #2

What you describe is essentially the nothing at stake problem. Several solutions have been proposed to solve this problem. You can give a validator a penalty if he votes on every fork/chain that happens on the network. If he votes/validate on chain A and B (different blocks), he'll lose his entire stake. In addition to this, you can require that every validator identity must be known and trustable, therefore when something like this happens you can know who's at fault. In its simplest sense, the solution lies in preventing validator to validate on more than 1 chains and to discourage validator to do something like that by making his identity (real identity) known to the network.

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits.
..........UNLEASH..........
THE ULTIMATE
GAMING EXPERIENCE
DUELBITS
FANTASY
SPORTS
████▄▄█████▄▄
░▄████
███████████▄
▐███
███████████████▄
███
████████████████
███
████████████████▌
███
██████████████████
████████████████▀▀▀
███████████████▌
███████████████▌
████████████████
████████████████
████████████████
████▀▀███████▀▀
.
▬▬
VS
▬▬
████▄▄▄█████▄▄▄
░▄████████████████▄
▐██████████████████▄
████████████████████
████████████████████▌
█████████████████████
███████████████████
███████████████▌
███████████████▌
████████████████
████████████████
████████████████
████▀▀███████▀▀
/// PLAY FOR  FREE  ///
WIN FOR REAL
..PLAY NOW..
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!