feat: add OWS wallet support via owsAccount()

[kevarifin14]

Summary

Adds owsAccount(walletNameOrId) — creates a viem Account from an OWS encrypted vault. Use with tempo() for headless signing without raw keys.

Usage

import { owsAccount } from 'mppx/ows'
import { tempo } from 'mppx/tempo'

// Before: raw key in code
const [charge] = tempo({ account: privateKeyToAccount('0x...') })

// After: key stays encrypted until needed
const [charge] = tempo({ account: owsAccount('my-wallet') })

Requires: npm install @open-wallet-standard/core

Changes

File	What
package.json	Added ./ows export, @open-wallet-standard/core as optional peer dep
src/ows.ts	New — owsAccount() adapter

No changes to existing code paths. OWS dependency is optional (peer dep).

Note: ows is added as an optional peer dependency to match the existing pattern (@modelcontextprotocol/sdk, hono, express, elysia). Happy to make it a regular dependency if the team prefers OWS as a first-party integration.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​open-wallet-standard/​core@​1.1.0

View full report

[tmm]

Thanks for the PR! Seems best if this is solved upstream by @open-wallet-standard/core exporting owsAccount (or could name owsToAccount) so any project that uses Viem can take advantage. Also, reduces maintenance burden in this repo as we are currently moving quickly with the core API.