Private Signed Transaction fails with latest Tessera config
See original GitHub issueWe have deployed a private contract using quorum.js using the latest tessera configuration as mentioned below https://github.com/jpmorganchase/tessera/wiki/Tessera-v0.9-sample-settings
We have signed and submitted the transaction using quorum.js as described by the documentation. The transaction in question goes through without any problem as we can see from the nonce being increased. But for some reason we aren´t able to get values when we call a constant/view method of this particular contract
{
"useWhiteList": false,
"jdbc": {
"username": "sa",
"password": "",
"url": "jdbc:h2:.//priv/db;MODE=Oracle;TRACE_LEVEL_SYSTEM_OUT=0",
"autoCreateTables": true
},
"serverConfigs": [{
"app": "P2P",
"enabled": true,
"serverSocket": {
"type": "INET",
"port": 10000,
"hostName": "http://172.19.240.100"
},
"sslConfig": {
"tls": "OFF",
"generateKeyStoreIfNotExisted": true,
"serverKeyStore": "/priv/server0-keystore",
"serverKeyStorePassword": "quorum",
"serverTrustStore": "/priv/server-truststore",
"serverTrustStorePassword": "quorum",
"serverTrustMode": "TOFU",
"knownClientsFile": "/priv/knownClients",
"clientKeyStore": "/priv/client0-keystore",
"clientKeyStorePassword": "quorum",
"clientTrustStore": "/priv/client-truststore",
"clientTrustStorePassword": "quorum",
"clientTrustMode": "TOFU",
"knownServersFile": "/priv/knownServers"
},
"communicationType": "REST"
}, {
"app": "Q2T",
"enabled": true,
"serverSocket": {
"type": "UNIX",
"path": "/priv/tm.ipc"
},
"communicationType": "UNIX_SOCKET"
}],
"peer": [{
"url": "http://172.19.240.101:10001/"
}, {
"url": "http://172.19.240.102:10002/"
}, {
"url": "http://172.19.240.103:10003/"
}, {
"url": "http://172.19.240.104:10004/"
}],
"keys": {
"passwords": [],
"keyData": [{
"privateKeyPath": "/priv/tm.key",
"publicKeyPath": "/priv/tm.pub"
}]
},
"alwaysSendTo": [],
"unixSocketFile": "/priv/tm.ipc"
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Private Signed Transaction fails with latest Tessera config #658
We have deployed a private contract using quorum.js using the latest tessera configuration as mentioned below
Read more >Error in doing private transactions for nodes on different VMs ...
The error signifies that Tessera to Quorum link isn't running. Can you share more details on your setup? Whats in the tessera log?...
Read more >Tessera SSL Configuration for P2P Communication
This blog walks through the steps for using self-signed certificate or third-party Certificate Authority (CA) certificates for configuring ...
Read more >Unable to send transactions with quorum nodes using tessera
I am unable send transactions between 2 quorum nodes on different machines using tessera privacy manager and raft consensus.
Read more >Send private transactions - GoQuorum - 22.7.0 - ConsenSys
In the geth console, run loadScript to deploy the contract and send a private transaction from node 0 to node 1.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, let me take another look then.
Hope this has helped. Please re-open or create another issue if there is still a problem.