feat(resolver): network transport via @parity/truapi-provider - #78
feat(resolver): network transport via @parity/truapi-provider#78BigTava wants to merge 9 commits into
Conversation
…dded smoldot light client
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Bundle Size ReportChunks over 500 KB:
All files
Commit: cb9b373 |
⚡ Performance Report
|
|
This is a Nova-side outage and not a dot.li test failure. Re-run Logs: https://github.com/paritytech/dotli-community/actions/runs/29525756736 |
…, and the bootnode preconnect
# Conflicts: # bun.lock # packages/resolver/package.json # packages/resolver/src/chain-specs/paseo.smol.json # packages/resolver/src/chain-specs/previewnet.smol.json
|
❌ E2E Product suite failed on Failed tests:
Logs: https://github.com/paritytech/dotli-community/actions/runs/30253820098 |
leonardocustodio
left a comment
There was a problem hiding this comment.
@valentinfernandez1 is this in your plans / PRs?
# Conflicts: # bun.lock # packages/resolver/src/smoldot.ts
…ity audit advisories
# Conflicts: # bun.lock # package.json # packages/resolver/package.json
Summary
dotli reads every chain through
@parity/truapi-provider's embedded smoldot light client, resolving each network from its genesis hash via the crate's bundled catalog, so the resolver no longer carries its own smoldot instance, database, or chain specs (gatewayrpcmode stays onpolkadot-api/ws).