[feat] Using scarb get_block to generate test blocks

[TAdev0]

• issue [feat] Using scarb get_block generate test blocks #51
• follows contribution guide
• code change includes tests

Includes:

• block containing pizza tx
• all 4 halving blocks
• segwit soft fork
• taproot soft fork
• Bitcoin Cash hard fork
• Bitcoin Gold hard fork
• Biggest block in Bitcoin history (Taproot Wizard)

Block 0 and Block of first p2p tx to Hal Finney were already added, now we have 13 blocks.

@maciejka if you have any idea of other blocks I could add

I removed the // TODO: implement in the block_filter.jq file so that it doesnt appear in all the TxIn of Transactions contained in generated blocks.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
raito	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 10, 2024 0:23am

[TAdev0]

@maciejka I guess we should wait for a correct script before merging this, so that all blocks after segwit contain correct is_segwit flag + witness field (and pre segwit block should also generate a witness field, but empty, to match our Transaction struct

[maciejka]

Wow, these files are huge. How compiler behaves? I am not sure what will happen to tests execution time if we include all of them.

[maciejka]

The point of the comment was to make it clear that it is not fully implemented.

[maciejka]

@maciejka I guess we should wait for a correct script before merging this, so that all blocks after segwit contain correct is_segwit flag + witness field (and pre segwit block should also generate a witness field, but empty, to match our Transaction struct

It is ok to merge work in progress. We will regenerate if necessary.

[TAdev0]

@maciejka dont know for the compile for now, repo was not correctly structured regarding Tests modules (no lib.cairo file in it) hence was not detected when building.

If thats ok for you i'll close this PR, and open a new one.