THE 2-MINUTE RULE FOR SCROLL BRIDGE

The 2-Minute Rule for scroll bridge

The 2-Minute Rule for scroll bridge

Blog Article

Clever Routing: Dynamically selects exceptional paths for asset transfers according to variables like Charge and velocity.

Gasoline limit necessary to finish the deposit on L1. This can be optional, ship 0 in the event you don’t would like to set it.

During the impending sections, We'll discover the technical areas of the bridge, including the good deal API required to employ its capabilities.

Visualize staying amongst the first to leverage Scroll Community’s abilities, with sufficient the perfect time to scope out the chances, analyze probable tasks, and possess your funds All set for when your favorite ventures go Dwell.

to purchase L2 service fees. If the quantity is not sufficient, the transaction will not be sent. All extra ETH is going to be despatched again to

Gas limit required to complete the deposit on L2. 170000 ought to be sufficient to method the transaction, but unused money are refunded.

The Sequencer provides a JSON-RPC interface and accepts L2 transactions. Each and every several seconds, it retrieves a batch of transactions from the L2 mempool and executes them to create a different L2 block and a new state root.

This transaction primarily "locks" your asset inside a secure good contract on Ethereum. The clever agreement retains your asset until an equal sum is minted within the Scroll community.

In addition, look at introducing comments mentioning the slots which were already used to keep track of the deprecated slots when upgrading the contracts.

On the other hand, to maximize its likely, users require a trusted mechanism to move their property forwards and backwards in between Scroll and Ethereum, together with other networks that may be integrated Sooner or later.

As an example, if a person needs to simply deposit ETH, in both variations they should get in touch with the depositETH functionality within Scrollbridge the L1GatewayRouter contract. The primary difference lies in who calls and passes the concept to the L1ScrollMessenger agreement. In the previous implementation, the message would come from the L1ETHGateway deal, whereas in The present implementation, the L1GatewayRouter would be the caller.

Scripts exist for the two Foundry and Hardhat, but plainly People Utilized in the latter are outdated and deprecated. That is error-susceptible and a priority since production environment variables can be employed in the incorrect scripts and therefore run unneeded/erroneous transactions.

14d timelock. Admin from the ScrollOwner agreement, indicating it may assign and revoke roles. The ScrollMultisig can suggest and terminate transactions, and the ExecutorMultisig can execute them.

Incorporates the assortment of queued L1 -> L2 messages, possibly appended utilizing the L1ScrollMessenger or even the EnforcedTxGateway. The latter contract, which might allow for people to send out L2 messages from L1 with their own personal deal with as the sender, is not enabled nonetheless.

Report this page