fix(desktop): bind local FISCO BCOS trust config - #627
Merged
ryan-wong-coder merged 2 commits intoAug 3, 2026
Merged
Conversation
ryan-wong-coder
force-pushed
the
agent/fisco-bcos-desktop-binding
branch
from
August 2, 2026 13:21
9320dd6 to
5ae142e
Compare
ryan-wong-coder
enabled auto-merge (squash)
August 3, 2026 04:36
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
1 participant
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.
Fixes #626
Summary
fisco_bcos_trust_config_filesetting for TrustDB Desktop.Root cause
The desktop verifier had no verifier-local FISCO BCOS trust configuration input. As a result, proofs with a FISCO BCOS anchor stopped at
verifier-local FISCO BCOS trust config is requiredeven though all other evidence stages passed.Validation
cd clients/desktop/frontend && npm run buildcd clients/desktop && go test ./...go test ./...Verification remains disconnected: the configured TrustConfig is read locally and no FISCO BCOS endpoint, DNS, provider, or blockchain RPC is contacted.