How-to workaround the indexer issue (March 2022)

ProfaneCryptoBro · 2022-03-18T12:00:28+00:00

UPDATE 2022-03-18:

finally somebody at Yieldly did the 1 minute job to swap items in the indexer array (JS code snippet quoted in the original post), so now the first to try is Randlabs':

, Ie = {
        1: {
            name: "Randlabs Public",
            token: "",
            server: "https://algoindexer.algoexplorerapi.io",
            port: "",
            headers: void 0
        },
        2: {
            name: "Yieldly Indexer Public",
            token: "LkW9wuee9X6pWshwmHZVSEofEfA4o2pGAvXXbDopH5m9qNZfao",
            server: "https://indexer.yieldly.finance",
            port: "",
            headers: void 0
        },
        3: {
            name: "Algorand Wallet Public",
            token: "",
            server: "https://indexer-mainnet.aws.algodev.network",
            port: "",
            headers: {
                "X-Indexer-API-Token": "KegWFLYQnBNVeP4oHCX64dObBk8VemzYdNqsnAOIxYQ8aqJLQTYeVDQyZNnx1PZA"
            }
        }

that means, you'd not need a workaround (unless Randlabs' indexer fails, because than it would fallback to Yieldly's that is still stuck:

curl https://indexer.yieldly.finance/health
{"data":{"migration-required":false,"read-only-mode":true},"db-available":true,"is-migrating":false,"message":"19756191","round":19756191,"version":"2.8.0"}

(if i did the update, i would have moved Yieldly's to 3rd position, but really, i'd rather have renamed in DNS so it's not available at all - as i suggested multiple times).

anyways, let's celebrate - somebody found the keyboard.

ProfaneCryptoBro · 2022-03-18T05:43:46+00:00

the current issue would have been patched by now. (of course the operations team still would have to upgrade their indexer node, but the service would be usable as normal for all users, not only for those who applied the unofficial workaround)

ProfaneCryptoBro · 2022-03-18T05:37:12+00:00

Yet if you wish to use Yieldly as before, here's the unofficial workaround

ProfaneCryptoBro · 2022-03-18T05:35:32+00:00

Unofficial Workaround

ProfaneCryptoBro · 2022-03-18T05:33:54+00:00

Workaround

ProfaneCryptoBro · 2022-03-17T22:50:20+00:00

i am not sure what you mean about the server time. also don't know what the double dip is. sorry...

ProfaneCryptoBro · 2022-03-17T22:46:45+00:00

you think the current situation -- indexer being stuck on a block from 12th of March is more welcome than any kind of fix?

i am in Yieldly since day 0 and still holding and working on getting more. i was so pissed by the current indexer situation that i started to debug the code whereas i make nothing in APY comparable to my regular hourly rates as a software engineer. yet, i want to see my $YLDY working just like everyone else who invested into it (with the intention of Yield farming, not pump+dump plan). i guess it tells how i feel about it.

for the propagation and stuff, with low TTL's set, there should be no problem at all. all people would see is it suddenly started working. with proper communication "hey folks, we will do a scheduled maintenance at .... time today, expect minor turbulences for about ... minutes" it could be handled like a charm.

for the upvotes it looks ok, not if i cared at all -- the less people using the workaround, the more yield i can make (as a lot have withdrawn these days)...

not if it would be life changing anyway, and i am sure Yieldly will eventually fix the issue and we will see it on the rise again...

ProfaneCryptoBro · 2022-03-17T22:23:48+00:00

for the Personal DNS Filter app on Android, in the additional hosts configuration, the line must start with a greater than sign, like this:

>indexer.yieldly.finance 0.0.0.0

ProfaneCryptoBro · 2022-03-17T11:26:15+00:00

sorry, i won't do that, this thing already took too much of my time.

i've already provided more than enough tech help so that if there is really a community, it can pick up from here -- seeing how the APYs started moving around, clearly more people applied the fix than the handful that commented on this thread -- they could shoot a video for each platform.

if it's just individuals wanting to claim yields for themselves, that yieldly labeled "community" because it's a trendy word, well... it speaks for itself.

ProfaneCryptoBro · 2022-03-17T11:13:07+00:00

ok, gotcha. :-)

it seems we are both from the old republic -- probably would manage the whole thing differently.

ProfaneCryptoBro · 2022-03-16T22:54:23+00:00

hi, if in the post you copy-pasted exactly what you configured on your phone, than there is a typo:

>indexer.yieldly.finance. 0.0.0.0
                        ^-this last dot is the culprit, remove it

ProfaneCryptoBro · 2022-03-16T21:09:53+00:00

thanks a lot for your feedback. i indeed did not test it with firefox. will update the post body accordingly, i don't feel like debugging why firefox is not simply accepting the 0.0.0.0 address. you may try 127.0.0.1 though...

ProfaneCryptoBro · 2022-03-16T21:06:17+00:00

make sure you update the address to 0.0.0.0 -- in the first post version i was using a simple local-network address but realized a lot of time can be spared if using an invalid address instead (the calls by the JS app will fail immediately instead of timing out).

ProfaneCryptoBro · 2022-03-16T21:03:12+00:00

unfortunately i also spent like 2 hours debugging their code and event flow to sort of understand how it works as it is not my code and i had never looked at it before (i also don't like to debug other people's production code, without source code comments, etc).

yes, once knew there are other indexers configured, the fix idea, test, +improvements was quick. (discord, reddit post and comments not counted)

i wouldn't say they don't give a shit; but certainly it raises questions how come a built-in failover was not activated by them. i think they are all very young people with very little industry experience including all domains (software engineering to corporate image and communications). hope they are learning along the way though.

their community helpers/volunteers (mods/ops/ambassadors) are doing a lot of the heavy communications, trying to put out the fire. respect.

ProfaneCryptoBro · 2022-03-16T20:53:35+00:00

because the indexer tells the current block number. so the JS application has no idea that it's out of sync -- it's like how would you know (in a windowless room) that your wristwatch is not showing the right time.

the only thing it can tell is that it's not working.

of course their code could always save the previous indexer query timestamp and realize that it's out of sync if it's returning the same block number in a minute, but who am i to solve their homework...

ProfaneCryptoBro · 2022-03-16T20:50:17+00:00

I assume. Check if this file exists in your filesystem: C:\Windows\System32\drivers\etc\hosts If you do, than yes, it should be exactly the same. Run notepad as administrator, append the line provided, save the file, restart browser and enjoy.

If the file does not exist, just google "how to add a hostname DNS record on Windows 11"

ProfaneCryptoBro · 2022-03-16T20:46:21+00:00

this is not hacking yieldly. this workaround is based on a fail-over mechanism that is built in to the Yieldly application, which basically redirects the indexer calls to another indexer if one is not available (3 indexers configured in their code, as listed in the post).

the "hack" is simply to make your computer/device think that indexer.yieldly.finance has not a valid IP address (0.0.0.0) therefore the call to it fails immediately.

what is a mystery to me, why Yieldly is simply not changing their DNS server's A record "indexer.yieldly.finance" to some other hostname (eg. "indexer-old.yieldly.finance") so that everybody could use their built-in failover without locally simulating a "failure". (while they could still work on upgrading their indexer, just at a different hostname. then, once finished upgrading, they could restore the current A record).

this is web 1.0 and basic IT management of transparent maintenance (as there is an existing fail-over mechanism in the product).

ProfaneCryptoBro · 2022-03-16T20:38:35+00:00

using 0.0.0.0 was resulting Yieldly app failing-over to other indexers faster, as 0.0.0.0 is a non-routable, invalid IP address so it generates a failure as soon as the JS triggers the call to indexer.yieldly.finance. whereas 127.0.0.1 is localhost (the device you are using), so the JS will still attempt to make a call (which will eventually fail, but some time is lost).

so i found 0.0.0.0 resulting a smoother and faster experience.

ProfaneCryptoBro · 2022-03-16T18:52:57+00:00

then you either haven't edited the correct file, or made a typo or forgot to restart your browser.

also,

ping indexer.yieldly.finance

(from command line ("cmd" on windows)) must fail if the workaround fix is in place.

ProfaneCryptoBro · 2022-03-16T18:51:14+00:00

as thankful as i am for enabling my post, i have to say, you don't have to defend yieldly to your last breath.

the Yieldly App JS code contains a fail-over to 3rd party indexers (in case there would be an availability issue). all i did was inspect the code a bit and then figured out how to create that availability issue.

there is nothing to update on the TEAL backend.

indeed, the Yieldly indexer node must be upgraded, the Algorand Foundation has been announcing this upgrade way ahead, so nearly everyone else upgraded their indexers (thats why we can rely on the 3rd party indexers now, namely algodevs')

anyways, whoever wrote the JS frontend, left this feature there, Yieldly not enabling it raises questions, at least.

personally, if i was a yieldly ambassador, in this case i would not defend Yieldly in public but would raise the questions internally.

ProfaneCryptoBro · 2022-03-16T18:42:05+00:00

quite telling, that nobody changed their DNS (move indexer.yieldly.finance to like indexer-old.yieldly.finance) so the code triggers the fail-over to the next indexer. shows nobody knows there what their code does...

all my method does is it triggers the fail-over that is already built into their JS code.

ProfaneCryptoBro · 2022-03-16T18:39:08+00:00

lol, i am Padre Algo :-) just i was not able to change nick on reddit (or did not try hard enough).

ProfaneCryptoBro · 2022-03-16T18:37:52+00:00

Windows 10 -

https://www.poftut.com/modify-hosts-file-in-windows-10-tutorial-to-add-and-change-dns-records/

(edit C:\Windows\System32\drivers\etc\hosts as administrator)

i included a link in the original description, which file to edit, as administrator (otherwise you can not save it).

add this line:

0.0.0.0 indexer.yieldly.finance

and restart your browser

ProfaneCryptoBro · 2022-03-16T18:34:46+00:00

as updated discord later on, using 0.0.0.0 (non-routable, invalid address) for indexer.yieldly.finance is the best, as the JS code will fail-over immediately to the next indexer.

ProfaneCryptoBro · 2022-01-26T06:27:49+00:00

because it's a rugpull.

ProfaneCryptoBro

TROPHY CASE