Also, events that no longer meet the minimum pow requirements get kicked out. So the more pow, the longer it'll be stored.
Adjusted to keep the database size constant. So it will get harder over time.
I deleted the ephemeral logic in github.com/fiatjaf/relayer so if anyone one posts an ephemeral event with pow, it will be stored.
The water bot and nost-commits bot do 10 leading bits I think.
I can browse it on https://coracle.social/relays/powrelay.xyz, but hey, it is not working. I can see many notes with basically no proof-of-work at all in there.
Believe it or not, so few people do POW still that two leading 'q's in the bech32 event id is plenty to meet the current cut-off.
https://nostrrr.com/relay/nrelay1qqf8wumn8ghj7ur0waex2mrp0yh8s7t6yttsar
Weird, I saw an option to type a relay URL. I don't even know wtf nrelay is
Very cool! Checkout the ocean boilers and bots on wss://powrelay.xyz
it's because he still thinks taxation is a good thing 😕
Bisq has some kind of DAO, that I guess works. I like the whole nostr rocket proposal but I guess we'll have to wait to see if it works out.
I'm putting all my eggs in the "AI will make it possible to run an Apple - sized enterprise as a single dev" dream.
🤔 good point. The pow threshold is: 2^target_difficulty / number_of_bytes
The current minimum can be queried with: curl https://powrelay.xyz/min
I'll add something to webpage and the relay metadata description
I recently changed wss://powrelay.xyz to return the highest POW / byte events by default. should I change it back?
discover gems like this, and more by using wss://powrelay.xyz as your global feed
Incredible example of accidental proof of work:
19 leading zeroes (1 in 500,000 chance) for a 🤙
44 leafing zeroes! nostr:nevent1qqsqqqqqqqqqcyn3vawusm37rhgnx6p8hn9thyxufjwnk3r9alh7qrspzfmhxue69uhhqmmhwfjkccte9eu8j7s4dkr6z
https://powrelay.xyz/explore?window=all to see the top 10
"Relays can be dumb" is a principle we should not discard lightly.
Don't cancel relays because they don't monitor and censor their content. Even the WEF could post on wss://powrelay.xyz and I would not remove it (as long as it had the necessary POW).
The proper solution is client side filtering. Gossip plans to introduce powerful capabilities with Lua scripting, perhaps you could train a simple ml model to exclude content you find objectionable and still benefit from all relays.
For what it's worth, I've discovered many interesting accounts browsing the top daily POW list on https://powrelay.xyz/explore
nostr:npub1ujsax5qggxkmvu6gwht9c30p0w2df56akngj3hfg3j3cr7daejgq2nnzxc
nostr:npub1xjsenwf98zypvyu039f7v767cm3j8sc0jf55qd38x94nn2zw5x9ska3rqt
nostr:npub12g820dm4gettjvrdq8x6dp53vm427v3uws78txyyavm0rckjdydq2u22cf
nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk
nostr:npub1pe5q9k9hetczq6ca77up6fpp5fajm4dr89hhf070ukaw3xtujkdqulw0zr
nostr:npub1qqqqqqz7nhdqz3uuwmzlflxt46lyu7zkuqhcapddhgz66c4ddynswreecw
wss://powrelay.xyz will send you the events with most POW that match your query.
I like POW because it is a trustless solution to content discovery. If you care about the content of a note, you should be willing to spend money mining POW for it. If not, then it's probably ok for people not to pay attention to it.