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.

Sign up for GitHub

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

Jump to bottom

Explicitly define some ambiguities #613

Merged
merged 3 commits into from Apr 8, 2023
Merged

Explicitly define some ambiguities #613

merged 3 commits into from Apr 8, 2023

Conversation

mawdegroot
Copy link
Contributor

This PR explicitly defines some of the remaining ambiguities:

  • The actually burned DC is used for $A$ in the DAO Utility Score
  • Not required to onboard to every subDAO the hardware is capable of
  • Payer of onboarding fees is explicitly left to the subDAO
  • Make explicit what devices need to be onboarded
  • Show the progression of the dynamic onboarding fee over time

@mawdegroot mawdegroot force-pushed the mg/explicit-definitions branch 3 times, most recently from 64f4f1d to e4bc595 Compare April 8, 2023 19:08
@vincenzospaghetti vincenzospaghetti merged commit aed1f18 into helium:main Apr 8, 2023
@vincenzospaghetti vincenzospaghetti mentioned this pull request Apr 8, 2023
Closed
@mawdegroot mawdegroot deleted the mg/explicit-definitions branch April 9, 2023 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@mawdegroot @vincenzospaghetti