chore(network): implementing no-op cross-chain app handlers (ava-labs…

…#304) * implementing cross-chain app handlers * nits Co-authored-by: Ceyhun Onur <[email protected]>
AshAvalanche · Oct 19, 2022 · 73bb000 · 73bb000
1 parent 91778ae
commit 73bb000
Showing 1 changed file with 15 additions and 0 deletions.
diff --git a/peer/network.go b/peer/network.go
@@ -260,6 +260,21 @@ func (n *network) AppRequestFailed(nodeID ids.NodeID, requestID uint32) error {
 	return handler.OnFailure(nodeID, requestID)
 }
 
+// CrossChainAppRequest is a no-op.
+func (n *network) CrossChainAppRequest(chainID ids.ID, requestID uint32, deadline time.Time, request []byte) error {
+	return nil
+}
+
+// CrossChainAppRequestFailed is a no-op.
+func (n *network) CrossChainAppRequestFailed(chainID ids.ID, requestID uint32) error {
+	return nil
+}
+
+// CrossChainAppResponse is a no-op.
+func (n *network) CrossChainAppResponse(chainID ids.ID, requestID uint32, response []byte) error {
+	return nil
+}
+
 // getRequestHandler fetches the handler for [requestID] and marks the request with [requestID] as having been fulfilled.
 // This is called by either [AppResponse] or [AppRequestFailed].
 // assumes that the write lock is held.