generated from jimmychu0807/substrate-front-end-template
-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Labels
$$~51-150usd~51-150usdREAD ONLYRequires research into how something should be implemented, write a thorough description.Requires research into how something should be implemented, write a thorough description.SubstrateDevsThis label is great for substrate devs, who detest frontend as I was told 😂This label is great for substrate devs, who detest frontend as I was told 😂p1Essential issue - priority 1Essential issue - priority 1
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


Question is how can we get these two values of individuals paraId.
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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
$$~51-150usd~51-150usdREAD ONLYRequires research into how something should be implemented, write a thorough description.Requires research into how something should be implemented, write a thorough description.SubstrateDevsThis label is great for substrate devs, who detest frontend as I was told 😂This label is great for substrate devs, who detest frontend as I was told 😂p1Essential issue - priority 1Essential issue - priority 1