v0.8.6
One fix. Drop-in upgrade from 0.8.5.
Fixed
PASEO_ASSET_HUB.genesisHashrefreshed after the Paseo Asset Hub chain reset (#32). Thepaseo-asset-hub-nextchain was reset, changing its genesis from0x173cea…to0xbf0488dbe9daa1de1c08c5f743e26fdc2a4ecd74cf87dd1b4b1eeb99ae4ef19f. The built-inPASEO_ASSET_HUBconfig carried the old hash, so the host's chain-feature handshake rejected product-sdk descriptors regenerated against the new chain — the product app would sitdisconnectedin E2E even though the RPC was reachable. The new value is verified against the live chain viachain_getBlockHash(0).
What you need to do
- Upgrade to
0.8.6. If you only use the built-inPASEO_ASSET_HUBconfig, no code changes are needed — the correct genesis comes with the upgrade. - If you hardcoded the old genesis (
0x173cea…) in your ownChainConfigor test assertions, update it to0xbf0488….