Amend CIP-0104 to align with Featured App Guidance 2.0b

Five North wants to endorse this. 

To be transparent, we are directly affected as app operators as well, one of them being Loop Wallet, which will no longer earn app rewards on user-submitted transactions. The new requirements also impact other projects we have underway. 

We support it regardless, because it is the right design for the longevity of the network and the stability of its reward economy:

1. Rewards follow real burn, enforced at the protocol level and saying goodbye to markers 
2. keeping rewards s under $1 per $1 of burn, forces apps to generate real revenue
3. Paying asset rewards after app rewards keeps app income predictable and rewards tied to genuine activity.

Thanks to everyone who worked on this. 

Y.

On Oct 23, 2026, at 04:18, Bernhard Elsner via lists.sync.global <bernhard.elsner=digitalasset.com@...> wrote:



Hi all,

As you’ve probably seen on tokenomics-announce, the Featured App Guidance 2.0b has been approved by the Tokenomics committee. The following PR amends CIP-0104 to align with the approved guidance: https://github.com/canton-foundation/cips/pull/262 

You can see the changes here and a preview of the full file is available on: https://github.com/meiersi-da/cips/blob/meiersi/cip104-amendment/cip-0104/cip-0104.md

Note that the amended roll-out plan proposes to start dry-running the new computation in December 2026 to give the community a preview of the new computation as soon as possible. To hit this timeline, the Splice maintainers will need to merge the corresponding Daml changes to Splice next Tuesday, 27th of October 2026 so that they make it into the Splice 0.10.0 release, which is likely before the CIP amendment has been fully voted. 

I believe that doing this early merge is the right thing to do for the following two reasons:

1. None of these changes impacts production app rewards. All of them only run in dry-run mode. The production enablement of traffic-based app rewards via a SV config vote on MainNet is gated as usual on the formal approval of the amended CIP-0104.

2. Merging these changes early gives the community extra time to preview and react to the new computation before it goes live.

If changes to this CIP-0104 amendment are required, then the Splice maintainers are confident that they can adopt them on top of the changes built for the preview; as they’ve proven to be able to do with this amendment itself.

I therefore recommend that the Splice maintainers perform this early merge. If the vote on this CIP does not go through by Tuesday 27th, I’ll coordinate directly with the SV node operators whether they are willing to accept a Splice 0.10.0 release with the dry-run code merged in parallel with the CIP voting.

I’m looking forward to your feedback on both the CIP amendment itself. From my side, this is ready for endorsement and voting as it is purely the implementation of the new tokenomics guidance that has been considered and discussed in detail over the last weeks.

Kind regards,

Bernhard

--

Dr. Bernhard Elsner

Chief Product Officer / +41 76 696 70 50

Digital Asset, creators of Daml

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.digitalasset.com/emaildisclaimer.html. If you are not the intended recipient, please delete this message.