Skip to content

fxadmin update readme - #282

Merged
tock-ibm merged 4 commits into
hyperledger:mainfrom
MayRosenbaum:fxadmin_update_readme
Aug 30, 2026
Merged

fxadmin update readme#282
tock-ibm merged 4 commits into
hyperledger:mainfrom
MayRosenbaum:fxadmin_update_readme

Conversation

@MayRosenbaum

@MayRosenbaum MayRosenbaum commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Type of change

update decode command description
update the compute-update command to include channel id
update the send command to require an output path for the prepared tx

Signed-off-by: May.Buzaglo <May.Buzaglo@ibm.com>
@MayRosenbaum
MayRosenbaum force-pushed the fxadmin_update_readme branch from 3dbc8a6 to 6e07b36 Compare August 23, 2026 14:01
Signed-off-by: May.Buzaglo <May.Buzaglo@ibm.com>
Signed-off-by: May.Buzaglo <May.Buzaglo@ibm.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the fxadmin CLI documentation to reflect recent UX/behavior changes around config decoding, config update computation, transaction sending, and ledger follow semantics.

Changes:

  • Refines the decode command description and flag documentation to clarify it extracts common.Config from a config block.
  • Updates compute-update docs/examples to include --current-block (to derive/stamp the channel ID onto the resulting ConfigUpdate).
  • Updates tx send docs/examples to require --output for writing the prepared configuration transaction, and clarifies quorum-based success semantics (also for submit) plus expands follow command explanation/output.
Suppressed comments (1)

tools/fxadmin/docs/README.md:464

  • This sentence uses past tense ("routers acknowledged") while describing current command behavior. Using present tense here will read more clearly and match the surrounding documentation.
The send command is equivalent to running `prepare` followed by `submit`. As with `submit`, it
succeeds only when a BFT quorum (`2f+1`) of the routers acknowledged the transaction, and fails
otherwise.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread tools/fxadmin/docs/README.md Outdated
| `--output` | yes | Path to the output ConfigUpdate protobuf file |
| Flag | Required | Description |
|-------------------| :------: | ---------------------------------------------- |
| `--current-block` | yes | Path to the current config block whose channel ID the update targets|
Comment thread tools/fxadmin/docs/README.md Outdated
Comment on lines +419 to +424
the per-router outcome. It **succeeds only when a BFT
quorum of the routers acknowledged** the transaction: with `n` parties (read from the
`--current-block`) the quorum is `2f+1`, where `f = (n-1)/3` is the number of faulty parties
the network tolerates. If fewer than a quorum acknowledge — because routers rejected the
transaction or were unreachable — the command fails, so a partial or failed delivery is
reported rather than silently succeeding.
Signed-off-by: May.Buzaglo <May.Buzaglo@ibm.com>
@tock-ibm
tock-ibm merged commit 18e652a into hyperledger:main Aug 30, 2026
3 checks passed
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.

3 participants