Avatar
jb55
32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245
I made damus, npubs, and zaps ⚡️ Independent bitcoin core and lightning dev.

This might kick the hornet's nest, and the swarm will be heading towards us.

bitcoin is defined by its implementation, if anyone could change it and convinced everyone to run it, it would change bitcoin. then that would be the new definition of the currency. if we want to maintain its current properties, then it is by definition a meritocracy that maintains that.

if it is never updated ever again then sure, but its still the product of this meritocracy.

the code that checks the limit is ineffective, inscriptions got around it via the witness trick. anytime it is tweaked it can be worked around, usually at the the cost of UTXO bloat. I used to be in favor of it but I have since been convinced by core devs otherwise.

huge if true. I will try to enable the zap button again on posts and see what happens

nostr:note1a63sx7ec8jvqxu5d6uqm077348xsw3y6fdmrh6tg468fgv67cykq5fwfng

how is he wrong? bitcoin is a meritocracy. if you have not contributed to bitcoin in any way why should anyone listen to you?

Your exact thought process lead to bitcoin cash, and how did that go?

I won’t be there so no fighting needed 😅

oh right i said i would launch notedeck beta… will do that today. Just testing windows installer atm

I’ve been building noteguard, notecrumbs, nostrdb, notedeck, damus iOS, damus android

I run all the teams and ship a large percentage of the code. yeah things move slow when you are one person running a company and building an embedded nostr relay powering two mobile clients and a desktop client that runs on all platforms, as well as a push notification server, njump-like server, etc. somehow we got all that done in 3 years while going to multiple conferences to promote nostr.

What have you been up to?

yes, i don’t want retards maintaining my money. I definitely want experts who have been thinking adversarially in this space longer than me.

I mean i have always been on the side of relaxing standardness (i miss puzzle transactions) but i think core is always going to side on removing knobs that produce foot guns, not adding more powerful customization. I think i plugin system would be cool so you could implement any logic you want, so noone would have to argue. I think the concern then would be social media campaigns for people to download certain plugins without realizing the effects it would have on tx distribution.

I said “ability”, I have a branch with this working, just trying to find the right ui for it. I’m thinking it could be a special mode you enable. “Private mode”? Uses more bandwidth is the tradeoff

yeah but if you do “pull everything” (which might be reasonable for smaller relays) it is at least the minimum amount of information revealed

mempool policy/standardness is not consensus code. It just extra rules on top that try to reduce the spam on the p2p network and which transactions you want to keep around in your “ready to accept” queue, aka mempool.

Since there could be more transactions you could fit in your system memory, mempool policy helps make sure you see transactions that have non-spammy things like some reasonable min fee or excessive data carrier sizes (this is the controversial bit, whether its worth maintaining that logic you can hack around anyways)

With or without this core setting you can still give the transaction to a miner directly to mine it, since consensus code doesn’t care about policy.

Replying to Avatar semisol

This appears to be some sort of metrics functionality. Don’t think there is any bad faith.

I’d recommend nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg fix this.

The public key seems to be used for certain personalization, so it makes sense they might store that for debugging, but still a privacy risk.

They could rework their debugging system to integrate tracing and logging to identify specific issues, without storing search queries or pubkeys. And limit retention to a few days, and only when necessary (query error or high latency).

nostr:note1g6lpr8p6jjmw8q7gj4336prk49efqk8htuwh00s43hsffy2kf2vsj390w5

So this is a lie ?

yeah without that it forces me to attempt to melt to accept it, if I knew every token was from a mint I trust then I could accept payment even if the mint is down, since I trust it to come up again.

is it safe to do that with those proofs somehow?

I don’t see how it’s good for scalability and privacy where there are glaring payment finality issues when actually using this in practice for commerce.

so its explicitly designed to be doublespend + rugpull tech. makes sense. I guess that is technically a feature for the sender

So we’re re-adding visa-like chargeback liabilities to payments. Why would anyone want this

is there a UI for it? it easy to use? I don't see any info on their website on how to run it. it looks like you need to run an LND node? this is way too complicated. it needs to be easy so anyone can do it.