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
Aurora Poppyseed, [23 Nov 2023 at 10:36:21]:
Nice so many questions! Gm btw
I was just wondering what would happen if they clicked on Lastic and Corego some Coretime during the same 6sec block
Then it would be the same if you would have two transactions done from two different accounts on the same chain. If there would be limited amount of cores, the one that is sooner wins the core. However if they are both in the same block, then it comes down to the one that pays the highest tip to the block author wins.
Will Lastic have its own token?
Will let @phillux answer this question..
Or blockspace can be bought with Dot?
Blockspace from the primary marketplace will be bought with Dot.
Interesting and necessary project for Polkadot coretimes. Will there be a testnet with nodes, or will Lastic run on another parachain?
Phil Polkadot Blockspace marketplace, [23 Nov 2023 at 10:53:54]:
Good question. We are still researching the best possible architecture for users. Ideally, we would leverage the work of other chains and keep our architecture lean and clean, as long as the performance is good for users. We are starting with user experience in mind, and want an architecture that best serves the users. The primary market (buying cores, buying instantaneous coretime), will be run on the new system parachain called the coretime chain, alongside the relay chain. We want to support both the primary market and create a liquid secondary market which will leverage smart contracts and/or a parachain on its own core.
Will Lastic have its own token?
I'll say this right now. Users of Lastic will not be required to have any token besides DOT. Coretime is settled in DOT and adding any token on top at this stage would only add friction. I know from personal experience I am 95% less likely to use an app if I need to buy a new token.
DOT will be used for both purchases and fees. That being said, we're researching the best way forward for incentivization of liquidity. Be sure that we will be fully transparent about any token before launch on Kusama.
Corego is Building
Corego is no longer active. The team split up and the devs have created RegionX, a collection of smart contracts that Lastic could potentially use. We are in close contact with Sergej and Oliver from RegionX and are collaborating already. Right now, our focus with them is to lower deposit fees for builders
Lastic services the leftover blockspace that the chains dont use?
Such good discussion from all of you! Happy to see good questions and comments come up. So yes, teams can buy directly from the relay chain. We are building an interface for both the PRIMARY and SECONDARY markets. the primary market is what polkadot as a system offers, namely bulk coretime and instantaneous coretime. Lastic will have a MUCH better interface than polkadot.js or straight up extrinsic calls which will make it much easier for teams to get. Lastic will build the SECONDARY market which will allow teams to split up their blockspace in many ways:
by allowing timeslice offerings (e.g., Team A purchases bulk, and Team B buys every 10th block from Team A on one core)
by allowing interlacing, although this won't happen short-term (i.e., sharing blocks amongst different teams)
by allowing brokerage trades, where a speculator buys in bulk and sells either the entire core or a portion to other teams
The text was updated successfully, but these errors were encountered:
Aurora Poppyseed, [23 Nov 2023 at 10:36:21]:
Nice so many questions! Gm btw
Then it would be the same if you would have two transactions done from two different accounts on the same chain. If there would be limited amount of cores, the one that is sooner wins the core. However if they are both in the same block, then it comes down to the one that pays the highest tip to the block author wins.
Phil Polkadot Blockspace marketplace, [23 Nov 2023 at 10:53:54]:
Good question. We are still researching the best possible architecture for users. Ideally, we would leverage the work of other chains and keep our architecture lean and clean, as long as the performance is good for users. We are starting with user experience in mind, and want an architecture that best serves the users. The primary market (buying cores, buying instantaneous coretime), will be run on the new system parachain called the coretime chain, alongside the relay chain. We want to support both the primary market and create a liquid secondary market which will leverage smart contracts and/or a parachain on its own core.
I'll say this right now. Users of Lastic will not be required to have any token besides DOT. Coretime is settled in DOT and adding any token on top at this stage would only add friction. I know from personal experience I am 95% less likely to use an app if I need to buy a new token.
DOT will be used for both purchases and fees. That being said, we're researching the best way forward for incentivization of liquidity. Be sure that we will be fully transparent about any token before launch on Kusama.
Corego is no longer active. The team split up and the devs have created RegionX, a collection of smart contracts that Lastic could potentially use. We are in close contact with Sergej and Oliver from RegionX and are collaborating already. Right now, our focus with them is to lower deposit fees for builders
Such good discussion from all of you! Happy to see good questions and comments come up. So yes, teams can buy directly from the relay chain. We are building an interface for both the PRIMARY and SECONDARY markets. the primary market is what polkadot as a system offers, namely bulk coretime and instantaneous coretime. Lastic will have a MUCH better interface than polkadot.js or straight up extrinsic calls which will make it much easier for teams to get. Lastic will build the SECONDARY market which will allow teams to split up their blockspace in many ways:
The text was updated successfully, but these errors were encountered: