-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPC: Remove anchor_txid
from AnchorInfo
#663
RPC: Remove anchor_txid
from AnchorInfo
#663
Conversation
itest/assertions.go
Outdated
@@ -69,9 +70,12 @@ func AssetAnchorCheck(txid, blockHash chainhash.Hash) AssetCheck { | |||
return fmt.Errorf("asset is missing chain anchor field") | |||
} | |||
|
|||
if a.ChainAnchor.AnchorTxid != txid.String() { | |||
anchorTxid := | |||
strings.Split(a.ChainAnchor.AnchorOutpoint, ":")[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the txid info was duplicate I now retrieve it by splitting the outpoint string
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should use wire.NewOutPointFromString
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call, is the hash reversed in the raw outpoint string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the outpoint string consists of the txid
and the vout
index. The txid
in the outpoint string is a hex encoding of the byte reversed hash.
There was a flake on a batch mint assets test, kicked it and passed, just flagging |
itest/assertions.go
Outdated
@@ -69,9 +70,12 @@ func AssetAnchorCheck(txid, blockHash chainhash.Hash) AssetCheck { | |||
return fmt.Errorf("asset is missing chain anchor field") | |||
} | |||
|
|||
if a.ChainAnchor.AnchorTxid != txid.String() { | |||
anchorTxid := | |||
strings.Split(a.ChainAnchor.AnchorOutpoint, ":")[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should use wire.NewOutPointFromString
here.
b45fa51
to
8f7b0c1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Just two or so nits.
I'm a fan of this change because it reduces our test surface.
8f7b0c1
to
da6dcea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! 💯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏽
Closes #654