04:58:05 <m-relay> <g​ingeropolous: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
07:57:13 <DataHoarder> mining blob would tell you what they are mining and other minces and maybe the template for coinbase/txs match
07:57:28 <DataHoarder> These just give all data directly
07:57:41 <DataHoarder> Even if rate limited you can fetch the data later
14:08:50 <m-relay> <r​ucknium:monero.social> DataHoarder: It looks like `monero-blocks` misses the most recent 1-2 blocks mined by nanopool. Any ideas on how to fix?
16:01:13 <DataHoarder> They are probably not updating the api quick enough?
16:01:18 <DataHoarder> Do they eventually appear?
16:01:36 <DataHoarder> They might wait 60 blocks before showing them to users as payouts?
16:01:47 <DataHoarder> Or orphan checks
16:01:52 <DataHoarder> I can look at it later better
16:06:38 <m-relay> <r​ucknium:monero.social> They seem to appear here, but the API request doesn't get them: https://xmr.nanopool.org/
16:07:22 <m-relay> <r​ucknium:monero.social> Yes, they seem to eventually appear.
16:08:49 <m-relay> <r​ucknium:monero.social> They are here, too: https://xmr.nanopool.org/api/v1/pool/blocks/0/500
17:36:07 <m-relay> <r​ucknium:monero.social> DataHoarder: There may be a similar issue with xmrpool.eu
18:50:12 <DataHoarder> I'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 
18:50:28 <DataHoarder> Unless I added code to explicitly exclude most recent due to orphaning issues
18:53:51 <m-relay> <r​ucknium:monero.social> Thanks for looking into it.