HALO: High-Availability Submission and Traffic Control for Multi-Hosted Applications - #745
Closed
kevmuko wants to merge 1 commit into
Closed
HALO: High-Availability Submission and Traffic Control for Multi-Hosted Applications#745kevmuko wants to merge 1 commit into
kevmuko wants to merge 1 commit into
Conversation
kevmuko
requested review from
hythloda,
isegall-da,
omaiko-intellecteu,
stas-sbi,
tkatrichenko and
waynecollier-da
August 29, 2026 05:01
|
SIG labels auto-detected and applied: If this is incorrect, you can update the labels from the right sidebar. |
|
@kevmuko, thank you for your interest in the Canton Development Fund! Your proposal needs a valid Champion. The champion field is either empty, contains placeholder text, or names an organization that is not a valid champion. Per CIP-0100, all external proposals require a Tech & Ops Committee champion. Next steps:
If you need help finding a champion, reach out to SIGs (https://github.com/canton-foundation/canton-dev-fund/blob/main/sig-directory.md). This PR is being closed automatically. You are welcome to reopen it once a champion is confirmed. |
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.
Development Fund Proposal Submission
Proposal file:
/proposals/2026-08-K2FLabs-halo-failover-load-balancer.md
Applicant
Organization:
K2F Labs
Author / Primary Contact:
Kevin Ko, kko@k2flabs.com
Champion:
Needs Champion
Proposal Classification
Proposal Type:
RFP / Roadmap Area:
RFP 4, Application-level resilience and party-level Highly Available failover (Protocol, Infrastructure, Scalability & Resilience). Secondary RFP 23, Validator and Shared Infrastructure Security and Resilience.
Label:
party-portability-data-resilience
Funding & Timeline
Total Funding Request:
2,850,000 CC (engineering 1,850,000 CC, adoption up to 1,000,000 CC)
Project Duration:
7 months engineering, adoption window 12 months from Milestone 3 acceptance
Maximum Amount:
N/A
Maximum Duration:
N/A
Summary
Co-validation lets a party be hosted on several validators, but an application still submits through one participant, and Canton's documentation states that an application cannot transparently fail over between participants because deduplication state is not shared. HALO is an open-source sidecar (Rust, Apache-2.0) that presents the unchanged Ledger API, routes each submission to a healthy host of the party, fails over to another host after a host is lost without duplicating a transaction, and adds traffic priority lanes, optional consumption-driven top-up and per-host observability. It makes co-validation cover submission as well as confirmation, for every application in every language, with no changes to Canton, Splice or any SDK.
Submission Checklist
Needs Championselected