lnd.xprv/lnwire/single_funding_response_test.go
Olaoluwa Osuntokun 6c7880ef76
lnwire: channels are now identified by outpoint
This commit modifies most of the wire messages to uniquely identify any
*active* channels by their funding output. This allows the wire
protocol to support funding transactions which open several channels in
parallel.

Any pending channels created by partial completion of the funding
workflow are to be identified by a uint64 initialized by both sides as
follows: the initiator of the connection starts from 0, while the
listening node starts from (1 << 63). These pending channel identifiers
are expected to be monotonically increasing with each new funding
workflow between two nodes. This identifier is volatile w.r.t to each
connection initiation.
2016-06-21 13:13:07 -07:00

34 lines
864 B
Go

package lnwire
import (
"bytes"
"reflect"
"testing"
)
func TestSingleFundingResponseWire(t *testing.T) {
// First create a new SFR message.
var rev [20]byte
cdp := pubKey
delivery := PkScript(bytes.Repeat([]byte{0x02}, 25))
sfr := NewSingleFundingResponse(22, rev, cdp, cdp, 5, delivery)
// Next encode the SFR message into an empty bytes buffer.
var b bytes.Buffer
if err := sfr.Encode(&b, 0); err != nil {
t.Fatalf("unable to encode SingleFundingSignComplete: %v", err)
}
// Deserialize the encoded SFR message into a new empty struct.
sfr2 := &SingleFundingResponse{}
if err := sfr2.Decode(&b, 0); err != nil {
t.Fatalf("unable to decode SingleFundingResponse: %v", err)
}
// Assert equality of the two instances.
if !reflect.DeepEqual(sfr, sfr2) {
t.Fatalf("encode/decode error messages don't match %#v vs %#v",
sfr, sfr2)
}
}