Damus
Kyma Fi profile picture
Kyma Fi
@kymafi

Disclosure - now streaming exclusively on wavlake ⚡️

Relays (9)
  • wss://relay-rpi.edufeed.org – read & write
  • wss://relay.damus.io – read & write
  • wss://relay.wikifreedia.xyz – read & write
  • wss://hotrightnow.nostr1.com – read & write
  • wss://relay.primal.net – read & write
  • wss://nos.lol – read & write
  • wss://relay.nostr.band – read & write
  • wss://theforest.nostr1.com/ – read & write
  • wss://premium.primal.net – read & write

Recent Notes

note1ygr2s...
Kyma Fi profile picture
lol guess how devs were on the Satoshi client dev team???

Just one. Things were more efficient and working great before a massive team of DEI hires needed huge funding from corrupt institutions that hate bitcoin. Plus the Satoshi client never deleted wallets or leaked ips like Core…
note1s7hlp...
Kyma Fi profile picture
4mb vbtyes are perfectly reasonable… we are talking about an average block of .5MB more than what Satoshi’s initial limit back in 2010 when we had near zero adoption. For comparison, BCH has a block size of 32MB lol 😂

Plus you are kind of mischaracterizing the change… the segwitt upgrade was technically a change from a 1MB byte limit to a 4 million weight unit (WU) limit. To simplify these calculations, the network often uses vBytes (virtual bytes) as a unit of measurement. One vByte is equal to 4 weight units.

So, a block limited to 4 million weight units is effectively limited to 1 million vBytes. It’s a more dynamic system that averages out to slightly more than the initial limit back in 2010. Thats completely reasonable considering how useful it is - Thats why it reached consensus.

It enabled lightning so that BTC could scale as a medium of exchange.

In other words you really just need to brush up on what segwitt actually did - it doesn’t cause “inflation”.
note1009kh...
Kyma Fi profile picture
You said <<< The blockchain has no concept of “spam.” It has no concept of “financial transaction.” It has no concept of “witness.” It only preserves irreversible bits.>>

It’s irrelevant because the nodes decide what is spam or arbitrary data. They decide what the protocol is.

And under Satoshi’s original protocol there was no block limit. It was specifically added to prevent spam lol

The 4mb of data from Segwitt isn’t spam. It’s a monetary use case. Plus most blocks are much lower than 4mb.
It still is virtually the same smaller limit Satoshi imposed in 2010 - around 1.5 to - 2mb.

On the other hand… The op return limit increase from core was not opened for monetary data. It was opened to appease companies like Citrea so they could literally run a “stablecoin scam” and it’s being used for other forms of spam. Same thing with the taproot exploit. That’s where most of the arb data is coming from…
Jack K · 1d
You can’t hide from the fact by muting me that SegWit has discounted arbitrary bits and your whole movement is to remove arbitrary bits from the chain. You are literally running code that discounts...
Kyma Fi profile picture
SegWit data is far from arbitrary; it is foundational to the Lightning Network’s ability to facilitate fast, low-cost, off-chain transactions.

And the 1MB block limit was to prevent spam attacks early on in the network development. It wasn’t a hard cap like the supply. That makes no sense to sacrifice the mechanism which allows it to be a medium of exchange for no reason at all. Segwitt bits don’t cause the chain bloat and aren’t arbitrary.

Unless you think sending zaps, or making payments on lighting is arbitrary lol
1
Jack K · 6h
The pricing is arbitrary. Why not 1/10? 1/1000? 1/2? Why 1/4? Why not 1/1 when the physical bits cost the same to store? The only moral answer in regards to the economics of energy is 1=1. But hey, now we can stuff spam in witness data for 1/4 of the cost and grow the chain memory up to 4x faste...
JesterHodl · 8h
Well, I had it installed for the Dolphin card, but they took it away.
note1pkh7t...
Kyma Fi profile picture
I wouldn’t see any value in increasing block size or segwitt discount. I don’t think it should change either. Lightning works wonderfully and it’s not the issue causing the chain bloat. It’s Core and their attitude of surrendering to spam, their resentment of the plebs and node runners.

Thats why I run Rdts. It’s temporary, and stops the bleeding, and sends a message that BTC is purely money, not a place to store data, jpegs, or run scams like citrea’s stablecoin. It has the added benefit of making core irrelevant lol
note1pwkj7...
Kyma Fi profile picture
… I didn’t say virtual bytes. It’s a virtual block size limit or vByte it’s a unit of measurement, not fiat lol. One vByte is equal to 4 weight units.

It’s part of the functionality that made lightning useful and allows bitcoin to be used as a medium of exchange on L2.

Satoshi’s limit of 1MB wasn’t a hard capped rule like the supply… it was a temporary solution to the spam problem to help keep the barrier to node entry low. It was obviously not a permanent monetary constant. Plus most blocks are around 1-2 mb anyway… Thats not inflation, it’s innovation confirmed through consensus.

Like I said before; Removing segwitt discount doesn’t address the spam problem cause it’s not the root cause of these current attacks. Removing the seg discount creates a worse problem… it ruins functionality of Lightning and use of bitocin as money.

note1pd04a...
Kyma Fi profile picture
Not true… a typical block isn’t 4mb and besides Satoshi originally shipped Bitcoin with no block size limit. You seem to be purposely ignoring that lol 😂

Removing the segwitt discount does nothing but harm lightning and doesn’t prevent large op returns or taproot exploits….

It certainly ignores the “CORE” problem. We need to address the centralization of the development client, not just tinker with weights.