The pluto goofy paradox.
I guess what my problem was that i have to scan a QR code everytime i make a zap.
I just want to click the button and set it to X sats and thats it.
Is there a way to set up every like to be a zap?
I want a simple solution, i dont want to configure things and such.
Actually, thats a good point.
On one side i think that this is more of a ME thing so client side makes more sense, as its easier to implement + less stuff to move around the wire.
However the whole magic here is that you have a protocol and you can take your npub where you want.
Wtch u tink?
nostr needs bookmarks!
xdHere is a picture of a random girl i took in a caffe.
I am using 4 new realays, lets see the difference.
Let me epxlain ordinals with an alegory.
You have a potato shop and you sell potatoes.
You are poor.
You really need to sell potatoes.
Some d00d comes and buys all your potatoes every day.
At one point you realize the d00d buys the potatoes to shove them up his ass.
Do you stop selling potatoes to the man?
While at Advancing Bitcoin Eduerd told me this Bitcoin Taproot joke.
Hope drinks comes faster than messages load 😬
I don't this so, as this is the chance of 1(single) key. 🤔
If you were to reverse a PubKey to PrivKey, then indeed there is a reductionfdfrom 2^256 to 2^128 and that because Birthday Paradox(Misnomer)
You are also correct regarding collisions with addresses.
When calculating the Bitcoin address you at some point do RIPEMD160 and you can find colissions there.
This project focuses on this https://lbc.cryptoguru.org/about
The probability of collision is 100%(because of the pidgeon hole principle:p)
I think the question is how many steps it takes to find one, and the answer is sqrt(N).
The Birthday Paradox, is also a misnomer.
You are right, its size limit.
Are there any payed relays that are faster?
Really annoying this whole looking for messages thing.
Indeed, i did say someone's in my OP.