Splice 0.10.2
Canton: Upgrade Canton to 3.7.3. asset_activity_records: asset-side activity records (CIP-104). Omitted from JSON when there is no asset activity. submitting_app_provider: the submitting app provider party identifier…
- The latest release in the 0.10 line.
Runs on Canton 3.7.3
- Canton: Upgrade Canton to 3.7.3.
-
Scan App
-
/v0/eventsresponses now include two new per-event fields:asset_activity_records: asset-side activity records (CIP-0104). Omitted from JSON when there is no asset activity.submitting_app_provider: the submitting app provider party identifier when the submitter is a featured app. Omitted from JSON when absent.
-
CIP-0104 v1.1 populates four optional fields on
OpenMiningRoundSummary:optIssuancePerFeaturedAppRewardCoupon,optUnclaimedAppRewards,optIssuancePerFeaturedAssetRewardCoupon, andoptTotalFeaturedAssetRewardCoupons. The two*Asset*fields carry the asset-side issuance ratio and the total featured-asset reward coupons. -
Explorer operators:
Because featured-app and featured-asset activity now have separate
issuance ratios, explorers should ingest the new
*Asset*fields alongside the existing app-activity ones; explorers that only read the app-activity fields will under-report total app rewards minted. -
Changed
/v0/internal/reward-accounting-process/rounds/{round_number}/activity-totalsto include additional fields. -
Added
POST /v0/reward-coupons-v2-disclosures, which returns base64-encoded created event blobs for activeSplice.Amulet:RewardCouponV2contracts (up to 100 contract IDs per request) for use by external reward-sharing automation.
-
-
SV App
-
Removed the remaining CometBFT support from the SV app and UI, including the
/v0/admin/domain/cometbft/{status,json-rpc,debug}endpoints, thesplice_sv_cometbft_*metrics and the CometBFT debug tab in the SV UI. -
Added support for the CIP-0104 v1.1 (TBAR) governance changes:
-
The amended activity record computation is only used for rounds opening at or after
the time set for the switch-over key
CIP-0104/use-amended-calculation-afterinsvOperationsSwitchOverTimesof the DSO rules configuration. SVs activate it with a “Set Decentralized Synchronizer Operations (DSO) Rules Configuration” vote. -
The “Set Amulet Rules Configuration” vote request now supports setting the new
Amulet configuration parameters
extraFeaturedAssetActivityWeight(default0.2),maxExtraFeaturedAssetActivityWeightPerAsset(default0.1), anddsoAppActivityWeight(default0.1). Leave a parameter blank to use its default. - The “Feature Application” vote request now supports setting all featured app metadata: app category (basic featured app, featured asset-moving app, or featured asset), app operations parties, and app composition weight.
- Added the vote request type “Update Featured Application Metadata (use with Splice 0.10.0 and later)” to change the metadata of an already featured app. Once the vote is accepted, SV app automation applies the change to the app’s featured app right; if that does not happen before the vote request timeout, the change expires and is discarded. The older “Update Featured Application Metadata (use before Splice 0.10.0)” vote request type can only change the app composition weight, and will be removed in Splice 0.11.0.
-
The SV app rejects creating a vote request to feature an app or update its metadata if:
- the provider is already featured (when featuring an app),
- the app operations parties contain duplicates or the provider itself, or
- one of the app operations parties is already the provider or an app operations party of another featured app.
-
The amended activity record computation is only used for rounds opening at or after
the time set for the switch-over key
-
Removed the remaining CometBFT support from the SV app and UI, including the
-
Helm charts and Docker images
- Removed the remaining CometBFT support including the cometbft Helm charts, docker images and unused
splice-infovalues.
- Removed the remaining CometBFT support including the cometbft Helm charts, docker images and unused