Skip to content

Clarify the meaning and capture point of reward_manifest.price - #485

Open
madninja wants to merge 1 commit into
masterfrom
clarify-reward-manifest-price
Open

Clarify the meaning and capture point of reward_manifest.price#485
madninja wants to merge 1 commit into
masterfrom
clarify-reward-manifest-price

Conversation

@madninja

Copy link
Copy Markdown
Member

Closes #484

reward_manifest.price was documented only as "Price of the token at time
rewards were calculated", which reads equally well as a spot quote taken when
the manifest is written or as an average over the reward period. Neither is
what the field carries.

What the field actually holds, per reward token:

  • HNT (both sub-DAOs since HIP-138): the Pyth HNT/USD ema_price point
    estimate, no confidence adjustment, as the on-chain end-of-epoch instruction
    read it from the canonical HNT/USD feed. The rewarder recovers that same
    value off-chain, so the manifest reports the price the chain applied for the
    epoch rather than a separately-sampled one.
  • MOBILE / IOT: the most recent price the Helium price oracle had published
    when the epoch's rewards were calculated.

The comment now states the statistic, the capture point, and that Pyth's EMA
averaging window is a property of the feed with no relation to the reward
period, and links Pyth's EMA documentation for the weighting details.

State which price statistic the field carries and when it is captured, so
"price of the token at time rewards were calculated" can no longer be read
as a spot quote at manifest-write time or as an average over the reward
period.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify the meaning and calculation of reward_manifest.price

1 participant