Featured Activity Markers

Activity markers can be created upon the execution of asset transfers in the context of token standard workflows.

Parties with the provider role which are featured on the network are the main beneficiaries of the marker, unless otherwise configured.

The marker is applied to transactions involving instruments managed by parties onboarded by the featured provider.

For example, consider this scenario:

• “P” is a featured party on the Network and has the provider role in the Utility

• “P” onboards another party “R” giving them a registrar role

• “R” creates an instrument “INST”

“P” will benefit from an activity marker whenever a token on INST is transferred. Part of the marker’s weight might be shared with the operator or with other parties, depending on configuration.

Configuration

The configuration for activity markers is defined for a given provider upon acceptance of the ProviderServiceRequest.

Example Scenario

1. The operator onboards the provider. As part of this process, the operator creates an AppRewardConfiguration for the provider, assigning a weight w to the operator and 1-w to the provider.

2. The provider onboards the registrar.

3. The registrar sets up an instrument.

4. A mint request by a token holder (sender) of that instrument is accepted by the registrar.

5. A token holder (sender) transfers tokens of that instrument to a token holder (receiver).

6. A burn request by the token holder (receiver) of that instrument is being accepted by the registrar.

For each of the steps 4-6, a Splice.Amulet:FeaturedAppActivityMarker is created for the provider and the operator, with weight 1-w and w, respectively, as specified by the AppRewardConfiguration in step 1. This results in six markers overall.

Reward Configuration

An AppRewardConfiguration is typically created for the provider when a ProviderServiceRequest is accepted. However, the operator can also create, update, or archive an AppRewardConfiguration at any time.

A provider can further refine reward sharing for a given instrument by specifying beneficiaries in the instrument’s InstrumentConfiguration. For example, the provider could allocate 60% of its own default share 1-w to itself and 40% to the registrar (or other parties). The provider beneficiary configuration of the instrument configuration would then be:

Party	Share
provider	0.6
registrar	0.4

The resulting reward distribution for activity markers would be:

Party	Share
operator	w
provider	(1-w) * 0.6
registrar	(1-w) * 0.4

Note

1. The provider must define beneficiary weights that sum to exactly 1 for the instrument configuration to be valid.

2. Minor rounding adjustments may be applied to ensure the final distribution totals 1.

3. If the operator changes its weight to w’ in the AppRewardConfiguration, the distribution will still equal 1, with the provider’s beneficiaries scaled proportionally (e.g., to (1 - w’) * 0.6 and (1 - w’) * 0.4 in the case above).

If you are a provider, please contact Digital Asset to ensure this functionality is enabled for your party with the correct reward split.