Skip to content
Mailing Lists/CIP-0074 BitGo interpretation and CIP-0160 Zenith update (objection window)Source on lists.sync.global ↗

CIP-0074 BitGo interpretation and CIP-0160 Zenith update (objection window)

supervalidator-announceCIP-00741 messagesstarted 23-02-2026
Also mentions:CIP-0056CIP-0091CIP-0160
  1. #1Amanda Martin23-02-2026source ↗

    Hi all,

    Sharing two items for Super Validator awareness and ratification. Unless an SV objects within 7 calendar days of this message, we will treat these as approved and proceed accordingly.

    1. CIP-0074: Add BitGo as an SV of Weight 5
      Context
      BitGo’s CIP includes deliverables tied to custody support for Canton Coin and CIP-0056 assets. BitGo flagged that “custody any CIP-0056 asset” is apparently not legally feasible in the US jurisdiction.

    Recommendation from Tokenomics:
    To remain consistent with prior custody provider awards, we recommend interpreting the acceleration bonus as earned at the moment Canton Coin support was delivered, using the 68 day sliding scale (weight 1.8667).
    The first milestone still requires CIP-0056 token support.
    The adoption bonus remains based on the CIP’s asset support language and will be released when achieved per the CIP.

    Action requested
    Please reply to this thread within 7 days if you object to this interpretation and approach. If no objections are received, we will finalize the conditional approval for the 1.8667 acceleration weight as described above and proceed with milestone reconciliation using this interpretation.

    Recorded vote in Tokenomics
    YES: Cumberland, DA, PG, IEU, 7Ridge

    Reference material
    CIP-0074 deck: https://docs.google.com/presentation/d/1Jcp4ZiNprjvUTrxtJSNdkMHj-uytujHLsqwx9c4kids/edit?usp=sharing

    1. CIP-0091:Add Zenith as an SV of Weight 10
      PR: https://github.com/canton-foundation/cips/pull/160

    Summary
    Obsidian has reviewed the updated text. The change reflects deploying the Canton test network in a local multi node scratch environment for testing rather than deploying on the public TestNet. DA indicated this is the preferred technical approach since public TestNet deployment generally implies a near term MainNet timeline that does not align with the CIP schedule as written. The EVM rename is not material.

    Action requested
    Please reply to this thread within 7 days if you object to this change. If no objections are received, we will treat the updated text as ratified and close out the approval process.

    Recorded vote in Tokenomics
    YES: Cumberland, DA, IEU, 7Ridge