| submitted by /u/CBDoctor
I have my Core 0.13.1 node configured to connect to 16 nodes, and invariably I see it connected only to other 0.13.1 nodes, even though, according to bitnodes leaderboard, these nodes form a minority.
Why is the selection logic this restrictive?
I am also noticing my 0.13.1 node that accepts incoming connecting as relatively overloaded I/O-wise since it upgraded.
I can understand this selection logic being necessary once SegWit activates, but why already, given we don’t know yet whether SegWit will activate?
I want to see Unspent transactions thus I use: http://api.blockcypher.com/v1/btc/main/addrs/xxxxxxxxxxxxxx?unspentOnly=true
I want to use a Token, thus I use http://api.blockcypher.com/v1/btc/main/addrs/xxxxxxxxxxxxxx/token=yyyyyyyyyyyyy
But when I try to use both, http://api.blockcypher.com/v1/btc/main/addrs/xxxxxxxxxxxxxx/token=yyyyyyyyyyyyy?unspentOnly=true
then I get an error that API call limits have been reached even though it is my first call for the day or hour , and if i remove the token then it works again.
How do I pass both the token and additional parameter (unspentOnly=true)
Is there a diagram like this available? I think it would be really interesting to see patterns across its lifetime