05-05-2022, 04:27 PM
given the sourcecode of the module 11300 the per token length as follows (check = check passed for your hash) $ is the seperator
$bitcoin
check
$64
2-3 check
$1702c5d1fef598b1858eed6b301cfbb309bda5cf13b0d4e1a20fd0a8a7e42e92
64-256 check
$16
2 check
$b742d007c100a0e2
16-36 check
$161236
1-6 check
$2
0-6 check
$00
0-9999999 hex check
$2
0-6 check
$00
0-9999999 hex check
so basically your token seems good, but the two last hex 00 seems not right when comparing to the example hashes for mode 11300
$bitcoin$96$d011a1b6a8d675b7a36d0cd2efaca32a9f8dc1d57d6d01a58399ea04e703e8bbb44899039326f7a00f171a7bbc854a54$16$1563277210780230$158555$96$628835426818227243334570448571536352510740823233055715845322741625407685873076027233865346542174$66$625882875480513751851333441623702852811440775888122046360561760525
you could test the following, produce a clean wallet.dat with the appropiate programm you are unsing and try to extract the hash for a simple and known pass like 12345678, take a look at these hash, mayb the wallet.dat you got is corrupt,
$bitcoin
check
$64
2-3 check
$1702c5d1fef598b1858eed6b301cfbb309bda5cf13b0d4e1a20fd0a8a7e42e92
64-256 check
$16
2 check
$b742d007c100a0e2
16-36 check
$161236
1-6 check
$2
0-6 check
$00
0-9999999 hex check
$2
0-6 check
$00
0-9999999 hex check
so basically your token seems good, but the two last hex 00 seems not right when comparing to the example hashes for mode 11300
$bitcoin$96$d011a1b6a8d675b7a36d0cd2efaca32a9f8dc1d57d6d01a58399ea04e703e8bbb44899039326f7a00f171a7bbc854a54$16$1563277210780230$158555$96$628835426818227243334570448571536352510740823233055715845322741625407685873076027233865346542174$66$625882875480513751851333441623702852811440775888122046360561760525
you could test the following, produce a clean wallet.dat with the appropiate programm you are unsing and try to extract the hash for a simple and known pass like 12345678, take a look at these hash, mayb the wallet.dat you got is corrupt,