Transactions stuck in queue on rpcnode about quorum-dev-quickstart

[joshuafernandes]

Hello @wildsheepz
Thanks for submitting this, could you please give us the following so we can look into this further?

• the version that you are running
• steps to reproduce this issue
• do you see blocks being created ie the chain head progressing?

Cheers

[wildsheepz]

I checked out master so its #206.
All I did was npm start, then browse to http://127.0.0.1:26000, connected metamask and tried to deploy a contract.

Anyway, I may have found the problem. The private key for rpcnode in "network/smart_contracts/permissioning/scripts/keys.js" is wrong.

    validator4: {
      name: "validator1",
      url: "http://127.0.0.1:21004",
      nodekey: "8f6ae009cdbbf6e6fa739b91a4483f251bbe89f6570d34856554533b36c93c55",
      accountAddress: "0xf48de4a0c2939e62891f3c6aca68982975477e45",
      accountPrivateKey: "0x7f012b2a11fc651c9a73ac13f0a298d89186c23c2c9a0e83206ad6e274ba3fc7"
    },        
    rpcnode: {
      name: "rpcnode",
      url: "http://127.0.0.1:8545",
      wsUrl: "ws://127.0.0.1:8546",
      nodekey: "0e93a540518eeb673d94fb496b746008ab56605463cb9212493997f5755124d1",
      accountAddress: "0xc9c913c8c3c1cd416d80a0abf475db2062f161f6",
      accountPrivateKey: "0x7f012b2a11fc651c9a73ac13f0a298d89186c23c2c9a0e83206ad6e274ba3fc7" <--- its the same as validator4
    },       

After correcting it and starting again, the txns are going through now.

[joshuafernandes]

Gotcha, thanks for that @wildsheepz we'll fix that key