Damus

Recent Notes

Alex Gleason · 6w
Onchain zaps is the purest form of expression of the Nostr protocol. It's the first thing anyone thought when the read NIP-01. For years we're been living a lie. Look what that brought us. This is wha...
hoppe2 profile picture
When the spec actually said it uses the same cryptographic scheme as Bitcoin to create identities, I did think, "Ah, so it derives the same key into a Bitcoin address and uses it to send and receive money." Because I heared it's a Bitcoin native protocol...
m0wer · 3d
I've never been more intellectually challenged in my life. AI has taken over all the "simple" tasks such as waiting for tests and fixing failures, dealing with dependencies, writing documentation, ......
hoppe2 profile picture
Yeah. Before even getting to the argument that " delegating simple tasks to AI frees up time to focus more on design" — in my case, I probably wouldn't have even thought about building anything in the first place if AI hadn't existed.

Recently I had to deal with handling a zero-confirm tx (obviously not talking about on-chain stuff, haha), and going through the process — proposing an approach, getting rebutted by AI, then re-rebutting AI's suggestion, and finally reaching a conclusion — I learned a lot along the way.
hoppe2 profile picture
I've noticed a lot of controversy in Western societies about introducing ID numbers. Since I live in a country that adopted this system decades ago, let me give you a heads up on a few things:

Every single time you sign up for something, you'll experience hell.

Site operators will also experience hell trying to manage all that personal data.

You'll see news about personal data breaches pouring in almost every day.

Using issue #3 as an excuse, they'll demand even more personal information under the pretext of better distinguishing identity theft from legitimate use.

Idiots won't realize this whole mess stems from government policies that force companies to collect personal data in the first place—instead, they'll blame companies for "failing to manage it properly," causing social division.

Enormous amounts of time and manpower will be wasted handling personal data that never would have been leaked if it hadn't been collected in the first place.

Under the pretext of protecting personal information, government intervention in corporate operations will expand dramatically
Super Testnet · 4d
Today I noticed this in the original LN whitepaper: "A Funding Transaction may have multiple outputs with multiple Commitment Transactions...[One output could] requir[e] additional signatures from sec...
hoppe2 profile picture
Batch openings don't seem to provide much scalability benefit, but sharing outputs could be significantly helpful — arc is considered to be implemented for this purpose. While it may not offer the immediate finality comparable to Lightning, it pertains to an area where economies of scale apply. In the future, large-scale ASPs will be able to conduct batch settlement transactions in every block, and when that happens, Arc enables:

1. Cheap utilization of vtxos with unilateral exit rights reset every block.
2. Much more reliable operation for zero-conf payments (here, meaning participation in a batch round rather than onchain confirmation) due to the incentive model — since it’s not anonymous customer but ASPs maintaining an ongoing business that must cooperate.
1
Super Testnet · 4d
> Batch openings don't seem to provide much scalability benefit I think they do. Suppose 10 people onboard to LN via Phoenix Wallet. Let's compare what it looks like with and without batching them. Without batching: 10 inputs, 10 signatures, and 20 outputs (the channel + change) With batching: 1 i...
Technician · 3w
Agree, but how do you stop the governments from dictating?
hoppe2 profile picture
If we're talking about things we can do at an individual level:

1. There are many things that are illegal but don't actually violate anyone's private property—if you've been in the habit of reporting such things, stop doing that immediately.
2. Encourage tax evasion.
3. Persuade others to join in on points 1 and 2 as well.
4. Advocate for, use, and spread the freedom-enabling technologies that make it easier for others to do these things.
5. Above all, stop voting.
6. Exclude, as much as possible, the voluntary Gestapo who can't be persuaded.

In fact, there's one path that's the easiest way to put all of this into practice—one that requires no special effort and is even beneficial to do: save in Bitcoin and pay in Bitcoin.
🎯1
utxo the webmaster 🧑‍💻 · 3w
God speed sir
utxo the webmaster 🧑‍💻 · 3w
Wow someone who understands nostr, this is nice, followed
The Fishcake (nostr.build) · 3w
nostr:nevent1qqsqqqpq6zacmcnksjqthc4hyd33jyuwfxpwkxh3a7qqqrhe4r8cfqgpp4mhxue69uhhjctzw5hx6egpzdmhxue69uhhwmm59ehx7um5wghxuet5qy8hwumn8ghj7mn0wd68ytnddakszrthwden5te0dehhxtnvdakqygqcjpws5htz82up4x96nrz...
hoppe2 profile picture
The reason the notification isn't going through is that the problematic note isn't tagging your pubkey. Also, per the Nostr standard spec(NIP), in order to send notifications properly, client is supposed to tag everyone involved — meaning all participants from the root note all the way down to that comment — but it looks like Wisp only tags the pubkey of the immediate parent note.
2🫡1
utxo the webmaster 🧑‍💻 · 3w
Yep it's a wisp iOS bug doggo is right
hoppe2 · 3w
And this goes without saying, but... it's not just about tagging — the client also needs to look up the inbox relays of every tagged person and publish to those relays as well.