-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tessera "storeraw" endpoint is not available --> can't perform private transactions #114
Comments
Can you please try setting up a development network using the following command ./setup.sh dev --project Test --nodecount 2 --tessera and then try performing private transactions by deploying private contract of quorum's 7 node example. Don't forget to replace the public key in privateFor field in private-contract.js file using your public key before deploying it. |
The issue seems to be caused by the a wrong generation of "tessera-config.json" which leads to some Tessera APIs being disabled. I replaced "tessera-config.json" by the following and it worked: { |
hi,masarwib, i use your method ,it doesn't work. wether something left? |
Hi guys,
I'm using QuorumMaker to run a Quorum network with two nodes and Tessera. The command i used: "./setup.sh dev --tessera --project --nodecount 2"
Also, i'm using web3j's contract wrappers to perform a very simple private transaction, but it keeps failing with a "404 not found" response whenever QuorumTransactionManager attempts calling Tessera's "storeraw" endpoint.
However, when i use a different approach: "Quorum.ethSendTransaction( privateTransaction)" it does work. But this approach is very verbose and requires nonce management.
I think the second approach works because it doesn't go through Tessera's "storeraw" endpoint.
Somehow QuorumMaker runs Tessera with "storeraw" endpoint disabled, in comparison, Quorum's 7nodes example does have this endpoint available in Tessera, thus private transactions are available through TransactionManager.
How can i make QuorumMaker run Tessera with above endpoint enabled?
The text was updated successfully, but these errors were encountered: