Skip to content

feat: add devnet as a selectable network - #22

Open
illegalcall wants to merge 5 commits into
paritytech:mainfrom
illegalcall:feat/add-devnet-network
Open

feat: add devnet as a selectable network#22
illegalcall wants to merge 5 commits into
paritytech:mainfrom
illegalcall:feat/add-devnet-network

Conversation

@illegalcall

@illegalcall illegalcall commented Jul 24, 2026

Copy link
Copy Markdown
Collaborator

Closes #20

Stacked on #21; review only the last commit until #21 merges.

Adds devnet as a build-time network (VITE_NETWORK=devnet) alongside paseo-next, with the devnet registry and gateways. Chain access is host-routed, so the descriptor selects the network. Contract addresses resolve live from the selected registry. Adds a devnet deploy script and a DEPLOYMENT.md note (CDM v0.9.0+, para-1000 faucet, and deploy-before-build guidance).

Typecheck and both build variants pass. A full devnet round needs the contract deployed there and a Desktop smoke test.

Bump product-sdk ^0.19.1, chain-client ^0.9.1, contracts ^0.9.2,
descriptors ^0.8.0, signer ^0.11.1, statement-store ^0.6.2, tx ^0.3.2;
drop @novasamatech/host-api(-wrapper). The two remaining wrapper call
sites (requestPermission, preimageManager) move to
@parity/product-sdk-host. Result-API migration: contract .tx unwrapped
in the getContract proxy, fromLiveClient and ensureContractAccountMapped
branch on .ok. Statement-store publish now returns a Result; call sites
already ignored the old boolean, so semantics are unchanged.

Closes paritytech#19
publish returns a Result instead of throwing since product-sdk 0.18, and
the multiplayer sends ignored it, so connection and size failures passed
silently. Unwrap every publish so a failed send surfaces to the player
instead of stalling the round.

Declare @parity/product-sdk-host directly and drop the unused
@parity/product-sdk umbrella so host no longer resolves only by hoisting.
Wrap the account mapping in try/catch so the cause logging runs whether
it returns an error or throws. Update the stale @novasamatech/host-api
reference in the AI-config files.
Two-network config (paseo-next, devnet) selected at build time via
VITE_NETWORK; default stays paseo-next. Descriptors load dynamically
and the host-routed chain client takes its identity from the loaded
descriptor, so no endpoints or genesis are pinned. fromLiveClient now
takes the selected network's registry address, so devnet resolves the
leaderboard against the devnet registry. Add the cdm devnet preset
deploy script and a paseo-next vs devnet note in DEPLOYMENT.md.

Closes paritytech#20
@illegalcall
illegalcall force-pushed the feat/add-devnet-network branch from 136ec2b to 30c7b2f Compare July 30, 2026 12:14
@illegalcall

Copy link
Copy Markdown
Collaborator Author

Applied the metadata-chunk fold: network selection is now a direct literal comparison on import.meta.env.VITE_NETWORK, so Vite drops the unselected network's chunk. Both build variants ship only the selected network's metadata. A full devnet round still needs the contract deployed there and a Desktop smoke test on my side.

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.

Add support for the latest environments (add devnet, retire summit/w3s)

1 participant