Non-alphabet IR node can't start #1548

New issue

Closed

opened 2025-12-28 17:35:49 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:35:49 +00:00

Owner

Originally created by @roman-khimov on GitHub (Dec 8, 2025).

Originally assigned to: @cthulhu-rider on GitHub.

Expected Behavior

Additional IR node starting fine.

Current Behavior

2025-12-08T07:37:41.354Z info neofs-ir/main.go:111 internal error {"msg": "FS chain: structurize containers in the contract: notary call addStructs contract method: can't convert account to inner ring multisig wallet: own public key was not found among multisig keys"}

And it exits after that (even though it's info). See https://rest.fs.neo.org/Aku38wpn2xEqfEPxmwyAa7N3VnAkMV8PEVkpLqwKM1z3/4464-1765181534/index.html#suites/ddefd573f06d301a5cd520af0020ca1e/6b1e138969e8e164/

Possible Solution

Fix something for non-alpha IRs.

Steps to Reproduce (for bugs)

Run our regular testsuite against master.

Regression

Yes, https://github.com/nspcc-dev/neofs-node/pull/3670

Your Environment

Version used: master

Originally created by @roman-khimov on GitHub (Dec 8, 2025). Originally assigned to: @cthulhu-rider on GitHub. ## Expected Behavior Additional IR node starting fine. ## Current Behavior > 2025-12-08T07:37:41.354Z info neofs-ir/main.go:111 internal error {"msg": "FS chain: structurize containers in the contract: notary call addStructs contract method: can't convert account to inner ring multisig wallet: own public key was not found among multisig keys"} And it exits after that (even though it's `info`). See https://rest.fs.neo.org/Aku38wpn2xEqfEPxmwyAa7N3VnAkMV8PEVkpLqwKM1z3/4464-1765181534/index.html#suites/ddefd573f06d301a5cd520af0020ca1e/6b1e138969e8e164/ ## Possible Solution Fix something for non-alpha IRs. ## Steps to Reproduce (for bugs) Run our regular testsuite against master. ## Regression Yes, https://github.com/nspcc-dev/neofs-node/pull/3670 ## Your Environment * Version used: master