How Proof of System works

[temroa]

i have read articles about it but there is something still i did not got and that is:

think this as a block hash f4bf9f7fcbedaba0392f108c59d8f4a38b3838efb64877380171b54475c2ade8

current target as a hexadecimal number 0000000000000000171A8B000000000000000000000000000000000000000000

current target as decimal number 566500670366816952120145379831520408210047884740723212288

and a=10 b=11 c=12 d=13 e=14 f=15

which is comparised to block hash decimal number target or hexadecimal number target? and if hexadecimal number target is answer at the block hash a taking 10 b 11 c 12 d 13 e 14 f 15 number right ? after computer making comparison if block hash under the target you create the block right ?

so did ı got this job true ?

[temroa]

are you talking about Proof of Stake or is there a Proof of System algo?

im talking about proof of work,system acception of block

[shorena]

are you talking about Proof of Stake or is there a Proof of System algo?

im talking about proof of work,system acception of block

#1 Yes, you got the hexadecimal system correct. It using 16 different symbols (0-9 & a-f) instead of the common 10 (0-9) of the decimal system.

#2 Yes, the target as a hexadecimal number is compared to the hash of the blocks header[1] interpreted as a hexadecimal number. If the hash is below the target you found a new valid block. If the hash is above the target you will have try again with a different block header (e.g. increase the nonce by 1). If you found a hash that is exactly the same as the target you also found a new block. Comparing hexadecimal numbers is easier for a computer than comparing decimal numbers due to the internal operations working on binary (0 & 1) system anyway. Hexadecimal is more easily transfered to binary than decimal to binary. Any single hexadecimal digit can be represented by 4 binary digits. You can transfer a decimal number to a binary number, but it does not match the digits easily so you have to take care of the carry.

Code:

0 -> 0000
1 -> 0001
...
4 -> 0100
...
a -> 1010
...
b -> 1011
f -> 1111

[1] https://en.bitcoin.it/wiki/Block_hashing_algorithm

[temroa]

are you talking about Proof of Stake or is there a Proof of System algo?

im talking about proof of work,system acception of block

#1 Yes, you got the hexadecimal system correct. It using 16 different symbols (0-9 & a-f) instead of the common 10 (0-9) of the decimal system.

#2 Yes, the target as a hexadecimal number is compared to the hash of the blocks header[1] interpreted as a hexadecimal number. If the hash is below the target you found a new valid block. If the hash is above the target you will have try again with a different block header (e.g. increase the nonce by 1). If you found a hash that is exactly the same as the target you also found a new block. Comparing hexadecimal numbers is easier for a computer than comparing decimal numbers due to the internal operations working on binary (0 & 1) system anyway. Hexadecimal is more easily transfered to binary than decimal to binary. Any single hexadecimal digit can be represented by 4 binary digits. You can transfer a decimal number to a binary number, but it does not match the digits easily so you have to take care of the carry.

Code:

0 -> 0000
1 -> 0001
...
4 -> 0100
...
a -> 1010
...
b -> 1011
f -> 1111

[1] https://en.bitcoin.it/wiki/Block_hashing_algorithm

i thank you for your great explanation but something is still confusing my mind at everywhere other than bitcoin sources i dont see block header's hash instead i see block's hash what is block header's hash ?

[shorena]

-snip-
i thank you for your great explanation but something is still confusing my mind at everywhere other than bitcoin sources i dont see block header's hash instead i see block's hash what is block header's hash ?

The block's hash is the hash of the blocks header. Its just not commonly used like that, people like it short.

[temroa]

can block's hash interpreted as hexadecimal number ? how this is happening ?

i mean if there is different characters other than a,b,c,d,e,f in block hash how will it happen ?

[foxkyu]

can block's hash interpreted as hexadecimal number ? how this is happening ?

i mean if there is different characters other than a,b,c,d,e,f in block hash how will it happen ?

what do you mean different character other than alphabet or number?? is symbol what are you talking about??
like this !@#$%^&* on hash??

[temroa]

can block's hash interpreted as hexadecimal number ? how this is happening ?

i mean if there is different characters other than a,b,c,d,e,f in block hash how will it happen ?

what do you mean different character other than alphabet or number?? is symbol what are you talking about??
like this !@#$%^&* on hash??

i mean other characters in alphabet not symbols

[shorena]

can block's hash interpreted as hexadecimal number ? how this is happening ?

i mean if there is different characters other than a,b,c,d,e,f in block hash how will it happen ?

what do you mean different character other than alphabet or number?? is symbol what are you talking about??
like this !@#$%^&* on hash??

i mean other characters in alphabet not symbols

A SHA256 produces an hexadecimal number by default you would have to go out of your way to translate it to a different system (e.g. alphanumerical), thus this situation does not come up under normal circumstances. If someone would temper with the resulting hash before broadcasting it, the other nodes in the network would consider the block to be invalid because it is in the wrong format.

[temroa]

can block's hash interpreted as hexadecimal number ? how this is happening ?

i mean if there is different characters other than a,b,c,d,e,f in block hash how will it happen ?

what do you mean different character other than alphabet or number?? is symbol what are you talking about??
like this !@#$%^&* on hash??

i mean other characters in alphabet not symbols

A SHA256 produces an hexadecimal number by default you would have to go out of your way to translate it to a different system (e.g. alphanumerical), thus this situation does not come up under normal circumstances. If someone would temper with the resulting hash before broadcasting it, the other nodes in the network would consider the block to be invalid because it is in the wrong format.

shortly sha256 hash of the block is already hexadecimal number right ?

[shorena]

can block's hash interpreted as hexadecimal number ? how this is happening ?

i mean if there is different characters other than a,b,c,d,e,f in block hash how will it happen ?

what do you mean different character other than alphabet or number?? is symbol what are you talking about??
like this !@#$%^&* on hash??

i mean other characters in alphabet not symbols

A SHA256 produces an hexadecimal number by default you would have to go out of your way to translate it to a different system (e.g. alphanumerical), thus this situation does not come up under normal circumstances. If someone would temper with the resulting hash before broadcasting it, the other nodes in the network would consider the block to be invalid because it is in the wrong format.

shortly sha256 hash of the block is already hexadecimal number right ?

Yes, in fact SHA256 hash of anything is.

E.g. SHA256(Hello temroa) = 5567d098c7115c4866f75b744bb8c453ee037fb4bc07ecfba9f9a9caa40b4aee

-> http://www.xorbin.com/tools/sha256-hash-calculator