ERC-3000: Optimistic enactment governance standard #3000

izqui · 2020-09-24T11:10:31Z

🚧 Under construction 🚧

Check spec

MicahZoltu · 2020-10-07T16:04:27Z

@izqui Discussed this in EIPIP meeting. Please add content to this EIP (i.e., get it into draft) ASAP if you want to keep this number.

izqui · 2020-10-07T16:42:38Z

@MicahZoltu alright, will do before the end of the week. Thanks for the notice

izqui · 2020-10-12T20:55:33Z

Ready for review and merging an initial draft @MicahZoltu

MicahZoltu

The discussion-to change is required before merging as a draft. The rest are either suggestions or may be required changes prior to moving this to Review (the phase after Draft).

MicahZoltu · 2020-10-13T07:46:41Z

EIPS/eip-3000.md

+eip: 3000
+title: Optimistic enactment governance standard
+author: Jorge Izquierdo (@izqui)
+discussions-to: https://github.com/ethereum/EIPs/pulls/3000


Discussion cannot be the pull request itself. The recommended location for discussion-to links is https://ethereum-magicians.org/ but creating a separate GitHub issue is also an option if you don't want to create a thread there.

MicahZoltu · 2020-10-13T07:52:30Z

EIPS/eip-3000.md

+ERC-3000 presents a basic on-chain spec for contracts to optimistically enact governance decisions made off-chain.
+
+The standard is opinionated in defining the 6 entrypoint functions to contracts supporting the standard. But it allows for any sort of resolver mechanism for the challenge/response games characteristic of optimistic contracts.
+
+While the authors currently believe resolving challenges [using a subjective oracle](https://aragon.org/blog/snapshot) is the right tradeoff, the standard has been designed such that changing to another mechanism is possible (a deterministic resolver like [Optimism's OVM](https://optimism.io) uses), even allowing to hot-swap it in the same live instance.


The Simple Summary should be quite short. Think email subject line, forum post sub-heading, or a blurb in the last line of a table. The second paragraph here is more appropriate for the Abstract, and the third paragraph is more appropriate for the Motivation.

Also consider not using the EIP number inline in the EIP (it is redundant) and keeping the tense as a technical document assertion.

Suggested change

ERC-3000 presents a basic on-chain spec for contracts to optimistically enact governance decisions made off-chain.

The standard is opinionated in defining the 6 entrypoint functions to contracts supporting the standard. But it allows for any sort of resolver mechanism for the challenge/response games characteristic of optimistic contracts.

While the authors currently believe resolving challenges [using a subjective oracle](https://aragon.org/blog/snapshot) is the right tradeoff, the standard has been designed such that changing to another mechanism is possible (a deterministic resolver like [Optimism's OVM](https://optimism.io) uses), even allowing to hot-swap it in the same live instance.

Interface for scheduling, executing and challenging contract executions.

MicahZoltu · 2020-10-13T07:54:06Z

EIPS/eip-3000.md

+## Data structures
+
+Some data structures are definied which are later used in the standard interfaces:
+
+```solidity
+library ERC3000Data {
+    struct Container {
+        Payload payload;
+        Config config;
+    }
+
+    struct Payload {
+        uint256 nonce;
+        uint256 executionTime;
+        address submitter;
+        IERC3000Executor executor;
+        Action[] actions;
+        bytes proof;
+    }
+
+    struct Action {
+        address to;
+        uint256 value;
+        bytes data;
+    }
+
+    struct Config {
+        uint256 executionDelay;
+        Collateral scheduleDeposit;
+        Collateral challengeDeposit;
+        Collateral vetoDeposit;
+        address resolver;
+        bytes rules;
+    }
+
+    struct Collateral {
+        address token;
+        uint256 amount;
+    }
+}
+```


This isn't a standard section, and while non-standard sections aren't explicitly prohibited, they are frowned on. In this case, this is very much part of the specification and should be a sub-section of the specification.

MicahZoltu · 2020-10-13T07:55:41Z

EIPS/eip-3000.md

+    event Configured(bytes32 indexed containerHash, address indexed actor, ERC3000Data.Config config);
+}
+```
+*See [up to date source](https://github.com/aragon/govern/blob/master/packages/erc3k/contracts/IERC3000.sol)*


Specifications should be standalone documents that do not depend on external documents. Consider either inlining linked code, or adding it as an asset in this repository at ../assets/eip-3000/IERC3000.sol.

MicahZoltu · 2020-10-13T07:56:30Z

EIPS/eip-3000.md

+
+### 1. Aragon Govern
+
+- [ERC-3000 spec (interfaces)](https://github.com/aragon/govern/blob/master/packages/erc3k)


This is the spec, anything else is not the spec but just a copy/mirror/implementation/derivative.

MicahZoltu · 2020-10-13T07:59:35Z

EIPS/eip-3000.md

+- [ERC-3000 spec (interfaces)](https://github.com/aragon/govern/blob/master/packages/erc3k)
+- [Implementation](https://github.com/aragon/govern/blob/master/packages/govern-core)


As mentioned above, wherever possible content should be inlined and not linked externally. This is especially true when the linked content is so directly correlated with this content and the license is different. It is better to not link to anything at all than to link to GPL licensed software because at least that way anyone who implements from this spec alone (without seeing the GPL code) can plausibly assert that they did not see the code, and thus did not copy that code. Linking to code that is copy left licensed risks users foot-gunning themselves by clicking through to the link.

MicahZoltu · 2020-10-13T08:00:11Z

EIPS/eip-3000.md

+
+## Security Considerations
+
+A ERC-3000 configuration specifies the resolver for challenges over scheduled items.


Suggested change

A ERC-3000 configuration specifies the resolver for challenges over scheduled items.

Configuration specifies the resolver for challenges over scheduled items.

izqui · 2020-10-13T16:41:11Z

Thanks for the thorough review @MicahZoltu. All concerns should have been addressed!

MicahZoltu

Just needs a Rationale section to be merged as draft. I still recommend heading the other feedback and getting merged to Review is a bit harder (more strict requirements), but all of that can wait until after Draft is merged except this one.

MicahZoltu · 2020-10-14T06:17:24Z

EIPS/eip-3000.md

+}
+```
+
+## Implementations


Suggested change

## Implementations

## Rationale

TBD

## Implementations

Rationale is a required section. It should focus on stating the reason why specific decisions were made over alternate choices. Some of the content currently is the Motivation would be more appropriate in the Rationale.

izqui · 2020-10-14T06:56:54Z

Alright @MicahZoltu, ready to go now!

Thanks for the review, and I will make further changes before asking to change to Review.

Interface for scheduling, executing and challenging contract executions based on off-chain approval

izqui marked this pull request as draft September 25, 2020 03:10

izqui force-pushed the patch-2 branch from 1b1f793 to d8b5549 Compare September 25, 2020 03:16

izqui changed the title ~~EIP X: On-chain enactment for off-chain voting~~ ERC-3000: On-chain enactment for off-chain voting Sep 25, 2020

izqui changed the title ~~ERC-3000: On-chain enactment for off-chain voting~~ ERC-3000: On-chain enactment for off-chain votes Sep 25, 2020

izqui changed the title ~~ERC-3000: On-chain enactment for off-chain votes~~ ERC-3000: On-chain enactment of off-chain votes standard Sep 25, 2020

izqui changed the title ~~ERC-3000: On-chain enactment of off-chain votes standard~~ ERC-3000: Binding off-chain voting standard Sep 25, 2020

ERC3000 scaffolding

e20d5f5

izqui force-pushed the patch-2 branch from d8b5549 to e20d5f5 Compare September 25, 2020 03:35

MicahZoltu mentioned this pull request Sep 30, 2020

EIPIP Meeting 18 Agenda ethcatherders/EIPIP#34

Closed

ERC-3000 draft

d1938e0

izqui marked this pull request as ready for review October 12, 2020 20:52

izqui changed the title ~~ERC-3000: Binding off-chain voting standard~~ ERC-3000: Optimistic enactment standard Oct 12, 2020

izqui changed the title ~~ERC-3000: Optimistic enactment standard~~ ERC-3000: Optimistic enactment governance standard Oct 12, 2020

ERC-3000 rename

77f4274

fix

ce96cf0

MicahZoltu suggested changes Oct 13, 2020

View reviewed changes

izqui added 3 commits October 13, 2020 17:37

review

1012418

fix

c2a6d5f

typo

024a77c

MicahZoltu approved these changes Oct 14, 2020

View reviewed changes

finalize draft

7410afa

MicahZoltu merged commit 92ed7c2 into ethereum:master Oct 14, 2020

Arachnid pushed a commit to Arachnid/EIPs that referenced this pull request Mar 6, 2021

ERC-3000: Optimistic enactment governance standard (ethereum#3000)

17b55fa

Interface for scheduling, executing and challenging contract executions based on off-chain approval

Ameralameri mentioned this pull request Jul 5, 2023

Alright @MicahZoltu, ready to go now! DefiLlama/chainlist#580

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ERC-3000: Optimistic enactment governance standard #3000

ERC-3000: Optimistic enactment governance standard #3000

izqui commented Sep 24, 2020 •

edited

Loading

MicahZoltu commented Oct 7, 2020

izqui commented Oct 7, 2020

izqui commented Oct 12, 2020

MicahZoltu left a comment

MicahZoltu Oct 13, 2020

MicahZoltu Oct 13, 2020

MicahZoltu Oct 13, 2020

MicahZoltu Oct 13, 2020

MicahZoltu Oct 13, 2020

MicahZoltu Oct 13, 2020

MicahZoltu Oct 13, 2020

izqui commented Oct 13, 2020

MicahZoltu left a comment

MicahZoltu Oct 14, 2020

izqui commented Oct 14, 2020


		### 1. Aragon Govern

		- [ERC-3000 spec (interfaces)](https://github.com/aragon/govern/blob/master/packages/erc3k)

		- [ERC-3000 spec (interfaces)](https://github.com/aragon/govern/blob/master/packages/erc3k)
		- [Implementation](https://github.com/aragon/govern/blob/master/packages/govern-core)


		## Security Considerations

		A ERC-3000 configuration specifies the resolver for challenges over scheduled items.

	A ERC-3000 configuration specifies the resolver for challenges over scheduled items.
	Configuration specifies the resolver for challenges over scheduled items.

ERC-3000: Optimistic enactment governance standard #3000

ERC-3000: Optimistic enactment governance standard #3000

Conversation

izqui commented Sep 24, 2020 • edited Loading

🚧 Under construction 🚧

MicahZoltu commented Oct 7, 2020

izqui commented Oct 7, 2020

izqui commented Oct 12, 2020

MicahZoltu left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

izqui commented Oct 13, 2020

MicahZoltu left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

izqui commented Oct 14, 2020

izqui commented Sep 24, 2020 •

edited

Loading