Release 449

[UnArbosFour]

Motivation

Prepare runtime release 449 so the release train can distinguish the new runtime from specification 448.

Changes

• Increment runtime/src/lib.rs spec_version from 448 to 449.
• No runtime logic, storage layout, APIs, dependencies, or transaction version are changed by this PR itself.

Behavioral impact

Nodes and clients will identify the resulting runtime as specification 449. This PR contains no migration and introduces no direct behavioral change beyond the version identifier.

Testing

No targeted runtime tests were run because the diff changes only the spec_version constant; release CI should validate the assembled runtime candidate.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
subtensor	Ready	Preview	Aug 21, 2026 4:56pm

[github-actions]

🛡️ AI Review — Skeptic (security review)

VERDICT: SAFE

VERY HIGH scrutiny (account has only 1 public repository), mitigated by repository write access and substantive merged history; no Gittensor association found; release-449 → main.

The PR contains only the mechanical runtime spec_version bump from 448 to 449. No trust-boundary, dependency, runtime-logic, or executable CI changes are present.

Findings

No findings.

Conclusion

The isolated release version bump introduces no security vulnerability or indication of malicious behavior.

---

🔍 AI Review — Auditor (domain review)

VERDICT: 👍

Gittensor association: UNKNOWN; newer account but active repository collaborator with substantial subtensor contributions.

PR body was empty/trivial; the Auditor has auto-filled it. Please review.

The diff solely increments spec_version from 448 to 449 for the release candidate. Overlapping PRs only share runtime/src/lib.rs and are not semantic duplicates.

Validation: git diff --check passed; the worktree is clean. Builds and tests were skipped because this constant-only change needs no runtime confirmation.

Findings

No findings.

Conclusion

The release-version bump is correct and introduces no domain correctness concerns. Ready to merge.

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍