The Scrollbridge Diaries

The Scrollbridge Diaries

Blog Article

Ultimately, the l2geth node will move the transaction into the L2ScrollMessenger contract for execution on L2.

Adapting parameters stored in variables as immutable values and assigning These values over the deployment

Although the protection with Foundry executes perfectly, it displays an vacant coverage for every one of the contracts In the src/libraries/verifier sub-directory.

This audit reviewed the improvements made to many Scroll contracts as Component of pull request #1011. These adjustments had The only objective of minimizing the gas price of the Procedure. The most noteworthy changes encompass:

1st, divide the duration in centimeters through the item of π as well as the circle’s diameter. Multiply The end result by 360 to get the angle in degrees.

This bridge presents entry to a broader number of assets and apps That will not be straight suitable with Scroll. Visualize it because the gateway that expands Scroll's horizons.

In addition, the likely to increase this features to other blockchains opens up enjoyable alternatives for cross-chain interactions.

In foreseeable future upgrades, end users should be able to bypass the L1ScrollMessenger and ship messages straight to the L1MessageQueue. If a message is shipped

This report provides our results and recommendations concerning the additions designed on the Scroll ZK-rollup protocol. We urge the Scroll crew to contemplate these findings of their ongoing initiatives to supply a secure and economical Layer 2 Answer for Ethereum.

In this kind of dropping state of affairs, as being the tackle that sent the message towards the L1ScrollMessenger contract is the one that will be termed to execute the onDropMessage hook, if these types of hook is not really carried out, the dropping mechanism will fail and the first consumer is not going to get their ETH back.

Deprecated: the operation scroll bridge of the contract has long been moved to your L1MessageQueue contract. It absolutely was accustomed to relay the L2 basefee on L1 in a reliable way using a whitelist. It absolutely was also accustomed to store and update values relevant to intrinsic gas Price tag calculations.

Generation of a whole new contract that inherits from the MessageQueue agreement and adds functionalities from the L2GasPriceOracle deal to decrease the dependency on external phone calls

There isn't any script defined within the package deal.json to run the Foundry protection. Consider adding one as done for the checks and for Hardhat's protection.

Hold a watch out for the interesting interactions that await you, from partaking with a big selection of copyright to Discovering Decentralized purposes on the Scroll network.