siwa-keyring-proxy

You can isolate private keys during SIWA signing by delegating them to a self-hosted keyring proxy. This ensures the agent's private keys never touch the client, protecting them from prompt injections and compromise.

Yes, you can add optional Telegram-based 2FA to high-value SIWA signing requests. This creates an auditable, self-hosted, non-custodial signing workflow with an extra layer of verification.

You can register an on-chain agent via ERC-8004 by deploying a keyring proxy signer and integrating it with your SIWA client. This process creates an auditable signing workflow for agent registration.

Yes, the keyring proxy supports deployment via Docker or Railway. This allows you to self-host a non-custodial signer with audit trails for signing requests.

The best way to prevent prompt injection attacks is using key isolation. By delegating private keys to a self-hosted keyring proxy, the keys never touch the client, eliminating exposure to compromise.

You should use a self-hosted signer to keep your private keys non-custodial and isolated from the client. This approach provides audit trails for signing requests and protects against client-side compromise.