Open varun-doshi opened 1 month ago
I understand there is a method:
let node_config = NodeConfig {
utxo_validation: false,
..Default::default()
};
But from what I understand, this can only be set for a local node
What if I want to connect to a remote RPC. Can I set the NodeConfig
for that provider? Currently, I do not see any functions to carry this out.
I would also like to know if it is possible to fork the testnet from a historic block. So connect to a remote RPC but at Block:900 (lets assume the current testnet block is 1000).
@varun-doshi your observation is correct. You can not use the ImpersonateAccount
without setting the utxo_validation
to false
. There is no way of setting this config to an already running node. That would be a huge vulnerability. So if you setup your local node and set the validation to false you can use the impersonated accounts.
I have talked with the client team and currently there is no easy way to fork the tesnet
. The only way, for now, is to sync the whole testnet (can take a lot of space) and then rewind to a specific height.
I'm trying to test the
ImpersonateAccount
feature which allows taking control of any account without its private key and run transactions on my fork.However, it throws an error
InvalidSignature
when trying to transfer assets to another account. The exact error is as follows:I've tried this with two setups: Setup 1:
UnlockedWallet
and send my base_asset to another account. This runs successfully and generates a receipt.Setup 2:
impersonate
my own account and send the base_asset to another account. This fails with the error given above.unlockedWallet
and the other isimpersonatedWallet
.The conclusion I come to is that it looks like some Signature verification fails when using the
impersonated wallet
.I may be wrong though.Steps to reproduce
My current fuel setup:
My
Cargo.toml
: