-
m-relay<gingeropolous:monero.social> i saw above that you might get rate limited. could you just act a miner and get a mining blob.. that maybe has the info you need? i dunno what comes over
-
DataHoardermining blob would tell you what they are mining and other minces and maybe the template for coinbase/txs match
-
DataHoarderThese just give all data directly
-
DataHoarderEven if rate limited you can fetch the data later
-
m-relay<rucknium:monero.social> DataHoarder: It looks like `monero-blocks` misses the most recent 1-2 blocks mined by nanopool. Any ideas on how to fix?
-
DataHoarderThey are probably not updating the api quick enough?
-
DataHoarderDo they eventually appear?
-
DataHoarderThey might wait 60 blocks before showing them to users as payouts?
-
DataHoarderOr orphan checks
-
DataHoarderI can look at it later better
-
m-relay<rucknium:monero.social> They seem to appear here, but the API request doesn't get them: xmr.nanopool.org
-
m-relay<rucknium:monero.social> Yes, they seem to eventually appear.
-
m-relay<rucknium:monero.social> They are here, too: xmr.nanopool.org/api/v1/pool/blocks/0/500
-
m-relay<rucknium:monero.social> DataHoarder: There may be a similar issue with xmrpool.eu
-
DataHoarderI'll see. If they aren't on the api not much I can do, but if they are there and not caught in my code that would not be good
-
DataHoarderUnless I added code to explicitly exclude most recent due to orphaning issues
-
m-relay<rucknium:monero.social> Thanks for looking into it.