Jeff Bencin

The `signer::v0::block_proposal_rejection` test is failing because `fetch_view()` fails to get the sortition view: ```console INFO [1719421727.355629] [stacks-signer/src/chainstate.rs:358] [signer_runloop] Latest state wasn't a sortition: SortitionInfo { burn_block_hash: 3ca9273766f766477b5ebcdb030742d4b17ae778085d75f6a4d4b99b291f180c, burn_block_height: 231, sortition_id:...

I've refactored this so that `signer::v0::block_proposal_rejection` passes. The basic flow now in `handle_block_proposal()` is: - Try to fetch a sortition view if we don't have one - If proposal fails...

I fixed the failing integration test be removing the call to `wait_for_validate_reject_response()`, which waits for a `BlockValidateResponse` from the node. Instead, we just check for a `BlockResponse` from the signer

I opened #5137, which adds better logging when deadlocks are suspected, and eventually gives up and returns an error (which may be recoverable or may crash the application) if rusqlite...

Another option is to add a re-entrant mutex around any database transaction (maybe by adding it to the `DBTx` type?). This would allow one thread to open multiple databases, but...

@kyranjamie Yeah I just got back to working on this, I'll set something up

Just an update on this: I ended up writing a CLI tool to perform the transfers. See [this](https://github.com/hirosystems/multisig-cli) project. I'll update this issue again when the PR to the Ledger...

I'm not sure if any work has been done to support this on Ledger yet, but I wanted to update this issue since [SIP-027: non-sequential multisig transactions](https://github.com/stacksgov/sips/pull/152) just passed ([vote...

> Which are the "correct" parameters needed here? Set `useNonSequentialMultiSig` to `true` when calling `makeUnsignedSTXTokenTransfer()` ([docs](https://stacks.js.org/interfaces/_stacks_transactions.UnsignedMultiSigOptions#useNonSequentialMultiSig)) That should be all that's needed to create a SIP-027 multisig tx. The process...

BTW you can easily test if a signed transaction is valid with `stacks-inspect`. Hex-encode the transaction and run this in the stacks-core repository: ```sh cargo build --release --bin=stacks-inspect target/release/stacks-inspect decode-tx...