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

Update 0069-reassertion-fee-reduction.md #516

Merged
merged 1 commit into from
Jan 5, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions 0069-reassertion-fee-reduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,12 @@ In order to help expand the network and ease the burden on new people joining th

Please note that I specifically chose 500,000 DC and not less (say 10,000 DC), to help prevent people from taking advantage of reduced reassertion fees, and to lesson the economical effect on the Network.

If approved by community (HNT) vote, this HIP will reduce **all** assertion fees in half, for three months, beginning immediately upon the migration to Solana, and will revert back after three months.

No code is required, since this may be accomplished via chain vars.

**PLEASE NOTE THAT FROM THIS POINT ON IS NO LONGER RELEVANT, ALL OF THE BELOW WILL NOT BE VOTED ON, AND MUST BE REWRITTEN IN A NEW HIP.**

In addition, to prevent location spoofing as a result of reassertion fees deduction, any given individual hotspot may only have its reassertion fees reduced every 525k blocks (approximately once per year).

Furthermore, in order to help prevent abuse of the reassertion fee reduction, there will be a minimum distance of 10KM (between the original location to the reasserted location) requirement.
Expand Down