witnet / web3-jsonrpc-gateway Goto Github PK

• Publish on NPM as well
• Polish Readme

As to avoid eventual incompatibilities w/ eth_getFilterChanges

Any of provided keys could eventually be used for signing transactions.

Currently, we are trying to use Node 14, 16 and 18 and the pipelines broke during the installation phase. We have to upgrade the CI pipelines to use Node 20.

This service should be easily dockerizable for quick, zero-dependencies deployment.

Here's an example of a similar dockerized NodeJS service inside the Witnet project:
https://github.com/stampery-labs/aragon-govern-discord-integration/tree/main/docker

The main difference would be the lack of need for this line:
https://github.com/stampery-labs/aragon-govern-discord-integration/blob/3dc150c8cfb1de29328ab076ee429055c01e2229/docker/Dockerfile#L25

And a rewrite of this other line:
https://github.com/stampery-labs/aragon-govern-discord-integration/blob/3dc150c8cfb1de29328ab076ee429055c01e2229/docker/Dockerfile#L31

• Build gateway
• Deploy to NPM
• Deploy to Dockerhub

• Fine tune infinite scroll component
• Implement UI for minting process

Provider URL: https://rinkeby.omgx.network

Test and upgrade Celo stacks.

• By using new config parameter CONFLUX_CONFIRMATION_EPOCHS
• Considering top of ledger as the epoch number return by the epoch tag set on CONFLUX_DEFAULT_EPOCH_TAG.

After adding new logic in centralized bridge implementation, support of eth_syncing method is now compulsory. Besides, VM execution error should be captured and sent back to client.

• Gas price max threshold should be read from configuration parameter (e.g. ETHERS_GAS_PRICE), instead of using client-provided gasPrice value.
• If gateway is set up to estimate gas price, this may lead to bridges unable to report back results if network's gas price raises with respect the gas price that was estimated when the request was posted.
• Gas limit max threshold should also be read from configuration parameter (e.g. ETHERS_GAS_LIMIT), instead of using client-provided gasLimit value.

This middleware can currently handle:

• getAccounts
• processEthSignMessage
• processTransaction

Missing methods:

• processDecryptMessage
• processEncryptionPublicKey
• processPersonalMessage
• processTypedMessage
• processTypedMessageV3
• processTypedMessageV4

We may not need every of them, but we can try to cover as many as possible for the sake of completion, just in case someone else uses this at some point.

Test and upgrade related testnet stacks.

When specifying a network that's not currently supported.