Avatar
Xtr3m3hodl
f54b90c805a590dbe475354708b03390d77baa96190535b4b8a521a409b56086

I don't have this problem with chrome mobile.

Replying to Avatar calle

nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk Snort and Iris haven't been working for me for weeks.

I see random connections to relays I've never set and also attempts to connect to onion relays that won't work on my machine. Am I the only one?

Same as well on Firefox Mobile

The blocksize war wasn't so much about the blocksize (or, even, scaling Bitcoin). It was really about who controls the consensus rules and how we upgrade the protocol.

For context, a bunch of startups raised tons of money between 2013 and 2016 based on ridiculous user sign-up projections and then we had a long and painful bear market and they were looking for scapegoats (the developpers that were "throttling the network") to justify the lack of growth. I am thinking here specifically of Coinbase, Bitpay and Blockchain.info.

The vibe I got is that they thought of Bitcoin itself as a corporation, that they were the equivalent of Bitcoin's board of directors because they represented the interest of VC investors, and thus they were entitled to decision making power over the network.

I don't doubt that a few people were genuine about scaling p2p e-cash (e.g. Roger Ver) but I suspect what really motivated them is that they believed control of the Bitcoin network would be an asset to their business interests, and lack of control was being used as an excuse to why their interests weren't being satisfied.

There was also a bunch of developers that I believe may have been afraid of losing their relevance (Gavin and Garzik specifically). Regardless of their intentions or psychology, it seemed clear to me that the consortium of vc-backed startups (particularly Bitpay, Coinbase, blockchain(.)info and Roger) had picked a team of developers they thought they could control and wanted to appoint them as a technical management team whicn would execute their strategy, and these guys were willing to step up for that role.

I was physically in the room when the CEO of Blockchain.info (with the very obvious support of Coinbase CEO Brian Armstrong) announced that Bitcoin Core devs were being fired and would be replaced. This was after a couple days of failed discussions with other industry people. This was the moment when I realized what was really going on.

And finally, you had a Bitcoin mining giant (Bitmain) controlling both asic production and mining pools with a vested interest in promoting the idea that Bitcoin was a democracy and the way to vote was to buy hashing power. The main ideology being pushed here was that a formal governance mechanism of the protocol needed to be established and that hashrate was the only objective measure of who makes decisions.

The underlying big blocker ideology was that the chaos of spontaneous consensus of nodes is unpredictable, flimsy, bad for business. The absence of a formal governance process was seen as the root cause of the issue.

These companies really believed they could control the protocol, and controlling development of the protocol was seen as a very valuable asset to your company. I imagine they thought of themselves as the founders of a new consortium that would solidify itself into a permanent institution. The business interests would pay developers and set the goals, and the mining interests would ratify their decisions with hash power voting. That was their plan.

This became blatantly obvious when Bitmain used its refusal to activate segwit as leverage to get what it wanted (a blocksize increase and recognition of its hashpower as a vote mecanism) even though Bitmain iself acknowledged it was not really opposed segwit.

It was classic traditional politics: I'll give you segwit if you give me something in return.

This is the language the VC suits, investors and tech startup people understand and they were very happy to "negotiate" and find "consensus".

This eventually materialized into the New York Agreement, negotiated literally as a backroom deal during theConsensuss shitcoin conference. I was there and I refused to attend.

This (private) meeting consecrated the alliance of startups/investors and bitcoin mining interests in their appointment of a technical management committee. If you think this sounds like Jekyll Island, you're not alone.

They packaged segwit with a blocksize increase (Segwit2x) and decided to force a hard fork as a condition to "allow" us to have Segwit.

We know the rest of the story: we ended up activating anyway via UASF (or more precisely, the miners activated Segwit after they New York Agreement signatories became scared UASF would lead to a chain split which they were going to lose). And the blocksize increase was also abandoned shortly after when they realized their hard fork would cause a chain split and that they would not be able to claim that their new shitcoin is the real bitcoin.

All these people were subsequently were very pissed off they couldn't control the network, which they thought they were entitled to. Some ragequit, others created a bunch of shitcoins out of spite, Roger went on to spearhead BCH as the real Bitcoin, all these fools realized they might as well make some money off of it, everyone went all-in on the shitcoin casinos after that. The "small blockers" eventually went on to evolve into the Bitcoin Maximalists and cypherpunks that today tell you to run your own node and own your own keys.

Reading this is so pleasant on the eye.

Also Bitcoin development doesn't just involve Bitcoin core. All the other opensource developments happening under the Bitcoin umbrella like lightning, cashu, statechains, btcpay server, etc

Reinstalling seemed to fix the issue. Probably got stuck with an older version.

Replying to Avatar Derek Ross

I greatly appreciate the work that nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg and nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 are doing to make self sovereign Lightning easier for the masses.

Building a traditional node and running a traditional node that doesn't run on your phone isn't overly complicated, but it's definitely not easy when problems arise. Troubleshooting is extremely technical and hard for most people.

I've helped a dozen or more people over the past year by connecting to their node or doing remote support and fixing a problem for them. I don't mind providing this assistance, but it's a screaming reminder that Lightning still has a long way to go where it's "plug and play" easy.

We haven't entered the "no-brainer" territory yet, but we're getting there, thanks to these two teams working hard for all us us.

I've struggled setting up initial deposit on Zeus. All wallets I try using with Zeus invoice keep failing.

Phoenixd is showing a lot of promise though it isn't a mobile node. Phoenix wallet is very reliable but at times more expensive to send than onchain which is weird.

Mutiny is really interesting. With the fedimint support, it just improves reliability of payments.

The ux experience when nostr clients have inbuilt lightning wallet is hard to beat. Primal got this right. Mutiny figured out the reverse which is pretty impressive.

The bar has been set . From a wallet development standpoint, nostr integration needs to have first class support.

Phoenixd is awesome. I like the tradeoffs compared to a full lightning node. This is a big win for lightning development

Any idea what the circles with numbers mean? I assume some kind of web of trust mechanism?

Because I meet more ideologically minded people here easily

until you get emails about what you missed from slack 😔

primal eliminated friction in making zap payments. I don't like it. nothing in life should be this easy.