Added steps to send and receive a payload in getting started #34
Conversation
Signed-off-by: Madeline <[email protected]>
Signed-off-by: Madeline <[email protected]>
|
Quorum talks to Tessera via IPC, so I wouldn't change ipc connection on Q2T server to http port |
NicolasMassart
added
the
documentation
|
|
@Krish1979 - will do. Is there a specific reason for supporting http on the Q2T server if it's not used? Would adding a note indicating that http is being used only for learning/education purposes and IPC is needed when you're using Tessera with Quorum address this? |
|
Q2T connection is http over IPC and not over web port as default but we could include support over http port as well. Also to keep it generic we will be connecting Besu to Tesser over Q2T server on a http port. I would wait till we add Besu <-> Tessera operability and then update the document to reflect all the updates. |
| } | ||
| ``` | ||
|
|
||
| Where `SGVsbG8sIFdvcmxkIQ==` is `Hello, World!` in Base64. |
There was a problem hiding this comment.
| Where `SGVsbG8sIFdvcmxkIQ==` is `Hello, World!` in Base64. | |
| Where `SGVsbG8sIFdvcmxkIQ==` is `Hello, World!` in Base64. |
Should be part of the result tab, so need to add spaces to increment it.
| === "Result" | ||
|
|
||
| ```bash | ||
| {"key": "5jZPbwuxncr7qrL9esCTnz3PByLlD50kdZy5JkW/JMKcFeTl7I3NeLIsje4C410EYb93HabhddoAVGpwgYF1LQ=="} |
There was a problem hiding this comment.
can you explain what this key is? Public, private? What care do we have to take with this?
|
Converted this PR to draft as it probably requires work to be up to date since Nov 2020... |
Added steps to send and receive a payload in getting started