-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does on demand coretime work? #173
Comments
Polkadot On-demand CoretimeStorages
|
I switched up the order a bit to allow for more clarity for the reader. Looks like a lot of things on the extrinsics side need to be implemented. To be continued 👍 Polkadot On-demand CoretimeWhat is On-demand Coretime?On-demand or instantaneous coretime refers to the ability to allocate computational resources (cores) on the Polkadot Ubiquitous Computer quickly and dynamically. This capability allows for efficient and flexible use of computational resources based on immediate needs. The inner workings of On-demand Coretime are specified in RFC-5. Definitions:
How to implement On-demand Coretime?The following sections describe the user flows necessary to enable seamless interaction with the on-demand coretime: User Flow for Parachain TeamsThis flow is for parachain teams who already have a ParaId and code they want to test, but need coretime to do so. Steps:
Checking Credit BalanceCurrently, checking the credit balance is a work in progress. For now, Coretime credits have been disabled. Follow the progress here: Parity issue #2210. Trader Flow for ProfitThis flow is for traders who aim to buy coretime for profit and place it into the Instantaneous Coretime Pool to earn a return on investment. Steps:
Receive Visualization & Notifications for Consumed Coretime
/// Record of a single contribution to the On-demand Coretime Pool.
#[pallet::storage]
pub type InstaPoolContribution<T> =
StorageMap<_, Blake2_128Concat, RegionId, ContributionRecordOf<T>, OptionQuery>;
RevenueClaimPaid {
/// The account to whom revenue has been paid.
who: T::AccountId,
/// The total amount of revenue claimed and paid.
amount: BalanceOf<T>,
/// The next region which should be claimed for the continuation of this contribution.
next: Option<RegionId>,
}, Storages
|
Explain what the reading of the state mean:
instaPoolIo
instaPoolContribution
instaPoolHistory
Extrinsic:
pool(... )
purchaseCredit(...) is already implemented, unclear is how to use what to input for it's amount
Make also a list of events and if it's possible to use some of them instead of reading the state directly.
https://lastic.squids.live/rococo-coretime/graphql
This issue is a bit longer one, I think some of the code is written on the coretime chain and some functions are on the relay chain.
How to implement On Demand Coretime?
It works in the following way:
issue resolve:
To implement it you should interact with the following functions:
Ask under the issue if something is unclear, comment if you are ready to take this issue on :)
The text was updated successfully, but these errors were encountered: