Skip to content

Login attempts that appear to fail client-side can silently succeed on-chain, leaving orphaned paid delegate keys #384

Description

@Olalekan2345

A memwal_login attempt where the local MCP client never received credentials (link likely expired mid-flow) was later found, via the dashboard's Delegate Keys table, to have actually completed its add_delegate_key transaction on-chain — real gas was spent creating a delegate key that was never used locally. No warning is surfaced when this happens, so users can accumulate paid, valid, unused signing keys without realizing it. Recommend detecting and flagging orphaned keys, or having the login flow verify local credential receipt before considering the on-chain step "committed" from the user's perspective.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions