You want to prove something like this ?
b71b3ed7348484a74 -> Address: 1MVDYM7EJ783viaKHqnELxmjmChE7r1pqz -> e0b8a17fadc11deab8283c551a2b7b64afcc82fb
b7b96fbb25f78bd6f -> Address: 1MVDYN3C8NRQaSkukCurdFjKRDBSEVGAYX -> e0b8a18ecf2119138251d432f6c565f648db4f4a
and continue to the next prefix?
1MVDYgVaSN6iKKEsbyjwnJhmjw8FFcGFWh -> e0b8a2baee1b77fc703455f37934dcda00c9acc0
1MVDYgVaSN6iKKEsbyrjzeEecNkBtnrAYw -> e0b8a2baee1b77fc703455f37f6a9743ac4bb6d4
1MVDYgVaSN6iKKEsbz2NL978m2L1drKTAj -> e0b8a2baee1b77fc703455f388362c96c023dbc1
1MVDYgVaSN6iKKEsbz4MVwBjXREGNsM2w9 -> e0b8a2baee1b77fc703455f38a069c9cac5acaf5
1MVDYgVaSN6iKKEsbz8Ns2ByakjEZR9ScZ -> e0b8a2baee1b77fc703455f38db3b065bdc4ba1a
1MVDYgVaSN6iKKEsbzDYbcWpXTPKPajKQV -> e0b8a2baee1b77fc703455f3926c6ae481234a3e
1MVDYgVaSN6iKKEsbzJUSjn7GFZzjpGbMp -> e0b8a2baee1b77fc703455f396ed249a7d44a59b
1MVDYgVaSN6iKKEsbzLMJFCnBjRxyQM58K -> e0b8a2baee1b77fc703455f398a41cf3cee942c0
1MVDYgVaSN6iKKEsbzN9YUX9yK8skSHq58 -> e0b8a2baee1b77fc703455f39a487fee2fb09828
||
1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ
^^^^^^^^^^^^^^
untill the next Prefix ??
No, it's not like that.
1MVDYgVaSN6iKKEsbyjwnJhmjw8FFcGFWh -> e0b8a2baee1b77fc703455f37934dcda00c9acc0
1MVDYgVaSN6iKKEsbyrjzeEecNkBtnrAYw -> e0b8a2baee1b77fc703455f37f6a9743ac4bb6d4
1MVDYgVaSN6iKKEsbz2NL978m2L1drKTAj -> e0b8a2baee1b77fc703455f388362c96c023dbc1
1MVDYgVaSN6iKKEsbz4MVwBjXREGNsM2w9 -> e0b8a2baee1b77fc703455f38a069c9cac5acaf5
1MVDYgVaSN6iKKEsbz8Ns2ByakjEZR9ScZ -> e0b8a2baee1b77fc703455f38db3b065bdc4ba1a.....
I don't think most of these are in the 68 bit range.
1MVDYgVaSN - This is the prefix I'm targeting
After finding the 1MVDYgVaSN prefix, I do the Hex calculations and move on to the next one.
Then I do the Hash160 comparison and calculations. Then I figure out which hex ranges it's likely to be in and continue scanning again.