Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

fix: ensure impersonated "large" accounts use compliant (fake) private keys #2602

Closed
wants to merge 3 commits into from

Conversation

davidmurdoch
Copy link
Member

@davidmurdoch davidmurdoch commented Mar 14, 2022

Transactions from "impersonated" accounts are still "signed" by Ganache, but the private key is faked. It was previously possible for the fake private key we generate for some accounts to cause an error when a transaction is eventually signed.

Fixes #2586

@davidmurdoch davidmurdoch changed the title fix: ensure a "large" address can be unlocked/used fix: ensure a "large" addresses can be unlocked/used Mar 14, 2022
@davidmurdoch davidmurdoch changed the title fix: ensure a "large" addresses can be unlocked/used fix: ensure a "large" address can be unlocked/used Apr 4, 2022
@davidmurdoch davidmurdoch force-pushed the develop branch 3 times, most recently from 96d6c7f to 47d583d Compare April 8, 2022 17:42
@davidmurdoch davidmurdoch changed the title fix: ensure a "large" address can be unlocked/used fix: enforce EIP-2 Apr 20, 2022
@davidmurdoch davidmurdoch changed the title fix: enforce EIP-2 fix: ensure impersonated "large" accounts generate compliant (fake) private keys Apr 20, 2022
@davidmurdoch davidmurdoch changed the title fix: ensure impersonated "large" accounts generate compliant (fake) private keys fix: ensure impersonated "large" accounts use compliant (fake) private keys Apr 20, 2022
@davidmurdoch
Copy link
Member Author

closing in favor of #2944

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
1 participant