EIP-1776: Legal Governance Token Standard

EIPS/eip-1776.md

@@ -0,0 +1,48 @@
+---
+eip: 1776 
+title: Legal Governance Token Standard
+description: Requires that a contract has an "owner", and that this owner has access to applicable functions so that it may easily enact the will of the DAO both on and off chain in any jurisdiction.
+author: John D Storey (@j0xhn)
+status: Draft 
+discussions-to: https://ethereum-magicians.org/t/eip-1776-erc20dao-extend-any-dao-framework-for-compliance-with-local-legal-jurisdictions
+type: Standards Track
+category: ERC
+created: 2022-02-20
+requires: 20 / 173
+---
+
+## Abstract
+While there will be many DAO token standards and patterns to come, this will allow each one to be connected with a trusted third party -- for example a laywer to carry out the will of the DAO -- without requiring all to have the same underlying governance structure. Empowering a sort of "Bring Your Own Governance" mentality.
+
+## Motivation
+Introducing this legal link is a crucial component for the governance of real world assets.  When paired with local jurisdictions will give the ability of a DAO to do real world actions such as list an item for sale, coordinate transportation or handle other "in-person" tasks on behalf of the digital DAO.
+
+## Specification
+The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
+
+The words “governance” or "utility" can be considered synonymous as one of the utilties is the governance.
+
+ERC-1776 (Token Contract)
+interface ERC4713 extends ERC20, ERC173 {
+
+    // @dev appends this name to applicable functions
+
+    function *_owner (){
+        // place duplication of contract function here with any needed alterations for owner to execute
+    };
+  }
+}
+
+## Rationale
+Allowing a third party fixes many problems faced when tokenizing a real world asset (RWA) that needs to interface with existing legal jurisdictions.
+
+## Backwards Compatibility
+The standard is ultimately designed to be backwards compatible with any token standard, but particularly to be composed with ERC20 compliant tokens as a way of allowing them to easily become DAO governance tokens, and other DAO frameworks to allow for benevolant dictators.
+
+## Security Considerations
+The security considerations mainly concern the role played by the issuers and the admin. If they do not correctly manage their members and allow for profit through non-participation it could fall into a security classification although it is designed to be a utility DAO token.
+
+It also introduces a single point of failure in which an admin could feasibly be attacked and exploited
+
+## Copyright
+Copyright and related rights waived via CC0.