STX Watch - Log #2 - 2025/04/13

• locked liquidity

• adding cant-be-evil to locked liquidity

Today I started exploring on how to identify locked liquidity. This is in my opinion one of the most important metrics that people completely ignore.

For example if a token has $20k in liquidity, but $19k of that liquidity is locked, its a much better entry point than a token which has 100k in liquidity but 0% of it locked - because it can simply disappear during a ‘bank run’.

So since tokens which have locked liquidity are to some extent safer, I really want to showcase them on STX Watch.

So far only Velar seems to have a proper token burn / locked liquidity, it would be great if ALEX and Bitflow started providing the same option.

The team at Velar gave me an api endpoint that their app is using which was of no good use cause I got 405 errors when fetching the data via my server. I wasted 3 hours to circumvent that, but had to finally gave up. Like seriously, why can’t people just do a proper API endpoint. I could probably write a whole post about that, the ALEX API is even worse and Hiro API is as reliable as an Indian car.

Anyway, I have to manually fetch that data every day for now. I also decided to add tokens which are ‘burned’ at cant-be-evil.stx to the mix. The results are really interesting - some tokens have 50% or even more of their marketcap locked up.

After that was done I integrated that new metric with pour point system. I don’t want new tokens to game it, which is easy when MC is low, so the max points we will distribute is 3.

The calculation is:

If locked liquidity < 5% of MC - 0 points / red
If locked liquidity > 5% of MC - 1 point / orange
If locked liquidity > 10% of MC - 2 points / yellow
If locked liquidity > 20% of MC - 3 points / green

Here an example with $MEME:

And an example with $WELSH, which surprisingly has no significant liquidity locked up

That was my Saturday. I also fixed some other smaller backend stuff.