FS chain deployment stucks on error in forming a role assignment transaction #172

New issue

Open

opened 2025-12-28 18:08:46 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:08:46 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (May 27, 2024).

i encountered stuck deployment with following error once:

calculating network fee: ... - witness hash mismatch

it appears when non-leader (not Az) node forms transaction designating Notary role to the committee (code)

i haven't been able to reproduce the problem yet. Note that deployment with the autoset option is protected from role designation errors

© @AnnaShaleva:

This error happens when your verification script script hash does not match the address of a non-contract signer. For example, the witness verification script is filled out incorrectly (it usually contains a push set of public keys and checksig\checkmultisig), for example, the keys are sorted incorrectly or some of the keys may be missing, I would check if there is a race anywhere in the code that composes the verification skriptik. Either the signer hash was filled in incorrectly, or it is completely empty, or someone cleaned it up after filling it.

Originally created by @cthulhu-rider on GitHub (May 27, 2024). i encountered stuck deployment with following error once: ``` calculating network fee: ... - witness hash mismatch ``` it appears when non-leader (not Az) node forms transaction designating Notary role to the committee ([code](https://github.com/nspcc-dev/neofs-contract/blob/c9813b6cd9840ac94c59f65b7cead212847a9433/deploy/notary.go#L628-L633)) i haven't been able to reproduce the problem yet. Note that deployment with the autoset [option](https://github.com/nspcc-dev/neofs-node/blob/9a9a5d5f4a9452cbb566d51548390d31f9038e5d/config/example/ir.yaml#L86) is protected from role designation errors --- _© @AnnaShaleva:_ > This error happens when your verification script script hash does not match the address of a non-contract signer. For example, the witness verification script is filled out incorrectly (it usually contains a push set of public keys and checksig\checkmultisig), for example, the keys are sorted incorrectly or some of the keys may be missing, I would check if there is a race anywhere in the code that composes the verification skriptik. Either the signer hash was filled in incorrectly, or it is completely empty, or someone cleaned it up after filling it.