โฉ– powrelay.xyz

day week month year all
32 thousand hashes per byte
Monero is privacy by default. 82uVZNFqwFYMXi5iVVesxGAH71EYSUzDaiUhBBcdJbRE161kzAuWuQhThDn3z8kVfWbAXMry7mLoKbRzb1WUPJgiTsj3FRB
Created at:
Fri Aug 4 10:22:51 UTC 2023
Kind:
1 Text note
Tags:
t monero
t privacy
nonce 717169 20
32 thousand hashes per byte
true
Created at:
Fri Jan 5 04:15:17 UTC 2024
Kind:
1 Text note
Tags:
p 450993540eeee16f798c768a441efed5c62c12df3829285d9c1e489bf9d65694
e 0000009f35f9692769154c1bc2b3a1b3eb8a305b690e2f810eae7c3d35260a87 root
nonce 7345700 21
32 thousand hashes per byte
+
Created at:
Mon Jul 3 12:30:22 UTC 2023
Kind:
7 Reaction
Tags:
e fe91390461e4cf610ec5b1491c886a521be6c99952b9c7f291c79b41335d720d
p 7cfe499ddb7b7ba7011d74fef03246d2ee423dfb67c3b7f72bb1a934face299b
nonce 9223372036859253987 24
32 thousand hashes per byte
+
Created at:
Sun Jul 2 17:17:03 UTC 2023
Kind:
7 Reaction
Tags:
e b73bc6d78c3499d2279a46a9ebca725b8f8afca0e8196c80f2fdfa82ab471605
p 8a981f1ae3fab3300b548c4f20654cb0f1d350498c4b66849b73e8546001dca0
nonce 4611686018428192706 24
32 thousand hashes per byte
+
Created at:
Mon May 15 06:59:50 UTC 2023
Kind:
7 Reaction
Tags:
e 67a279d0662a195911905ecd011c524cd610808cd762fd893a73c6a76deede5d
p fcf70a45cfa817eaa813b9ba8a375d713d3169f4a27f3dcac3d49112df67d37e
nonce 5764607523034696145 21
32 thousand hashes per byte
That's one hop away (you trust Uncle Jim). But if one of Uncle Jim's friends (2nd hop) signs the attestation? What if its 3 hops away? It gets real tricky real fast.
Created at:
Mon Dec 4 20:40:59 UTC 2023
Kind:
1 Text note
Tags:
p 4535551a40271b059ab92b71e7ab7e8700061a2d91b0d20f313ef82f052eb085
p 4d5ce768123563bc583697db5e84841fb528f7b708d966f2e546286ce3c72077
p df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200
p 97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322
e 063d1c33bf12ba076926331c1368418e186b0f810aba839d82d5db441af0a6fc wss://nostr.einundzwanzig.space/ root
e 647da011c6cb73ddecc182877aa1f3e3d48b17804527fe829c8064dcb526e975 wss://relay.nostr.band/ reply
nonce 6789367 25
32 thousand hashes per byte
+
Created at:
Tue Apr 4 03:38:22 UTC 2023
Kind:
7 Reaction
Tags:
e 1c38cecebe3b197a2221dd481ecfa6b74e52cd92db7626d53fdf2737dc101c99
p 32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245
nonce 15372286728091363889 21
32 thousand hashes per byte
No, just rent computers from gcp (when it was working). Will take less than 10 minutes, it just buys as much computers as necessary to get it done fast, but it'll be expensive. No one was using it so I turned off the servers for now. Gonna make something better soon, I think it's too annoying to have to have to go to a separate website, it should be a dvm or something. When more people use it, I expect it'll follow the usual trajectory of naive cpu algo โ†’ gpu โ†’ fgpa โ†’ asic
Created at:
Wed Nov 8 17:50:30 UTC 2023
Kind:
1 Text note
Tags:
p 8f44c56131b362668b0e01be8c71b24786598bb68fb909cfd78fabfb058dd0f0
e 34065bc13315fa67aa1b9d1eb1f0d8b97fcf0d1cfdee535f12a4567b2b934df7 wss://nostr-01.bolt.observer/ root
nonce 4611686018429694583 24
32 thousand hashes per byte
Agree. Maybe you could start a nostr POW service (like https://powrelay.xyz/work.html) that accepts monero (or RandomX mining) as payment in exchange for nostr POW. That's the beauty of POW, since it's trivial to verify, it's also trivial to outsource.
Created at:
Sat May 20 19:01:21 UTC 2023
Kind:
1 Text note
Tags:
p 93724d393f5f0881d9e4bcc195e056ee8bcb9fd3a0af4b3398bc3fddd28d99bf
p 3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d
p da93192957495fb59f6ef1ce19e74947b0792b6eaa1b134a015c0326e4097d1a
e 21506bec1ce96284d86647b3c0875d2435b58781b56ffec5948bc5ac099ddb25 wss://eden.nostr.land/ root
e 14d5bc89287d956d62040da4aa65a6ecff070f2b83bdce5bb67c6ca4618f7311 wss://nos.lol/ reply
nonce 4611686018427737918 21
32 thousand hashes per byte
Question for relay devs: I want to subscribe to all events that augment the events I'm currently displaying (zap receipts, reactions, and deletions). I'm considering making subscriptions with a long set of IDs in an "#e" filter. So my questions are: 1) How long can that get before relays complain the list is too long? 2) If I add a bunch of IDs to an existing subscription, does it start over, or does it remember that it already gave results for the previous ids? (I presume it would start over, which won't be useful for me) 3) If I then instead open new subscriptions every time I need to watch another batch of events, how many of those can I have before the relay gets mad at me? Because I'd be making new subscriptions every 10 seconds or so for a very long time without closing the old subscriptions. 4) Would it be more efficient for me to be watching all the events my user might see on screen all the time, or should I dump and restart subscriptions whenever the user changes to a different feed? That second method would be watching much fewer events, but would rewrite subscriptions frequently thus pulling redundant data. I know I can look at the NIPs and program to that, but I thought I'd get to the best plan of attack faster by just asking. nostr:npub1xhfxu35se0s63x90v8xr29txr66l5a3m277skshy2zvu3ve0658sla4xw3 nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4
Created at:
Fri Jun 16 00:04:23 UTC 2023
Kind:
1 Text note
Tags:
client gossip
p 35d26e4690cbe1a898af61cc3515661eb5fa763b57bd0b42e45099c8b32fd50f
p 00000000827ffaa94bfea288c3dfce4422c794fbb96625b6b31e9049f729d700
p 218238431393959d6c8617a3bd899303a96609b44a644e973891038a7de8622d
nonce 2305843009214496894 24
< prev 487 next >