Post
Topic
Board Announcements (Altcoins)
Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released
by
Hotmetal
on 11/09/2014, 18:07:55 UTC

We could have a site that queries all in the list for your address on the api port.

Edit: I've set up a SRV record as an example. _bb._tcp.us.cncoin.farm that has all the pools listed on the first page that have dns names for connecting. That is one issue with this approach. All pools would have to have a name and not an IP for a SRV record to work. You can see what it returns with
Code:
dig SRV _bb._tcp.us.cncoin.farm

in linux, or
Code:
nslookup -type=all _bb._tcp.us.cncoin.farm
in windows.
example output:
Code:
;; ANSWER SECTION:
_bb._tcp.us.cncoin.farm. 7199   IN      SRV     10 0 11007 bbr.poolto.be.
_bb._tcp.us.cncoin.farm. 7199   IN      SRV     0 0 7777 bbr.cncoin.farm.
_bb._tcp.us.cncoin.farm. 7199   IN      SRV     0 0 1111 mine.bbr.unipool.pro.
_bb._tcp.us.cncoin.farm. 7199   IN      SRV     0 0 7777 boolberry.extremepool.org.

Notice it gives a port. It has a priority that I have set the non-us pool to a higher number to give it less priority. Could do the opposite with a _bb._tcp.non-us or _bb._tcp.eu or whatever, even separate lists for cpu/gpu ports. Obviously, it should be managed by core boolberry team or at least not a pool operator, and then miner would have to use something like libsrv (first google hit I saw) to query this record. We could even have a complimentary SRV record to determine API port of these servers I guess. What do you think?

Reference I used for SRV records here: http://www.zytrax.com/books/dns/ch8/srv.html

Quite an elegant solution actually. No other coin offers this type of integration either. Allowing a core boolberry team member to operate it means complaints about scams, faulty pooling payouts etc can easily be addressed and failure to fix a problem or comply will mean the majority of every day people will not be served automagically from the boolberry master pool.