Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update EIP-6366: Move to Review #6770

Merged
merged 10 commits into from
Oct 24, 2023
Merged

Update EIP-6366: Move to Review #6770

Changes from 3 commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
c9a207b
Update eip-6366 following the suggestion from Victor
chiro-hiro Mar 24, 2023
eeaa17b
Update eip-6366.md
chiro-hiro Mar 24, 2023
8b90362
Update status to review
chiro-hiro Mar 24, 2023
42ceb1e
Update EIPS/eip-6366.md
chiro-hiro Apr 10, 2023
1f945b9
Update EIP-6366 and move metadata to EIP-6617
chiro-hiro Sep 22, 2023
5a7bdd5
Fix the EIP link issue
chiro-hiro Sep 22, 2023
4210a38
Update eip-6366.md
chiro-hiro Oct 3, 2023
fe2a963
Update EIPS/eip-6366.md
chiro-hiro Oct 10, 2023
7ce6f64
Remove duplicated requires
chiro-hiro Oct 10, 2023
4d3c0b5
Merge branch 'master' into feature/update_eip_6366
chiro-hiro Oct 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions EIPS/eip-6366.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
eip: 6366
title: Permission Token
description: A new token that held the permission of an address in an ecosystem
description: A new token that holds the permission of an address in an ecosystem
chiro-hiro marked this conversation as resolved.
Show resolved Hide resolved
author: Chiro (@chiro-hiro), Victor Dusart (@vdusart)
discussions-to: https://ethereum-magicians.org/t/eip-6366-a-standard-for-permission-token/9105
status: Draft
status: Review
type: Standards Track
category: ERC
created: 2022-01-19
chiro-hiro marked this conversation as resolved.
Show resolved Hide resolved
Expand All @@ -13,13 +13,13 @@ requires: 6617

## Abstract

This EIP offers an alternative to Access Control Lists (ACLs) for granting authorization and enhancing security. An `uint256` is used to store permission of given address in a ecosystem. Each permission is represented by a single bit in `uint256` as described in [ERC-6617](./eip-6617.md). Bitwise operators and bitmasks are used to determine the access right which is much more efficient and flexible than `string` or `keccak256` comparison.
This EIP offers an alternative to Access Control Lists (ACLs) for granting authorization and enhancing security. An `uint256` is used to store permission of given address in a ecosystem. Each permission is represented by a single bit in a `uint256` as described in [ERC-6617](./eip-6617.md). Bitwise operators and bitmasks are used to determine the access right which is much more efficient and flexible than `string` or `keccak256` comparison.
chiro-hiro marked this conversation as resolved.
Show resolved Hide resolved

## Motivation

Special roles like `Owner`, `Operator`, `Manager`, `Validator` are common for many smart contracts because permissioned addresses are used to administer and manage them. It is difficult to audit and maintain these system since these permissions are not managed in a single smart contract.

Since permission and role are reflected by the permission token balance of the relevant account in the given ecosystem, cross-interactivity between many ecosystems will be made simpler.
Since permissions and roles are reflected by the permission token balance of the relevant account in the given ecosystem, cross-interactivity between many ecosystems will be made simpler.

## Specification

Expand Down Expand Up @@ -65,7 +65,7 @@ interface IEIP6366Core {
* Allows `_delegatee` to act for the permission owner's behalf, up to the `_permission`.
* If this function is called again it overwrites the current granted with `_permission`.
* `approve()` method SHOULD `revert` if granting `_permission` permission is not
* a subset of all available permission of permission owner.
* a subset of all available permissions of permission owner.
* @param _delegatee Delegatee
* @param _permission Subset permission of permission owner
*/
Expand Down