You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We need to complete the translation layer between Bitcoin messages and zebra_network::{Request, Response} pairs.
Describe the solution you'd like
Each Message variant should generate a zebra_network::Request, or be explicitly ignored. Each zebra_network::Response variant should generate a Message, or in the case of Response::Nil, generate no message. (Done in Message/Request translation #1075)
teor2345
changed the title
Fill in zebra-network::{Request, Response} protocol and test translation.
Test translation for zebra-network::{Request, Response} protocol
Dec 14, 2020
Is your feature request related to a problem? Please describe.
We need to complete the translation layer between Bitcoin messages and
zebra_network::{Request, Response}
pairs.Describe the solution you'd like
Each
Message
variant should generate azebra_network::Request
, or be explicitly ignored. Eachzebra_network::Response
variant should generate aMessage
, or in the case ofResponse::Nil
, generate no message. (Done in Message/Request translation #1075)Refactor the Zebra requests and response state into distinct request/response pairs (Refactor zebra-network Bitcoin to Zebra protocol translation layer #1515)
The translation should be tested by connecting two connection state machines and seeing that they translate back and forth correctly.
The translation should be tested against
zcashd
, as much as possibleSome of this work was implemented a long time ago, and some of it was implemented in #1016. The rest is to be completed.
Prerequisite for actually handling the requests in #889.
The text was updated successfully, but these errors were encountered: