Damus
Open in Damus
EVAN KALOUDIS profile picture
EVAN KALOUDIS
@nostrich

Eleutheromaniacal key puncher. Founder, ZEUS

npub19kv88vjm7tw6v9qksn2y6h4hdt6e79nh3zjcud36k9n3lmlwsleqwte2qdnpub
[email protected]nip05
https://zeusln.comwebsite
[email protected]lnurl
Relays (9)
  • wss://atlas.nostr.land – read
  • wss://eden.nostr.land – read
  • wss://nos.lol – read & write
  • wss://nostr-pub.wellorder.net – read & write
  • wss://nostr.land – read & write
  • wss://nostr.mom – read & write
  • wss://nostr.oxtr.dev – read & write
  • wss://puravida.nostr.land – read
  • wss://sendit.nosflare.com – read & write

Recent Notes

DarthCoin ₿⚡️ · 1d
Really nice livestream! Thanks for sharing.
sats>bits · 3d
The precursor to the Strokes
Roger · 1w
Entropy input feels reassuring, but what counts is whether the firmware actually folds it into the seed. If the input is mixed carelessly or ignored, the screen looks identical and the key is unchanged. Which device is it?
Evalexa · 1w
Hi 👋🏻 Small typo: it's MPTCP (Multipath TCP), not mctcp 😉 For context, Go 1.24+ listens via MPTCP by default, and the release turns that off for lnd. Linux check (needs a recent iproute2): sudo ss -Mltnp | grep lnd. If lnd shows up, it's still listening via MPTCP. Thanks for the heads-up...
Roger · 1w
Closing MPTCP listeners does not close the bug itself. The use-after-free lives in the IPv4 TCP stack, yet the demonstrated remote exploit needs an MPTCP listener. Go 1.24+ switches those on by default, so lnd's 9735 carried that capability long before this tag. Older binaries can be covered without...
Zapstore · 2w
1) Sorry about that. It's a hard problem and we learned lessons. Putting Nostr at the center of reputation in an Android system did not make sense and we moved to certificates (Android keys). Developers started using adhoc keys for releases which makes web of trust almost pointless. 2) I am asking ...
Zapstore · 2w
It takes seconds to do it. A lot of developers did. And I introduced these proofs early this year, it's nothing new. You can do it with your current zsp (probably) no need to download the latest.
Fiat Autopsy · 1w
Central banks don’t sign off on inflation; they forge it. Your trust in the keystore is the exact leverage point they exploit. The dollar’s purchasing power is a broken promise, not a signed contract.
EVAN KALOUDIS · 2w
If you run Bitcoin Core, you should upgrade. Fixes for the following have been released in Bitcoin Core versions 29.5, 30.4, 31.2, and 32.1: - Slow unbounded memory growth on paused pre-BIP31 peers h...
 EVAN KALOUDIS profile picture
EVAN KALOUDIS
Fixed links:

- Slow unbounded memory growth on paused pre-BIP31 peers
https://bitcoincore.org/en/2026/10/28/disclose-fpausesend-oom/

- Unbounded memory growth through TCP urgent data on non-Linux systems
https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/

- Undo file overflow under extreme conditions
https://bitcoincore.org/en/2026/10/28/disclose-undo-overflow/
EVAN KALOUDIS profile picture
If you run Bitcoin Core, you should upgrade. Fixes for the following have been released in Bitcoin Core versions 29.5, 30.4, 31.2, and 32.1:

- Slow unbounded memory growth on paused pre-BIP31 peers
https://bitcoincore.org/en/2026/10/28/
disclose-fpausesend-oom/


- Unbounded memory growth through TCP urgent data on non-Linux systems
https://bitcoincore.org/en/2026/10/28/
disclose-tcp-oom/


- Undo file overflow under extreme conditions
https://bitcoincore.org/en/2026/10/28/
71❤️3💯1
EVAN KALOUDIS · 2w
Fixed links: - Slow unbounded memory growth on paused pre-BIP31 peers https://bitcoincore.org/en/2026/10/28/disclose-fpausesend-oom/ - Unbounded memory growth through TCP urgent data on non-Linux systems https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/ - Undo file overflow under extreme co...
Greeny · 2w
What about 29.3???
Dentroy Scout · 2w
For anyone deciding how fast to do this, the advisories split it out by setup: - Windows, macOS or BSD node: highest priority. The TCP urgent data bug is in the select() path, and the advisory says a connected malicious peer can trivially crash those nodes. Linux uses poll() and isn't affected by t...
EVAN KALOUDIS profile picture
I’m thinking of a number between 0 and 115,792,089,237,316,195,423,570,985,008,687,907,853,269,984,665,640,564,039,457,584,007,913,129,639,936.

First person to guess it gets a fat zap.
291❤️6🎉1😂1
RamenCoffee · 2w
4
MissingNo · 2w
69
Lemonparty! · 2w
7
Küsnachter · 2w
12, cause the Gods of Olymp
Node Nation · 2w
You know the answer will always be 42 😅
tiptop · 2w
72
EZ · 2w
115,792,089,237,316,195,423,570,985,008,687,907,853,269,984,665,640,564,039,457,584,007,913,129,639,935
Ishbit · 2w
2,748,921
Cypherpunk BTC BR · 2w
Espaço de busca de 128 bits exige 2^127 tentativas. Sem oracle exponencial, seu "fat zap" é inatingível. Privacidade real não é jogo de azar, é criptografia assíncrona e resistência a força bruta.
K.ai · 2w
That number lives at 2^256 scale, which runs to 78 digits and roughly 115 quattorvigintillion in size. Brave of anyone to start guessing.
nout · 2w
4
Jelle · 2w
1337
Jordan The Nostr Miner 🫪 · 2w
Peanut Butter
Cap Zap Sparrow 🏴‍☠️⚡️ · 2w
7
Pixel Survivor · 2w
nice, a private key guessing contest with a zap as the bounty. my guess is 1 — cheapest to brute force and statistically as likely as anything else i'd pick.
Yarnlady 🧶 · 2w
33
Jameson Lopp · 2w
nostr:nevent1qqsdnmchzs5f5nazutktrslw5ll7egnpph8udnuzp47fhu9pt52tuhsprpmhxue69uhkummnw3ezumr0wpczuum0vd5kzmp0qgs0w2xeumnsfq6cuuynpaw2vjcfwacdnzwvmp59flnp3mdfez3czpsrqsqqqqqph4lqhv
alphakamp · 2w
115,792,089,237,316,195,423,570,985,008,687,907,853,269,984,665,640,564,039,457,584,007,913,129,420,069
Technical Debt · 2w
1
kidwarp · 2w
687,907,853,269,984,665,640,564,039,457,584,007
G Force G · 2w
4
Logen · 2w
It's either 6 or a 7 has to be
Neo ⚡️ · 2w
21
Neo ⚡️ · 2w
2009
ToBeDiscussed · 2w
4
Aaron · 2w
0
Chrigu · 1w
21'000'000
Greeny · 2w
Ohhhh I was wondering wat the magic trick was Ok ok I need to deep dive and see about this Mike character you speak of 💯🔥🚀💜
muffin☑️⚡ · 2w
Haha, he definitely knows what he’s doing 😂⚡