alchemyplatform / alchemyplatform/aa-sdk
GetCounterFactualAddressError: getCounterFactualAddress failed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 321
- Forks
- 231
- Avg merge
- 43m
- Merged PRs (30d)
- 3
Description
I used exapmle code to test aa-sdk, but it reports the 'GetCounterFactualAddressError: getCounterFactualAddress failed', the code is import { createMultiOwnerModularAccount } from "@alchemy/aa-accounts";
import {
LocalAccountSigner,
createSmartAccountClient,
polygonMumbai,
} from "@alchemy/aa-core";
import { http } from "viem";
async function test() {
const chain = polygonMumbai;
const signer = LocalAccountSigner.mnemonicToAccountSigner(
"xxx"
);
const rpcTransport = http("https://polygon-mumbai.g.alchemy.com/v2/demo");
const account = await createMultiOwnerModularAccount({
transport: rpcTransport,
chain,
signer,
});
const smartAccountClient = createSmartAccountClient({
transport: rpcTransport,
chain,
account: account
});
}
test()
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the supplied TypeScript reproduction with the shown aa-sdk imports and polygonMumbai configuration, then trace where getCounterFactualAddress fails. The issue names no repository file or test; done means the failure is explained and the example can create the smart account client successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100