Repository navigation
Conversation
|
Follow-up |
|
Fork CI rehearsal passed at 7cc9a17 against upstream main 4466280, using unchanged workflows and an identical merge tree: CI — 40 jobs passed and backward compatibility passed. The fork-only release-note check was skipped; the unchanged checker passed separately using PR number 2238. Ready for maintainer approval of official upstream CI; these rehearsal results do not replace upstream checks. |
|
Synced with upstream The cancellation conflicts with #2262 are resolved through one lease-release dispatcher. Ordinary wallet-funded batches retain upstream cleanup. Custom anchors release only recorded leases using the batch-specific owner ID; foreign inputs never reach the ordinary wallet-unlock fallback. Added mixed-input and all-foreign cancellation regressions. Publication/cancellation boundaries and immutable signed transactions are unchanged. Validation before updating this PR:
Failure history: attempt 1 had one PostgreSQL integration partition fail during daemon startup near the harness's 10-second readiness deadline. The retained logs show incomplete migrations/connection closure and one node opening RPC just after the deadline. The failed-only retry passed on the identical source and binary artifacts, without timeout or workflow changes. The initial failure remains recorded on the rehearsal PR; the underlying resource/timing cause is not conclusively established. The rehearsal retains its existing fork-only release-note metadata skip because its PR number differs from upstream #2238. The unchanged release-note script passed locally with |
|
Resolved the new merge conflict after upstream #2265 and fast-forwarded this PR to The conflict was two independent additions at the same position in Validation before this update:
The fork's existing release-note metadata job remains skipped because its PR number differs; the unchanged checker passed locally using The tested fork merge GitHub now reports this PR as conflict-free ( |
|
Merged current upstream Verified: Two caveats:
|
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
Co-authored-by: Sadiq Jaffer <SadiqJaf@users.noreply.github.com>
ed563e0 to
0aa2321
Compare
|
Converting this to draft for now. I'm reworking the caller-defined genesis anchor flow natively on the current mint flow (v0.8.5 caretaker) instead of rebasing this revision, since |
Summary
This adds a caller-controlled Bitcoin anchor PSBT flow for minting batches. It's a slimmed-down rewrite of the previous revision of this PR (13 commits instead of 35), rebased on
mainat10759c4a.FundBatchaccepts a caller-funded anchor PSBT.PrepareBatchcommits the asset tree and pauses before publication, so an external signer can finalize caller-controlled inputs.FinalizeBatchvalidates the signed PSBT, persists it in the existingminting_tx_psbtcolumn, and resumes publication and confirmation.assets mint fund/prepare/finalize, with hardened PSBT output-file handling.Safety properties
PkScriptis resolved fromNonWitnessUtxo. Nothing is broadcast without a watchable trigger set.CommittedafterPrepareBatch) can't be cancelled.SIGHASH_ALLorSIGHASH_DEFAULTon finalized inputs.Removed from the previous revision
Historical key repair, the publish-error tokenizer matrix, the MuSig2 itest, the legacy lease markers and the DB migration have all been dropped. NUMS and external anchor keys are still tracked in #2237.
Validation
tapgarden,tapdb,lndservices,rpcserverandcmd/commands.testMintCustomAnchorPsbt.Fixes #721