The old /protocol/tip20-rewards/overview route now redirects to the T7 deprecation guidance, so I do not think the removed rewards overview itself needs to be restored.
I did find two remaining references to startReward() in the evergreen protocol docs:
src/pages/docs/protocol/fees/spec-fee.mdx lists it as a TIP-20 fee-token inference call.src/pages/docs/protocol/transactions/spec-tempo-transaction.mdx lists it in limited-key spending-limit tracking.
The current TIP-20 ABI exposes distributeReward() rather than startReward(). The T7/T8 upgrade docs say new reward opt-ins and distributions are deprecated/no-ops, while previously settled rewards remain claimable.
Before proposing a narrow documentation update, could you confirm:
- Should these sections be updated to omit reward calls from the current evergreen behavior, or retained as explicitly labeled pre-T7 historical behavior?
- If historical behavior should remain documented, is
distributeReward() the intended selector to describe for the pre-T7 path?
- Is the T7/T8 upgrade wording the preferred source of truth to reuse?
Happy to prepare a focused docs PR once the intended framing is clear.
The old
/protocol/tip20-rewards/overviewroute now redirects to the T7 deprecation guidance, so I do not think the removed rewards overview itself needs to be restored.I did find two remaining references to
startReward()in the evergreen protocol docs:src/pages/docs/protocol/fees/spec-fee.mdxlists it as a TIP-20 fee-token inference call.src/pages/docs/protocol/transactions/spec-tempo-transaction.mdxlists it in limited-key spending-limit tracking.The current TIP-20 ABI exposes
distributeReward()rather thanstartReward(). The T7/T8 upgrade docs say new reward opt-ins and distributions are deprecated/no-ops, while previously settled rewards remain claimable.Before proposing a narrow documentation update, could you confirm:
distributeReward()the intended selector to describe for the pre-T7 path?Happy to prepare a focused docs PR once the intended framing is clear.