This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 42
Consider a governance token for v2 #119
Labels
Milestone
Comments
By way of implementation, it would be really easy to add issuance to the outsourced logging. So any time a log event is fired, a corresponding number of governance tokens are issued. |
Not sure if the outsourced logging contract would logically make most sense for the mint. What about each |
Makes sense to me 🤷♂️ especially since we've discussed some other spots where we might want to give out the governance token. |
what I mean is that the logging calls are already authenticated state
changes. So you can reuse authentication and probably save a call
…On Mon, Aug 12, 2019, 08:00 Matt Luongo ***@***.***> wrote:
What about each Deposit calling TBTCSystem and minting it through there?
Makes sense to me 🤷♂ especially since we've discussed some other spots
where we might want to give out the governance token.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#119?email_source=notifications&email_token=ACNN4MLLX7QYBIFPQX24CUDQEF3JZA5CNFSM4HMJPUH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4CZ4YA#issuecomment-520461920>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACNN4MOBWRFVPBLVOX2ZSJTQEF3JZANCNFSM4HMJPUHQ>
.
|
mhluongo
changed the title
Consider a governance token
Consider a governance token for v2
Apr 26, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Via the rationale in #22, each time a deposit is funded with 1 BTC
Right now, we aren't concerned with how this token will be used to make governance decisions- only that it's properly distributed for later governance.
The text was updated successfully, but these errors were encountered: