New answers tagged block
0
A non-negative signed varint is just a normal varint but should be put into a signed integer rather than an unsigned integer as with normal varints. You just need to also check that it is a non-negative integer.
For example, instead of decoding a 32 bit varint as a uint32_t, you decode it as int32_t and check that it's value is >= 0.
Your code looks ...
0
These websites https://goochain.net/ or https://blockchair.com/ allow you to query by dates the bitcoin blockchain
-1
I would say that a Dust Attack on Bitcoin is the most dangerous system that hackers use to steal Bitcoin. According to this article:
https://dust-attack.blogspot.com/2019/03/blog-post.html?m=1
2
In addition to Chytrik's mention of a dust attack, dust limit transactions are also used heavily by the Omni Layer to identify the recipient of an omni asset. Transactions such as those will follow pattern of one dust (or near dust) output, an OP_RETURN output, and a change output.
While dust attacks tend to create thousands of dust outputs in a handful of ...
2
This output value corresponds to the dust limit that is imposed on bitcoin transactions.
Many of these outputs may have been generated as a dust attack to de-anonymize users/ addresses.
0
A block's timestamp should only be treated as an approximate time that the block was mined. There is no way to enforce a miner to include 'the actual time', because it is impossible for the network to ascertain the truth of this. So instead, the network imposes a rule that the timestamp must adhere the following rules in order to be considered valid:
(The ...
Top 50 recent answers are included
