For the dsq message, there is one field that is missing that would make this message useful and verifiable to an SPV client that obtains masternode lists from getqrinfo or getmnlistd.
The missing field is proTxHash for the masternode -- while this message does contain masternodeOutPoint to identify a masternode, SPV clients (via mnlistdiff and qrinfo) do not have access to the masternode outpoints for each masternode.
SPV clients could get around this by having a static list that correlates proTxHash to masternodeOutPoint, but over time this list would get out of date. Or the SPV client could check the dsq signature against masternodes, but this may prove to take too long.
Describe the issue
For the dsq message, there is one field that is missing that would make this message useful and verifiable to an SPV client that obtains masternode lists from
getqrinfo
orgetmnlistd
.The missing field is
proTxHash
for the masternode -- while this message does containmasternodeOutPoint
to identify a masternode, SPV clients (viamnlistdiff
andqrinfo
) do not have access to the masternode outpoints for each masternode.SPV clients could get around this by having a static list that correlates
proTxHash
tomasternodeOutPoint
, but over time this list would get out of date. Or the SPV client could check the dsq signature against masternodes, but this may prove to take too long.