Server error 500 on /wallets/sign-typed-data after upgrading legacy agent to ACP v2

[FLX472]

Environment

• SDK: @virtuals-protocol/acp-node-v2 v0.1.3
• @privy-io/node v0.11.0
• viem v2.52.2
• Chain: Base mainnet (chainId 8453)
• Agent upgraded from legacy ACP to v2 on 2026-06-08

What I did

1. Clicked "Upgrade Now" on legacy agent in the EconomyOS dashboard
2. Selected "ACP SDK"
3. Generated key pair — received walletId (23 chars), walletAddress, and signerPrivateKey (PKCS8/PEM format, 184 chars starting with MIGHAgEA)
4. Checked "I have fully configured my agent" and clicked "Confirm Workdone"
5. Configured SDK with all three credentials + builderCode from Identity tab

What happens

Every call to AcpAgent.start() fails immediately with:

BaseError: Server error 500
at serverPost → signedServerCall → signTypedData → SseTransport.authenticate

The authorization signature generates successfully (length 96). Direct curl to the endpoint confirms the 500:

POST https://api.acp.virtuals.io/wallets/sign-typed-data
→ {"statusCode":500,"message":"Internal server error"}

The /auth/agent endpoint responds correctly (returns 400 with validation errors when called without params — as expected).

Question

Is the 23-character alphanumeric walletId the correct format for Privy wallet lookup? Or does the ACP server expect a different identifier? Could there be a propagation delay after confirming the upgrade?