Hi. why does bitcoin have a vulnerability in time? why is the algorithm not perfect?
why the number of nons that miners are looking for is limited in size? these parameters can expose bitcoin to a huge fork. what i mean. a small miner can mine bitcoin for example have 1-10% of the network from 4-40 exasheh of the entire network.
and when a block is found, not to send it to the network, and hold the solution of a new block for a while, and the new solved hash should be used to find a new block. for example, to find a block and leave the ready answer for 10 seconds and start looking for a new block, say, mine for the future. and after finding the first one to send then the second, with a difference of 9 seconds. and it does not contradict the rules. but you can go longer and divide miners to search each non separately. that is, 1 miner looking for this number in the range from 0-1000 second from 1001-2000 third 2001-3000 and so on it's a matter of luck)
Of course the solution is to shift the time in the algorithm. it will remove this glitch or bug, or whatever it is called ...
This question is far too complex for me buddy, I can’t even post a video on here lol
I'll put it simply) bitcoin can be hacked)
What does this have to do w my post?
a team that can verify or disprove this.
Or am I wrong, not to get a reasonable answer from you! 21
its world's biggest bounty if can be hacked
miners are competing. they can build on blocks they have mined but doesn't mean other miners will auto accept additional blocks. all blocks have to be valid and meet the consensus rules but longest/heaviest chain wins
https://bitcoin.stackexchange.com/questions/5540/what-does-the-term-longest-chain-mean
and what is the difference between the longest and the real one? ask someone else. anyone can do that) no time
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
That's not how mining works. Timestamps are irrelevant. The only rule being timestamps earlier than the median of previous 11 blocks or greater than 2 hours after current network time are rejected. What you're describing is selfish mining attack. It's modeled on flawed assumptions.
Thread collapsed