Skip to content

Align CIP-104 reward engine with updated Product Order Form terms #270

Description

@gyorgybalazsi

Context

Gabi forwarded a note from Bayo Akins (2026-07-23): the Product Order Form for the Utility is being updated to align with the CIP-104 tokenomics transition. The changes are described as administrative, but they touch the exact reward mechanics our CIP-104 reward engine implements. Filing this so engineering tracks alignment.

Source: Slack thread

Commercial changes (per the note)

  1. Traffic-based app rewards — "marker-based reward sharing" is replaced with Traffic-Based App Reward sharing (CIP-104). Existing commercial reward-sharing arrangements remain unchanged; only the underlying mechanism and terminology change.
  2. Billing use case removed — the Billing use case is discontinued; all pricing/terms for it are removed.
  3. DA Registry-specific agreement — the Product Order Form becomes specific to the DA Registry (Digital Asset Tokenization Product), replacing the previous generic Utility Product Order Form.

Engineering alignment to verify

  • Traffic-based rewards: confirm the Mode A coupon-reassignment automation (PR CIP-104 Mode A coupon-reassignment automation #255) implements the traffic-based RewardCouponV2 mechanics the updated agreement now references — no lingering assumptions from the old marker-based model.
  • Beneficiary split: confirm the governance-configured reward-sharing split (SetProviderAppRewardBeneficiaries) matches the "existing commercial arrangements remain unchanged" commitment.
  • Billing removal: check whether any reward-engine or DecMan code paths, config, or docs assume the discontinued Billing use case, and flag for removal if so.
  • DA Registry scope: confirm the reward engine's decparty/app-provider assumptions are consistent with a DA-Registry-specific agreement (vs. generic Utility).

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions