docs: Answer the second round of operator onboarding questions#814
Merged
Conversation
|
Collaborator
Style Guide AuditAudited 1 file(s) against the Sui Documentation Style Guide. 3 violation(s) found. All must be fixed before merge.
|
From the validator channel: - 2.3 shows the concrete sui keytool sign / sui client execute-signed-tx commands for the offline registration flow (operators were assembling these from chat). - 2.4 documents how to find the operator address for an openssl PEM (derivation one-liner, verified against sui keytool output) and says to fund the operator with at least 2 SUI: the node's startup address-balance bootstrap moves exactly 1 SUI, so 1 SUI total fails with InsufficientCoinBalance (hit by an operator). - 2.4 states that metadata updates are automatic: the node diffs its config against the on-chain record at startup, so editing endpoint-url and restarting is enough. - 5.3 placeholder unified with 2.3/2.4; 5.4 gains an explicit 'last operator step' marker (operators asked where to stop).
Bridgerz
force-pushed
the
docs-operator-feedback-2
branch
from
July 14, 2026 21:50
54eed46 to
2123f50
Compare
bmwill
approved these changes
Jul 14, 2026
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
3 participants
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.
Stacked on #804 (same sections of the runbook). Fixes from the second wave of validator-channel feedback, all claims verified against code before documenting:
Offline signing commands (asked by Coinage x DAIC, answered in-thread by Nodes.Guru)
§2.3 now shows the exact
sui keytool sign --address ... --data ...andsui client execute-signed-tx --tx-bytes ... --signatures ...invocations (flags verified against the current sui CLI), with a note for hardware/multisig custody. §5.3 cross-references instead of repeating.Operator address derivation (Coinage x DAIC)
Operators who generated their key with openssl had no documented way to compute its Sui address. §2.4 now covers both paths:
sui keytool generateprints it, and for an existing PEM there's a one-liner (pubkey DER → blake2b-256 over0x00 || pubkey) that I verified derives the identical address tosui keytoolfor a test key.Fund the operator with at least 2 SUI (hit by Brightlystake)
sweep_to_address_balancebootstraps the account's address balance with exactly 1 SUI at startup (sui_tx_executor.rs:2101), so an operator holding exactly 1 SUI fails the simulation withInsufficientCoinBalance— precisely the error reported. §2.4 now says to fund with at least 2 SUI and explains why.Metadata updates are automatic (asked by Brightlystake, Triton.One)
Verified: the register builder diffs config vs the on-chain member record and sends only stale fields, and the node runs it at startup. §2.4 now states that editing the config and restarting is sufficient; no manual re-register.
"Where do operator steps end?" (Galaxy)
§5.4 gains an explicit last operator step marker; steps 4-6 are admin/network.