You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contributing to a Coretime order costs DOT tokens. Anyone can contribute to the order with the DOT tokens they hold; however, users won't do that if they are not incentivized.
One way of incentivization is if the parachain holds significant value to them. This could be because they are using it or because they are the ones building the project(not wanting to 'their' chain to stall).
Another way of incentivization is for the parachain to define rewards for the contributors. This is similar to what we had in the crowdloan model. Parachains distribute their own native currencies to everyone who contributed in case they win the slot(in our case procuring coretime).
We want to allow parachains to easily incentivize anyone helping them in the procurement process.
Implementation
The initial idea was to have the reward logic placed in each parachain. However, even though this would offer more flexibility, it would require parachains to be able to read data about contributions from the RegionX parachain. This would end up being quite complex.
The new approach is to have the rewarding logic placed on the RegionX parachain. It would still be the parachain that defines the reward amount and the currency for rewarding, however, the rewarding would take place on RegionX. This also means that tokens used for rewarding would need to be on the RegionX parachain to enable reward distribution.
This way, the RegionX parachain can easily read the contribution data (since it is on the same chain) and implement the reward logic, so the parachains don't have to.
The text was updated successfully, but these errors were encountered:
Goal
Contributing to a Coretime order costs DOT tokens. Anyone can contribute to the order with the DOT tokens they hold; however, users won't do that if they are not incentivized.
One way of incentivization is if the parachain holds significant value to them. This could be because they are using it or because they are the ones building the project(not wanting to 'their' chain to stall).
Another way of incentivization is for the parachain to define rewards for the contributors. This is similar to what we had in the crowdloan model. Parachains distribute their own native currencies to everyone who contributed in case they win the slot(in our case procuring coretime).
We want to allow parachains to easily incentivize anyone helping them in the procurement process.
Implementation
The initial idea was to have the reward logic placed in each parachain. However, even though this would offer more flexibility, it would require parachains to be able to read data about contributions from the RegionX parachain. This would end up being quite complex.
The new approach is to have the rewarding logic placed on the RegionX parachain. It would still be the parachain that defines the reward amount and the currency for rewarding, however, the rewarding would take place on RegionX. This also means that tokens used for rewarding would need to be on the RegionX parachain to enable reward distribution.
This way, the RegionX parachain can easily read the contribution data (since it is on the same chain) and implement the reward logic, so the parachains don't have to.
The text was updated successfully, but these errors were encountered: