So since the old (original) profanity is vulnerable, from an ethical standpoint as well as for contract and EOA addresses I have created in the past (can't remember if that was done with Profanity or not). Is it possible to release the PoC on how to precompute the dataset? I assume it's done by just using the vulnerable version of profanity (v1) at least the mt19937_64 generation part.
Would also be nice to ethically drain wallets / contracts containing any amount of ETH, then somehow have the funds returned to the original owner. Just like what happened with the parity- hack and the "White Hat Group" who used the same exploit to secure the compromised wallets.
So since the old (original) profanity is vulnerable, from an ethical standpoint as well as for contract and EOA addresses I have created in the past (can't remember if that was done with Profanity or not). Is it possible to release the PoC on how to precompute the dataset? I assume it's done by just using the vulnerable version of profanity (v1) at least the mt19937_64 generation part.
Would also be nice to ethically drain wallets / contracts containing any amount of ETH, then somehow have the funds returned to the original owner. Just like what happened with the parity- hack and the "White Hat Group" who used the same exploit to secure the compromised wallets.