You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead, we should read these private keys from environment variables and set them in the GitHub CI environment. Similar to what was done recently on the TS SDK: FuelLabs/fuels-ts#1858. We should generate a new test wallet, fund it through the faucet, and then set the env var on GitHub.
The text was updated successfully, but these errors were encountered:
Maybe not relevant here, but as we also had references to WALLET_ADDRESS, we started reading it from the environment/secrets as well. If we need to change things in the future, no code modifications will be necessary.
Maybe not relevant here, but as we also had references to WALLET_ADDRESS, we started reading it from the environment/secrets as well. If we need to change things in the future, no code modifications will be necessary.
To avoid leaking testnet wallets' private keys, we shouldn't hardcode these wallets' private keys like we do, e.g., in here:
https://github.com/FuelLabs/fuels-rs/blob/master/packages/fuels/tests/providers.rs#L597
Instead, we should read these private keys from environment variables and set them in the GitHub CI environment. Similar to what was done recently on the TS SDK: FuelLabs/fuels-ts#1858. We should generate a new test wallet, fund it through the faucet, and then set the env var on GitHub.
The text was updated successfully, but these errors were encountered: