guardian-auth-signature-flows

Implement and debug Guardian authentication and Falcon/ECDSA signature flows across server and clients.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/hduoc2003/leviathan-guardian --skill guardian-auth-signature-flows-hduoc2003
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guardian-auth-signature-flows
Source: https://github.com/hduoc2003/leviathan-guardian/tree/main/.agents/skills/guardian-auth-signature-flows
Command: npx skills add https://github.com/hduoc2003/leviathan-guardian --skill guardian-auth-signature-flows-hduoc2003

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Guardian's authentication and signature flows span the Rust server, Rust client, TypeScript clients, and multisig SDKs, making crypto-adjacent changes fragile and error-prone. This Skill guides safe edits to request signing, ack signing, keystores, and Falcon/ECDSA scheme handling without breaking cross-boundary behavior. ## Core Features & Use Cases - Signature Path Classification: Identifies whether a change affects request auth metadata, proposal signatures, ack signing, keystores, encoding, or scheme selection before editing. - Boundary-First Editing: Directs changes to the lowest boundary module first (server verification, Rust client auth, TS HTTP auth) and normalizes hex, bytes, base64, and public keys at conversion boundaries. - Dual-Scheme Validation: Enforces testing both Falcon and ECDSA whenever a touched path supports both schemes, preserving x-pubkey, x-signature, x-timestamp, ack_sig, ack_pubkey, and ack_scheme behavior. - Use Case: When modifying ack signing in crates/server/src/ack, use this Skill to locate all downstream consumers in the multisig SDKs and examples, then run the targeted cargo and npm test suites plus smoke tests. ## Quick Start Use the guardian-auth-signature-flows skill to update the request signing logic in the TypeScript client and verify both Falcon and ECDSA paths still pass.

Frequently Asked Questions about guardian-auth-signature-flows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change request signing in the Guardian TypeScript client?▼

Edit packages/guardian-client/src/auth-request.ts and conversion.ts, normalizing hex, bytes, and base64 at the boundary module. Preserve the x-pubkey, x-signature, and x-timestamp header behavior, then run npm test in packages/guardian-client.

How do I test both Falcon and ECDSA signature schemes in Guardian?▼

Run cargo test -p guardian-client and cargo test -p guardian-server, plus npm test in packages/guardian-client. If the change reaches multisig execution, also run the miden-multisig-client tests and the Rust and TypeScript multisig smoke tests.

Does Guardian auth require public keys for ECDSA signatures?▼

Yes, ECDSA proposal signature flows require public key information downstream, so do not drop public key data when editing those paths. Verify public key requirements separately for ECDSA proposal signatures.

Which files handle ack signing on the Guardian server?▼

Ack signing lives in crates/server/src/ack/mod.rs, the miden_falcon_rpo and miden_ecdsa subdirectories, and the ack-keygen binary. Auth verification is in crates/server/src/metadata/auth and the HTTP and gRPC API layers.

Why did my signature change break multisig proposal execution?▼

Execution depends on ack_sig, ack_pubkey, and ack_scheme fields remaining populated, and on signature encoding consumed by the multisig SDKs. Check packages/miden-multisig-client signature and encoding utilities and run the multisig smoke tests to confirm end-to-end behavior.