v0.4 · OMG Network
- Child chain now accepts fee in a transaction submitted to it via
- List of accepted fee tokens and the corresponding amount can be retrieved via a query to
- The fee amount in a transaction is implicitly determined by the amount of token difference between outputs and inputs.
- The fee amount must be correct as specified in
/fees.all. Underpaying or Overpaying a fee in a transaction will result in a returned error.
- Integrator can create a transaction with a valid fee amount via
/transaction.createAPI endpoint by specifying fee tokens. Alternatively, a client can build the transaction with a valid fee from scratch via a call to fees.all before the transaction build process.
- Currently, the fees are statically set per each environment. This is expected to change once a more dynamic fee model has been applied, however, consuming fee API is expected to stay the same from integration’s point of view.
Two flavors of the watcher are now available: Watcher and WatcherInfo.
- 1.The Watcher (watcher) contains the security-critical features for monitoring and interacting with the childchain. It contains a limited set of APIs that allow you to securely transact with the OMG Network, such as transaction submission, retrieval of UTXOs, challenge data, in-flight exits, etc.
- 2.The WatcherInfo (watcher_info), like the Watcher, contains the security-critical features for monitoring and interacting with the childchain. Additionally, the WatcherInfo contains an additional set of informational API endpoints that allow convenient retrieval of data related to the network and transactions, namely accounts, blocks, transactions, fees, network statistics, etc.
In general, run and/or integrate with the WatcherInfo to utilize the full set of watcher functionalities. Integrate with the Watcher when you have specific requirements to utilize only the security-critical components.
- The Watcher or WatcherInfo may return an “operation:service_unavailable” error when a potential issue within itself or the network is detected. The issue ranges from Ethereum disconnectivity, slow Ethereum sync to potential byzantine events. Once the issue is resolved, endpoints are served again. The list of current events can be retrieved from /alarm.get.
/fees.allthat lists all supported fee tokens and their rates. Available only on the ChildChain and WatcherInfo.
/stats.getendpoints for informational purposes. Available only on the WatcherInfo.
/transaction.allto return each transaction output’s creating_txhash and spending_txhash. Available only on the WatcherInfo.
/transaction.getto return transaction type (txtype) and transaction output type (otype). The currently possible types are Payment V1 and Fee Token Claim.
- Watcher and WatcherInfo no longer serve WebSocket events for new transactions and exits.
NOTE: This is handled by
/transaction.submit_typed, so it is unlikely to affect integrators.
The environment variables with prefixes RINKEBY_, ROPSTEN_, and MAINNET_ have been replaced with ETHEREUM_NETWORK and their non-prefixed names. To upgrade from previous versions, migrate the old configurations to the following new ones:
The following new environment variables can be configured to modify the behavior of your self-hosted Watcher and WatcherInfo.
from 3.0.0-alpha.6 to 3.0.0-0.4.1
- Library has been updated to work with the updated contracts and latest APIs from
- Introduced input validation so users are able to catch input errors earlier and avoid confusing stack traces
- Examples folder has been updated to show ithe mplementation of new functionality as well as more helper functions.
- See better balance and UTXO information.
- See ERC20 & ETH specific examples for deposits, transactions, exits, and process exits.
getFees- new function to retrieve supported fee tokens and amounts to make transactions.
createTransaction- arguments are retrieved as an object for better readability. Metadata can also be passed as a simple string instead of being encoded beforehand.
sendTransaction- arguments are retrieved as an object for better readability. It also accepts payments and fee object to provide consistency with other function calls in the library.
inFlightExitGetInputChallengeData- new function that gets the data to challenge an invalid input piggybacked on an in-flight exit.
inFlightExitGetOutputChallengeData- new function that gets the data to challenge an invalid output piggybacked on an in-flight exit.
In most functions, arguments are now passed as objects in this module for easier readability. Please check the API documentation for more details.
Constructor- arguments are retrieved as an object and passing the abi is no longer necessary.
- Vault contracts will be instantiated along with returning the contract address for you.
getExitTime- new function that will calculate the exit schedule required before an exit can be processed and released.
getExitQueue- new function that will retrieve the exit queue for a particular token.
getDepositExitData- new function that allows you to get the exit data for a deposit without using the Watcher.
deposit- simplified the API so users can call one function to deposit both ETH and ERC20.
getStandardExitId- new function that gets a standard exit id to use for processing standard exits.
getInFlightExitId- new function that gets the inflight exit id to use when processing an inflight exit.
getInFlightExitData- new function that retrieves in-flight exit data from an array of exit ids.
deleteNonPiggybackedInFlightExit- new function that deletes an in-flight exit if the first phase has passed and nobody has piggybacked the exit.
createTransactionBodyhas been improved and made smarter to help users form transaction bodies more easily.