Bitcoin Forum
November 15, 2024, 04:07:28 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Qs about Proof of Work concept ?  (Read 141 times)
ansdb (OP)
Newbie
*
Offline Offline

Activity: 80
Merit: 0


View Profile
January 16, 2019, 02:00:43 PM
 #1

i hv some question that make me confused   Huh  Grin

1 - is after the creation of the genesis block we can say that the network now is safe and it will be safe ? because all the upcoming blocks will be rely on that block ?

2 - is the Block Hash just the sum of the Txs in the block decrypted with Hash Function Tech + the previous block hash ( is those things considered as Input that gives the Output ( block hash ) ) ? is this correct ?

3 - is every Tx inside the block has its own Hash ?

4 - if someone in the network that own 15% of the global HashRate want to modify a block in which way he can do it (manually or ...) ?

5 - if someone or some entity in the network that own 51% of the global HashRate want to modify a block in which way he can do it (manually or ...) ?

6 - is the calculation that the miners do is some sort of x + 15 = 2 so they need to calculate this to create a block the first one who find x = -13 gets a reward ? is this correct ?

7 - if a miner A create a block he gets a reward from the network ?
8 - if a miner B just validate Txs don't create any block what he should get as a reward  ?

franky1
Legendary
*
Offline Offline

Activity: 4410
Merit: 4766



View Profile
January 16, 2019, 03:59:45 PM
 #2

1.a. its more so that when a new block is added the previous/older block(s) are safer to trust as stronger. EG a transaction in a block 100 blocks ago (100 confirms) is safer than a transaction with only 1 confirm

1.b. because a block contains the hash of previous blocks then to have a valid block does require clear links that do go all the way back to the genesis block. for instance you cannot just copy ethereums block history or litecoins block history to be a bitcoin attack chain. because although their blockheights(number of blocks) are more. the genesis wont match

2. https://en.bitcoin.it/wiki/Block_hashing_algorithm

3. yes each tx has its own hash which is called a TXID (transaction identifier)

4. he can only ultimately alter which transactions were in a block. thats the easy part.. catching up with the network after is the harder part
say blockheight was 570000 and someone wanted to edit out a tx in 569999. they would do that but then they would need to PoW mine the hash for their 569999 and then add that hash to their 5700000 then PoW hash that block.
the rest of the network would probably be on 570002 at this point because while he went back everyone else continued forward
so the person editing would need to catch up and race against the network hoping to get ahead so the network would accept the alteration.. which at 15% has little chance of happening

5. save as last point but much more chance.

6. in simplified terms the block header has a nonce. ASIC create a hash that is the block header and where the nonce changes. this makes the hash change. they keep changing the nonce until they find a hash that meets the difficulty requirements

7. imagine it like 15 different groups(pools) racing each other to get a block hash result that meet the rules. only one can win per block.

8. continuing from point 7. the other pools dont get anything. its like a 100m race the first one to cross the line wins.. as long as they are not found cheating

I DO NOT TRADE OR ACT AS ESCROW ON THIS FORUM EVER.
Please do your own research & respect what is written here as both opinion & information gleaned from experience. many people replying with insults but no on-topic content substance, automatically are 'facepalmed' and yawned at
ansdb (OP)
Newbie
*
Offline Offline

Activity: 80
Merit: 0


View Profile
January 16, 2019, 10:07:29 PM
 #3

Firstly thanks a lot for the anwsers and your help i really appreciate it, cuz i found difficulties when asking that kind of Questions just a few people reply and answer question  Smiley

Quote
6. in simplified terms the block header has a nonce. ASIC create a hash that is the block header and where the nonce changes. this makes the hash change. they keep changing the nonce until they find a hash that meets the difficulty requirements

what a form that the nonce take (Numbers ...)? and from where it is generated ?

Quote
7. imagine it like 15 different groups(pools) racing each other to get a block hash result that meet the rules. only one can win per block.

but the other unrewarded pools can create a block and win the reward in the next (x) time ?
franky1
Legendary
*
Offline Offline

Activity: 4410
Merit: 4766



View Profile
January 16, 2019, 10:40:03 PM
 #4

Firstly thanks a lot for the anwsers and your help i really appreciate it, cuz i found difficulties when asking that kind of Questions just a few people reply and answer question  Smiley

Quote
6. in simplified terms the block header has a nonce. ASIC create a hash that is the block header and where the nonce changes. this makes the hash change. they keep changing the nonce until they find a hash that meets the difficulty requirements

what a form that the nonce take (Numbers ...)? and from where it is generated ?

Quote
7. imagine it like 15 different groups(pools) racing each other to get a block hash result that meet the rules. only one can win per block.

but the other unrewarded pools can create a block and win the reward in the next (x) time ?

6. the nonce. is just a space to put in a number.
imagine you had some text :
'blahblahblahdeblah'
the text and a nonce would be like
blahblahblahdeblah000000
if you hashed it you would get
161F37591904929E6EBFDD9BA4DFB22C092204DE58D552E46FF9F771AAF186D4
so changing the nonce changes the result
blahblahblahdeblah000000=161F37591904929E6EBFDD9BA4DFB22C092204DE58D552E46FF9F771AAF186D4
blahblahblahdeblah000001=86E8E440341479C85888F906EE103579BE4EF34582FDECB546BBF43AC3C3A904
blahblahblahdeblah000002=887C68F2C56015B3CBFE4D3E76531AA2A1B4855CE9394940F783B0BE01BF1ABC
blahblahblahdeblah000003=E110996EBDBFFD6FB63D78FEABE2AF3F89577CE031A9764C6D6C4C98F3711794
blahblahblahdeblah000004=576889D3D11E55ACA59B4176B2119ED8B7DD8B571C0622AEFB0B4564F1D2D71D

7. if a few pools crate blocks within seconds of each other there is a chance that different users would get different blocks. depending on how they are connected to each other.(a small rar chance of this happening)

ALL the pools then restart working on the next block. and again whoever is fastest wins.
and this time the gap between first and second place might be wider so now the winner is a clear winner which then makes all users choose to trust the fastest clear winner. and so will hold onto the blocks that are linked to the winner chain of previous linked hashes and ignore the second place

people in second place dont win anything. they just have to retry and hope at some point they gt to first place.

due to issues where users might (rarely) hold a different block due to the race competition.. block rewards are not spendable instantly.. but instead untill 100 other blocks are stacked/linked ontop because the chances of people editing blocks and then catching up (point 4) and also the races swapping latest blocks. are not going to be a concern to a block 100 blocks deep(100 confirms) as the odds of negative impact resulting in changing something 100 blocks ago is soo small. its then deemed safe to let the winner finally spend their rewards of the block they won 100 blocks ago

I DO NOT TRADE OR ACT AS ESCROW ON THIS FORUM EVER.
Please do your own research & respect what is written here as both opinion & information gleaned from experience. many people replying with insults but no on-topic content substance, automatically are 'facepalmed' and yawned at
ansdb (OP)
Newbie
*
Offline Offline

Activity: 80
Merit: 0


View Profile
January 17, 2019, 04:58:56 PM
 #5

thanks a lot for your help  Smiley
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!