Skip to content
CCPEDIAby Unity Nodes
ReleasesSplice 0.5.17

Splice 0.5.17

BFT sequencer connections are recommended again with this upgrade. To enable them, remove the config flags to disable them from the SV and validator configuration used to disable them. Going forward unusable splice DARs…

  • SVs
  • BFT sequencer connections are recommended again with this upgrade. To enable them, remove the config flags to disable them from the SV and validator configuration used to disable them.
  • SV and Validator app
    • Going forward unusable splice DARs will be automatically unvetted by the super validators. This will be used for DARs that can already not be used, e.g., because a downgrade of AmuletRules to that version is not possible so it does not force more aggressive upgrades for validators or app devs. The minimum supported versions are:
      nameversion
      amulet0.1.14
      amuletNameService0.1.14
      dsoGovernance0.1.19
      validatorLifecycle0.1.5
      wallet0.1.14
      walletPayments0.1.14
  • Scan
    • Added a new /v1/domains/{domain_id}/parties/{party_id}/participant-id endpoint that returns all participant IDs hosting a given party, supporting parties hosted on multiple participants. The previous /v0 endpoint only supported single-participant hosting.
    • Added an optional external_transaction_hash field to the response of GET /v1/updates/{update-id}, GET /v2/updates/{update-id}, GET /v1/updates, and GET /v2/updates endpoints. While currently not set, this field will eventually include the transaction hashes signed by external parties.
    • Experimental: Added an optional app_activity_records field to the response of GET /v0/events/{update-id} and POST /v0/events endpoints. This is currently never set but will eventually include traffic summaries and app activity records are included alongside verdicts in event history items. This is part of the CIP-0104 preview and is subject to change. App activity record computation will be enabled step-by-step on Dev/Test/MainNet, once the SVs have successfully concluded their performance testing.
  • SV UI
    • Fixed the SV UI to correctly handle parties hosted on multiple participants (e.g., the DSO party).
  • LocalNet
    • LocalNet now supports running multiple synchronizers side by side for testing multi-synchronizer scenarios. By default, only the global synchronizer is active. To enable the second synchronizer called app-synchronizer, start LocalNet with the multi-sync Docker Compose profile (--profile multi-sync). The app-provider and app-user participant nodes are cross-connected to both synchronizers. See multi-sync-localnet for details.