v1 P-384 identity migration to v2 Ed25519 - lost points

[vintagechocolate]

I am unable to migrate my v1 node identity to v2. My v1 private key (P-384/secp384r1) is rejected by v2 CLI with a Uint8Array expected error. I have accumulated points under my v1 identity that appear to be trapped.

Identity loaded from provided key
Fatal error: ... (truncated) ...
error: Uint8Array expected
      at gY (/$bunfs/root/aios-cli:.......)
      ...

v1 used P-384 (384-bit/48-byte keys) while v2 README specifies Ed25519 (256-bit/32-byte keys). The crypto libraries expect different key lengths and curves.

@bug, breaking-change, v1-v2-migration, identity

[vintagechocolate]

I also noticed hyperspace wallet show displays an Ethereum address on Base (0xF9F6...). Are the points stored on chain as USDC, or are they separate from the node identity? If points are on-chain, can they be recovered via the wallet private key even if the node identity (P-384) cannot be migrated?

[irumudikkilli]

+1, same issue. macOS, Apple M2 Max, CLI v5.1.4.

My old Hyperspace desktop app (v0.2.3) stored a P-384 key in ~/Library/Application Support/me.ginkoe.hivetissue/.settings.dat. After installing v2:

1. hyperspace migrate says "No v1 config found" — because the migrator only checks ~/Library/Application Support/hyperspace/key.pem, not the old desktop app's .settings.dat path.

2. Even if I place the key where the migrator looks, it detects the 48-byte P-384 key and prints:
   "Found v1 P-384 key (48 bytes). P-384 keys cannot be migrated to Ed25519."
   "To recover points, use: hyperspace identity import --hex-p384"

3. The --hex-p384 flag does not exist — hyperspace identity import only accepts -k, --key (Ed25519 base58/hex). The flag is referenced in the error message but was never registered on the command.

4. hyperspace login also fails with OAuth error: server_error, so I can't even link my account via the cloud.

Old P-384 public key:
MHYwEAYHKoZIzj0CAQYFK4EEACIDYgAEhkVAMnN55XkqsGvBmAsiJvcBxZTdNZ2b7BBILtviYRYRCMqDFKFYwdi6sVFEnXKcxCIWLczfx/WBoFhFoSmzxGrglk8uSByn1a3jZ5QTHgNv3RBiHPQCcDLfoJ2mea5B

Current v2 agent: 0xAGH9UUMY

The dashboard's own Known Issues section says "P-384 desktop keys (1,094 nodes) need manual identity linking" — is there a timeline for the --hex-p384 flag or another way to link?