Skip to content

CIP-0086 Add Chainsafe weight for the completed milestone(s) on DevNet#341

Open
sbile wants to merge 7 commits into
canton-foundation:mainfrom
sbile:cip-0086-update-chainsafe-weight-on-5n-sv-devnet
Open

CIP-0086 Add Chainsafe weight for the completed milestone(s) on DevNet#341
sbile wants to merge 7 commits into
canton-foundation:mainfrom
sbile:cip-0086-update-chainsafe-weight-on-5n-sv-devnet

Conversation

@sbile
Copy link
Copy Markdown
Contributor

@sbile sbile commented Apr 23, 2026

According to this announcement, Chainsafe has met milestones for ERC-20 Middleware MVP Complete and Available on MainNet (1.0) AND partially met Acceleration Bonus (0.95 out of 2.0) for a total of 1_9500 basis points.

Following CIP-0086: Native ERC‑20 Middleware for Canton Network, Fivenorth adds weight for completed milestones to Chainsafe's separate party, on a separate Validator from the ghost SV validator, to mint its weight of 1.95.

This PR is part of a stack and depends on PR #329. Please merge the
dependency first, and we will rebase this PR once it is cleared.

Vasilis Dialinos and others added 4 commits April 14, 2026 12:18
…-reward-weight-change]

PER CIP-0113

https://github.com/canton-foundation/cips/blob/main/cip-0113/cip-0113.md
Further SV has a max weight of 8 and will be hosted on an escrow
validator.

5N reward weight is increased by 8_0000 bps and the extra 8_0000 bps are
attributed to the party
further-ghost-1::122021b2533a670a0eefc3a68e998ef77f56c0b2dc1ef2f40a8f829122079847931b

This party is hosted on 5nghost-devnet-2 validator with disabled wallet
and reward minting.
…t [allow-total-reward-weight-change]

According to this announcement
https://lists.sync.global/g/tokenomics-announce/message/295, Chainsafe
has met milestones for ERC-20 Middleware MVP Complete and Available on
MainNet (1.0) AND partially met Acceleration Bonus (0.95 out of 2.0) for
a total of 1_9500 basis points.

Following CIP-0086: Native ERC‑20 Middleware for Canton Network,
Fivenorth adds weight for completed milestones to Chainsafe's separate
party, on a separate Validator from the ghost SV validator, to mint its
weight of 1.95.
@sbile sbile requested a review from a team as a code owner April 23, 2026 13:25
@sbile
Copy link
Copy Markdown
Contributor Author

sbile commented May 13, 2026

Hi @stas-sbi, can you please review this one as well for consistency with the recently merged PRs (#343, #342)? Thank you!

@stas-sbi
Copy link
Copy Markdown
Contributor

Hi @stas-sbi, can you please review this one as well for consistency with the recently merged PRs (#343, #342)? Thank you!

dso.json is currently in sync with the runtime https://info.sv-1.dev.global.canton.network.sync.global/runtime/dso.json, merging this PR would make out of sync

@sbile
Copy link
Copy Markdown
Contributor Author

sbile commented May 13, 2026

Apologies @stas-sbi , I didn't realize that the supporting vote for this PR did not reach quorum on Devnet. Given that we want to onboard another SV very soon, what would be the best approach you think,

  1. create the 3 new PRs for the new SV weights and after it goes through, i recreate the Vote and PR to align all 3 environments for Chainsafe, or
  2. create the 3 new PRs for the new SV weights while the Devnet PR and vote would also contain the Chainsafe amendment?
  3. something else?

Thanks in advance!

@stas-sbi
Copy link
Copy Markdown
Contributor

Sure, no problem. Anything works as long as we have a PR to merge that aligns the configs with the runtime weights.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants