feat(protocol): add personal server registration signing

[tnunamak]

Summary

• add canonical Personal Server registration typed-data/signing helpers
• add viem-compatible signer adapter for local accounts and wallet clients
• add isolated first-party Account helper for the constrained PS registration signing endpoint

Architecture

• protocol helpers are Account/Privy/OAuth-free
• Account integration is isolated under src/account and only knows an accountOrigin + endpoint contract
• Account helper defaults to the stable v1 route, but normalizes the current experimental Account response shape so unity can test before the v1 route is added

Validation

• npm test --workspace @opendatalabs/vana-sdk -- --run src/protocol/eip712.test.ts src/protocol/personal-server-registration.test.ts src/account/personal-server-registration.test.ts
• npm run typecheck --workspace @opendatalabs/vana-sdk
• npm run build --workspace @opendatalabs/vana-sdk
• push hook: npm run typecheck and npm run test:coverage (610 tests passed)

Notes

• stacked on docs(vana-sdk): surface VanaStorage as the default storage provider #144 (volod/vana-storage-org-default) so the PR diff is focused; rebase/retarget to main after docs(vana-sdk): surface VanaStorage as the default storage provider #144 lands

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
vana-console	Ignored		May 14, 2026 3:42pm
vana-rbac-auditor	Ignored		May 14, 2026 3:42pm
vana-vibes-demo	Ignored		May 14, 2026 3:42pm

[github-actions]

Findings:

• packages/vana-sdk/src/account/personal-server-registration.ts:164: AccountPersonalServerRegistrationRequest exposes chainId and verifyingContract via BuildPersonalServerRegistrationTypedDataInput, but the Account POST body drops both. If a caller passes either override and Account returns a signed response without typedData, buildSignedResult() reconstructs typed data using the overrides, while Account likely signed the default/config domain. That can return a signature paired with the wrong typed data. Either send these fields, or remove them from the Account request type and only allow config.

• packages/vana-sdk/src/account/personal-server-registration.ts:100: parseAccountResponse() always calls response.json() before checking response.ok. A 500/404 HTML or empty response will throw a JSON parse error instead of the intended status/error message. Consider await response.json().catch(() => ({})), as other gateway code does.

Verification note: I attempted the targeted tests and typecheck, but this checkout is missing installed dev deps (vitest and @types/node), so they could not run locally.

[tnunamak]

Unity integration is merged to dev and deployed on the dev surfaces.

• Unity PR: https://github.com/vana-com/unity-surfaces/pull/54
• Dev merge commit: https://github.com/vana-com/unity-surfaces/commit/203416b8f9e8ce03111f84b5e64c947935c29723
• Test page: https://app-dev.vana.org/demo/account-signature
• Account v1 endpoint: https://account-dev.vana.org/api/v1/intents/personal-server-registration/sign

Local/dev validation passed on Unity: Account/Web typecheck, Account/Web tests, runtime boundary check, Account/Web build, plus Vercel dev deployments.

[tnunamak]

Checked the automated findings. Both are addressed on current head:

• a84748b forwards chainId and verifyingContract in the Account request body, so fallback reconstruction cannot drift from the requested domain.
• 69436e3 changes Account response parsing to tolerate non-JSON/empty error bodies and throw AccountPersonalServerRegistrationError with status/code/details instead of leaking a JSON parse failure.

Re-ran SDK focused tests/typecheck/build locally before the Unity integration; Unity PR #54 is merged to dev and dev CI/deployments are green.

[tnunamak]

Added support for the other signature we discussed: PS Lite owner binding.

Current SDK head now includes:

• protocol/personal-server-lite-owner-binding: builds/signs vana.account.v1:ps-lite-owner:<wallet> using generic/viem signers
• account/personal-server-lite-owner-binding: adapts an Account-style { getAddress, signMessage } client

Validation:

• focused owner-binding tests pass
• SDK typecheck/build pass
• push hook passed full typecheck + coverage: 45 files / 619 tests

Unity follow-up PR using the helper: https://github.com/vana-com/unity-surfaces/pull/55