Skip to content

bug: proxy commands fail on nested events and save regular proxy mapping backwards #916

@bitloi

Description

@bitloi

Proxy receipts can include events in a nested structure (event.event.event_id), but current proxy command handling expects event.event_id. Because of that, successful proxy create and proxy add calls can fail to read PureCreated / ProxyAdded data correctly.

There is also a data mapping issue in the interactive save path for proxy add: regular proxy values are written backwards in the address book. The delegatee and delegator end up swapped between ss58_address and spawner, which makes saved proxy config inconsistent and confusing to reuse.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions