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.

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

Crypto2099 Information and Voting Reservation #68

Conversation

Crypto2099
Copy link
Collaborator

Reserving entries for:

  1. Informational metadata post (Key 411) which should generally take the format of an array of string
  2. Crypto2099 On-Chain Voting Mechanism keys for Ballot Proposal, Voter Registration/Identification Information, and Voter Ballots.

Adding metadata label reservations for Crypto2099 On-Chain Voting mechanism (https://vote.crypto2099.io)

Reserved 98 slots for submission of voting ballots to support the "Vote by Dust" or other potential future use cases where multiple votes may be submitted in a single transaction.
@mmahut
Copy link
Contributor

mmahut commented Feb 20, 2021

Can you please elaborate on "General information metadata"?

@Crypto2099
Copy link
Collaborator Author

Can you please elaborate on "General information metadata"?

I have used this index, as have other including Andrew Westberg and more, to submit "general" metadata information to document on-chain. 411 was the old telephone prefix in the United States to dial "information" and the concept here was to reserve a documented index to use for these.

The format is designed to be an array of strings that can be recompiled into a cohesive piece of text, utilizing an empty string entry as a "paragraph break".

Example:

{
  "411": [
      "This is line one of my information...",
      "it wraps around to another line because the first line is >64char",
      "",
      "This is a new paragraph.",
    ]
}

@crptmppt
Copy link
Contributor

@Crypto2099 Hi! Can you resolve the conflicts / rebase the branch?

@Crypto2099
Copy link
Collaborator Author

Closing this one in favor of #80 which follows the new format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants