Skip to content

Add FA weights to CIP-0104 spec #238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bame-da wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add FA weights to CIP-0104 spec #238

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b90c88a
Add FA weights to spec
bame-da Jun 30, 2026
bb81772
Apply suggestions from code review
bame-da Jun 30, 2026
8185745
Update cip-0104.md changelog
bame-da Jun 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions cip-0104/cip-0104.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,7 @@ Use the view hashes visible to the sequencer on the confirmation request to dete
```

using integer arithmetic, and attribute `per_app_traffic_weight` to every app confirmer of the envelope.
6. For every featured app involved, multiply the `per_app_traffic_weight` by the `activityWeight` set on the `FeaturedAppRight`.

Note that the computation in Item 5 takes care of distributing the traffic cost not attributed to app envelopes in a weighted fashion among the app envelopes.
When all envelopes have an app confirmer, it becomes `per_app_traffic_weight = envelope_traffic_cost / num_app_confirmers`, as expected.
Expand Down Expand Up @@ -154,6 +155,17 @@ Note that the CIP proposes introducing extra endpoints instead of extending the
1. Traffic summaries can be read by clients as soon as the corresponding message has been sequenced, and not only once the confirmation request has been completed, which may be up to 30s later.
2. The `/v2/events` stream is not held up by a potentially delayed app activity record computation.

#### Featured App Weights

The CIP proposes to add the ability to adjust the app rewards that a featured app receives by setting a weight on the `FeaturedAppRight` contract. The weight is applied in the [activity record computation](#activity-record-computation-details).
Concretely:

1. Add a field `activityWeight` to `FeaturedAppRight`.
2. Adjust the `DsoRules_GrantFeaturedAppRight` governance choice to optionally take `activityWeight`, with the default being `1.0`.
3. Add a new `DsoRules_UpdateFeaturedAppRight` governance choice to adjust the `activityWeight`.
4. Adjust the SV UIs and backing APIs to allow SV governance to change the `activityWeight` on `FeaturedAppRight`


### Free Protocol-Conformant Confirmation Responses

The Canton Protocol is changed so that the confirmation responses expected to be sent by a confirming participant node become de-facto free.

@meiersi-da meiersi-da Jun 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing later below: adjust the changelog. Also have a look at the header. I believe there's some changelog as well.

@bame-da bame-da Jun 30, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I adjusted the changelog at the bottom, I saw nothing at the top.

Expand Down Expand Up @@ -422,6 +434,7 @@ TODO: build and reference here
This CIP is licensed under CC0-1.0: [Creative Commons CC0 1.0 Universal](https://creativecommons.org/publicdomain/zero/1.0/)

## Changelog
- 2025-06-30: Propose amendment for featured app weights.
- 2026-02-12: CIP Approved.
- 2026-01-29: draft published
- 2026-01-10: change to share app rewards among confirmers instead of informees