can someone try to debunk this? (without "why?")

in an md5 blockchain system the previous block of a chain is hashed by 7 md5 hashes which act as shards for anti-collision purposes and single concatenated hash strings as prev_block's value.

this hash string comprised of 7 md5 hashes which act a salt for the md5 word puzzles that are necessary for a miner to solve in order to publish a block.

as an unresearched example: 3 words are appended to the sharded md5 prev_block hash string value, resulting in a crackable string like:

202cb962ac59075b964b07152d234b702a7feabdc8aba98e5d326bb8dd0ff7105bde2ee1bb30d362f4f0cf9995be3273f68d364c9754c6a72f78c1d444b898551fbe67791d843298f0d7c1d910092891 universe banana water

every miner shares the same dictionary wordlist — and as soon as the previous block hash followed by 3 valid words from the shared wordlist is cracked and broadcast to peers to bft the authenticity of the miner's claim — the puzzle is solved, the miner is rewarded a transaction fee and publishes a new block to the chain containing pending tx from the mempool sent by external users as broadcasts to mining nodes.

the correct hash for the aforementioned challenge string would be the md5 value: 059cb0d9ed5d8da51b6eefc6366e32a6 which would, again, be broadcast by a miner to other miners as to authenticate that the correct challenge string has been cracked by the winning miner - running bft checks across the node network to verify that the miner has solved the word puzzle and is allowed to publish the block for tx fees.

the previous block is hashed in chunks (shards), e.g. 1/7th of the block data (with the final portion containing slightly less or more data) gets its own unique md5 hash which produces 7 md5 hashes next to each other as the new previous block hash.

such a previous block hash string would look like:

202cb962ac59075b964b07152d234b702a7feabdc8aba98e5d326bb8dd0ff7105bde2ee1bb30d362f4f0cf9995be3273f68d364c9754c6a72f78c1d444b898551fbe67791d843298f0d7c1d910092891

eliminating prev_block md5 hash collision and enabling the creation of a mostly md5 based blockchain outside of stronger encryption (sha256) being used for keypair generation and tx/msg signing.

mad <3,

x.com/123456