juanpmcianci
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

Your note will be visible on your profile and discoverable by anyone.
Your note is now live.
This note is visible on your profile and discoverable online.
Everyone on the web can find and read all notes of this public team.
See published notes
Unpublish note
Please check the box to agree to the Community Guidelines.
View profile
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Goal-oriented minting ### Introduction In these notes we present a goal-oriented, adaptive minting mechanism. In particular, the core idea behind this mechanism is to 1. propose a set of observable, measurable (on-chain), quantities of interest — commonly known as Key Performance Indicators (KPIs), together with some time-dependent target values for these metrics, and 2. Adjust the minting rate according to how close (or far) these network parameters are from their target, in such a way that a *positive sum game is created*. That is, in a way so that token recipients benefit whenever the network benefits. We formalize these ideas in the following section. ### Formalized Mathematical Model **Purely goal-driven.** Suppose we have $N$ different KPIs. Let $\Theta \subset \mathbb{R}^N$ be the set of all possible states of our KPIs, let $\theta_t \in \Theta$ represent a specific state of these indicators at any given time $t$, and let $\theta_t^*\in\Theta$ be the vector of these target values at time $t$. We consider that to each KPI $i$ there corresponds a (relative) level of importance $w_i\geq0$ with $\sum^N_iw_i=1$. This gives us a way of *favoring* one KPI over the other (or weight them all equally as $w_i=1/N, \ \forall i=1,..,N$). Furthermore, for any $i=1,2,\dots,N$, let $\delta_i:\mathbb{R}^2\to[0,1]$ denote an arbitrary measure of *distance* between $\theta_{i,t}$ and $\theta^*_{i,t}$ at time $t.$ Notice that here I am using the term “distance” in a very loose way. Here each $\delta_i$ is non-decreasing with $z=\theta_{i,t}-\theta_{i,t}^*$* and has the property that $$\delta_i( \theta_{i,t}, \theta^*_{i,t})=0,\ \forall \ \theta_{i,t}\geq \theta^*_{i,t}$. Furthermore, we define the N-dimensional distance $\delta:\Theta^2\to[0,1]$ as $$ \begin{align} \delta(\theta_t,\theta^*_t):=\sum_{i=1}^N w_i\delta_i( \theta_{i,t}, \theta^*_{i,t}) \end{align} $$ Notice then that under our formulation each specific KPI has its own distance function \delta_i and (time-dependent) target value $\theta^*_{i,t}.$ Lastly, let $\rho_m,\rho_M\in \mathbb{R}_{\geq 0}$ denote the minimum (possibly 0) and maximum minting rates at any moment in time. These upper and lower bounds provide some *safety* rails so that (i) *at least some* tokens are minted when things are not going well or (ii) we don’t over mint when things are going well. For any fixed $$ $t$, we can then define the *instantaneous minting rate* as: $$ \begin{align}\rho(\theta_t,\theta_t^*) = \rho_m + \left[\rho_M - \rho_m\right] \cdot\left( 1 - d(\theta_t, \theta_t^*) \right)\end{align} $$ Notice then that, as the network hits its KPIs (i.e., $\delta\approx 0$), then we have that $\rho\approx \rho_M$. Conversely, when the network is lagging behind its KPIs, $\rho\approx\rho_m.$ The formulation above thus induces a (simple) goal-adaptive minting mechanism: If tokens are being minted at every epoch $\tau$ (e.g., every $M\geq1$ blocks), thus, the network mints $\rho(\theta_\tau,\theta_\tau^*)$ tokens until it runs out of tokens to distribute (if at all). **Goal-and-time.** The previous formulation only depended on how close the network is to achieving its goals. Notice that, in general, one can have this adaptive minting rate to be a function also of time; this is desirable if one wants to explicitly include a dependency of time (to account for, e.g., adoption times, etc). In order to account for this, let us introduce a sigmoid decay function $\sigma:\mathbb{R}_{\geq 0}\times \Theta^2\to[0,1]$ defined by: $$ \begin{align}\sigma(t, \theta_t,\theta_t^*) = \left(1-\frac{1}{1 + e^{-\kappa(1- \delta) (t-\tau(1-\delta))}}\right)\sigma_0 \end{align} $$ where we used $\delta=\delta(\theta_t,\theta_t^*)$ above. Here, $\sigma_0$ is a normalization factor, $\kappa,\tau\in \mathbb{R}_+$ the shape and decay parameters of the decay function, as shown below. Thus, intuitively, if the network is taking longer to "take off" for example, the decay parameter (how long is it subsidized for) decreases ![image](https://hackmd.io/_uploads/Sy0hFHMRA.png) Finally, we can combine Eqs (2) and (3) to define the overall token distribution rate as: $$ \begin{align}r(t, \theta,\theta_t^*) := \rho(t) \cdot \sigma(t, \theta_t,\theta^*_t)\end{align} $$ This function, $r$, encapsulates the dynamic, responsive nature of our token distribution model, adjusting both the level and decay of distribution based on real-time performance against set targets ### Example Metrics These metrics are pretty specific to each protocol and depend on their core KPI. they can be e.g., amount at stake (e.g., Ethereum), onboarded data (e.g., Filecoin), TVL, etc. Notice that these goals can also be given in terms of rates (data growth rate, etc.) **A cautionary tale:** It is pretty optimistic to assume that the goals set at a (pre-product) protocol design stage will hold as true goals indefinitely without need for change. Furthermore, once these metrics are hardcoded it becomes *very tricky* to change them —usually requiring some community consensus and a network upgrade. An example of this is Filecoin, which uses a goal-oriented mechanism for its block rewards. Their KPI is onboarded data at time t. As a target they chose a function called *baseline power,* which is a curve that grows exponentially. While this level of growth is attainable at the earlier stages of the protocol such an onboarding of data cannot continue forever, which means that eventually that target will become unattainable (indeed, several results in the literature suggest that technology adoption curves are sigmoid). This makes their minting rate *stuck* at a relatively underperforming level, even though onboarded data has remained relatively stable (*network QA Power below).* This is shown in the figure below. ![image](https://hackmd.io/_uploads/rkEWcSzC0.png) **Figure:** Filecoin’s historical storage power (blue and green) vs goal (*baseline power, light blue). Source: [Starboard Ventures](https://dashboard.starboard.ventures/capacity-services).* **Take-home message**: goals need to be adaptive (i.e., they can’t be “set and forget”); otherwise they might lead to unwanted behaviors. **Goal adaptability.** In our model, goal adaptability could be implemented in two main ways: 1. **Flexible KPI Reassessment**: The KPIs themselves can be reassessed periodically to ensure they are still relevant. This might require governance mechanisms that allow for adjusting the weightings or even introducing new metrics if the old ones no longer capture the state of the network adequately. 2. **Dynamic Target Values**: Rather than fixing the target values of KPIs at the outset, we propose a dynamic approach where these targets evolve based on historical data, market trends, and the network’s overall health. This ensures that the minting mechanism remains responsive to changing conditions. For example, the target values could follow non-linear trajectories such as sigmoid or logarithmic functions to account for adoption saturation or technical plateaus. One such way of doing so is to combine a 1559-like adaptivity mechanism for $\theta^*_{i,t}$ together with an [AIMD](https://en.wikipedia.org/wiki/Additive_increase/multiplicative_decrease) mechanism (a TCP congestion control algorithm). $$ \begin{align}\theta^*_{i,t+1} &= \theta^*_{i,t} \cdot \left(1 + \eta_t \cdot \frac{\theta_{i,t} - \theta^*_{i,t}}{\theta^*_{i,t}}\right) \\\eta_{t+1} &=\begin{cases}     \eta_t + \Delta_\eta & \text{if } \theta_{i,t} > \theta^*_{i,t} \\    \eta_t \cdot \gamma & \text{if } \theta_{i,t} \leq \theta^*_{i,t}\end{cases}\end{align} $$ where $\gamma, \Delta_\eta$ are arbitrary parameters related to the speed of adaptation in the AIMD mechanism . Notice that this needs to be instantiated with a minimum value as well as an initial condition. ![image](https://hackmd.io/_uploads/B1Ni9Sf0R.png) **Remark:** this idea has been applied by [Reijsbergen et. al (2022)](https://ieeexplore.ieee.org/document/9680496) in the context of proposing an adaptive EIP-1559 transaction fee mechanism.

Import from clipboard

Paste your markdown or webpage here...

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template has been removed or transferred.
Upgrade
All
  • All
  • Team
No template.

Create a template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

Slide Example

API Docs

Edit in VSCode

Install browser extension

Contacts

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

Note content is identical to the latest version.
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully