You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR introduces permit fee which is generated along with our traditional permit rewards. Permit fee is not shown in github comments (you may find it only in a DB) so treasury wallet (permit fee spender) must somehow claim it.
Possible solution could be to create a separate repository which treasury account owner (or contributors) could fork, then set their EVM private key in github secrets and run CRON workflow for redeeming permits automatically (permit data can be fetched from supabase DB with public anon key).
Possible solution could be to create a separate repository which treasury account owner (or contributors) could fork, then set their EVM private key in github secrets and run CRON workflow for redeeming permits automatically (permit data can be fetched from supabase DB with public anon key).
Cool idea lets do it. We can make it more sophisticated later.
This PR introduces permit fee which is generated along with our traditional permit rewards. Permit fee is not shown in github comments (you may find it only in a DB) so treasury wallet (permit fee spender) must somehow claim it.
Possible solution could be to create a separate repository which treasury account owner (or contributors) could fork, then set their EVM private key in github secrets and run CRON workflow for redeeming permits automatically (permit data can be fetched from supabase DB with public anon key).
Claim transaction example.
The text was updated successfully, but these errors were encountered: