add 3 more Ink interface

[open-junius]

Description

Follow the PR #2768, update the Ink contract in ts-tests and verify all 3 new query functions.

Related Issue(s)

• Closes #[issue number]

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Other (please describe):

Breaking Change

If this PR introduces a breaking change, please provide a detailed description of the impact and the migration path for existing applications.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have run ./scripts/fix_rust.sh to ensure my code is formatted and linted correctly
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

Please include any relevant screenshots or GIFs that demonstrate the changes made.

Additional Notes

Please provide any additional information or context that may be helpful for reviewers.

[github-actions]

🛡️ AI Review — Skeptic (security review)

VERDICT: SAFE

LOW/BASELINE scrutiny: open-junius has repo write permission, substantial prior contribution history, no committer mismatch except the expected subtensor-ai-review bot auto-fix commit, and no Gittensor allowlist match found; branch add-tests-for-new-query -> devnet-ready.

Static-only Skeptic review found the diff limited to Ink contract metadata, an updated WASM test artifact, and three added zombienet EVM contract tests for read-only query messages. No .github/, runtime/pallet source, dependency manifests, lockfiles, build scripts, workflow/tooling, or package-manager files were changed. A targeted static strings scan of the updated WASM showed only normal Ink seal imports and no shell, network, filesystem, credential, or supply-chain indicators.

Findings

No findings.

Conclusion

No malicious intent or security vulnerability found in the changed surface. Remaining risk is ordinary binary test-artifact review risk for the updated WASM, with no concrete security issue identified.

---

🔍 AI Review — Auditor (domain review)

VERDICT: 👍

Gittensor: UNKNOWN; author has repo write permission and substantial prior contribution history. No overlapping PRs were prefetched.

The Auditor proposed a replacement PR description, but the current body is non-trivial; not overwriting. Maintainers: ask the Auditor to regenerate if you want it.

This PR is limited to the Ink contract artifact/metadata and the zombienet EVM wasm-contract test suite. The updated bittensor.json source hash matches the committed bittensor.wasm BLAKE2b-256 hash, and the three added tests cover the new read-only Ink query messages.

No runtime or pallet code changed, so no spec-version bump is required. Verification performed: b2sum -l 256 ts-tests/ink/bittensor.wasm matched ts-tests/ink/bittensor.json and git diff --check passed. I did not run the zombienet suite because no finding required runtime confirmation.

Findings

No findings.

Conclusion

Approved. The PR adds focused EVM/Ink coverage for the new query interfaces without changing on-chain behavior, and I found no domain issue blocking merge.

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍