Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.canton.network/llms.txt

Use this file to discover all available pages before exploring further.

When your application runs on Canton Network, economically meaningful events can be recorded as app activity. The preferred mechanism for this is the FeaturedAppActivityMarker contract. SV (Super Validator) automation converts these markers into AppRewardCoupon contracts, which translate to Canton Coin (CC) rewards for your application.

​
What is a FeaturedAppActivityMarker?

This section was copied from existing reviewed documentation. Source: docs/src/background/tokenomics/feat_app_act_marker_tokenomics.rst Reviewers: Skip this section. Remove markers after final approval.
A FeaturedAppActivityMarker records a specific activity event in your application. It signals to the network that something economically relevant happened — for example, a real-world asset was locked, a token was minted, or a license was renewed. After CIP-0078, only featured apps receive rewards. Unfeatured apps can still create markers, but they will not generate reward coupons.

​
When to Create Markers

This section was copied from existing reviewed documentation. Source: docs/src/background/tokenomics/feat_app_act_marker_tokenomics.rst Reviewers: Skip this section. Remove markers after final approval.
Beyond the basics above, other examples of appropriate markers include settling a payment or trade, and renewing or issuing a license. Do not create markers for routine housekeeping operations (cache refreshes, health checks, internal bookkeeping) that do not represent user-facing economic value.

​
How to Create Markers

The FeaturedAppActivityMarker contract is specified in CIP-0047. Your Daml code creates the marker as part of the transaction that performs the economically meaningful action.
This section was copied from existing reviewed documentation. Source: docs/src/background/tokenomics/feat_app_act_marker_tokenomics.rst Reviewers: Skip this section. Remove markers after final approval.
The marker contract includes fields that identify your application, the type of activity, and metadata about the event. Refer to CIP-0047 for the exact contract interface and required fields.
This section was copied from existing reviewed documentation. Source: docs/src/background/tokenomics/feat_app_act_marker_tokenomics.rst Reviewers: Skip this section. Remove markers after final approval.
It is possible to share the attribution of activity for the FeaturedAppActivityMarker. The FeaturedAppRight_CreateActivityMarker choice accepts a list of AppRewardBeneficiary contracts. Then a FeaturedAppActivityMarker is created for each beneficiary with the weight field set appropriately.

​
Markers in cn-quickstart

In cn-quickstart, the license renewal flow creates a FeaturedAppActivityMarker when a license is renewed. The marker is created inside the Daml choice that performs the renewal, so it is part of the same transaction and recorded atomically. To receive rewards from your markers, your application must be featured on the network.

​
On DevNet

You can self-feature your application on DevNet for testing purposes. This lets you verify that your markers are created correctly and that the SV automation converts them into reward coupons, without going through the formal review process.

​
On TestNet and MainNet

For TestNet and MainNet, the process is:
  1. Submit your application via the GSF (Global Synchronizer Foundation) form. You provide details about your application, the types of activities you record, and why they represent genuine economic value.
  2. Tokenomics committee review — The GSF tokenomics committee evaluates your submission. They assess whether the recorded activities reflect real economic value and whether the marker creation is appropriate.
  3. Approval and featuring — If approved, your application is added to the featured apps list. From that point, your markers generate reward coupons.

​
Reward Mechanics

The reward calculation depends on the number and type of activity markers your application creates, relative to other featured apps on the network. The exact formula is governed by the tokenomics rules defined by the GSF. Key points:
  • Rewards are paid in CC to the app provider party
  • More activity markers (representing genuine economic events) generally means more rewards
  • The reward pool is shared across all featured apps, so your share depends on your relative activity
  • Gaming the system (creating markers for non-economic events) risks losing featured status

​
Testing Markers Locally

On LocalNet (via cn-quickstart), the SV automation that converts markers to coupons is part of the local Splice infrastructure. You can:
  1. Trigger an action in your application that creates a marker
  2. Query PQS for active FeaturedAppActivityMarker contracts to verify they were created
  3. Wait for the SV automation cycle, then query for AppRewardCoupon contracts to confirm conversion
This local testing loop lets you validate your marker creation logic before deploying to DevNet.

​
Further Reading