LasticXYZ / LasticXYZ/LasticUI
research how to find a persons paraId (best to find it in polkadot js) - ONLY READ CODE
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
When a person purchases a paraId, is this written somewhere in the state, or is there some event that happens, that we can track to mark that change, and if so which event?
Write implementation details for other developers or yourself, this issue requires only searching in substrate.
Try to be as through as possible in your desciption.
on polkadot js this functionality looks like:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains/parathreads
An example issue resolve could look like this:
To implement it you should interact with the following functions:
It works in the following way:
- person should buy the core, then call this extrinsic
- to visualize do ....
If you want to take this issue on, comment underneath.
Contributor guide
No contributing guide indexed for this repository
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 by reading the Substrate code related to paraId purchases and the Polkadot.js parachains/parathreads view linked in the issue. Identify where the individual paraId values are stored or which event exposes them, then document the relevant functions, extrinsics, and event or state data so another developer can implement the lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100