fix: canonical NameUpdateTx RLP serialization seems to want NamePoint…

…ers in the reverse order than specified in the JSON.

aeternity/transactions.go

@@ -312,6 +312,16 @@ func (t *NameUpdateTx) RLP() (rlpRawMsg []byte, err error) {
 		return
 	}
 
+	// reverse the NamePointer order as compared to the JSON serialization, because the node seems to want it that way
+	i := 0
+	j := len(t.Pointers) - 1
+	reversedPointers := make([]*NamePointer, len(t.Pointers))
+	for i <= len(t.Pointers)-1 {
+		reversedPointers[i] = t.Pointers[j]
+		i++
+		j--
+	}
+
 	// create the transaction
 	rlpRawMsg, err = buildRLPMessage(
 		ObjectTagNameServiceUpdateTransaction,
@@ -320,7 +330,7 @@ func (t *NameUpdateTx) RLP() (rlpRawMsg []byte, err error) {
 		t.Nonce,
 		nID,
 		t.NameTTL,
-		t.Pointers,
+		reversedPointers,
 		t.ClientTTL,
 		t.Fee.Int,
 		t.TTL)

aeternity/transactions_test.go

@@ -261,6 +261,7 @@ func TestNameUpdateTx_RLP(t *testing.T) {
 			fmt.Println(txJSON)
 
 			gotTx, err := BaseEncodeTx(&tx)
+
 			if (err != nil) != tt.wantErr {
 				t.Errorf("NameUpdateTx.RLP() error = %v, wantErr %v", err, tt.wantErr)
 				return