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

Lining up safe harbour durations #20

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

paulbarclay
Copy link

The durations of the rule were contradictory, between (a)(1) - 3 years from the first token sale, and (e) - 3 years from filing the notice of reliance. Also, Section (h) allows filing as soon as practicable, meaning a prior Token, which has already had more time to reach Network Maturity, could gain extra time to reach Network Maturity that a new Token could not.

To that effect, make the duration the later of (a) three years after the date of first sale of tokens, or (b) three years after the rule is effective. The second ensures a level playing field for projects that previously sold tokens; their clock starts on a clearly-defined day. Apologies to the SEC employees who, three years after that date, have to sift through a couple of thousand exit reports.

The durations of the rule were contradictory, between (a)(1) - 3 years from the first token sale, and (e) - 3 years from filing the notice of reliance. Also, Section (h) allows filing as soon as practicable, meaning a prior Token, which has already had more time to reach Network Maturity, could gain extra time to reach Network Maturity that a new Token could not.

To that effect, make the duration the later of (a) three years after the date of first sale of tokens, or (b) three years after the rule is effective. The second ensures a level playing field for projects that previously sold tokens; their clock starts on a clearly-defined day. Apologies to the SEC employees who, three years after that date, have to sift through a couple of thousand exit reports.
@paulbarclay
Copy link
Author

Addresses issue #19

@paulbarclay
Copy link
Author

Now also addresses issue #33

@wasima2020
Copy link

Now also addresses issue #33

Agreed - Existing projects, pioneers, must not be excluded from the safe harbor - thanks for recognizing.

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.

2 participants