Archive of the libbitcoin Slack #general channel.
bx fetch-block-hashes -t 100000) where you can get a properly ordered list of transactions in a block. If you needed to generate a merkle proof for a particular tx, you could use that result. This new command does work against version3 servers if you wanted to try it:
/bx fetch-block-hashes -t 100000
hashes
{
hash 8c14f0db3df150123e6f3dbbf30f8b955a8249b62ac1d1ff16284aefa3d06d87
hash fff2525b8931402dd09222c50775608f75787bd2b87e56995a7bdd30f79702c4
hash 6359f0868171b1d194cbee1af2f16ea598ae8fad666d9b012c8ed2b79a236ec4
hash e9a66845e05d5abc0ad04ec80f774a7e585c6e8db975962d069a522137b80c1d
}/bx fetch-header -t 100000
header
{
bits 453281356
hash 000000000003ba27aa200b1cecaad478d2b00432346c3f1f3986da1afd33e506
merkle_root f3e94742aca4b5ef85488dc37c06c3282295ffec960994b2c0d5ac2a25a95766
nonce 274148111
previous_block_hash 000000000002d01c1fccc21636b607dfd930d31d01c3a62104612a1719011250
time_stamp 1293623863
version 1
}size_t for one of is_coinbase_pattern ’s parameters. But is that enough? I mean, `size_t` is an unsigned int after all.
Shouldn’t it be a uint64_t?size_t is generally 64 bits on 64 bit systems. Parts of libbitcoin (such as database) require 64 bit systems also.