ah yes, you will understand this pretty good, i have been working with that library heavily of late, and you can change the precomputed vectors size, the downside is that you are trading memory for computation, you probably want to parameterise it for battery vs storage balance
Discussion
Yeah... I figured something was up. I generally prefer larger static segments over runtime performance hits, it's just when compiled the binaries are nearly 2MB. So it balloons quickly. It also means embedded applications are limited.
well, if you got battery problems and storage problems at the same time, yeah, but that's elliptic curves for you
making small devices that use low power implicitly requires a bigger chunk of memory to store those precomps
i'm pretty sure that there is a fairly high size limit at which point the two cost the same in energy
in the early days, because of how shitty javascript is, #nostrudel didn't even verify event signatures, and probably this is still a thing with some of them...
this is why i find it comical that people consider nodejs a serious server dev language
it's slower and uses more memory than python!!!!
anyhow, so if your device has space, use it, otherwise, you have to try and avoid verifying signatures...
perhaps advise downstream devs to do signature verification only immediately prior to display, as very often mute lists will exclude them from display (and the comedy of that whole charade with web devs is another larf itself, especially for the snowflakes and angry drunk people being trolled)