You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, through the API, we can get a bunch of info about multiple MNs using a single URL based on pubkeys, for instance: https://www.dashninja.pl/api/masternodes?testnet=0&portcheck=1&pubkeys=[PUBKEY1,PUBKEY2,PUBKEY3,…,…,…]
But now the whole Dash network is DIP3 compliant. It would be very useful to get the same multiple MNs info based on protxhash, using an URL that would look like this: https://www.dashninja.pl/api/masternodes?testnet=0&portcheck=1&protxhash=[HASH1,HASH2,HASH3,…,…,…]
The problem with the current pubkey URL is that multiple DIP3 masternodes may share the same payout address (i.e. pubkey). So they won't be retrieved by the current API.
The text was updated successfully, but these errors were encountered:
Currently, through the API, we can get a bunch of info about multiple MNs using a single URL based on pubkeys, for instance:
https://www.dashninja.pl/api/masternodes?testnet=0&portcheck=1&pubkeys=[PUBKEY1,PUBKEY2,PUBKEY3,…,…,…]
But now the whole Dash network is DIP3 compliant. It would be very useful to get the same multiple MNs info based on protxhash, using an URL that would look like this:
https://www.dashninja.pl/api/masternodes?testnet=0&portcheck=1&protxhash=[HASH1,HASH2,HASH3,…,…,…]
The problem with the current pubkey URL is that multiple DIP3 masternodes may share the same payout address (i.e. pubkey). So they won't be retrieved by the current API.
The text was updated successfully, but these errors were encountered: