Contract Metadata Standards and Conventions #52
Draft
accessor-io wants to merge 7 commits into
Draft
Conversation
corrected filename
corrected creation date
initial draft commit
- Initial reorganization of ENSIP-X document structure - Added Table of Contents with internal anchors - Added Terminology and Conformance Language section - Restructured sections into standard specification flow - Moved large schemas and examples to appendices - Added explicit Conformance section - Consolidated Security Attestation content - Improved readability with tables and consistent formatting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Initial pull request for Contract Metadata Standards and Conventions. This pull request suggests a technical standard to Ethereum Name Service that will guide project maintainers, owners and authorities across Ethereum Blockchain Network in naming deployed and verified contracts. This document will provide hierarchical structure requirements and guidance for metadata tool builders and or services.