chore(deps): bump github.com/gnolang/gno from 0.0.0-20260914072242-1bf7282dd85e to 0.2641.2 in /backend

[dependabot]

Bumps github.com/gnolang/gno from 0.0.0-20260914072242-1bf7282dd85e to 0.2641.2.

Release notes

Sourced from github.com/gnolang/gno's releases.

chain/topaz

gno topaz

Topaz is a fresh testnet for the Gno testnet line — a new chain, not a hardfork.

• Release tag: chain/topaz
• Target commit: fc4052651
• Previous release tag: chain/test13
• Previous release commit: f45cc5c88
• Full release compare: tags/chain/test13...tags/chain/topaz
• Topaz release-candidate PR: #5945

Summary

This time we started from scratch. test13 was a hardfork of gnoland1 that replayed the whole source-chain history at genesis; for topaz we prototyped the next step of that approach (gnoland1 replay + test13's own tx history) and abandoned it: the genesis ballooned to ~3 GB, months of master drift broke most replayed transactions (an effectively unbounded patching effort), and every node would have spent hours in InitChain before its first block. Topaz instead builds a fresh 2.7 MB genesis from the repo's examples/ tree in about a minute, and a node boots it in seconds.

Consequently, no state carries over from test13 — balances, realms, and registered names start from zero. Grab GNOT from the faucet and re-register.

The chain: chain-id topaz-1, 90 curated packages at genesis, aeddi as sole GovDAO T1 member, 2 founding validators with operator-keyed valoper profiles, namespace enforcement (r/sys/names) enabled from block 1, 10 pre-funded faucets, and unrestricted token transfers (test13 launched with a locked bank; topaz does not).

Code baseline: master 959cefd91 — 133 commits ahead of test13's baseline.

Changes since test13

Breaking / consensus-relevant:

• fix(grc20)!: token id decoupled from symbol (#5908)
• secp256k1 validator keys no longer supported (#5949)
• package name must match the last path element at addpkg (#5048)
• cockroachdb/apd replaced by math/big.Rat in the VM (#5867)
• type-check + preprocess gas now metered at AddPackage/Run (#5892)

VM correctness — a large batch of gnovm fixes, notably: interface-bound method dispatch (#5737), embedded field/method lookup (#5721, #5739), deterministic type-check verdicts (#5893), tuple assignment order (#5790), map-delete object reclaim (#5882, #5899).

New features:

• sub-realm identities via realm.Sub(subpath) (#5890)
• mempackage storage split into prod and test blobs (#5891)
• vesting accounts PoC (#5840)
• tm2 p2p address book (#5861)
• concurrent ABCI queries via snapshot isolation (#5431)
• gnoweb package overview source doc (#5572)

Genesis / operator tooling (developed for the topaz effort, landed on master):

• loud genesis-replay failures (#5924)
• GnoTxMetadata provenance fields (#5925)
• unified genesis signature-skip for replay txs (#5926)
• gnogenesis fork provenance, tx patching + inspect (#5927)
• valid, payable fork valoper-seed output (#5928)

... (truncated)

Commits

• See full diff in compare view

[dependabot]

Labels

The following labels could not be found: backend, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[netlify]

✅ Deploy Preview for memba-multisig canceled.

Name	Link
🔨 Latest commit	3d77147
🔍 Latest deploy log	https://app.netlify.com/projects/memba-multisig/deploys/6ab404cb3ebafa0008ed56c3

[zxxma]

Closing: this bump cannot merge. The tagged release 0.2641.2 lacks SessionAddr and VerifySignaturePayload, which the backend uses from the pinned commit 1bf7282dd85e, so the backend does not compile against the tag (the two failing checks). The pin moves when a tagged gno release carries both.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.