Hello, we have added kano.is pool support in the MinerBox monitoring app based on our users request but seems our US processing server IP is blocked by pool and we have complains that users facing accounts monitoring issues, so we need some support from tech staff for resolving issue. We PM the details regarding API calls and IP address to "kano (OP)" please check, if it's disrupting pool server please let us know and we will delist pool support from app and inform users, thanks.
It was permanently blocked a few months back for accessing the API with many random garbage usernames,
and usernames with hex codes in them.
The two usernames that were valid before the flurry of invalid usernames,
were accessing the API way more often than the limit and way more often than what you said in PM,
so I take it you have no control over that access rate so you should set it like other apps:
access the pool from the app, not pass their information to your servers,
that way when the user exceeds the rate, only that user is blocked.
if say the truth it's technically impossible, the address field which users inserting is limited with size and type of symbols, so before reaching your mentioned hex codes to your server it should be a problem for our servers, that's why we assume that it's impossible. We are taking care to avoid such kind of cases. We are working and partnering with many pools and never get any complains and in case of any type of issue we are localizing it sharply to keep clean the infrastructure.
before adding the account we are checking the api key, after getting ok for that checking (reply from pool server) the address is appears for user and we are polling info for that user once every 5min, the timeframe is fixed and even more that frequency api calls is only for users who enabling notifications service for rest one the data is requested when they are opening account and in that case also request to pool can't be done more frequent as once per 5 min. Exception is "Pool info" data for which we are calling api every 2 min.
we are suggesting to our users device independent monitoring and notification service, and it's based on their account so no care from which device they are loging to their account all their pool sets and configurations are available, that's why we are using our servers for originating account calls
Summarizing all worries and making both our users happy we can suggest the steps to mitigate issues.
1. in PM we provide the api call which we are using to check if user is existing one and we can add that account for monitoring (please check and give details if any update needed)
2. if account is abandoned and we are receiving error from pool we are stopping to call it (some details regarding pool info in PM)
3. if you have some special api call for checking user and adding restriction please provide it and we will handle accordingly.
4. if you have some api calls limitations which you can't configure for our service then let us know we will see how we can fix it.