Whitelisting (tax exemption) feature according to prop #11824 #393
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- several fixes for tax exemption handling
- upgrade test
- added test
9 tasks
|
I already adjusted this to be compatible with the upcoming v3.0.1 (sdk 0.47). Waiting for the merge to fix remaining issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
alternative implementation to #388 using message types and v1 governance
Introduce zone-based tax exemption.
Zones are always tax-free internally.
Optionally they can be set to be tax-free for incoming and/or outgoing txs.
Cross-Zone transactions are always taxed, unless cross-zone exemption is also set for the zone
Report of required housekeeping
(FOR ADMIN) Before merging