optimism-oracle-service's Introduction

optimism-ts-services

[Optimism] Client-Side Services

Fraud Prover

Environment Variable	Required?	Default Value	Description
`L1_WALLET_KEY`	Yes	N/A	Private key for an account on Layer 1 (Ethereum) to be used to submit fraud proof transactions.
`L2_NODE_WEB3_URL`	No	http://localhost:9545	HTTP endpoint for a Layer 2 (Optimism) Verifier node.
`L1_NODE_WEB3_URL`	No	http://localhost:8545	HTTP endpoint for a Layer 1 (Ethereum) node.
`RELAY_GAS_LIMIT`	No	9,000,000	Maximum amount of gas to provide to fraud proof transactions (except for the "transaction execution" step).
`RUN_GAS_LIMIT`	No	9,000,000	Maximum amount of gas to provide to the "transaction execution" step.
`POLLING_INTERVAL`	No	5,000	Time (in milliseconds) to wait while polling for new transactions.
`L2_BLOCK_OFFSET`	No	1	Offset between the `CanonicalTransactionChain` contract on Layer 1 and the blocks on Layer 2. Currently defaults to 1, but will likely be removed as soon as possible.
`L1_BLOCK_FINALITY`	No	0	Number of Layer 1 blocks to wait before considering a given event.
`L1_START_OFFSET`	No	0	Layer 1 block number to start scanning for transactions from.
`FROM_L2_TRANSACTION_INDEX`	No	0	Layer 2 block number to start scanning for transactions from.

Message Passer

The Message Passer is used to confirm L2 to L1 messages on L1. By default, it will send transactions to L1 when it detects that it needs to. It can also be configured to write data to a Google Sheet so that the transactions can be closely inspected.

To run in spreadsheet mode, the following environment variables are used:

Environment Variable	Description
`SPREADSHEET_MODE`	Set this to anything to run in spreadsheet mode
`SHEET_ID`	The ID of the Google Sheet, can be found in the URL
`CLIENT_EMAIL`	A service account email address
`CLIENT_PRIVATE_KEY`	A service account RSA private key

The key and service account can be managed at console.developers.google.com. A Google Sheet must be created with the correct row headers and the SHEET_ID can be pulled from the URL of the Google Sheet.

optimism-oracle-service's People

Contributors

Watchers

optimism-oracle-service's Issues

should update `findAllEvents` logic

set L1_START_OFFSET value in .env file

We should adjust this value to scan the event.

should check if it works with `number` type

Currently, we use number type, not BigNumber type to make transaction proof.

Oracle challenge against not forwarding fast withdrawal

If the user tries to withdraw some big amount, say 100000 TON, and in the worst case, Oracle service doesn’t forward the request to Oracle contract, then he/she might have to wait for DTD to get back the tokens. This could be a problem since the amount involved is huge. Do we punish the Oracle service for not processing a genuine FW? Like, slashing a % of their bond in Oracle contract and then give the penalty to the user.

There is a similar problem in Hop protocol. If the bonder doesn’t serve a request, then the user needs to wait for 1 week to settle the Transfer Roots and get back their tokens. I believe in future, they will introduce a bonding/slashing mechanism for bonders.

Recommend Projects