Random number seed setter about taurion_gsp HOT 3 CLOSED

Why do you need this? That's somewhat hard, because the RNG is seeded based on the block hashes. We could introduce some way to control this with e.g. command-line flags, but that then seems like a risk since people could accidentally get out of sync with everyone else by using those. (Or someone with malicious intents could convince people who do not know what they are doing to set those flags.)

from taurion_gsp.

Hmmmmm. I am just looking or an easy way to make front-end unit testing, but if that bring such complications, let it be then

from taurion_gsp.

Yes sure, but I don't understand for what exactly you need this RNG seeding change. If mainnet contains "enough complicated" behaviour to test the frontend, just let it sync to the actual mainnet chain block by block (e.g. using invalidateblock and reconsiderblock) to test the frontend.

Otherwise, you could just create a script that creates some situations you want to test on regtest similar to our integration tests for the GSP, for which you don't need a particular RNG seed.

from taurion_gsp.