[hiciefte]

Addresses migration note local-signing-not-private-key-collection ("Manual payout: local signing") for the restored 2021 article Emergency Multisig payout tool (src/content/docs/wiki/emergency-multisig-payout-tool.md, wiki revision 2011, 20 January 2021).

The restored guide tells traders to copy their wallet's private keys into a text editor, save the key in a bisqWallet.txt file and remove the wallet password. This PR replaces that part with the local key lookup and signing that Bisq 1 v1.10.11 provides, consistent with #6 (Manual payout). Title, headings, step order, tables, the Precautions section and the Warning's advice are unchanged.

Commits

1. Format the emergency payout source for review (formatting only). The article was imported as one 6.7 KB source line. This decodes its 135 
 entities into line breaks, using the same rule as the formatting baseline. The rendered page differs from main only in writing a newline as \n instead of 
.
   This is one of the three additional historical articles, whose receipt is output_sha256 in migration/additional-articles.json, not the 209-article fidelity manifest. So the commit also lets a migration/source-formatting.json record belong to an additional article (scripts/check-source-fidelity.mjs, scripts/lib/additional-articles.mjs), adds a test and one sentence to CONTRIBUTING.md. The receipt hash itself is not changed.
2. Keep emergency payout keys local (wording).
3. Reject non-integer formatting offsets for additional articles. Review found that commit 1's check undid the recorded line breaks without validating the offsets: a string offset made slice() drop text, so inserted content could vanish before the receipt hash was taken and an edited article passed the gate. It now applies the same checks as for the 209 originals (an array of safe integers inside the file, and the undone text must hash to the recorded imported file), with a test using a synthetic record.
4. Say what to do when the key is not found, and never to send a screenshot (wording, from review).

Wording changes

Section	Before	After
Warning	In this process traders copy and paste their private keys from the Bisq software into a notepad.	In the original 2021 process, traders copied and pasted their private keys from the Bisq software into a notepad. (The precaution that follows is unchanged.) Added at the end: If you use LOCATE KEY IN WALLET (see Get private keys), switch only after the payout is confirmed: it finds keys only in the wallet that made the trade.
What you need	Open a text editor where you can gather all this information.	... all this information, except private keys.
Get private keys	"To access your Bisq wallet private key", five steps (Ctrl+J, Include private keys, COPY TO CLIPBOARD into a text editor, find priv HEX=, save in bisqWallet.txt), and the note that a password-protected wallet must have its password removed.	In Bisq 1 v1.10.11, keep private keys inside Bisq. After you import the unsigned transaction (see Sign Transaction), LOCATE KEY IN WALLET on the SIGN screen finds your key for this trade in the wallet and fills the privateKeyHex field; GENERATE SIGNATURE then signs on your computer. Share only the resulting signature: never send a private key or seed words to the mediator or anyone else. / If the field shows Not found in wallet, check that Bisq is running with the data directory you used for this trade; do not paste a key from anywhere else, and ask the mediator for help. You do not need to remove your wallet password: Bisq uses the password you entered at startup. / This replaces the original 2021 steps, which copied wallet data including private keys into a text editor and saved the key in a bisqWallet.txt file.
Sign Transaction, step 2	Go to SIGN and paste your private key for this trade (priv HEX=) and click GENERATE SIGNATURE.	Go to SIGN, click LOCATE KEY IN WALLET to fill in your private key for this trade, and click GENERATE SIGNATURE.
Sign Transaction, step 3	Copy the signature hex that you get and share it with the mediator	... share it with the mediator. Use the copy icon next to it; do not send a screenshot of the SIGN screen, because it shows your private key.

The removed steps remain in the preserved original wikitext (public/wiki-source/emergency-multisig-payout-tool.wiki.txt), linked from the page's "Source and history" section.

Sources

All at Bisq commit ea9d5dff90c99ac462f2b0a7bf9ef92683956619, the target of tag v1.10.11.

• SignPane.java L55-L98: "Locate key in wallet" needs the inputs first, searches the running wallet's listing for the buyer's or seller's public key and fills privateKeyHex, or writes "Not found in wallet". privateKeyHex is a plain text field on the same screen as the signature, which has a copy icon. "Generate Signature" computes the signature locally.
• CommonPane.java L36-L60: the key search on the wallet listing.
• ImportPane.java L70-L80: IMPORT FROM STRING fills the inputs, including both public keys, so step 1 of Sign Transaction prepares what Locate needs.
• BuildPane.java L106-L135: the build step combines the buyer and seller signatures; it takes no private key.
• AutoTooltipButton.java L35-L46: button labels are shown in upper case.
• Password: BisqSetup.java L458-L477 sets the wallet key after the startup password prompt, and BtcWalletService.java L144-L154 passes that key into the wallet listing (the old "only if not encrypted" line is commented out). The bitcoinj fork pinned by Bisq is not in the Bisq repository; its compiled jar (commit 6c32c062, hash matching gradle/verification-metadata.xml) decrypts a key with the given AES key when it formats the listing.

What was checked and what was not

• Checked: the source files above, read at the pinned commit; the bitcoinj fork from its compiled jar. The edited page was built and viewed in the local build. Ctrl+G still opens the support tool in v1.10.11, so the article's shortcut is unchanged.
• Not done: nothing was run in the Bisq application. No signature was generated, no payout was built or broadcast, no wallet was used, and LOCATE KEY IN WALLET was not tried on a password-protected wallet. The password sentence rests on the code reading above.
• Not changed (out of scope, for reviewers): the "What you need" table. At the pinned commit the Inputs pane also has a depositTxLegacy checkbox and computed fee fields, which the 2021 table does not list; depositTxId is listed.

Expected check results

• Commit 1: npm test 38/38 pass; DOCS_SITE=https://hiciefte.github.io DOCS_BASE=/bisq-docs/ npm run build passes.
• Commits 2 to 4 (wording): the restoration gate fails as intended. For additional articles the same receipt check runs in both places:
  • node scripts/check-source-fidelity.mjs: Source fidelity FAILED: additional rendered article drift: emergency-multisig-payout-tool (formatted source)
  • npm test: 38 of 39 pass; the failing test is "additional historical sources retain raw, rendered and media receipts".
  • Running the remaining build steps directly (template, section, link and category checks, browse indexes, astro build, check-site.mjs) passes: 601 pages, links and fragments.
    The receipt was not refreshed to hide the difference.
• Already on main, not changed here: check-source-fidelity.mjs checks the additional articles before the 209 originals and stops at that failure, so a wording branch for an additional article does not get the originals checked in the same run. The diff of this PR touches no original article.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 0032233b-9e99-4a09-b695-e6ef9cdb798f

Commits

Reviewing files that changed from the base of the PR and between 574168b and fb49800.

Files selected for processing: 6

• CONTRIBUTING.md
• migration/source-formatting.json
• scripts/additional-articles.test.mjs
• scripts/check-source-fidelity.mjs
• scripts/lib/additional-articles.mjs
• src/content/docs/wiki/emergency-multisig-payout-tool.md

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[hiciefte]

Automated note: moved to #97, opened from a fork with the same changes and corrected commit authorship. Please continue the review there.