Skip to content

fix: pin async-substrate-interface==1.6.4 + bump bt-decode to 0.8.0#153

Merged
mizu-tx merged 1 commit into
mainfrom
fix/pin-async-substrate-interface
Jun 23, 2026
Merged

fix: pin async-substrate-interface==1.6.4 + bump bt-decode to 0.8.0#153
mizu-tx merged 1 commit into
mainfrom
fix/pin-async-substrate-interface

Conversation

@elliot-bitcast

Copy link
Copy Markdown
Contributor

Problem

async-substrate-interface>=1.4.2 was an open-ended floor pin. pip resolves this to 2.2.0 (latest), which has two breaking changes that crash import bittensor:

  1. scalecodec/cyscale conflict — 2.x adds a runtime conflict check that raises RuntimeError on import
  2. ScaleObj removed from async_substrate_interface.types — bittensor 9.12.2 imports it directly → ImportError

This was reported by a miner/validator hitting the error on fresh install.

Fix

  • Pin async-substrate-interface==1.6.4 (latest compatible 1.x, same as bitcast-x)
  • Bump bt-decode==0.6.00.8.0 (required by async-substrate-interface 1.6.4)

Verification

Reproduced the crash with 2.2.0, then verified the fix:

pip install -r requirements.txt  ✅ clean install
import bittensor                   ✅ (v9.12.2)
from async_substrate_interface.types import ScaleObj  ✅
from async_substrate_interface import SubstrateInterface  ✅
import bt_decode                   ✅

Context

Same fix already applied to bitcast-x in commit 3cb60e2 (4 May 2026). This PR brings the main neuron repo in line.

async-substrate-interface>=1.4.2 was unpinned, allowing pip to resolve
to 2.x which breaks bittensor 9.12.2 with two hard import errors:
1. scalecodec/cyscale namespace conflict (RuntimeError on import)
2. ScaleObj removed from async_substrate_interface.types (ImportError)

Pin to 1.6.4 (latest compatible 1.x). This requires bt-decode==0.8.0
(1.6.4 depends on it); bt-decode==0.6.0 is incompatible.

Same fix already applied to bitcast-x in commit 3cb60e2.

Tested: pip install -r requirements.txt + import bittensor passes clean.
@mizu-tx mizu-tx merged commit 2f61d21 into main Jun 23, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants