GETH Expert with Knowledge about Web3.js and Geth Subscriptions
Budget: $30 – $250 USD
Hello ,
I need someone with experience in Geth and Web3.js to change my Geth so that it uses 2 different endpoints for receiving txpool updates and for sending transactions .
I am using a gateway in the server where Geth client is deployed, and this gateway (which acts as a peer) can provide a stream of txpool .
There is another separate websocket which should be used for sending the transactions .
To clarify the task :
1. There is a ws client that needs to be added to geth node, this ws client has direct ws connection with gateway (the code for ws client is already in documentation provided) .
[receiving tx] this ws client subscribes to newTxs stream from gateway, when it receives tx from gateway, it should push it to geth tx pool, or merge newTxs stream into newPendingTransactions stream. Then we can simply subscribe to the newPendingTransactions like before
2. [sending tx] every time when you call eth_sendRawTransaction, the tx needs to be forwarded to ws client, which then sends this tx to gateway's blxr_tx endpoint. Then we can simply use eth_sendRawTransaction like before .
Max budget is $250 for what should be a rather simple task for someone experienced in geth / web3.js subscriptions .
You just need to create the web3.js subscriptions code and provide the necessary configuration (for example, geth flags to run the scripts with these subscriptions, any configuration changes, etc ) .
You are expected to deliver a small document with the necessary steps of configuring geth to use both endpoints, according to description .
If you read description and can complete the task, please msg me, otherwise your bid will be disregarded .
Thank you
I need someone with experience in Geth and Web3.js to change my Geth so that it uses 2 different endpoints for receiving txpool updates and for sending transactions .
I am using a gateway in the server where Geth client is deployed, and this gateway (which acts as a peer) can provide a stream of txpool .
There is another separate websocket which should be used for sending the transactions .
To clarify the task :
1. There is a ws client that needs to be added to geth node, this ws client has direct ws connection with gateway (the code for ws client is already in documentation provided) .
[receiving tx] this ws client subscribes to newTxs stream from gateway, when it receives tx from gateway, it should push it to geth tx pool, or merge newTxs stream into newPendingTransactions stream. Then we can simply subscribe to the newPendingTransactions like before
2. [sending tx] every time when you call eth_sendRawTransaction, the tx needs to be forwarded to ws client, which then sends this tx to gateway's blxr_tx endpoint. Then we can simply use eth_sendRawTransaction like before .
Max budget is $250 for what should be a rather simple task for someone experienced in geth / web3.js subscriptions .
You just need to create the web3.js subscriptions code and provide the necessary configuration (for example, geth flags to run the scripts with these subscriptions, any configuration changes, etc ) .
You are expected to deliver a small document with the necessary steps of configuring geth to use both endpoints, according to description .
If you read description and can complete the task, please msg me, otherwise your bid will be disregarded .
Thank you