Maintenance - We're currently working on things and you might experience some issues. Should be wrapped up soon!

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

3
[New proposal submitted] Update registrations
Author Summary
carlslarson is in New proposal submitted
Post Body

There have been a few more pre-registrations. In order to allow these pre-registrants to actually register a new merkle root must be accepted by the dao contract and this is done by winning a 2/3 majority vote of dao members with votes weighted by karma (not REC). Proposals and voting occur on the dao dapp. Proposals currently only last 24 hours (6000 blocks) as it's expected to pass things straightforwardly during the testnet deployment phase. For verification purposes updated user registration data including new user merkle proofs can be found at this git branch.

Ok, so if the above doesn't make much sense, the real point is essentially to have a process that is two-fold:

  1. Verify-ably compile user registration data (karma, first content timestamp) as well as trustlessly allow user self-registration
  2. Submit approval of new user registration batches to existing dao member vote (existing dao can set terms on these new reg batches)

Author
Account Strength
100%
Account Age
10 years
Verified Email
Yes
Verified Flair
No
Total Karma
25,929
Link Karma
9,845
Comment Karma
15,068
Profile updated: 3 days ago
Posts updated: 7 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
6 years ago