Avatar
dolu
59b96df8d8b5e66b3b95a3e1ba159750a6edd69bcbba1857aeb652a5b208bd59

GM

This morning, I have an idea for Nostr Proxy.

Is it required for the proxy to validate schnorr signatures for each events?

Because stored events in relays are already validated and client validate events too when getting them.

So... is it required for the proxy to validate them?

Schnorr signature validation is really CPU intensive. It validates ~5000 events/min when opening 7 global feeds.

Ok, RAM is under 100Mo constantly with ~10 users.

CPU is still under attack. I don't know what to search

nproxy.zerologin.co => lunanode vps

nproxy.cc => railway

But it's not a server problem, I have something that eat my CPU. I've not fixed this problem...

Can you please try wss://nproxy.cc instead of wss://nproxy.zerologin.co

Not definitive, but it's deployed elsewhere

Deploying the new relay pool now!

Not now! OMG What have I done

Ok, time to deploy the new relaypool to https://nproxy.zerologin.co

Stress test incoming!

Test publishing with the new relay pool

Replying to Avatar dolu

NO WAY!

91 clients connected to https://nproxy.zerologin.co ?!

Are you guys crazy?

I have to deploy the next test version elsewhere to not shutdown all of you

100+

I can't believe it's true. It's a bug for sure.

NO WAY!

91 clients connected to https://nproxy.zerologin.co ?!

Are you guys crazy?

I have to deploy the next test version elsewhere to not shutdown all of you

#[0] when I make a REQ on your relay with a limit, this limit is not considered

ex: ["REQ","global",{"kinds":[1],"limit":20}]

It just send me events without limit

I don't know what's your relay implementation, but it's probably an issue with it

I liked hamstr.to, but snort is really great too.

Too bad I can't see publications and conversations responses in the same page

Yes, thanks!

I'm focused on the performance issue, it's more important for now 😵

Time to create a custom relays pool for Nostr proxy!

GM nostère