Repository navigation
Conversation
Ports ReconcileDedicatedSynchronizerParametersTrigger from archive/prepaid-traffic-main at 086bea6 (originally #33, #65): a zero base traffic rate and the global synchronizer's read cost, read through Scan. The Scan client comes back with it. The parameter checks from the archive's SyncOperatorTrafficIntegrationTest move into SyncOperatorIntegrationTest. Signed-off-by: sadiq1971 <sadiqurr8@gmail.com>
Signed-off-by: sadiq1971 <sadiqurr8@gmail.com>
…sync operator Ported from archive/prepaid-traffic-main at 086bea6 (originally part of #31): the task type, the grant and the staleness check of SvOnboardingUnlimitedTrafficTrigger move to GrantUnlimitedTrafficTriggerBase in apps-common, so the sync operator's triggers can reuse them. Staleness uses lookupSequencerTrafficControlState, so a member whose traffic state has gone is treated as stale instead of failing the task. Signed-off-by: Haiko Schol <haiko@chainsafe.io>
…nchronizer [ci] The dedicated synchronizer runs at a zero base rate and the paymaster pays afterwards, so the sync operator keeps every member's traffic limit at the maximum: - MediatorUnlimitedTrafficTrigger, ported from archive/prepaid-traffic-main at 086bea6 (originally #31), for the synchronizer's mediators. - ParticipantUnlimitedTrafficTrigger for participants that have a ParticipantSynchronizerPermission and have joined. A participant without a permission gets nothing, even on an open synchronizer. - PreJoinParticipantTrafficTrigger buys the maximum for admitted participants before they join, so a late joiner can finish connecting. Canton accepts this from protocol version 37; below that the trigger does nothing and the grant follows the join. The sync operator tests run splitwell on protocol version 37 (start-canton.sh -t). SyncOperatorIntegrationTest checks the mediator grant, that a joined participant without a permission gets nothing, that admitting it grants the maximum, and that a participant admitted before it joins connects with the maximum and transacts. Closes ChainSafe/canton-extending-mainnet#151 Signed-off-by: Haiko Schol <haiko@chainsafe.io>
A ping from bob to alice over splitwell also waits for alice's vetting of the ping package to reach splitwell. Alice's topology was refused for lack of traffic until she was admitted, and her outbox had not caught up within the test's window in CI. Bob's connect only returns once his own topology is sequenced, so a ping to himself checks that he transacts without depending on alice. Signed-off-by: Haiko Schol <haiko@chainsafe.io>
Signed-off-by: sadiq1971 <sadiqurr8@gmail.com>
Signed-off-by: sadiq1971 <sadiqurr8@gmail.com>
…nlimited-traffic [ci] Signed-off-by: Haiko Schol <haiko@chainsafe.io>
The sync operator stores the traffic charged to participants in each finished 10-minute interval, read from the sequencer at both ends, and serves it on an authenticated GET /v0/traffic-report. Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
…sync operator Ported from archive/prepaid-traffic-main at 086bea6 (originally part of #31): the task type, the grant and the staleness check of SvOnboardingUnlimitedTrafficTrigger move to GrantUnlimitedTrafficTriggerBase in apps-common, so the sync operator's triggers can reuse them. Staleness uses lookupSequencerTrafficControlState, so a member whose traffic state has gone is treated as stale instead of failing the task. Signed-off-by: Haiko Schol <haiko@chainsafe.io>
…nchronizer [ci] The dedicated synchronizer runs at a zero base rate and the paymaster pays afterwards, so the sync operator keeps every member's traffic limit at the maximum: - MediatorUnlimitedTrafficTrigger, ported from archive/prepaid-traffic-main at 086bea6 (originally #31), for the synchronizer's mediators. - ParticipantUnlimitedTrafficTrigger for participants that have a ParticipantSynchronizerPermission and have joined. A participant without a permission gets nothing, even on an open synchronizer. - PreJoinParticipantTrafficTrigger buys the maximum for admitted participants before they join, so a late joiner can finish connecting. Canton accepts this from protocol version 37; below that the trigger does nothing and the grant follows the join. The sync operator tests run splitwell on protocol version 37 (start-canton.sh -t). SyncOperatorIntegrationTest checks the mediator grant, that a joined participant without a permission gets nothing, that admitting it grants the maximum, and that a participant admitted before it joins connects with the maximum and transacts. Closes ChainSafe/canton-extending-mainnet#151 Signed-off-by: Haiko Schol <haiko@chainsafe.io>
A ping from bob to alice over splitwell also waits for alice's vetting of the ping package to reach splitwell. Alice's topology was refused for lack of traffic until she was admitted, and her outbox had not caught up within the test's window in CI. Bob's connect only returns once his own topology is sequenced, so a ping to himself checks that he transacts without depending on alice. Signed-off-by: Haiko Schol <haiko@chainsafe.io>
The participant admin API in integration tests now only allows the services Splice uses, which excludes the ping service. Signed-off-by: Haiko Schol <haiko@chainsafe.io>
haikoschol
force-pushed
the
feat/sync-operator-unlimited-traffic
branch
from
November 9, 2026 11:40
1dd309c to
a5d8ecf
Compare
…erator-traffic-report Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
…affic-report Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
A successor sequencer takes over the counters at the upgrade but not their history, so it reports zero before it. Read up to the announced upgrade time from the current sequencer and later times from the successor, and once the successor is current, don't read it from before its upgrade. Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
Fork main took V082. Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
The app serves one logical synchronizer, which keeps its id across an upgrade, so the key needs only the interval. Also say why an interval can be stored twice, drop a store test that the trigger tests cover, and lowercase the integration test's clue labels like the rest of the file. Signed-off-by: Sebastian Lindner <33971232+salindne@users.noreply.github.com>
salindne
changed the base branch from
feat/sync-operator-unlimited-traffic
to
main
November 13, 2026 19:05
Collaborator
Author
|
Replaced by #111 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs ChainSafe/canton-extending-mainnet#152
Summary: the sync operator app reports the traffic charged to participants per 10-minute interval, summed across participants as #87 asks. Once an interval is over,
TrafficReportTriggerreads every member's consumed traffic from the sequencer'sGetLsuTrafficControlStateat its start and end and stores the participants' total, since the sequencer prunes its journal.GET /v0/traffic-reportserves each interval asOk,UndeterminedorCannotProvide. It needs a JWT, soauthis a new required config field.A successor sequencer takes over the counters at an upgrade but not their history, so it reports zero for every member before the upgrade time. The trigger reads up to the announced upgrade time from the current sequencer and later times from the successor. Once the successor is current, an interval spanning the upgrade that wasn't stored yet reports
CannotProvide.Both queries use the primary key, here with a year of intervals (52,560 rows):
Query plans
GetLsuTrafficControlStatewith a timestamp is documented for disaster recovery; is calling it every 10 minutes OK?sync-operator-internal.yaml. Should it be external?