paritytech / paritytech/triangle-js-sdks
Share a single warm connection to common chains (individuality, bulletin, assethub) for all Applications to use
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 8
Description
In reference to Reusable Components
Products should not have to worry about fetching chain types/descriptors or opening fresh connections to chains (which makes app startup slower)
All apps will be interacting with the same 3 chains (asset hub, bulletin, individuality). The Product SDK should expose some unified typed interface to these chains, which is routed through a warm connection the Host owns making apps more snappy on startup. The Host would own which environment this points to (Paseo vs Polkadot vs Preview Net)
Something like:
import { chains } from "@novasamatech/product-sdk"
chains.assetHub.<regular papi TypedAPI>
chains.bulletin.<regular papi TypedAPI>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Reusable Components document and the Product SDK and Host entry points. Trace how chain types, descriptors, and connections are currently obtained for individuality, bulletin, and asset hub. Done means the SDK exposes typed interfaces for all three chains through warm Host-owned connections, with the Host selecting the environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100