Keys endpoint

Generate SPECTER spending/viewing keys and meta-address payload

Single-call key generation

POST /api/v1/keys/generate returns spending and viewing keypairs plus a meta-address.

Use output in next steps

Feed meta_address into the stealth create endpoint.

Endpoint

POST /api/v1/keys/generate

No request body is required.

Typical flow

1. Call the endpoint

   Trigger key generation once per new recipient identity.

2. Store secrets securely

   Persist spending_sk and viewing_sk in encrypted storage only.

3. Publish meta-address

   Use meta_address with IPFS + ENS/SuiNS registration.

Example calls

cURL

curl -s -X POST http://localhost:3001/api/v1/keys/generate | jq .

JavaScript

const res = await fetch("http://localhost:3001/api/v1/keys/generate", {
  method: "POST"
});

const keys = await res.json();
console.log(keys.meta_address);

Response schema

spending_pk · string · required

Hex-encoded spending public key.

spending_sk · string · required

Hex-encoded spending secret key (sensitive).

viewing_pk · string · required

Hex-encoded viewing public key.

viewing_sk · string · required

Hex-encoded viewing secret key (sensitive).

meta_address · string · required

Hex-encoded SPECTER meta-address combining spending + viewing public keys.

view_tag · integer · required

Base view tag derived from viewing public key bytes.

Never log or commit spending_sk or viewing_sk.

How `view_tag` is computed here

The endpoint computes view_tag from the viewing public key bytes (compute_view_tag(viewing.public.as_bytes())).

What this endpoint does not do

It does not persist key material to disk and does not register ENS/SuiNS records.