CoreJam System Chain on EVM L2s with OP Stack #33
Conversation
sourabhniyogi
changed the title
|
With respect to (1) I believe this is out of scope of adding EVM contracts to Polkadot per-se (though is something I'd very much like to see). As long as Polkadot's DA is exposed, L2 stacks can be built anywhere on top of Polkadot. As you mentioned in the RFC, I did indeed write a post advocating for every chain to have smart contracts. I think my arguments on synchronous composability still hold. I'd tentatively support having some very limited amount of Polkadot relay-chain blockspace allocated to smart contracts, though in the event that on-chain processing becomes the bottleneck for the number of cores, I'd advocate for the smart contract functionality to be outmoded by the number of cores. |
|
CoreJam already provides for the possibility of permissionless logic to be introduced for determination on the Relay-chain itself. CoreJam, as it already stands, enables both (1) and (2) without needing to reassign "blockspace" in this way. |
sourabhniyogi
changed the title
Polkadot+Kusama should support the possibility of having up to 10-30% of its blockspace weight allocatable to EVM and WASM Smart Contracts. This is not for Polkadot to be a yet another EVM Chain, but specifically to: 1. support the use of Polkadot's Data Availability resources to non-Substrate [largely EVM] L2 Stacks, which will bring in additional demand for DOT and through those networks, new users and developers 2. (assuming CoreJam Work Packages have some direct relation to EVM Contracts + WASM Contract *Interpretation*), support Polkadot 2.0 experimentation in its transformation into a “map reduce” computer and bring in new classes of CoreJam+CorePlay developers in addressing sync/asynchronous composability
sourabhniyogi
force-pushed
the
support-non-substrate-l2
branch
from
75b904f
to
b8649b1
Compare
sourabhniyogi
changed the title
sourabhniyogi
changed the title
This proposal adapts the CoreJam architecture to EVM L2s, specifically utilizing OP Stack + Solidity instead of Polkadot/Substrate. Almost all CoreJam concepts are retained, but CoreJam's Rust relay chain interfaces are replaced with Solidity/EVM Contracts + OP Stack's Golang, situated in a "system chain".
sourabhniyogi
force-pushed
the
support-non-substrate-l2
branch
from
64eefd1
to
d2c40a9
Compare
sourabhniyogi
changed the title
Original: Polkadot+Kusama should support the possibility of having up to 10-30% of its blockspace weight allocatable to EVM and WASM Smart Contracts. This is not for Polkadot to be a yet another EVM Chain, but specifically to:
Updated: This proposal attempts to adapt the CoreJam architecture to EVM L2s, specifically utilizing OP Stack + Solidity instead of Polkadot/Substrate. Almost all CoreJam concepts are retained, but CoreJam's interfaces are replaced with Solidity/EVM Contracts + OP Stack's Golang.