fau/1 device.
Algorithm
- Build the canonical string (UTF-8):
- Sign with Ed25519 (raw 32-byte secret).
- Send signature as base64url (no padding) in
X-FAU-Signature.
Headers on the request:
Test keypair
For vectors only — never use in production.
SHA-256 of empty string:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Vectors
1. Bodyless GET (/papi/pending)
Why: commonest call — fetch pending approvals.
Canonical:
2. GET with query (/papi/activity?limit=50)
Why: query string must be inside the signed target.
Canonical ends with the empty-body hash. Signature:
3. POST with JSON body
Why: body hash must match bytes exactly (no re-serialization after sign).
Signature:
deny / once / 30_days — the point of this vector is hashing, not the
decision enum.
4. Lowercase method normalized
Input methodpost must sign as POST. Path /papi/pause, body {"paused":true},
timestamp 1760000003, nonce cGF1c2Utbm9uY2UtMDAxMg.
Signature:
5. Non-ASCII JSON body
Body:{"note":"Café — naïve ☕ 東京"} (UTF-8). Path /papi/decide, timestamp
1760000004, nonce dW5pY29kZS1ub25jZS0wMQ.
Signature:
How to use these vectors
- Implement canonicalization + sign + verify in your language.
- Assert your canonical string equals each vector’s canonical (byte-for-byte).
- Assert your signature verifies with the test public key (or matches exactly if your encoder is deterministic for the test secret).
- Only then wire production keys.
/papi/activity without ?limit=50.