Bloxberg Network #10
Comments
|
docker-compose.yml from 1node-clique My ethereum.json I am not sure if the RPC address in docker-compose should point to this but the one in ethereum gives the below error. My Error: |
|
So you get 504 error. I would expect this address to be the correct one. You tried it multiple times? URL is correct and works, I just tried with curl: ➜ ~ curl --location --request POST 'https://core.bloxberg.org/' \
--header 'Content-Type: application/json' \
--data-raw '{
"jsonrpc":"2.0",
"method":"web3_clientVersion",
"params":[],
"id":1
}'
{"jsonrpc":"2.0","result":"Parity-Ethereum//v2.6.6-beta-5162bc2-20191205/x86_64-linux-gnu/rustc1.39.0","id":1}I think the 504 can also potentially happen if you don't provide enough gas for the contract deployment. Maybe even @girzzly has an idea? |
|
Gas Price is set to 20000. Maybe @girzzly can share his .json rpc used for connecting ^^ |
|
Maybe the problem is, that caliper is not connected to a real wallet or web3j provider. |
|
Caliper uses web3j in its implementation. After looking into the docs, I wonder if it makes sense to specifcy the bloxberg url there. I think what we need to do is specify the url of a node, for which we have the private key and password, so that this node acts as our agent. I'm referring to this part from the docs about the benchmark address:
So this means, we indeed need to have e.g. a Geth or Parity node running somewhere, which is connected to bloxberg and then we have to specify the URL of this node. I made a rough sketch about the involved parts:
|
|
Putting this here now. But will move to ReadME:
Some flags of Geth. It would be interesting to see and compile new bc.dat if needed. |
|
So the current status of this: Geth is running locally connected to Bloxberg Network but peer connections are missing. When running simple scenario test, it fails at Invalid JSON RPC Response. Initially it complained Gas Price was too high so I fixed this by editing the One possible reason could be:
|
|
So after 2 peers and block sync I get this error when running benchmarks. I await complete sync. |
|
Which gas limit did you configure? The error is clear in this regard: web3 allows configuring the gas limit when sending transactions, is there a config in Caliper for this? |
|
There are some ways to configure gas related properties for deploying contracts from Caliper: The module.exports.init = function(blockchain, context, args) {
if(!args.hasOwnProperty('money')) {
return Promise.reject(new Error('simple.open - \'money\' is missed in the arguments'));
}
if(!args.hasOwnProperty('txnPerBatch')) {
args.txnPerBatch = 1;
}
initMoney = args.money;
txnPerBatch = args.txnPerBatch;
bc = blockchain;
contx = context;
return Promise.resolve();
}; |
|
So,
Overall change which affects this project:
Some possible PR: So here they have to change the rpc to http to be compliant to something that will be outdated in the near future even though they are not going to remove them completely. They seem to be using websocket now but hasn't been provisioned in the locally running geth nor is it exposing the WS port. Which is 8546 (default) nor has it been specified to make WS 8545 |
So the try would be to point the test scenario to Bloxberg Network.
The text was updated successfully, but these errors were encountered: