You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Use case: There is an existing system that can manage users' stake via proxy. In order to enable it, a user needs to add proxy for their account, and then the existing system will be able to add or remove stake on the user's behalf as needed. The EVM users (with H160 addresses) need to be able to use this system as well.
Describe the solution you'd like
For that reason we need the EVM H160 addresses to be able to add ss58 proxy addresses and allow them to call subtensorModule add_stake and remove_stake extrinsics.
Describe alternatives you've considered
No response
Additional context
This is also a security concern as adding proxy accounts in a non-transparent (to the user) way can be dangerous long-term. - Perhaps this can be resolved with block explorer that would show that an address has a proxy.
Implementation details
Add methods add_proxy and remove_proxy to the staking precompile. These methods should accept bytes32 public key of the proxy and call proxy pallet internally to add proxy address with permission to call add_stake and remove_stake extrinsics.
The text was updated successfully, but these errors were encountered:
This could be very useful to update EVM holders delegation without having to do transactions all the time. Later down the line I'm wondering if it could also help do more on subtensor from EVM without necessarily having to do cross-transactions / calling precompile contracts all the time.
About the security concerns, would they be different from the current proxy pallet implementation on subtensor?
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Use case: There is an existing system that can manage users' stake via proxy. In order to enable it, a user needs to add proxy for their account, and then the existing system will be able to add or remove stake on the user's behalf as needed. The EVM users (with H160 addresses) need to be able to use this system as well.
Describe the solution you'd like
For that reason we need the EVM H160 addresses to be able to add ss58 proxy addresses and allow them to call subtensorModule add_stake and remove_stake extrinsics.
Describe alternatives you've considered
No response
Additional context
This is also a security concern as adding proxy accounts in a non-transparent (to the user) way can be dangerous long-term. - Perhaps this can be resolved with block explorer that would show that an address has a proxy.
Implementation details
Add methods
add_proxy
andremove_proxy
to the staking precompile. These methods should accept bytes32 public key of the proxy and call proxy pallet internally to add proxy address with permission to calladd_stake
andremove_stake
extrinsics.The text was updated successfully, but these errors were encountered: