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
Improve the security and usability of signer by allowing to create a permissioned mode signer where users can specify the permissions associated with those signers. Operations that violates those permission setups would be rejected in the transaction.
Out of scope
We are trying to define a permission standard to specify permissions in the current aptos framework. Despite such standard could be extended to any modules on blockchain, we will be limiting our focus on the aptos framework only so that we can iterate on this standard faster.
The current solution is intended to be used by Aptos Framework only. We are open to encoperate the changes to the Move on Aptos language extensions in the future if we want to extend the permission system to the general public.
High-level Overview
Right now Move on Aptos has one single permission that is represented as signer.
Smart contract uses signer to identify who authenticate this operation. Typical code would look like let addr = signer::address_of(x) and use addr as the issuer for this operation.
e.g: framework code will use signer to determine which account issued the withdraw
Smart contract needs signer to move items into/away from account.
AIP Discussion
Summary
Improve the security and usability of signer by allowing to create a permissioned mode signer where users can specify the permissions associated with those signers. Operations that violates those permission setups would be rejected in the transaction.
Out of scope
We are trying to define a permission standard to specify permissions in the current aptos framework. Despite such standard could be extended to any modules on blockchain, we will be limiting our focus on the aptos framework only so that we can iterate on this standard faster.
The current solution is intended to be used by Aptos Framework only. We are open to encoperate the changes to the Move on Aptos language extensions in the future if we want to extend the permission system to the general public.
High-level Overview
Right now Move on Aptos has one single permission that is represented as signer.
signer
to identify who authenticate this operation. Typical code would look likelet addr = signer::address_of(x)
and useaddr
as the issuer for this operation.signer
to determine which account issued the withdrawsigner
to move items into/away from account.Read more about it here: https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-103.md
The text was updated successfully, but these errors were encountered: