Skip to content

docs(signers): document SignOptions and explain feasibility #379#434

Open
lambaaryan011 wants to merge 1 commit intobitcoindevkit:masterfrom
lambaaryan011:docs/signoptions-explanation
Open

docs(signers): document SignOptions and explain feasibility #379#434
lambaaryan011 wants to merge 1 commit intobitcoindevkit:masterfrom
lambaaryan011:docs/signoptions-explanation

Conversation

@lambaaryan011
Copy link
Copy Markdown

Issue #379: Document SignOptions

This PR adds comprehensive documentation to the SignOptions struct, explaining what each option does and what it's used for.

Changes

  • Security Guards: Clarified that trust_witness_utxo and allow_all_sighashes are pre-flight validations protecting against attacks
  • Deprecated Options: Marked try_finalize and assume_height as deprecated with migration guidance to use finalize_psbt() separately
  • Infeasible Options: Documented tap_leaves_options, sign_with_tap_internal_key, and allow_grinding with explanations of architectural limitations due to the generic GetKey abstraction

References

Testing

  • cargo build succeeds
  • cargo test passes (381 tests)
  • ✅ No new code logic changes - documentation only

…ations, and infeasible options

- Added 'Security Guard' labels for trust_witness_utxo and allow_all_sighashes
- Marked try_finalize and assume_height as DEPRECATED with migration guidance
- Documented infeasible options with architectural explanations
- All tests passing (381 tests)
- Resolves issue bitcoindevkit#379
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant