브라우저의 읽어주기 지원을 확인하는 중…
이 읽기 자료는 현재 영어로 제공됩니다. 인터페이스에는 선택한 언어가 적용됩니다.
영어 원문 읽기 →An account can have several keys
Distinguish account identity from a key's permissions.
On NEAR, the address identifies the account while its access keys determine what can be authorized.
- NEAR account ID
- Full-access key
- Restricted function-call key
Read the account ID
NEAR supports named accounts, such as human-readable names, and implicit accounts derived from key material. An account can hold assets and a contract. Treat the complete account ID as the destination: a similar-looking name is not another spelling of the same account, and mainnet and testnet have separate state.
Read each permission
Full-access keys control the account. Function-call keys restrict authorization to a contract and potentially methods, with an optional allowance. Multiple keys can coexist. Check an app's requested scope, not just login success.
Classify two permissions
Use a fictional account and the access-key documentation.
- Give one key full account control.
- Give another permission to call a named method on one example contract.
- Explain why an app needing that method does not automatically need full account control.
Permissions can be narrower than the account that grants them.
Read the permission scope before approving an app connection.
진도는 이 기기에 저장됩니다.