Add event to pure proxy deletion#7995
Conversation
It is required to kill the pure proxies later.
b6495f8 to
93f89d1
Compare
|
@ggwpez since this modifies an already existing |
bkchr
left a comment
There was a problem hiding this comment.
You can get the extrinsic index from the EventRecord::Phase already. You don't need to store it here extra.
|
@bkchr thanks for pointing that out; will roll back that change, but still keep the Regarding Just to check: there's no better way to check these data through the PJS dashboard than to use |
In the tutorial they are also subscan. Generally this is quite horrible and should not use PJS. However, I'm not sure if there already exists a dedicated proxy UI (probably mainly around multisigs right now). |
Did you mean that they shouldn't be using both Subscan and PJS for this task? |
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
# Description ~~The `PureCreated` event, used in the `pure_proxy` extrinsic, is used to track the creation of pure proxies. It now has the `extrinsic_index` of the `pure_proxy` call from the block in which it was executed, which is required to kill the pure proxies later.~~ The `pallet_proxy::kill_pure` extrinsic now emits an event. ## Integration N/A ## Review Notes N/A
Description
ThePureCreatedevent, used in thepure_proxyextrinsic, is used to track the creation of pure proxies.It now has the
extrinsic_indexof thepure_proxycall from the block in which it was executed, which is required to kill the pure proxies later.The
pallet_proxy::kill_pureextrinsic now emits an event.Integration
N/A
Review Notes
N/A