Mark Tyneway
Mark Tyneway
It should be possible to build an aggregated validity proof service for the OP Stack. A blockchain has inputs and outputs. The inputs to an OP Stack chain are all...
As of Ecotone, the L1 Attributes transaction includes the following information: - baseFeeScalar - blobBaseFeeScalar - sequenceNumber - l1BlockTimestamp - l1BlockNumber - basefee - blobBaseFee - l1BlockHash - batcherHash Not...
We would like to add support for the ability to use an L1 based ERC20 token as the native gas token on L2. This feature needs to specified before consideration...
### Enabling a L2 Native ERC20 Token to Pay for Gas This is an experimental feature and it is not clear if it will ever be included in the OP...
Right now there are various config values in the L1 system config smart contract that are related to the fees charged on L2. These values can easily be set in...
Right now it is difficult to contribute or consume the specs because of the way that they are laid out. It is not clear where to add new information and...
Every executing message that is included adds cost to the derivation pipeline. There needs to be some mechanism by which that cost is paid for by users. There are a...
**Description** Adds an experimental spec for a deposit queue. This feature is meant to solve: - Complexity of `ResourceMetering` - No deposit transaction frontrunning grief - Consistent amount of gas...
Can validity proofs be utilized to improve the scalability of the interop protocol? It isn't immediately clear if they can without first shipping the devnet and then seeing how much...
Right now, the L1 portion of the fee is defined in native code. With various hardforks, the fee calculations are changed. This adds tech debt to the state transition function...