> turning elliptic curve signatures into a new inflating monetary asset
this is not what I am saying; What I am saying is mining over a nostr event.
the event:
{ target: npub1xxxxxxxxxxxxxxxxxxxxxxxx
nonce: 59h998543...
}
If you sha256 this event, the result starts with a certain number of zeros.
ah yeah, i forgot that was what it meant
there's a lot of very fast SHA256 mining hardware that can be applied to this, so what i said about it being ded multiply that by two orders of magnitude
sure, most current generation miners can't be persuaded to hash anything other than 80 bytes but there is still pretty fast ones that can be reprogrammed, you have to implement a sponge function either way and the limitation is just a question of how you write the firmware, mostly
still, you did mention PoW npubs as well, as a "backup" which only marginally increases the durability of the scheme
genuine question:
why did you mine your npub so that it ends with 'mleku'?
i switched to a milk-only diet for about 5 months starting in december last year, due to having no money due to suddenly learning my sponsorship was over as i just had landed in madeira, and mleko is the word for milk in yugoslavian languages, so i put the "u" on the end to reflect the serbo-croatian "position" case (at/on)
and i built a key miner, yes, way back then, i've updated it a lot... this is the original that i used to make my current key, took 4 days:
https://github.com/mleku/vainstr
this is the updated version, which optionally (preferably) uses the bitcoin-core/secp256k1 CGO library and it can mine a mleku key in about 3-7 minutes
https://github.com/mleku/nodl/tree/master/cmd/vainstr
i have since quit the milk diet because it was too much lactose and i got fat, now i mainly eat hamburger patties and other forms of beef, and i've started using up my stash of psillium husk because it helps me digest fats easier, and my energy levels have gone up drastically in the last few days since starting on that
oh, thanks for sharing this interesting story, and sharing the code I used.
However, I was more interested in why did you mind that key instead of using a random one?
it was a deal i made with myself to not go online until i mined a key haha
okay, so just for fun. I thought you did it as an anti-impersonation mechanism
well, at 4 days mining it was kinda, but now it's under an hour, i'd need to make a longer name next time... maybe i should re-adopt elfspice :)
also that's why i'm like "hmmm not sure this PoW thing on keys is gonna do you much good" when i can get 40 zero bits at the front of a key in minutes...
hm actually, 25 bits
What if I take an ASIC, make it mine, and people can pay 10$ to me to have these PoW keys or even better these PoW endorsements (so you can use the same old key), in order to get a "golden badge" displayed next to their name on clients, as a form of anti-impersonation.
Like, I would pay for it, and other would as well I think.
And if the market for anti-impersonation service gets big enough, it can actually work at scale.
golden rule of PoW: if it enables income via spam, it will be adopted by spammers
also, then you still have to pay to not be flooded by spam, when you could just make relays paid
💯 full circle
all forms of spam prevention boil down to paid access, really
bitcoin uses proof of work, and uniquely can use it because it is money, and there is only one money, and the vast graveyards of proof of work shitcoins stands testament to the there can be only one problem
proof of work is to spam-prevent the PROVIDERS of the bitcoin service
the users have to pay transaction fees, which is the spam prevention
so the same applies to nostr, except that we don't have a consensus so there is no competition for that, we just have a user spam problem
so, we just need transaction fees, and because it's a relay, and it's not just one-off service, you switch to subscription model, but the problem is
you need auth to do paid subscription model!
Agreed! Except for the subscription model.
Making content publication and micro-payment the exact same action is the way to go.
why is subscription model not?
it has a lower cognitive burden, and requires the use of rate limiters when the user exceeds their service level
you would not make even lightning transactions as often as you like and reply to notes
at this point in time subscription model makes sense because most LN payments are going to be custodial and the friction level is going to be high, i have to click and wait to do zaps as it is, you want me to do that for every like and reply?
if it isn't in the protocol yet, then don't make unrealistic expectations about an immediately paid transaction model without recognising that this simply is impractical and has not only a high cognitive burden but a much higher message cycle cost
1. Subscriptions do not have a lower cognitive burden in highly competitive, open markets. They're nightmare to handle for the subscribers. There's a reason people don't have subscriptions to every bar they have some drinks in.
2. That's why eCash is inevitable
