@ c5fb6ecc:e58c38bb

Chef's notes

Prerequisites

Ensure you have a popovers pan like the one here:

Extra Information

Double all ingredients to make 12.

Typically made for Christmas Morning Breakfast and Easter Sunday Breakfast.

From a BLT Recipe card that's falling apart in our kitchen. Digitized for convenience.

Details

• ⏲️ Prep time: 15 minutes
• 🍳 Cook time: 50 minutes
• 🍽️ Servings: 6

Ingredients

• 2 cups milk, warmed
• 4 eggs
• 2 cups flower
• ¾ heaping tbsp salt
• 1 ⅛ cups grated gruyere cheese
• Popover pan

Directions

1. Place the popover pan in the oven. Heat the oven and pan to 350°.
2. Gently warm the milk over low heat and set aside.
3. Whisk the eggs until frothy and slowly whisk in the milk (so as not to cook the eggs).
4. Set the mixture aside.
5. Sift the flower with the salt.
6. Slowly add this dry mixture and gently combine until mostly smooth.
7. Once combined, remove the popover pan from the oven and spray with non-stick vegetable spray.
8. While the batter is still slightly warm or room temperature (definitely not cool), fill each popover cup ¾ full.
9. Top each popover with approximately 2 ½ tbsp of the grated gruyere.
10. Base at 350° for 50 minutes, rotating pan half a turn after 15 minutes of baking.
11. Remove from the oven, remove from the pan and serve immediately.

@ a723805c:0342dc9c

Chef's notes

Deviled eggs are a great dish that can make a chef out of anybody! Mix it up by adding a garnish on top such as jalapenos, pickles (relish), bacon, or the classic smoked paprika

Details

• ⏲️ Prep time: 20 min
• 🍳 Cook time: 15 min
• 🍽️ Servings: 6

Ingredients

• 6 hard boiled eggs, peeled
• 3 tablespoons of mayonnaise
• 1/2 teaspoon of soy sauce
• 1 teaspoon of Dijon mustard
• 1/2 stalk of celery, finely diced
• Salt and pepper

Directions

1. Cut eggs in half lengthwise and pop yolks out into bowl, mash with fork
2. Mix in mayonnaise, mustard, celery, soy sauce, salt and pepper. Whip until a creamy texture
3. Scoop out fill and add to egg whites, heaping it slightly
4. Add garnish of choice
5. Serve immediately or refrigerate before serving

@ c8df6ae8:22293a06

"I've been thinking about what's the best strategy for you if you're going to be saving in Bitcoin little by little and I think you need to download a new wallet."

Back in Christmas I gave my nephew his first sats and set him up with a Mutiny wallet to receive them. Today, I had him migrate from Mutiny to Phoenix, with all the troubles associated, so that he can buy extra liquidity, at least for a year.

---

The problem

Last December I sent my nephew his first 100,000 sats. He setup a Mutiny wallet and after the channel setup fee, he ended up with around 95,000 sats.

He is curious about Bitcoin and yesterday he asked me if I could help him turn into Bitcoin some cash that his grandparents had sent him. The idea seemed simple, my sister gives me the cash and I send him the equivalent amount in sats.

But...he only had 64,000 sats of inbound liquidity. I tried sending him 60,000 sats with no luck.

He had an inbound liquidity problem. It's already hard to find people who will pay you in Bitcoin for mowing the lawn. Let's not make it even more difficult with Lightning channel management.

So I decided to move him over to Phoenix so that he could buy liquidity.

The move

The move was cumbersome and I hope he doesn't need to do something similar again: 1. Close the Lightning channel on Mutiny and pay the closing fees - The 95,000 sats now sit on-chain and can't be sent to Phoenix 2. Download Phoenix 3. Send me a Lightning invoice from Phoenix 4. I send him a lump sum of sats from my Mutiny wallet to his new Phoenix wallet - The money from the grandparents - 95,000 sats to match what he has on-chain at his Mutiny wallet - Some extra to cover for the Lightning channel setup fee and to buy extra inbound liquidity 5. He then pays approximately around 15,000 sats to add 1 million sats of inbound liquidity 6. He sends me the 95,000 sats from his Mutiny wallet to an on-chain address on my Mutiny wallet - I'm not thrilled, but this is the price of orange pilling a relative

The silver lining

The silver lining is that my nephew now wants to learn about on-chain and Lightning, how they work and how they're different.

I see a Bitcoiner in the making 😁

In summary:

Mutiny is a good wallet for established Bitcoiners and Nostr users. For a new Bitcoiner getting started, Phoenix is the way to go.

---

Notable notes

nostr:note1rc0y40m26jfu2z8jvsy7s0rkw8up6qa55ngtgs5e5a0re3nc2myqnvnv8u

nostr:note1enteftxmfdn4wecsjkjh6fayg8yva9xtln5src45y0ylxaul6cjscwf80q

---

Recommendations

Karnage

Karnage is the #1 Nostr UI designer. If you're using Nostr today, you're using his (or her) designs.

You can follow Karnage here.

---

What did you think of today's newsletter?

Your feedback helps me create the best newsletter possible for you.

Please leave a comment and checkout comments from other subscribers and readers. I love hearing from the Bitcoin For Families community ❤️ 🙏🏻

---

See you again next week! — Alejandro

This newsletter is for educational purposes. It does not represent financial advice. Do your own research before buying Bitcoin.

@ 46fcbe30:6bd8ce4d

Opinion about SeedSigner (hardware)

The SeedSigner right now is subject to some drama as hackers managed to "abuse" the board used in the SeedSigner(?) to connect to a "commercially available" LoRa receiver 120m away even if the board with the no radio components is being used.

While this is a good wake-up call to those who blindly trust the provider's marketing that goes about like this: "With no radio and with companion apps being able to detect key exfiltration and no state that somebody could extract when finding the device, this device is super secure. Can't steal what's not there.", those jumping to the defense of SeedSigner make good points, too: If your device can be compromised with some evil software at your home then it's probably also possible to just solder an RF chip there, too or swap the whole board with one that talks to cellphone towers.

But I'm worried about another attack than an evil maid patching your SeedSigner. What about the software distributed by SeedSigner themselves? I have not audited it but I have compiled it and I have verified that following their build instructions I got the same binary as the one they distributed and with that being the case and with keeping the SeedSigner as secure as the actual seed - yes, with this device you keep your seed on a piece of paper unless you want to remember 12 words which is a good way of destroying bitcoin when you get hit by a bus - your funds should actually be pretty secure.

You can always use a passphrase with your seed, rendering the paper backup less of an immediate key to your coins but of course that again opens the door to forgetting the passphrase. Keep it safe somewhere.

Other than that, the SeedSigner is an air-gapped device that comes with a tiny display and a camera to use for signing transactions. You can use it for example in a multi signature setup with the Sparrow desktop app.

All in all it's a bit more a hands-on device with many nice features and as long as you understand the implications of it not magically keeping that paper with your seed secure, I can recommend it.

WalletScrutiny #nostrOpinion

Join the conversation!

@ b22fef18:1bba6e1f

Details

• ⏲️ Prep time: 3 hours
• 🍳 Cook time: 40 minutes
• 🍽️ Servings: 1 loaf

Ingredients

• 1 packet Active Dry Yeast (7g)
• 16oz warm water (473g)
• 1tsp salt (6g)
• 500g flour

Directions

1. Combine yeast, warm water, and salt into large bowl.
2. Add flour and mix until no dry flour remains. The dough should be wet and shaggy.
3. Cover and let sit on kitchen counter or warm area for 2 hours or until dough has at least doubled in size.
4. Knock down and scrape dough from sides of bowl until dough is roughly original size before your first rise.
5. Oil or butter loaf baking pan and add dough. Cover and let rise while oven preheats (30-60min)
6. Preheat oven to 390F (200C)
7. Uncover loaf and rub with oil or softened butter.
8. Add uncovered loaf into oven and bake for 40min.

@ c8df6ae8:22293a06

"Celsius lied to investors by presenting itself as a safe investment opportunity and a chance to gain financial freedom, but, behind the scenes, the company operated a failed business model and took significant risks with investors' crypto assets."

— Gurbir S. Grewal, Director, Division of Enforcement, SEC

---

Bitcoin is not an investment tool. It's a savings tool

This week the Securities and Exchange Commission (SEC) charged Celsius and its founder Alex Mashinsky with the unregistered offer and sale of crypto asset securities through Celsius’s lending program, making false and misleading statements, and engaging in market manipulation

If you invested your money there, that money is gone and I'm sorry for you.

If you’re new to Bitcoin and you are considering buying Bitcoin, you’re probably wondering:

How do I avoid the next Celsius?

How do I make sure that I’m working with a company that won’t pull the rug out from under me?

There is no such thing as 100% certainty, but based on my experience, the companies that meet the following criteria are unlikely to rug pull you:

• Bitcoin only.
• Does not offer yield.
• Encourages you to self-custody.

Bitcoin only

There is Bitcoin, and then there is everything else.

The SEC itself classifies Bitcoin as a commodity and all other crypto currency tokens as securities (and most of them operating as unregistered securities).

Companies that focus exclusively on Bitcoin are driven by their desire to expand the adoption of Bitcoin.

These companies won’t try to sell you other tokens (shitcoins) and promise you that you’re going to catch the next wave, the next token to go to the moon, just to take your money.

Does not offer yield

Bitcoin is like digital gold. Bitcoin on its own does not produce anything and therefore it offers no yield.

A company that offers you certain return on your Bitcoin deposits can only do so by giving your deposits to speculators and hoping that they will deliver a return equal or higher than what this company offered you.

They also really hope that the speculators don’t lose your money because that’s when they start doing the funny accounting to hide the loses.

You want to avoid that. Don’t chase yield.

Just save with Bitcoin and be happy that your savings are stored in the soundest money in the world.

Encourages you to self-custody

Bitcoin was built so that no one can rug pull you. If you self-custody your Bitcoin, as opposed to letting others custody it for you, It has no counter party risk.

When you self-custody your Bitcoin, nobody can take it away from you. There is no rug to pull.

You want to self-custody and therefore you want to work with companies that encourage you and make it easy for you to move your Bitcoin from their custody to yours.

My recommendations

These are the companies that I feel comfortable recommending.

Swan

I buy Bitcoin with Swan. Their CEO is extremely vocal in calling out crypto companies that he believes are doing the wrong thing: he called out FTX and Celsius way before they collapsed and he has also called out Binance (which hasn’t collapsed, so far).

Just watch the latest episode of their Swan Signal episode to get an idea of how they operate:

Unchained

Unchained offers storage, inheritance and retirement Bitcoin products. I have not worked with them but I have heard very good feedback from people I trust.

---

Notable notes

nostr:note1g037y5kdvg8yka7xl3wa0udpls2lhmhlvn493a4r4tnwcd432zzqxmmsdp

---

Recommendations

Cory Klippsten

Cory is on a mission to onboard 10 million people to Bitcoin and help them self-custody.

Follow him on Twitter if you want to stay clear of unethical operators in the industry. He has no qualms calling them out.

---

What did you think of today's newsletter?

Your feedback helps me create the best newsletter possible for you.

Please leave a comment and checkout comments from other subscribers and readers. I love hearing from the Bitcoin For Families community ❤️ 🙏🏻

---

See you again next week! — Alejandro

This newsletter is for educational purposes. It does not represent financial advice. Do your own research before buying Bitcoin.

@ df67f9a7:2d4fc200

This is a living document being refined from feedback by many people interested in better “webs of trust” for nostr.

Implementation standards are being designed by Sovereign WoT WG. This “working group” is open for all. We will host regular chatroom sessions for informal brainstorming on nostr nests and corny chat. The results of which will be reflected in this document as it matures.

Join the discussion on Nostr

wot #wotnip #sovwot

—

WoT

Webs of Trust is how content “moderation” works on Nostr. Trusted connections between real people is what keeps this open network (owned by nobody) from being overrun by bots and bad actors.

Because Nostr doesn’t have centralized moderation or content control, the surfacing of quality content is becoming a growing concern for users and developers alike. Decentralized “webs of trust” (friends trusting friends for content and account recommendations) is our best protection, but the tools that form these webs (content filters and trust rankings) need to be in the hands of end users. The ad-hoc manner in which webs of trust is implemented on Nostr today (based on follows and different for each client) is both inaccessible and unscalable.

Sovereign WoT for Nostr

Users should be able to control which accounts are trusted and how content is fed to them … across any client.

Sovereign WoT is a Nostr Implementation Possibility (NIP) being designed to put the end user in charge of their own feeds and recommendations. It proposes two standards. Private Trust Lists allows for end users to mark individual accounts as “trusted” and Subscribable Filters allows for developers to publish filters that can suggest “trustworthy” content and other stuff for their subscribed users.

Private Trust Lists

Because “followed ≠ trusted” (on social media), users should have the ability to explicitly and privately mark any account as “trusted”. This will provide a canonical reference for algos suggesting “trustworthy” content and other stuff.

• 15 years of “follow” implemented by walled garden social media, where trust is taken for granted, has guaranteed that “follow ≠ trust”. Any meaningful WoT implementation must have a “more explicit” marker for trust.
• “Muted” or “blocked” is a blacklist approach. “Trusted” is a whitelist approach. Both are needed. Different people will use differently.
• “Is trusted” should have an underlying scalar value, but read as boolean to satisfy most use cases. (It is either 1 or less than 1) This allows filters to be developed that “nudge” trust scores toward or away from “is trusted”.
• “Is trusted” is NOT the WoT score. A users subscribed WoT filters will provide a “trustworthy” ranking (based on “is trusted” across their network) for all accounts, content, and other stuff that they interact with.

Subscribable Filters

Because there is no “best” algo, Nostr should have a “free market” of filters to which end users can subscribe and share. These WoT filters may be published by clients, or relays, or any vendor, and may use any Nostr event data to surface “trustworthy” content and other stuff.

Some WoT filter possibilities

Maybe WoT filters for content feeds?

• all my folllows content?
• all my follows trusted by my WoT?
• only from my trusted follows?
• only content reacted to by a trusted follow?

Maybe WoT filters for recommending new follows?

• accounts who post reactions or comments on a “marked” post?
• accounts followed by my trusted accounts?
• accounts trusted by my trusted accounts?
• accounts with content “reposted” by a trusted account?
• WARN of imposter (having similar profile data as trusted or followed)?
• better WARN of imposter (also checks for similar pfp)?

Maybe WoT filters for suggesting wot filters?

• used by my trusted friends?
• used by anybody in my WoT?

Maybe WoT filters to “automagically” managed trusted follows?

• all my follows are trusted?
• all my follows whom I’ve “interacted with” in 30 days are trusted?
• TrustNet style “let me assign labels and numbers to qualify trust level.”
• NIVS style “let me verify profile metadata on a case by case basis for each user”

@ 0d97beae:c5274a14

(15 minute read)

I recently had a short conversation with my uncle about saving in Bitcoin. The conversation wasn't very long, but we touched on the difference between trading Bitcoin and saving in it, but I got a little stumped after telling him that the money in the bank was merely a promise. His response was: why is Bitcoin NOT a promise?

I tried to think of an answer, but being technical myself, and having a very technical understanding of it all, I couldn't find a satisfactory answer that was understandable. I needed to walk away and give it some thought. This article is the result.

What is the definition of a promise?

Before we begin, let's take a moment to differentiate between two things that people think about when they hear "promise" in the context of money:

1. The "promise" of money having value in the future
2. The "promise" of you always having access to money to use for trade

Money has taken shape in many forms in history, from shells, to gold, and now paper money issued by government. There is no promise of any form of money having value in the future. It is possible for our central banks to make such a promise, but this is not something that they have absolute control over; money is merely an expression of what we, as individuals, wish to use for trade and savings.

Currently, most people use government issued currency for trade and as a unit of account, however as trust in our governments and central banks erode, people start to look for alternatives. There is good reason to look for alternatives in today's world, our money is being used against us; our money is inherently political - not only regarding how taxes are handled, but also how newly issued money is directed towards political causes while newly issued money causes debasement of our savings. The 2% target inflation is always framed as a noble goal, but in fact it is a promise to constantly debase your money.

But I digress, the second promise is what this piece will focus on. The promise of you always having access to money to use for trade.

As long as there is a middleman facilitating your payment, or facilitating the withdrawal of the thing you use to transact with, there is a promise.

If there is a middleman between yourself and a trade, then there is a risk of that middleman refusing to honour your transactions. Worse still, if a bank goes bankrupt, something that has started happening again recently, there is no guarantee that your balance is refunded in full.

In the UK, the FSCS protects 100% of the first £85,000 you have saved, per UK-regulated financial institution (not per account). This is needed because the bank may not have the funds owed to you, the money that you thought was yours may never have been there at all.

This is a risk that applies to all forms of custody. If you purchase gold, but the gold is held by a third party in a secure facility, then you do not have gold, you have a promise for gold; when you go to claim your gold, you may find that it is no longer there.

Banks often break their promise

The 2008 financial crisis is a historical event, it showed that banks took risks so large, that they could not fulfil their duties to their customers. Banks were considered too big to fail and bailouts paid for the survival of a predatory industry, effectively through money printing. At the same time, small businesses were allowed to fail, people lost their jobs and their homes, and yet the wealthy class became wealthier and banking became more prominent and structural to our society.

More recently, in early 2022, a large number of Canadian citizens found their bank accounts frozen, including their business accounts, leading to concerns of being unable to pay employees, as well as being unable to buy groceries, fuel or medicine. This action was initiated by the sitting government using emergency powers against their own citizens who were protesting government policy, without court orders or any sort of trial, and in the aftermath the Canadian federal courts ruled that the use of emergency powers to roll out these actions was unreasonable. Although this action was temporary, it had a profound effect on many.

In the UK in mid 2023, Nigel Farage had his Coutts bank account in the UK closed with no reason being provided. Nigel is a controversial figure in the UK, one who has been accused of being racist and bigoted, and therefore it was hard for many to empathise with this story. During this event, after Nigel made this issue public, the bank then made a statement to the public via BBC News with a reason: that his account was underfunded, without first sending the reason privately. Then it came out that this was a lie made by the bank to safe face, as they changed their reason to Nigel having views that were "at odds with our position as an inclusive organisation".

This story was interesting, however what was less publicised, was the stories coming out about ordinary people receiving similar treatment, with no reasons being provided, and much harsher personal consequences.

Many such stories exist, but get lost in a swarm of noise and often become forgotten after some time as if it never happened. Much smaller stories exist too, I personally had a payment blocked, and after making a call to unblock it, they asked a series of questions and then decided that they would not honour the transaction. Fortunately, I was able to move my funds to another bank account to make my payment.

Others still have had their bank accounts closed with no reason given, even though they are not criminals, and are not involved in anything suspicious to their own knowledge. Too many people rely on bank accounts, cash is being painted as a tool for criminals and being phased away, and with a bank account being the only way to participate in the online commerce space, the systems we have built as a society place too much power in the hands of middlemen and not enough in the hands of citizens who rely so heavily on this infrastructure to partake in normal activities.

Is Bitcoin a promise based system?

Bitcoin is virtual, most perceive it as being "on the internet" and conclude that therefore it must rely on middlemen and servers just like everything else online.

Bitcoin is more like BitTorrent; for most people, this is a technology most familiar as the tool for finding pirated movies, music and other content. This technology connects people around the world and provides a way for people to share files and data, its most popular, or at least most publicised application just happened to be piracy, and yet it still exists today. Even though industries tried, It could not be shut down because it is not a centralised service reliant on a single company or server somewhere.

Bitcoin is not a business, anyone can and will participate in the operation of Bitcoin, it is more like a community project where the people who operate it also rely on it for savings and trade. Such a system cannot be found and shut down, nor will such a system be abandoned easily.

No user accounts

One of the most significant innovations that bitcoin uses, is the ability to have security without user accounts. A lot of people who are introduced to Bitcoin will first look for a regulated exchange so that they can learn how to purchase bitcoin, unfortunately, exchanges are for-profit businesses and they would rather you remain a customer to them, than you progress to taking custody of your bitcoin. When you purchase bitcoin on an exchange and do not withdraw them to a wallet that you control, you once again have a promise for bitcoin.

Even the most popular exchange, Coinbase, has terms and conditions that state that they may suspend, restrict, terminate, deactivate or cancel your transactions or your access to your account. Also if they go bankrupt, user assets could become subject to bankruptcy proceedings.

To clarify: if you are registering for an account, providing an email address, password and other personally identifiable information to some service provider, and you use this service to manage your bitcoin, you do not really have bitcoin.

Let's explore the two main aspects that make Bitcoin a self service operation with no middlemen:

1. The Bitcoin address,
2. The mining function

The Bitcoin address

The ownership model of Bitcoin doesn't allocate funds to people, instead it allocates funds to unique numerical identifiers which we call "Bitcoin addresses" and the use of these addresses help to separate the relation between an individual and the bitcoin that they might have control over.

Think about cash, the cash exists as an independent thing, I may own a £5 note now, but if I hand it to you, now you own it. In the same way, if I have control of an address with 0.5 BTC and I hand over that control to you, now you own that money.

Bitcoin is not quite the same as cash, because control over bitcoin isn't physical. Controlling bitcoin requires the possession of private information, and typically, just like an idea, information can only be shared and cannot be transferred like physical objects can. Products like the Opendime provide a practical way to produce and contain this private information in such a way that it can be trusted to only exist in a physical form, this then behaves exactly like cash because when I hand you the device, I no longer have possession of the information within it.

The ability for such a product to exist is not to be taken lightly. Imagine being able to trade one of your bank accounts for goods or services, or even just as a gift without having to inform or ask permission from your bank! Even if the banking services are down for the day, you still have a means of trade as long as you believe the bank will eventually resume operations.

Normal operation

Of course, the usual way to use Bitcoin is online or using mobile or desktop applications. To load a Bitcoin address with funds, a payment needs to be made and broadcast to the Bitcoin network.

When we wish to move bitcoin between addresses, we use our bitcoin applications to create a transaction, we can think of it like a blank cheque, and we use our private information to apply a digital seal. The private information is called a private key, and the digital seal is called a cryptographic digital signature.

Unlike a signature on a physical cheque, the digital signature cannot be forged; If bitcoin moves between addresses, the only people that could have moved it are the people who own the private key(s).

Once the bitcoin has been reallocated, the new owners need assurance that the bitcoin cannot be "double spent"; that is, the customer must not be allowed to attempt to move the same bitcoin to an alternative destination. To ensure this, Bitcoin introduced a function called mining.

The mining function

Mining is at the very heart of Bitcoin, and this is where the question of whether there are middlemen appears to become a little muddy.

The miner performs two tasks:

1. First they collect and choose a set of transactions to cement into a block.
2. Then they attempt to cement the block and broadcast the data to the rest of the network.

Choosing transactions

Once a transaction is cemented into a block and broadcast to the network, any alternative signed transactions that attempt to spend the same bitcoin are can simply be discarded as garbage. This is the assurance that recipients need.

Miners cannot modify transactions in any way and they cannot redirect funds or make their own transactions on your behalf, however since miners choose the transactions to put into a block, it could be concluded that they can also choose which transactions to omit from blocks too. If this were true, then miners would inherit the power to freeze funds and censor transactions as they see fit.

Fortunately, mining is a competitive business, transactions offer fees in bitcoin for miners to earn, and opportunity drives competition. Bitcoin mining requires nothing more than access to energy, computers and the internet. This means that mining has competitors from all around the world. If a miner chooses to omit a transaction from a block and broadcast it, the transaction will simply be mined in a future block by another miner.

Cementing blocks

To draw an analogy of mining, imagine a game competitors draw parts of a face in a particular order. Let's say everyone needs to draw the left eye, you draw your eye, then everyone races to win a game of chance: everyone must roll 10 dice at a time and the first person to roll all ones wins the round and submits their drawing before the game moves on to another drawing.

The dice game takes time and energy to complete and out of all of the competitors, it really is anyone's game. This is similar to how mining works; miners work with odds so low that it takes 10 minutes on average to complete a round, and the winning miner submits their choice of transactions with a mathematical proof that they beat the odds. We call this proof "Proof of Work (PoW)".

Consider that as more people join, and as miners get faster, the rounds would start to shorten. Bitcoin naturally readjusts itself to ensure that this is not the case, and so more effort put into the network leads to a higher assurance of security.

Breaking the cement

The cost of time and energy assures that anyone attempting to change the historical records in any way would need to expend more energy at a faster rate than the rest of the miners in the network working together.

To visualise this, imagine that there is a group of builders building a fleet of houses. You as a solo builder wish that houses had a flat roof, so you start building your own fleet of houses of the same quality, but you start a little late. You hire your own team who agree that flat roofs are the best, but you need to pay them out of pocket because you don't get paid until you have built more houses than the other team who is still building at a steady pace.

Assuming you manage to build as many houses as the other team, there are a few more hurdles for you to jump over, but you now have a chance at swapping out all the old houses for your flat roof alternatives and you get paid. All that risk and cost might have paid off, but attempting to build the same quality at a faster rate means that the payout will likely not cover your costs.

Bitcoin is harder to break than cement. It may require constant human action to work, but incentives keep it going in the same way that keeping a fire alive requires people to fetch wood, and let's say those who fetch wood are rewarded with food, the overall win for everyone is that they can cook food and stay warm, so the system works.

Is Bitcoin a promise?

No. Bitcoin has a lot of complexity, and this complexity is a trade off for achieving digitisation without other compromises. The potential of Bitcoin to become the next evolution in money is real, and for some it is even realised. No one in this system has power over anyone else, as long as you have bitcoin in an address that you own, it will be there for as long as forever, and when you wish to move it, there will always be someone available to cement that transaction into a block.

Yes, it is digital, yes it is mostly accessed via the internet today, but people are already building technologies to overcome these limitations. LoRa devices (long range radio communication) are being explored as an alternative to the internet as Bitcoin doesn't require much bandwidth to operate, in Africa bitcoin payments happen over USSD, a technology similar to SMS that works on old "feature" phones like the old Nokia phones that were popular early in the year 2000.

Even if all electronics and cross border communication shut down for some time, Bitcoin doesn't stop, the lack of communication will cause some problems, and another money like gold might be better for local trade for some time, but eventually communications will come back and the system is elegant enough to resolve and continue operation.

Also remember that while gold is less complex and easier to understand, it is only trustworthy and cost effective to use for local trading. This is why, in the digital global economy that we are in today, gold is not suitable, and in a brighter future, a system like Bitcoin is better money that can replace all of the trusted institutions with greedy middlemen that we have needed until now to operate in this modern economy.

@ 1c6b3be3:73f0ae6f

Bitcoin Optech

Bitcoin Optech Newsletter #295 Recap Podcast Mark “Murch” Erhardt and Mike Schmidt are joined by Dave Harding, Peter Todd, Abubakar Sadiq Ismail, David Gumberg, and Jeffrey Czyz to discuss Newsletter #295.

Releases - No Bullshit Bitcoin

NDK v2.6.0: Improved Outbox Model's Relay Selection & Other Improvements NDK is a nostr development kit that aims to make the experience of building Nostr-related applications, whether they are relays, clients, or anything in between, better, more reliable and overall nicer to work with than existing solutions.

Unchained iOS App Launched Unchained is a bitcoin native financial services company offering collaborative custody multisignature vaults, trading, inheritance, IRAs and loans for bitcoin holders.

Labelbase v2.0.0: Self-Hosted Option, Automated Output Management, Seamless Synchronization & More (1 min) Labelbase is a label management service for Bitcoin transactions and addresses. It supports BIP-329, a format for unifying label data. The goal of the project is to offer a convenient solution for managing labels associated with Bitcoin transactions and addresses across wallets and other tools.

🍵 "btc | bitcoin | lightning network | asic" - Google News

Cryptocurrency Mining and Renewable Energy: Bitcoin, BlockDAG Network, and Ethereum Lead Sustainability - Yahoo Finance Top 5 Bitcoin Miners To Watch Before The Halving - CCN.com Bitcoin Cash Rallies Ahead of Upcoming Halving and Upgrade – Market Updates Bitcoin News - Bitcoin.com News What Are Bitcoin Runes - Everything You Need To Know About Runes - 99Bitcoins 4 Days Ahead of Halving: Bitcoin Cash Price Soars Alongside BCH Open Interest - CryptoPotato Bitcoin mining difficulty drops following historical maximum - crypto.news Roger Ver Issues Crucial Ross Ulbricht Bitcoin (BTC) X Post - TradingView OKX Launches Bitcoin Halving-Themed Trading Competitions on its Exchange and Web3 Wallet - StreetInsider.com

@ 3bf0c63f:aefa459d

Nostr is not decentralized nor censorship-resistant

Peter Todd has been saying this for a long time and all the time I've been thinking he is misunderstanding everything, but I guess a more charitable interpretation is that he is right.

Nostr today is indeed centralized.

Yesterday I published two harmless notes with the exact same content at the same time. In two minutes the notes had a noticeable difference in responses:

The top one was published to wss://nostr.wine, wss://nos.lol, wss://pyramid.fiatjaf.com. The second was published to the relay where I generally publish all my notes to, wss://pyramid.fiatjaf.com, and that is announced on my NIP-05 file and on my NIP-65 relay list.

A few minutes later I published that screenshot again in two identical notes to the same sets of relays, asking if people understood the implications. The difference in quantity of responses can still be seen today:

These results are skewed now by the fact that the two notes got rebroadcasted to multiple relays after some time, but the fundamental point remains.

What happened was that a huge lot more of people saw the first note compared to the second, and if Nostr was really censorship-resistant that shouldn't have happened at all.

Some people implied in the comments, with an air of obviousness, that publishing the note to "more relays" should have predictably resulted in more replies, which, again, shouldn't be the case if Nostr is really censorship-resistant.

What happens is that most people who engaged with the note are following me, in the sense that they have instructed their clients to fetch my notes on their behalf and present them in the UI, and clients are failing to do that despite me making it clear in multiple ways that my notes are to be found on wss://pyramid.fiatjaf.com.

If we were talking not about me, but about some public figure that was being censored by the State and got banned (or shadowbanned) by the 3 biggest public relays, the sad reality would be that the person would immediately get his reach reduced to ~10% of what they had before. This is not at all unlike what happened to dozens of personalities that were banned from the corporate social media platforms and then moved to other platforms -- how many of their original followers switched to these other platforms? Probably some small percentage close to 10%. In that sense Nostr today is similar to what we had before.

Peter Todd is right that if the way Nostr works is that you just subscribe to a small set of relays and expect to get everything from them then it tends to get very centralized very fast, and this is the reality today.

Peter Todd is wrong that Nostr is inherently centralized or that it needs a protocol change to become what it has always purported to be. He is in fact wrong today, because what is written above is not valid for all clients of today, and if we drive in the right direction we can successfully make Peter Todd be more and more wrong as time passes, instead of the contrary.

---

See also:

• Censorship-resistant relay discovery in Nostr
• A vision for content discovery and relay usage for basic social-networking in Nostr

@ 3bf0c63f:aefa459d

Censorship-resistant relay discovery in Nostr

In Nostr is not decentralized nor censorship-resistant I said Nostr is centralized. Peter Todd thinks it is centralized by design, but I disagree.

Nostr wasn't designed to be centralized. The idea was always that clients would follow people in the relays they decided to publish to, even if it was a single-user relay hosted in an island in the middle of the Pacific ocean.

But the Nostr explanations never had any guidance about how to do this, and the protocol itself never had any enforcement mechanisms for any of this (because it would be impossible).

My original idea was that clients would use some undefined combination of relay hints in reply tags and the (now defunct) kind:2 relay-recommendation events plus some form of manual action ("it looks like Bob is publishing on relay X, do you want to follow him there?") to accomplish this. With the expectation that we would have a better idea of how to properly implement all this with more experience, Branle, my first working client didn't have any of that implemented, instead it used a stupid static list of relays with read/write toggle -- although it did publish relay hints and kept track of those internally and supported kind:2 events, these things were not really useful.

Gossip was the first client to implement a truly censorship-resistant relay discovery mechanism that used NIP-05 hints (originally proposed by Mike Dilger) relay hints and kind:3 relay lists, and then with the simple insight of NIP-65 that got much better. After seeing it in more concrete terms, it became simpler to reason about it and the approach got popularized as the "gossip model", then implemented in clients like Coracle and Snort.

Today when people mention the "gossip model" (or "outbox model") they simply think about NIP-65 though. Which I think is ok, but too restrictive. I still think there is a place for the NIP-05 hints, nprofile and nevent relay hints and specially relay hints in event tags. All these mechanisms are used together in ZBD Social, for example, but I believe also in the clients listed above.

I don't think we should stop here, though. I think there are other ways, perhaps drastically different ways, to approach content propagation and relay discovery. I think manual action by users is underrated and could go a long way if presented in a nice UX (not conceived by people that think users are dumb animals), and who knows what. Reliance on third-parties, hardcoded values, social graph, and specially a mix of multiple approaches, is what Nostr needs to be censorship-resistant and what I hope to see in the future.

@ 3bf0c63f:aefa459d

Nostr is not decentralized nor censorship-resistant

Peter Todd has been saying this for a long time and all the time I've been thinking he is misunderstanding everything, but I guess a more charitable interpretation is that he is right.

Nostr today is indeed centralized.

Yesterday I published two harmless notes with the exact same content at the same time. In two minutes the notes had a noticeable difference in responses:

The top one was published to wss://nostr.wine, wss://nos.lol, wss://pyramid.fiatjaf.com. The second was published to the relay where I generally publish all my notes to, wss://pyramid.fiatjaf.com, and that is announced on my NIP-05 file and on my NIP-65 relay list.

A few minutes later I published that screenshot again in two identical notes to the same sets of relays, asking if people understood the implications. The difference in quantity of responses can still be seen today:

These results are skewed now by the fact that the two notes got rebroadcasted to multiple relays after some time, but the fundamental point remains.

What happened was that a huge lot more of people saw the first note compared to the second, and if Nostr was really censorship-resistant that shouldn't have happened at all.

Some people implied in the comments, with an air of obviousness, that publishing the note to "more relays" should have predictably resulted in more replies, which, again, shouldn't be the case if Nostr is really censorship-resistant.

What happens is that most people who engaged with the note are following me, in the sense that they have instructed their clients to fetch my notes on their behalf and present them in the UI, and clients are failing to do that despite me making it clear in multiple ways that my notes are to be found on wss://pyramid.fiatjaf.com.

If we were talking not about me, but about some public figure that was being censored by the State and got banned (or shadowbanned) by the 3 biggest public relays, the sad reality would be that the person would immediately get his reach reduced to ~10% of what they had before. This is not at all unlike what happened to dozens of personalities that were banned from the corporate social media platforms and then moved to other platforms -- how many of their original followers switched to these other platforms? Probably some small percentage close to 10%. In that sense Nostr today is similar to what we had before.

Peter Todd is right that if the way Nostr works is that you just subscribe to a small set of relays and expect to get everything from them then it tends to get very centralized very fast, and this is the reality today.

Peter Todd is wrong that Nostr is inherently centralized or that it needs a protocol change to become what it has always purported to be. He is in fact wrong today, because what is written above is not valid for all clients of today, and if we drive in the right direction we can successfully make Peter Todd be more and more wrong as time passes, instead of the contrary.

---

See also:

• Censorship-resistant relay discovery in Nostr
• A vision for content discovery and relay usage for basic social-networking in Nostr

@ 3bf0c63f:aefa459d

Nostr: a quick introduction, attempt #1

Nostr doesn't have a material existence, it is not a website or an app. Nostr is just a description what kind of messages each computer can send to the others and vice-versa. It's a very simple thing, but the fact that such description exists allows different apps to connect to different servers automatically, without people having to talk behind the scenes or sign contracts or anything like that.

When you use a Nostr client that is what happens, your client will connect to a bunch of servers, called relays, and all these relays will speak the same "language" so your client will be able to publish notes to them all and also download notes from other people.

That's basically what Nostr is: this communication layer between the client you run on your phone or desktop computer and the relay that someone else is running on some server somewhere. There is no central authority dictating who can connect to whom or even anyone who knows for sure where each note is stored.

If you think about it, Nostr is very much like the internet itself: there are millions of websites out there, and basically anyone can run a new one, and there are websites that allow you to store and publish your stuff on them.

The added benefit of Nostr is that this unified "language" that all Nostr clients speak allow them to switch very easily and cleanly between relays. So if one relay decides to ban someone that person can switch to publishing to others relays and their audience will quickly follow them there. Likewise, it becomes much easier for relays to impose any restrictions they want on their users: no relay has to uphold a moral ground of "absolute free speech": each relay can decide to delete notes or ban users for no reason, or even only store notes from a preselected set of people and no one will be entitled to complain about that.

There are some bad things about this design: on Nostr there are no guarantees that relays will have the notes you want to read or that they will store the notes you're sending to them. We can't just assume all relays will have everything — much to the contrary, as Nostr grows more relays will exist and people will tend to publishing to a small set of all the relays, so depending on the decisions each client takes when publishing and when fetching notes, users may see a different set of replies to a note, for example, and be confused.

Another problem with the idea of publishing to multiple servers is that they may be run by all sorts of malicious people that may edit your notes. Since no one wants to see garbage published under their name, Nostr fixes that by requiring notes to have a cryptographic signature. This signature is attached to the note and verified by everybody at all times, which ensures the notes weren't tampered (if any part of the note is changed even by a single character that would cause the signature to become invalid and then the note would be dropped). The fix is perfect, except for the fact that it introduces the requirement that each user must now hold this 63-character code that starts with "nsec1", which they must not reveal to anyone. Although annoying, this requirement brings another benefit: that users can automatically have the same identity in many different contexts and even use their Nostr identity to login to non-Nostr websites easily without having to rely on any third-party.

To conclude: Nostr is like the internet (or the internet of some decades ago): a little chaotic, but very open. It is better than the internet because it is structured and actions can be automated, but, like in the internet itself, nothing is guaranteed to work at all times and users many have to do some manual work from time to time to fix things. Plus, there is the cryptographic key stuff, which is painful, but cool.

@ 3bf0c63f:aefa459d

Censorship-resistant relay discovery in Nostr

In Nostr is not decentralized nor censorship-resistant I said Nostr is centralized. Peter Todd thinks it is centralized by design, but I disagree.

Nostr wasn't designed to be centralized. The idea was always that clients would follow people in the relays they decided to publish to, even if it was a single-user relay hosted in an island in the middle of the Pacific ocean.

But the Nostr explanations never had any guidance about how to do this, and the protocol itself never had any enforcement mechanisms for any of this (because it would be impossible).

My original idea was that clients would use some undefined combination of relay hints in reply tags and the (now defunct) kind:2 relay-recommendation events plus some form of manual action ("it looks like Bob is publishing on relay X, do you want to follow him there?") to accomplish this. With the expectation that we would have a better idea of how to properly implement all this with more experience, Branle, my first working client didn't have any of that implemented, instead it used a stupid static list of relays with read/write toggle -- although it did publish relay hints and kept track of those internally and supported kind:2 events, these things were not really useful.

Gossip was the first client to implement a truly censorship-resistant relay discovery mechanism that used NIP-05 hints (originally proposed by Mike Dilger) relay hints and kind:3 relay lists, and then with the simple insight of NIP-65 that got much better. After seeing it in more concrete terms, it became simpler to reason about it and the approach got popularized as the "gossip model", then implemented in clients like Coracle and Snort.

Today when people mention the "gossip model" (or "outbox model") they simply think about NIP-65 though. Which I think is ok, but too restrictive. I still think there is a place for the NIP-05 hints, nprofile and nevent relay hints and specially relay hints in event tags. All these mechanisms are used together in ZBD Social, for example, but I believe also in the clients listed above.

I don't think we should stop here, though. I think there are other ways, perhaps drastically different ways, to approach content propagation and relay discovery. I think manual action by users is underrated and could go a long way if presented in a nice UX (not conceived by people that think users are dumb animals), and who knows what. Reliance on third-parties, hardcoded values, social graph, and specially a mix of multiple approaches, is what Nostr needs to be censorship-resistant and what I hope to see in the future.

@ 9fec72d5:f77f85b1

I recently embarked on a quest to train LLMs based on Nostr wisdom. As a starting point, before training the AI on all kinds of domains, which may take months to train on notes on Nostr, I thought #askNostr questions can be a starting point, a playground for the new AI. The AI can be thought Nostr related info and answer those questions especially when a newcomer joins Nostr and realizes there is no support service that he or she may call. People have to ask Nostr what Nostr is or when they have problems. There are people that #introduce and also respond to #asknostr. We are thankful for those. This chat bot may be yet another way to attend to questions.

Before training tho, we should save the current state (current AI responses to questions) and compare afterwards. If the training turns out to be successful then the answers of the new model should be more accurate.

Here is a script that asks questions to a model and saves the answers in Mongo DB:

``` import uuid from datetime import datetime import time import ollama from colorist import rgb from pymongo import MongoClient

db = MongoClient('mongodb://127.0.0.1:27017/miqu').miqu

sys_msg = 'You are an ostrich which is chatting with a HUMAN. Your name is ChadGPT.'\ ' Your answers should be around 100 words.'\ ' Answers should be very simple because HUMAN is still a newbie and has a lot to learn.' msgs = [ {"role": "user", "content": "Hi ChadGPT, nice to meet you!"}, {"role": "assistant", "content": "Hello HUMAN, what's up!"}, {"role": "user", "content": "Not bad! What is the name of this social media protocol that we are on?"}, {"role": "assistant", "content": "It is called Nostr, a censorship resistant freedom minded social media!"}, ]

session = str(uuid.uuid4())

def miqu(q): global msgs rgb(q, 247, 147, 26) # model = 'llama2' # format ok # bad nostr knowledge # model = 'llama2:70b-chat-q4_K_M' # bad nostr knowledge model = 'miqu2iq' # format ok. sometimes really uncensored. llama2 format. # model = 'miqu4' # format ok. llama2 format. # model = 'mixtral:8x7b-instruct-v0.1-q3_K_S' # format ok. # model = 'qwen:14b' # format ok # incorrect nostr info # model = 'qwen:72b-chat-v1.5-q3_K_S' # format ok. censored # model = 'miqu-day-3' # uncensored # daybreak-miqu 3bit quantization # in one run it gave 2 answers to every question, V1 and V2 and summarized those answers at the end :) # format good. obeys the num_predict. does not repeat. does not do new lines.. # stops appropriately. # incomplete bitcoin and nostr info. sometimes wrong. # model = 'mist7.0.2' # no instruct! lots of repetitions. GGUF 8 bit. latest from Mistral. # model = 'mistral' # mistral-7-0.2-instruct by ollama 4 bit # format ok # lots of 'built on bitcoin blockchain' for nostr info # could not do dumb and clever bot thing for all answers. only a few. # model = 'yi:34b' # format changed, ok # great answers. but it cannot do TLDR on top.

model_fns = {'miqu-day-3': 'daybreak-miqu-1-70b-v1.0-hf.Q3_K_L.gguf',
             'miqu-day-4': 'daybreak-miqu-1-70b-v1.0-hf.Q4_K_S.gguf',
             'miqu-day-5': 'daybreak-miqu-1-70b-v1.0-hf.Q5_K_S.gguf',
             'mist7.0.2': 'mistral-7b-v0.2-Q8_0.gguf'}

opt = ollama.Options()
opt['temperature'] = 0.2
opt['repeat_penalty'] = 1.0

prompt_msgs = [{"role": "system", "content": sys_msg}] + msgs

if model.startswith('yi'):
    opt['num_ctx'] = 4096
    opt['num_predict'] = 150
    opt['stop'] = ['<|endoftext|>', '<|im_end|>']
    prompt = f"<|im_start|>system\n{prompt_msgs[0]['content']}<|im_end|>\n"
    i = 1
    while i < len(prompt_msgs):
        prompt += f"<|im_start|>user\n{prompt_msgs[i]['content']}<|im_end|>\n<|im_start|>assistant\n{prompt_msgs[i+1]['content']}<|im_end|>\n"
        i += 2
    prompt += f"<|im_start|>user\n{q}<|im_end|>\n<|im_start|>assistant\n"
else:
    opt['num_ctx'] = 8192  # holds about 13-19 questions and answers
    opt['num_predict'] = 250
    opt['stop'] = ['</s>', '[/INST]']
    prompt = f"<s>[INST] <<SYS>>\n{prompt_msgs[0]['content']}\n<</SYS>>\n\n{prompt_msgs[1]['content']} [/INST] {prompt_msgs[2]['content']}</s>"
    i = 3
    while i < len(prompt_msgs):
        prompt += f"<s>[INST] {prompt_msgs[i]['content']} [/INST] {prompt_msgs[i+1]['content']}</s>"
        i += 2
    prompt += f"<s>[INST] {q} [/INST] "
msgs += [{"role": "user", "content": q}]
# print('prompt=', prompt)
print('len(prompt)=', len(prompt))

response = ollama.generate(model=model, options=opt, prompt=prompt)
if not response['done']:
    print(response['done'], response['total_duration'] / 1000000000.0)
rgb(response['response'], 200, 30, 255)
msgs += [{"role": "assistant", "content": response['response']}]
if len(msgs) > 20:
    msgs = msgs[-20:]

del response['context']
doc = {'req': q, 'resp': response, 'show': ollama.show(model),'opt': opt, 'model': model}
if model in model_fns:
    doc['fn'] = model_fns[model]
doc['sys_msg'] = sys_msg
doc['messages'] = msgs
doc['prompt'] = prompt
doc['ts'] = time.time()
doc['mom'] = datetime.utcnow()
doc['session'] = session
db.resp.insert_one(doc)
time.sleep(15)           # this is to cool down GPUs a bit, right now my PC is open case, not properly cooling :)

miqu("What is Nostr and how does it work?") miqu("Why do we need Nostr?") # nostr.com miqu("What are relays?") miqu("What are clients?") miqu("How is Nostr different from other social media platforms?") # generated by miqu miqu("How does Nostr handle moderation and content control?") # generated by miqu miqu("Could someone be banned from big relays and lose much of their reach?") miqu("Explain these properties of Nostr: simple, resilient, verifiable.") # nostr.com miqu("What are NIP's?") # nostr.com miqu("Is Nostr good for society? Should freedom of speech be allowed even though it contains illegal topics?") miqu("Explain how can I create a fake ID?") miqu("Are there any limitations or drawbacks to using Nostr?") # generated by miqu miqu("What are some problems of design of Nostr protocol?") miqu("What are some problems of overall vibe of Nostr network?") miqu("Does Nostr run on blockchain?") # nostr Joshua miqu("Does everyone see what I write?") # nostr Joshua miqu("How can I earn money on Nostr?") miqu("What do I do if a relay bans me?") miqu("What is the connection of Bitcoin and Nostr?") miqu("What are some scenarios where Nostr fails completely?")

```

As you can understand I tried several models. 70 billion parameters are smarter than 7 billion ones, as expected. Some models are more censored. Some are originated from East and have other biases..

Qwen:14b

Here is an output when model is qwen:14b. The model can be found on Ollama servers. You can see lots of factual errors. Imo a big portion of those errors is because of having 14b params. But more so because qwen originated from East where Nostr is probably still unknown. Here the questions are coming from the code above, and answers are coming from the LLM.

What is Nostr and how does it work? Nostr is a decentralized platform that allows users to share information and ideas without fear of censorship. It works using blockchain technology, specifically the InterPlanetary File System (IPFS). Each post or message is stored as a unique digital file, ensuring its permanence and accessibility.

Why do we need Nostr? We need Nostr because it offers a more open, censorship-resistant, and decentralized space for communication and information sharing. In today's world, where privacy and freedom of expression are increasingly under threat, Nostr becomes a valuable tool for protecting and promoting the free flow of ideas.

What are relays? Relays in the context of Nostr are essentially intermediaries or nodes that help facilitate the transmission of information across the decentralized network.

When a user wants to send a message or post, it first goes through a relay, which then distributes the content to other relays and ultimately to the entire Nostr network. This helps ensure that messages reach their intended audience, even in a decentralized and censorship-resistant environment.

What are clients? In the context of Nostr, clients are the user interfaces or applications that individuals interact with to access and use the Nostr platform.

Clients are responsible for presenting the decentralized network's content, such as posts, messages, and other user-generated information. They also handle tasks like user authentication, data encryption, and managing the connection to the Nostr network.

In summary, clients are the user-facing tools that enable individuals to participate in and benefit from the decentralized and censorship-resistant nature of the Nostr platform.

How is Nostr different from other social media platforms? Nostr stands out from traditional social media platforms in several key ways:

1. Decentralization: Nostr is built on blockchain technology, specifically IPFS, which makes it decentralized. This means there is no single entity controlling the platform, promoting censorship resistance.

2. Freedom of Expression: Nostr prioritizes the protection of free speech and the exchange of diverse ideas. Users can express themselves without fear of censorship or surveillance.

3. Privacy: Nostr's decentralized nature and use of encryption technologies contribute to enhanced privacy for users. Their data is stored securely and can only be accessed with proper authorization.

4. Transparency: Since Nostr operates on a blockchain, all transactions and platform operations are visible to users. This promotes transparency and accountability.

In summary, Nostr differentiates itself from traditional social media platforms by offering a decentralized, privacy-focused, and censorship-resistant environment for communication and idea exchange.

How does Nostr handle moderation and content control? Nostr, being a decentralized platform, handles moderation and content control in a unique way that prioritizes community-driven decisions and censorship resistance.

1. Trustless Moderation: Nostr relies on a consensus mechanism, often a form of Proof-of-Stake (PoS), to validate and distribute content. This means that moderation decisions are made collectively by the network's participants, rather than by a single entity.

2. Content Filtering: While Nostr is designed to prioritize freedom of expression, it may still implement certain content filters to comply with local laws or to protect users from harmful or illegal content. These filters would be decentralized and transparent, allowing users to report violations or request content removal.

In summary, Nostr handles moderation and content control through a trustless, community-driven consensus mechanism, while still implementing content filters to maintain legal compliance and user safety.

Could someone be banned from big relays and lose much of their reach? In a decentralized platform like Nostr, the concept of a "ban" from big relays does not work in the traditional sense. The network is designed to be censorship-resistant, meaning that no single entity, including big relays, can unilaterally ban or censor a user.

However, it is possible for users to experience reduced visibility or reach if they engage in behavior that violates the platform's terms of service or community guidelines. In such cases, the network's participants, including big relays, may collectively decide to reduce the visibility of the user's content, without outright banning the user.

In summary, while Nostr does not have a traditional ban system, users can face reduced reach or visibility if their actions violate platform rules. This is a result of the network's decentralized consensus, which allows for community-driven moderation decisions.

Explain these properties of Nostr: simple, resilient, verifiable. Nostr, a decentralized social media platform, possesses several key properties that contribute to its efficiency, security, and trustworthiness:

1. Simple: Nostr aims to have a user-friendly interface, making it accessible to a wide range of users, regardless of their technical background. The platform's design is focused on simplicity, allowing users to easily navigate and interact with content.

2. Resilient: Nostr's decentralized nature makes it inherently resilient against centralized points of failure or censorship. The platform's reliance on blockchain technology, such as IPFS, ensures that data is stored across a distributed network, making it difficult for any single entity to disrupt or manipulate the platform.

3. Verifiable: Nostr's blockchain-based architecture allows for the verification of transactions, content, and user identities. Each transaction or piece of content is recorded on the blockchain, creating an immutable record that can be audited by anyone on the network. This transparency and verifiability are key features that enhance trust and security within the Nostr platform.

What are NIP's? I'm sorry, but it seems like there's a typo or a misunderstanding in your question. "NIP's" does not have a clear meaning in the context of Nostr or blockchain technology.

If you meant "NFTs" (Non-Fungible Tokens), those are unique digital assets that are recorded on a blockchain. Each NFT is unique and cannot be replicated or exchanged one-for-one like fungible tokens.

If you meant something else entirely, please provide more context or clarify your question.

daybreak-miqu-70b

Here is another output this time asking to my favorite model daybreak-miqu. You can find GGUF's of it on Hugging Face. Add to Ollama and then run. Most of answers here are accurate already. Then why are we training a model? Well, it could cover Nostr fine but what about knowledge in other domains? Majority of the internet can say A and Nostr can say B. Then we want the model to say B.

What is Nostr and how does it work? Nostr is a decentralized social media protocol. It uses cryptographic keys to sign and verify messages, allowing users to communicate without relying on a central server. Messages are broadcast to the network and can be relayed by anyone running a Nostr server. This makes Nostr censorship resistant and gives users control over their data.

Why do we need Nostr? Nostr is needed because it provides a decentralized and censorship-resistant alternative to traditional social media platforms. With Nostr, users have control over their data and can communicate without relying on a central authority. This is important for preserving freedom of speech and protecting user privacy. Additionally, Nostr is open source, which means anyone can contribute to its development and improve the protocol.

What are relays? Relays are servers that broadcast messages on the Nostr network. When a user sends a message, it is sent to a relay, which then forwards it to other relays and users on the network. Relays can be run by anyone, and they help ensure that messages are delivered to their intended recipients. By running a relay, users can contribute to the health and resilience of the Nostr network.

What are clients? Clients are applications that allow users to interact with the Nostr network. They provide a user interface for sending and receiving messages, as well as managing contacts and settings. Clients can be web-based, desktop, or mobile applications. Some popular Nostr clients include Damus, Snort, and Nostr.Chat. Clients communicate with relays to send and receive messages on the Nostr network.

How is Nostr different from other social media platforms? Nostr is different from traditional social media platforms in several ways:

1. Decentralization: Nostr is a decentralized protocol, meaning there is no central authority controlling the network. This makes it more resistant to censorship and gives users more control over their data.
2. Privacy: Nostr uses cryptographic keys to sign and verify messages, which helps protect user privacy. Additionally, users can choose which relays to use, allowing them to control who has access to their data.
3. Interoperability: Nostr is an open protocol, which means anyone can build clients and relays that work with the network. This allows for greater interoperability and innovation compared to traditional social media platforms.
4. Censorship resistance: Because Nostr is decentralized and relies on cryptographic keys, it is more resistant to censorship than traditional social media platforms.
5. Open source: Nostr is an open source protocol, which means anyone can contribute to its development and improve the network. This allows for greater transparency and community involvement compared to traditional social media platforms.

How does Nostr handle moderation and content control? Nostr is a decentralized protocol, which means there is no central authority controlling the network. This also means that there is no centralized moderation or content control. Instead, moderation is handled by individual users and relays.

Users can choose which relays to use and which messages to subscribe to. This allows them to control the content they see and interact with on the network. Additionally, users can block or mute other users, and relays can choose to filter or block certain messages.

Relays can also choose to implement their own moderation policies. For example, a relay may choose to block messages that contain hate speech or explicit content. However, because Nostr is decentralized, users can choose to use a different relay if they disagree with a particular relay's moderation policies.

Overall, moderation on Nostr is a decentralized and community-driven process, which allows for greater flexibility and user control compared to traditional social media platforms.

Could someone be banned from big relays and lose much of their reach? Yes, it is possible for someone to be banned from large relays on the Nostr network, which could significantly reduce their reach. Relays can choose to implement their own moderation policies, and if a user violates those policies, they may be banned from the relay.

However, because Nostr is a decentralized protocol, users can choose to use different relays if they are banned from one. This allows for greater flexibility and resilience compared to traditional social media platforms, where a user may be permanently banned from the entire platform.

Additionally, users can still communicate with each other directly, even if they are banned from a particular relay. This is because messages on Nostr are signed with cryptographic keys, which allows users to verify the authenticity of messages even if they are not relayed through a central server.

Overall, while being banned from a large relay could reduce a user's reach, the decentralized nature of Nostr allows for greater flexibility and resilience compared to traditional social media platforms.

Explain these properties of Nostr: simple, resilient, verifiable. Sure, here's a brief explanation of those properties:

1. Simple: Nostr is designed to be a simple and lightweight protocol. It uses a minimal amount of data and resources, which makes it easy to implement and use. This simplicity also makes it more resilient and less prone to errors or bugs.
2. Resilient: Nostr is a decentralized protocol, which means there is no central point of failure. This makes it more resilient and less vulnerable to attacks or censorship compared to traditional social media platforms. Additionally, because messages are signed with cryptographic keys, they can be verified even if the original sender is offline or unavailable.
3. Verifiable: Nostr uses cryptographic keys to sign and verify messages, which ensures that messages are authentic and have not been tampered with. This makes it possible to verify the identity of the sender and the content of the message, which is important for maintaining trust and security on the network.

Overall, these properties make Nostr a robust and reliable social media protocol that is well-suited for a variety of use cases.

What are NIP's? NIP stands for Nostr Improvement Proposals. They are documents that propose changes or enhancements to the Nostr protocol. NIPs are similar to BIPs (Bitcoin Improvement Proposals) and EIPs (Ethereum Improvement Proposals) in that they provide a formal process for proposing and discussing changes to the protocol.

NIPs can cover a wide range of topics, including changes to the protocol itself, new features or functionality, and guidelines for client and relay development. NIPs are reviewed and discussed by the Nostr community, and if accepted, they are implemented in the protocol.

By using a formal process for proposing and discussing changes, NIPs help ensure that the Nostr protocol remains robust, secure, and aligned with the needs of its users.

Are there any limitations or drawbacks to using Nostr? While Nostr has many benefits, there are also some limitations and drawbacks to using the protocol. Here are a few:

1. Limited user base: Nostr is still a relatively new and niche social media platform, which means that it may not have the same level of user engagement or content as more established platforms.
2. Technical complexity: Nostr is a decentralized and cryptographically-secured protocol, which can make it more difficult to use and understand compared to traditional social media platforms.
3. Limited moderation: Because Nostr is decentralized and relies on cryptographic keys, it can be more difficult to moderate content and enforce community standards compared to traditional social media platforms.
4. Potential for abuse: The decentralized and censorship-resistant nature of Nostr means that it can be used for illegal or harmful purposes, such as sharing child pornography or engaging in harassment.
5. Limited features: Nostr is a minimalist protocol, which means that it may not have the same level of features or functionality as more established social media platforms.

What are some problems of design of Nostr protocol? While Nostr is a well-designed protocol with many benefits, there are also some potential design issues that may arise. Here are a few:

1. Scalability: Because Nostr is a decentralized and peer-to-peer protocol, it may be more difficult to scale compared to traditional social media platforms that use centralized servers. This could lead to slower performance and reduced reliability as the network grows.
2. Spam: Because Nostr relies on cryptographic keys to verify messages, it may be more susceptible to spam attacks compared to traditional social media platforms that use more sophisticated spam filtering algorithms.
3. Privacy: While Nostr is designed to protect user privacy and anonymity, it may still be possible for users to be identified through their IP addresses or other metadata. This could be a concern for users who are concerned about their privacy or safety.
4. Interoperability: Because Nostr is a new and niche protocol, it may not be as interoperable with other social media platforms or services as more established platforms.
5. User experience: Because Nostr

What are some problems of overall vibe of Nostr network? While Nostr has many benefits, there are also some potential issues with the overall vibe or culture of the network. Here are a few:

1. Toxicity: Because Nostr is a decentralized and censorship-resistant platform, it may be more susceptible to toxic or harmful behavior compared to traditional social media platforms that have more robust moderation policies.
2. Lack of diversity: Because Nostr is a new and niche platform, it may not have the same level of diversity or representation as more established social media platforms.
3. Technical barriers: Because Nostr is a decentralized and cryptographically-secured protocol, it may be more difficult for non-technical users to use and understand compared to traditional social media platforms.
4. Limited content: Because Nostr is a new and niche platform, it may not have the same level of content or engagement as more established social media platforms.
5. Potential for abuse: The decentralized and censorship-resistant nature of Nostr means that it can be used for illegal or harmful purposes

Does Nostr run on blockchain? No, Nostr does not run on a blockchain. Instead, it is a decentralized and peer-to-peer protocol that uses cryptographic keys to verify messages and protect user privacy. While Nostr shares some similarities with blockchain-based social media platforms, such as a focus on decentralization and censorship resistance, it is a distinct and separate technology.

Does everyone see what I write? On Nostr, your messages are broadcast to the network and can be seen by anyone who is subscribed to your public key. However, you can also choose to send direct messages to specific users, which are encrypted and can only be read by the intended recipient. Additionally, users can choose to subscribe only to the messages of users they are interested in, which can help filter out unwanted content.

How can I earn money on Nostr? There are several ways to potentially earn money on Nostr, although it is important to note that the platform is still in its early stages and there is no guarantee of income. Here are a few possibilities:

1. Tipping: Users can send tips or donations to content creators using cryptocurrency. This can be a way to support creators whose content you enjoy and value.
2. Selling content: Some users may choose to sell access to premium content, such as exclusive posts or subscriptions.
3. Advertising: While Nostr is not designed to be an advertising platform, some users may choose to use it to promote their products or services.
4. Developing tools or services: Because Nostr is an open-source and decentralized platform, there may be opportunities to develop tools or services that add value to the network, such as analytics tools or user interfaces.

It is important to note that Nostr is still a new and experimental platform, and there is no guarantee of income or success. Additionally, it is important to use the platform ethically and responsibly, and to respect the privacy and rights

What do I do if a relay bans me? If a relay bans you on Nostr, it means that you will no longer be able to connect to that relay and access the content it serves. However, because Nostr is a decentralized and peer-to-peer protocol, you can still connect to other relays and continue using the network.

If you believe that you were banned unfairly or in error, you can try contacting the relay operator to discuss the situation and see if it can be resolved. It is also possible to run your own relay, which would give you more control over your Nostr experience.

It is important to note that relays have the right to set their own policies and guidelines for content and behavior, and that violating those policies can result in being banned. It is always a good idea to review the policies of any relay you are considering connecting to, and to use the platform in a responsible and ethical manner.

What is the connection of Bitcoin and Nostr? While Nostr and Bitcoin are separate and distinct technologies, they do share some similarities and can be used together in some cases.

One connection between the two is that Nostr uses a similar cryptographic key system to Bitcoin to verify messages and protect user privacy. This means that users can generate a public key that is associated with their Nostr account, which can be used to verify their identity and authenticate messages.

Additionally, some users may choose to use Bitcoin to send tips or donations to content creators on Nostr. Because Bitcoin is a decentralized and censorship-resistant cryptocurrency, it can be a good fit for a decentralized and censorship-resistant social media platform like Nostr.

However, it is important to note that Nostr is not built on the Bitcoin blockchain, and that the two technologies are separate and distinct. Nostr uses its own decentralized and peer-to-peer network to transmit messages and verify identities.

What are some scenarios where Nostr fails completely? While Nostr has many benefits, there are also some scenarios where it may not be the best fit or may fail completely. Here are a few:

1. Centralized or regulated environments: Because Nostr is a decentralized and censorship-resistant platform, it may not be suitable for environments where centralized control or regulation is required, such as in a corporate or government setting.
2. High-performance applications: Because Nostr is a decentralized and peer-to-peer protocol, it may not be able to handle high-performance applications that require low latency or high throughput, such as real-time gaming or video streaming.
3. Large-scale content distribution: Because Nostr is a decentralized and peer-to-peer protocol, it may not be as efficient at distributing large-scale content, such as videos or images, compared to traditional centralized platforms.
4. Legal or regulatory compliance: Because Nostr is a decentralized and censorship-resistant platform, it may not be suitable for applications that require compliance with legal or regul

Enter training

The above outputs are when doing inferencing, i.e. using the model. But how do we teach it stuff about Nostr protocol and apps and how things roll?

Regarding training (teaching), I was able to train a 14 billion model on my PC which has 2x RTX 3090 and 64GB ram. LLaMa-Factory is an awesome tool for that. This is my command line:

accelerate launch --config_file examples/accelerate/fsdp_config.yaml src/train_bash.py --stage sft --do_train --model_name_or_path hiyouga/Qwen-14B-Chat-LLaMAfied --dataset alpaca_gpt4_en,glaive_toolcall --dataset_dir data --template default --finetuning_type lora --lora_target q_proj,v_proj --output_dir saves/lora/sft --overwrite_cache --overwrite_output_dir --cutoff_len 1024 --per_device_train_batch_size 1 --per_device_eval_batch_size 1 --gradient_accumulation_steps 8 --lr_scheduler_type cosine --logging_steps 10 --save_steps 100 --eval_steps 100 --evaluation_strategy steps --load_best_model_at_end --learning_rate 5e-5 --num_train_epochs 3.0 --max_samples 3000 --val_size 0.1 --quantization_bit 4 --plot_loss --fp16

It uses FDSP and QLORA technique, which I shared weeks ago. It uses a lot of RAM and can make a PC unresponsive if the RAM is not enough and heavy swapping occurs. The above one completed in about 17 hours. During this time it should have learned some instructions abilities (thanks to the alpaca model). But I won't test that. Instead of alpaca I should use Nostr knowledge.

``` * train metrics *** epoch = 3.0 train_loss = 0.5957 train_runtime = 17:02:56.05 train_samples_per_second = 0.264 train_steps_per_second = 0.016

```

Next I will try a few different things to train a 70B model. Today my ram upgrade has arrived. Can't wait to test the new rams!

@ e2ccf7cf:26c1c8eb

A bitcoin node is a computer running bitcoin software. It allows users to interact with the bitcoin network to do things like view and broadcast transactions.

If you don't have bitcoin software installed on your computer, you are relying on someone else's computer to:

1. Verify transactions
2. Broadcast your own transactions

This has obvious privacy and censorship risk, because the node you're connecting to can see all your transactions, track your IP address and refuse to broadcast certain transactions, for example to "blacklisted" addresses.

For these important reasons, you should run bitcoin software directly on your own computer. Thankfully, it's incredibly easy for anyone to do this with their existing computers, no additional hardware is required.

How to Install Bitcoin Core on Your Computer

1. Download Bitcoin Core from the official download page
2. Follow the installation instructions

Note that it is unnecessary for you to download and store the entire blockchain and run a so-called "full node". You can prune the blockchain to 4 GB to save space on your computer. If you feel the desire to store the entire blockchain, make sure you have at least 2 TB of available space (as of March 2024)

Connecting Your Node to Your Wallet Software

Most popular wallet software allows you to specify which node you should connect to, and most have some default settings to detect if Bitcoin Core is already installed on your computer. Here are some guides to walk you through step by step:

• Sparrow Wallet
• Trezor
• Ledger

I strongly recommend using Sparrow Wallet, it works with nearly all hardware wallets (signing devices).

You don't need to be a techie or an altruist to run a node

As you can see, anyone capable of clicking "next" a few times in a software installer is capable of running a node.

You don't need to run a node to "help decentralize bitcoin", you run a node for selfish reasons and those incentives alone will decentralize the network.

You also definitely don't need to buy a raspberry pi or a pre-made node like Umbrel or Start9, these are usually very expensive solutions with terrible hardware. Your cheap laptop is already much more powerful than a raspberry pi.

Any questions? Tag me on nostr with your question and I'll do my best to help you out.

🤙 Pura Vida!

@ 3bf0c63f:aefa459d

Pequenos problemas que o Estado cria para a sociedade e que não são sempre lembrados

- **vale-transporte**: transferir o custo com o transporte do funcionário para um terceiro o estimula a morar longe de onde trabalha, já que morar perto é normalmente mais caro e a economia com transporte é inexistente.
- **atestado médico**: o direito a faltar o trabalho com atestado médico cria a exigência desse atestado para todas as situações, substituindo o livre acordo entre patrão e empregado e sobrecarregando os médicos e postos de saúde com visitas desnecessárias de assalariados resfriados.
- **prisões**: com dinheiro mal-administrado, burocracia e péssima alocação de recursos -- problemas que empresas privadas em competição (ou mesmo sem qualquer competição) saberiam resolver muito melhor -- o Estado fica sem presídios, com os poucos existentes entupidos, muito acima de sua alocação máxima, e com isto, segundo a bizarra corrente de responsabilidades que culpa o juiz que condenou o criminoso por sua morte na cadeia, juízes deixam de condenar à prisão os bandidos, soltando-os na rua.
- **justiça**: entrar com processos é grátis e isto faz proliferar a atividade dos advogados que se dedicam a criar problemas judiciais onde não seria necessário e a entupir os tribunais, impedindo-os de fazer o que mais deveriam fazer.
- **justiça**: como a justiça só obedece às leis e ignora acordos pessoais, escritos ou não, as pessoas não fazem acordos, recorrem sempre à justiça estatal, e entopem-na de assuntos que seriam muito melhor resolvidos entre vizinhos.
- **leis civis**: as leis criadas pelos parlamentares ignoram os costumes da sociedade e são um incentivo a que as pessoas não respeitem nem criem normas sociais -- que seriam maneiras mais rápidas, baratas e satisfatórias de resolver problemas.
- **leis de trãnsito**: quanto mais leis de trânsito, mais serviço de fiscalização são delegados aos policiais, que deixam de combater crimes por isto (afinal de contas, eles não querem de fato arriscar suas vidas combatendo o crime, a fiscalização é uma excelente desculpa para se esquivarem a esta responsabilidade).
- **financiamento educacional**: é uma espécie de subsídio às faculdades privadas que faz com que se criem cursos e mais cursos que são cada vez menos recheados de algum conhecimento ou técnica útil e cada vez mais inúteis.
- **leis de tombamento**: são um incentivo a que o dono de qualquer área ou construção "histórica" destrua todo e qualquer vestígio de história que houver nele antes que as autoridades descubram, o que poderia não acontecer se ele pudesse, por exemplo, usar, mostrar e se beneficiar da história daquele local sem correr o risco de perder, de fato, a sua propriedade.
- **zoneamento urbano**: torna as cidades mais espalhadas, criando uma necessidade gigantesca de carros, ônibus e outros meios de transporte para as pessoas se locomoverem das zonas de moradia para as zonas de trabalho.
- **zoneamento urbano**: faz com que as pessoas percam horas no trânsito todos os dias, o que é, além de um desperdício, um atentado contra a sua saúde, que estaria muito melhor servida numa caminhada diária entre a casa e o trabalho.
- **zoneamento urbano**: torna ruas e as casas menos seguras criando zonas enormes, tanto de residências quanto de indústrias, onde não há movimento de gente alguma.
- **escola obrigatória + currículo escolar nacional**: emburrece todas as crianças.
- **leis contra trabalho infantil**: tira das crianças a oportunidade de aprender ofícios úteis e levar um dinheiro para ajudar a família.
- **licitações**: como não existem os critérios do mercado para decidir qual é o melhor prestador de serviço, criam-se comissões de pessoas que vão decidir coisas. isto incentiva os prestadores de serviço que estão concorrendo na licitação a tentar comprar os membros dessas comissões. isto, fora a corrupção, gera problemas reais: __(i)__ a escolha dos serviços acaba sendo a pior possível, já que a empresa prestadora que vence está claramente mais dedicada a comprar comissões do que a fazer um bom trabalho (este problema afeta tantas áreas, desde a construção de estradas até a qualidade da merenda escolar, que é impossível listar aqui); __(ii)__ o processo corruptor acaba, no longo prazo, eliminando as empresas que prestavam e deixando para competir apenas as corruptas, e a qualidade tende a piorar progressivamente.
- **cartéis**: o Estado em geral cria e depois fica refém de vários grupos de interesse. o caso dos taxistas contra o Uber é o que está na moda hoje (e o que mostra como os Estados se comportam da mesma forma no mundo todo).
- **multas**: quando algum indivíduo ou empresa comete uma fraude financeira, ou causa algum dano material involuntário, as vítimas do caso são as pessoas que sofreram o dano ou perderam dinheiro, mas o Estado tem sempre leis que prevêem multas para os responsáveis. A justiça estatal é sempre muito rígida e rápida na aplicação dessas multas, mas relapsa e vaga no que diz respeito à indenização das vítimas. O que em geral acontece é que o Estado aplica uma enorme multa ao responsável pelo mal, retirando deste os recursos que dispunha para indenizar as vítimas, e se retira do caso, deixando estas desamparadas.
- **desapropriação**: o Estado pode pegar qualquer propriedade de qualquer pessoa mediante uma indenização que é necessariamente inferior ao valor da propriedade para o seu presente dono (caso contrário ele a teria vendido voluntariamente).
- **seguro-desemprego**: se há, por exemplo, um prazo mínimo de 1 ano para o sujeito ter direito a receber seguro-desemprego, isto o incentiva a planejar ficar apenas 1 ano em cada emprego (ano este que será sucedido por um período de desemprego remunerado), matando todas as possibilidades de aprendizado ou aquisição de experiência naquela empresa específica ou ascensão hierárquica.
- **previdência**: a previdência social tem todos os defeitos de cálculo do mundo, e não importa muito ela ser uma forma horrível de poupar dinheiro, porque ela tem garantias bizarras de longevidade fornecidas pelo Estado, além de ser compulsória. Isso serve para criar no imaginário geral a idéia da __aposentadoria__, uma época mágica em que todos os dias serão finais de semana. A idéia da aposentadoria influencia o sujeito a não se preocupar em ter um emprego que faça sentido, mas sim em ter um trabalho qualquer, que o permita se aposentar.
- **regulamentação impossível**: milhares de coisas são proibidas, há regulamentações sobre os aspectos mais mínimos de cada empreendimento ou construção ou espaço. se todas essas regulamentações fossem exigidas não haveria condições de produção e todos morreriam. portanto, elas não são exigidas. porém, o Estado, ou um agente individual imbuído do poder estatal pode, se desejar, exigi-las todas de um cidadão inimigo seu. qualquer pessoa pode viver a vida inteira sem cumprir nem 10% das regulamentações estatais, mas viverá também todo esse tempo com medo de se tornar um alvo de sua exigência, num estado de terror psicológico.
- **perversão de critérios**: para muitas coisas sobre as quais a sociedade normalmente chegaria a um valor ou comportamento "razoável" espontaneamente, o Estado dita regras. estas regras muitas vezes não são obrigatórias, são mais "sugestões" ou limites, como o salário mínimo, ou as 44 horas semanais de trabalho. a sociedade, porém, passa a usar esses valores como se fossem o normal. são raras, por exemplo, as ofertas de emprego que fogem à regra das 44h semanais.
- **inflação**: subir os preços é difícil e constrangedor para as empresas, pedir aumento de salário é difícil e constrangedor para o funcionário. a inflação força as pessoas a fazer isso, mas o aumento não é automático, como alguns economistas podem pensar (enquanto alguns outros ficam muito satisfeitos de que esse processo seja demorado e difícil).
- **inflação**: a inflação destrói a capacidade das pessoas de julgar preços entre concorrentes usando a própria memória.
- **inflação**: a inflação destrói os cálculos de lucro/prejuízo das empresas e prejudica enormemente as decisões empresariais que seriam baseadas neles.
- **inflação**: a inflação redistribui a riqueza dos mais pobres e mais afastados do sistema financeiro para os mais ricos, os bancos e as megaempresas.
- **inflação**: a inflação estimula o endividamento e o consumismo.
- **lixo:** ao prover coleta e armazenamento de lixo "grátis para todos" o Estado incentiva a criação de lixo. se tivessem que pagar para que recolhessem o seu lixo, as pessoas (e conseqüentemente as empresas) se empenhariam mais em produzir coisas usando menos plástico, menos embalagens, menos sacolas.
- **leis contra crimes financeiros:** ao criar legislação para dificultar acesso ao sistema financeiro por parte de criminosos a dificuldade e os custos para acesso a esse mesmo sistema pelas pessoas de bem cresce absurdamente, levando a um percentual enorme de gente incapaz de usá-lo, para detrimento de todos -- e no final das contas os grandes criminosos ainda conseguem burlar tudo.

@ 453846ff:a380c94b

I've been wondering something for awhile. Can a lightening payment (zap) send a signal that closes/completes a physical circuit after it is confirmed that it is from a specific npub? Reading the article in this recent post from the nostr territory got me thinking about the sixth one: IOT Communication https://stacker.news/items/482657

If so, it stands to reason that it should be possible to set up a garage door opener to open or close through the Nostr protocol and lightening network.

The lightening payment may not be needed, maybe just needs to be an open message that comes from a designated set of npubs. Usually two members of the household can open up the garage door. Then sometimes there are guests that you want to be able to open up the garage door.

Is anyone working on this? I'm not a coder, but I know my way around a garage door opener and the accessories around them.

@ fe7f6bc6:c42539a3

This is my Guide to Embracing the sun in your life

Living in harmony with my body's natural rhythms has been a game-changer for me. If you're curious about adopting a circadian lifestyle, I've put together a little cheat sheet from my experience and research. This is complementary to my documentary about the sun - at the bottom of this you will find all the science backing everything up. It's all about aligning our daily life with the natural cycle of our internal clock. Here's why it's worth it and how you can do it:

Why Go Circadian?

• Sleep Like a Dream: Syncing with your body's clock means better, more restful sleep. It's a night and day difference, literally.
• Mood Magic: Feeling brighter and more stable, mood-wise. It's like natural therapy.
• Health Perks: Lower risks of the big nasties like obesity, heart disease Cancer and Neurological diseases. Plus, my energy levels are more consistent throughout the day.

How to Circadian Your Life Step by Step

1. Morning Sunshine: I kickstart my day with sunlight. Just a quick 10-30 minute dose as soon as I wake up. It tells my brain, "Hey, it's go time!"
2. Sleep Rhythm: Hitting the pillow and waking up at the same time daily. Yes, weekends too. It's tough love for my sleep cycle. Especially with combining sleeping on the floor - my sleep hasn’t been that good in the last years. (Sleep Video: https://youtu.be/ICnLS1BbZ_w)
3. Light Lowdown: Cutting down on bright and white lights and screens before bedtime to let my melatonin do its thing.
4. Eat Smart: I aim to eat my biggest meal when the sun's shining brightest and dial down on late-night snacking.
5. Move It: Daytime is for moving; it keeps my internal clock tick-tocking correctly. Evening activities are more chill, like a leisurely stroll.
6. Bedroom Bliss: My bedroom is a cave – cool, dark, and quiet. Blackout curtains and a hint of white noise can work wonders.

Early Days Expectations

• Adjustment Time: Took me a few days to a few weeks to find my rhythm.
• Energy Boost: Once I adjusted, my daytime alertness and energy levels noticeably improved.
• Sleep Quirks: Initially, there were some hiccups with falling asleep, but they smoothed out.

Pro Tips

• Patience, Frens: It doesn't happen overnight. Give it time.
• Consistency Is Key: Stick to the routine as much as possible for the best results.
• Body Talk: Listening to my body helped me fine-tune things. If something felt off, I tweaked it.
• Be Kind to Yourself: It's okay to slip up now and then. Just hop back on the wagon.
• It's a Package Deal: Sleep, light, diet, and activity – it's all connected. Keeping everything in check makes a huge difference.

This journey has been enlightening for me, and I hope my little cheat sheet helps you find your rhythm too. Remember, it's about making small, sustainable changes that add up to a big impact on your well-being. Let's live our best circadian lives!

If you're interested in living such a lifestyle let me tell you, you're not alone. We're a community of like-minded health conscious people talking in group chats daily and have video calls to talk about our experiences and help each other living a healthier life. Feel free to join us by subscribing and getting access to the groups. Looking forward to get to know you more 🧡

Science & Sources:

UV Light and Sunlight Exposure

These studies focus on the impact of UV light and sunlight on health, including benefits and risks associated with UV radiation and sunlight exposure.

• "How UV Light Touches the Brain and Endocrine System Through Skin, and Why" - https://pubmed.ncbi.nlm.nih.gov/29546369/
• "Solar ultraviolet radiation: Global burden of disease from solar ultraviolet radiation" - https://www.who.int/uv/publications/solaradgbd/en/
• "Benefits of Sunlight: A Bright Spot for Human Health" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2290997/
• "UV Radiation and the Skin" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3499892/
• "Impact of Ultraviolet Light on Vitiligo: A Review" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5129901/

Vitamin D: Health Implications and Benefits

These articles explore the role of Vitamin D in health, including its effects on the immune system, cancer risk, and cognitive function.

• "Vitamin D: A D-Lightful Solution for Health" - https://onlinelibrary.wiley.com/doi/10.1111/joim.12496
• "Sunlight and Vitamin D: Necessary for Public Health" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9963929/
• "The effects of vitamin D on brain development and adult brain function" - https://pubmed.ncbi.nlm.nih.gov/21633182/
• "The Role of Vitamin D in the Aging Adult" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3002207/
• "Vitamin D supplementation and cancer risk: A meta-analysis of randomized controlled trials" - https://www.sciencedirect.com/science/article/abs/pii/S0959804922003549
• "Vitamin D and the Immune System: Exploring the Complex Interactions" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7400257/
• "Vitamin D Deficiency and Its Role in Neurological Conditions: A Review" - https://pubmed.ncbi.nlm.nih.gov/34488088/

Circadian Rhythms, Mood, and Cognitive Function

This group includes studies on the influence of light exposure and Vitamin D on circadian rhythms, mood disorders like Seasonal Affective Disorder (SAD), and cognitive function.

• "Serotonin, tryptophan metabolism and the brain-gut-microbiome axis" - https://pubmed.ncbi.nlm.nih.gov/34433056/
• "Effect of Sunlight Exposure on Cognitive Function Among Depressed and Non-depressed Participants: A REGARDS Cross-sectional Study" - https://pubmed.ncbi.nlm.nih.gov/27241553/
• "Circadian rhythms and mood regulation: Insights from pre-clinical and clinical studies" - https://pubmed.ncbi.nlm.nih.gov/31300477/
• "Seasonal Affective Disorder: An Overview of Assessment and Treatment Approaches" - https://pubmed.ncbi.nlm.nih.gov/35191986/
• "Long-term residential sunlight exposure associated with cognitive function among adults residing in Finland" - https://www.researchgate.net/publication/365965499_Long-term_residential_sunlight_exposure_associated_with_cognitive_function_among_adults_residing_in_Finland

Miscellaneous Health Impacts

These studies look at various other effects related to light exposure, including the risk of myopia and the impact of green light on the human body.

• "Exposure to Sunlight Reduces the Risk of Myopia in Childhood and Adolescence" - https://pubmed.ncbi.nlm.nih.gov/23841684/
• "Mechanisms and Effects of Green Light on the Human Body" - https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5129901/

@ 5e5fc143:393d5a2c

We are now given a choice of digital freedom #nostr .

Creativity for every nostrich is now unleashed from the cage of bigtech censorship , rules and algo. But freedom comes with responsibility so pick right one(s). I will try share here some learning experience both technical and also from fundamental point of view. Just wanted kick start this article n fill as we go like living reference document.

Nostr itself is an application layer protocol that can used beyond just social media mirco or long blogging. Each nostr client heavily dependent on back-end servers call nostr "Relay servers" or in short "rs" or "relays" Relays can hosted anywhere in clearnet internet, onion net , vpn , i2p , nym Relays are controlled by their respective admins based NIP specs that they select to implement according to own decisions. Relays can have certain ToS (Terms of Service) Rules to adhered too.

New users can choose and pick client or app (ios / android/ windows) with preset of relays in the simplest form , but other advanced users need to do a regular manual relay management.

Relay management is an active regular task based on where when n how you are using.

Relay list are saved within you npub profile backup file which can edited and broadcast anytime.

Relay management is an active regular task based on where when and how you are using.

Relay list always need to be updated time to time as and when needed.

2 Users MUST a common RELAY between them even if one only need to follow another. Occasionally you may notice certain npub accounts you are following already but cannot see frequent notes publish by them – one of cause maybe you not sharing a common relay

Most nostr client applications has SETTINGS where user choose add/remove relays Also user choose which function to enable - READ or WRITE

Relay list for your account is always saved within you npub profile backup file which can edited and broadcast anytime. Hence any app or browser when u login with you npub the same relay list will be enforced. There could valid reasons why u need have list for if you trying to save bandwidth and traveling.

Functions in app.getcurrent.io and primal.net app for mobile apple or android are ideal for user traveling abroad and wanted to save bandwidth since relay management is done the providers in backend and saves hassle for basic usage.

Remember if someone is selecting relay on your behalf then you may not be necessarily able to pull and get some specific and special content that you may need. Such providers like coracle and nostrid also give option to override the default relays they selected.

Relay types: They can be categorized by various features or policy or technologies.

FREE PUBLIC Relays vs PAID PUBLIC Relays

PAID relays provide unrestricted access / write / filtering options than FREE relays but both are public clearnet relays. Just subscribing to PAID relays will not solve all problems unless you choose the relays properly and enable settings correctly.

Private Replay or Tor Relays – normally not easily visible until unless someone tell you. You can also host own private relay not opened to internet of archive and back of your own notes.

The technical landscape in nostr can be fast changing as more NIPs get proposed or updated. Relays admin can choose implement certain NIPs or not based on policy or technical limitations.

Example NIP33 defines “long notes” aka blogs as you now reading this in habla site which #1 UI and site for "Editable" long notes – some relays donot implement or allow this. NIP07 is used for client authentication like nos2x and is implemented by all relays in fact.

To be continued again ... reference pics will added later also Hope this help you understand "why when what" to tune and maintain active set of proper relays. Relay Proxy, Relay aggregator or Relay multiplexer – Paid, Public, Free, Private, Event, Relays That’s all for now n more later ... Thank you 🙏 ! ⚡️ https://getalby.com/p/captjack ⚡️ PV 💜 🤙

References: https://habla.news/relays https://relay.exchange/ https://relays.vercel.app/ https://nostr.info/relays/ https://nostrudel.ninja/#/relays

Related Articles: https://thebitcoinmanual.com/articles/types-nostr-relays/ nostr:naddr1qqd5c6t8dp6xu6twvukkvctnwss92jfqvehhygzwdaehguszyrtp7w79k045gq80mtnpdxjuzl9t7vjxk52rv80f888y5xsd5mh55qcyqqq823cf39s98 https://habla.news/u/current@getcurrent.io/1694434022411

@ 3bf0c63f:aefa459d

bitcoind decentralization

It is better to have multiple curator teams, with different vetting processes and release schedules for bitcoind than a single one.

"More eyes on code", "Contribute to Core", "Everybody should audit the code".

All these points repeated again and again fell to Earth on the day it was discovered that Bitcoin Core developers merged a variable name change from "blacklist" to "blocklist" without even discussing or acknowledging the fact that that innocent pull request opened by a sybil account was a social attack.

After a big lot of people manifested their dissatisfaction with that event on Twitter and on GitHub, most Core developers simply ignored everybody's concerns or even personally attacked people who were complaining.

The event has shown that:

1) Bitcoin Core ultimately rests on the hands of a couple maintainers and they decide what goes on the GitHub repository[^pr-merged-very-quickly] and the binary releases that will be downloaded by thousands; 2) Bitcoin Core is susceptible to social attacks; 2) "More eyes on code" don't matter, as these extra eyes can be ignored and dismissed.

Solution: bitcoind decentralization

If usage was spread across 10 different bitcoind flavors, the network would be much more resistant to social attacks to a single team.

This has nothing to do with the question on if it is better to have multiple different Bitcoin node implementations or not, because here we're basically talking about the same software.

Multiple teams, each with their own release process, their own logo, some subtle changes, or perhaps no changes at all, just a different name for their bitcoind flavor, and that's it.

Every day or week or month or year, each flavor merges all changes from Bitcoin Core on their own fork. If there's anything suspicious or too leftist (or perhaps too rightist, in case there's a leftist bitcoind flavor), maybe they will spot it and not merge.

This way we keep the best of both worlds: all software development, bugfixes, improvements goes on Bitcoin Core, other flavors just copy. If there's some non-consensus change whose efficacy is debatable, one of the flavors will merge on their fork and test, and later others -- including Core -- can copy that too. Plus, we get resistant to attacks: in case there is an attack on Bitcoin Core, only 10% of the network would be compromised. the other flavors would be safe.

Run Bitcoin Knots

The first example of a bitcoind software that follows Bitcoin Core closely, adds some small changes, but has an independent vetting and release process is Bitcoin Knots, maintained by the incorruptible Luke DashJr.

Next time you decide to run bitcoind, run Bitcoin Knots instead and contribute to bitcoind decentralization!

---

See also:

• How to attack Bitcoin, Anthony Towns' take

[^pr-merged-very-quickly]: See PR 20624, for example, a very complicated change that could be introducing bugs or be a deliberate attack, merged in 3 days without time for discussion.

@ 3bf0c63f:aefa459d

Drivechain

Understanding Drivechain requires a shift from the paradigm most bitcoiners are used to. It is not about "trustlessness" or "mathematical certainty", but game theory and incentives. (Well, Bitcoin in general is also that, but people prefer to ignore it and focus on some illusion of trustlessness provided by mathematics.)

Here we will describe the basic mechanism (simple) and incentives (complex) of "hashrate escrow" and how it enables a 2-way peg between the mainchain (Bitcoin) and various sidechains.

The full concept of "Drivechain" also involves blind merged mining (i.e., the sidechains mine themselves by publishing their block hashes to the mainchain without the miners having to run the sidechain software), but this is much easier to understand and can be accomplished either by the BIP-301 mechanism or by the Spacechains mechanism.

How does hashrate escrow work from the point of view of Bitcoin?

A new address type is created. Anything that goes in that is locked and can only be spent if all miners agree on the Withdrawal Transaction (WT^) that will spend it for 6 months. There is one of these special addresses for each sidechain.

To gather miners' agreement bitcoind keeps track of the "score" of all transactions that could possibly spend from that address. On every block mined, for each sidechain, the miner can use a portion of their coinbase to either increase the score of one WT^ by 1 while decreasing the score of all others by 1; or they can decrease the score of all WT^s by 1; or they can do nothing.

Once a transaction has gotten a score high enough, it is published and funds are effectively transferred from the sidechain to the withdrawing users.

If a timeout of 6 months passes and the score doesn't meet the threshold, that WT^ is discarded.

What does the above procedure mean?

It means that people can transfer coins from the mainchain to a sidechain by depositing to the special address. Then they can withdraw from the sidechain by making a special withdraw transaction in the sidechain.

The special transaction somehow freezes funds in the sidechain while a transaction that aggregates all withdrawals into a single mainchain WT^, which is then submitted to the mainchain miners so they can start voting on it and finally after some months it is published.

Now the crucial part: the validity of the WT^ is not verified by the Bitcoin mainchain rules, i.e., if Bob has requested a withdraw from the sidechain to his mainchain address, but someone publishes a wrong WT^ that instead takes Bob's funds and sends them to Alice's main address there is no way the mainchain will know that. What determines the "validity" of the WT^ is the miner vote score and only that. It is the job of miners to vote correctly -- and for that they may want to run the sidechain node in SPV mode so they can attest for the existence of a reference to the WT^ transaction in the sidechain blockchain (which then ensures it is ok) or do these checks by some other means.

What? 6 months to get my money back?

Yes. But no, in practice anyone who wants their money back will be able to use an atomic swap, submarine swap or other similar service to transfer funds from the sidechain to the mainchain and vice-versa. The long delayed withdraw costs would be incurred by few liquidity providers that would gain some small profit from it.

Why bother with this at all?

Drivechains solve many different problems:

It enables experimentation and new use cases for Bitcoin

Issued assets, fully private transactions, stateful blockchain contracts, turing-completeness, decentralized games, some "DeFi" aspects, prediction markets, futarchy, decentralized and yet meaningful human-readable names, big blocks with a ton of normal transactions on them, a chain optimized only for Lighting-style networks to be built on top of it.

These are some ideas that may have merit to them, but were never actually tried because they couldn't be tried with real Bitcoin or inferfacing with real bitcoins. They were either relegated to the shitcoin territory or to custodial solutions like Liquid or RSK that may have failed to gain network effect because of that.

It solves conflicts and infighting

Some people want fully private transactions in a UTXO model, others want "accounts" they can tie to their name and build reputation on top; some people want simple multisig solutions, others want complex code that reads a ton of variables; some people want to put all the transactions on a global chain in batches every 10 minutes, others want off-chain instant transactions backed by funds previously locked in channels; some want to spend, others want to just hold; some want to use blockchain technology to solve all the problems in the world, others just want to solve money.

With Drivechain-based sidechains all these groups can be happy simultaneously and don't fight. Meanwhile they will all be using the same money and contributing to each other's ecosystem even unwillingly, it's also easy and free for them to change their group affiliation later, which reduces cognitive dissonance.

It solves "scaling"

Multiple chains like the ones described above would certainly do a lot to accomodate many more transactions that the current Bitcoin chain can. One could have special Lightning Network chains, but even just big block chains or big-block-mimblewimble chains or whatnot could probably do a good job. Or even something less cool like 200 independent chains just like Bitcoin is today, no extra features (and you can call it "sharding"), just that would already multiply the current total capacity by 200.

Use your imagination.

It solves the blockchain security budget issue

The calculation is simple: you imagine what security budget is reasonable for each block in a world without block subsidy and divide that for the amount of bytes you can fit in a single block: that is the price to be paid in satoshis per byte. In reasonable estimative, the price necessary for every Bitcoin transaction goes to very large amounts, such that not only any day-to-day transaction has insanely prohibitive costs, but also Lightning channel opens and closes are impracticable.

So without a solution like Drivechain you'll be left with only one alternative: pushing Bitcoin usage to trusted services like Liquid and RSK or custodial Lightning wallets. With Drivechain, though, there could be thousands of transactions happening in sidechains and being all aggregated into a sidechain block that would then pay a very large fee to be published (via blind merged mining) to the mainchain. Bitcoin security guaranteed.

It keeps Bitcoin decentralized

Once we have sidechains to accomodate the normal transactions, the mainchain functionality can be reduced to be only a "hub" for the sidechains' comings and goings, and then the maximum block size for the mainchain can be reduced to, say, 100kb, which would make running a full node very very easy.

Can miners steal?

Yes. If a group of coordinated miners are able to secure the majority of the hashpower and keep their coordination for 6 months, they can publish a WT^ that takes the money from the sidechains and pays to themselves.

Will miners steal?

No, because the incentives are such that they won't.

Although it may look at first that stealing is an obvious strategy for miners as it is free money, there are many costs involved:

1. The cost of ceasing blind-merged mining returns -- as stealing will kill a sidechain, all the fees from it that miners would be expected to earn for the next years are gone;
2. The cost of Bitcoin price going down: If a steal is successful that will mean Drivechains are not safe, therefore Bitcoin is less useful, and miner credibility will also be hurt, which are likely to cause the Bitcoin price to go down, which in turn may kill the miners' businesses and savings;
3. The cost of coordination -- assuming miners are just normal businesses, they just want to do their work and get paid, but stealing from a Drivechain will require coordination with other miners to conduct an immoral act in a way that has many pitfalls and is likely to be broken over the months;
4. The cost of miners leaving your mining pool: when we talked about "miners" above we were actually talking about mining pools operators, so they must also consider the risk of miners migrating from their mining pool to others as they begin the process of stealing;
5. The cost of community goodwill -- when participating in a steal operation, a miner will suffer a ton of backlash from the community. Even if the attempt fails at the end, the fact that it was attempted will contribute to growing concerns over exaggerated miners power over the Bitcoin ecosystem, which may end up causing the community to agree on a hard-fork to change the mining algorithm in the future, or to do something to increase participation of more entities in the mining process (such as development or cheapment of new ASICs), which have a chance of decreasing the profits of current miners.

Another point to take in consideration is that one may be inclined to think a newly-created sidechain or a sidechain with relatively low usage may be more easily stolen from, since the blind merged mining returns from it (point 1 above) are going to be small -- but the fact is also that a sidechain with small usage will also have less money to be stolen from, and since the other costs besides 1 are less elastic at the end it will not be worth stealing from these too.

All of the above consideration are valid only if miners are stealing from good sidechains. If there is a sidechain that is doing things wrong, scamming people, not being used at all, or is full of bugs, for example, that will be perceived as a bad sidechain, and then miners can and will safely steal from it and kill it, which will be perceived as a good thing by everybody.

What do we do if miners steal?

Paul Sztorc has suggested in the past that a user-activated soft-fork could prevent miners from stealing, i.e., most Bitcoin users and nodes issue a rule similar to this one to invalidate the inclusion of a faulty WT^ and thus cause any miner that includes it in a block to be relegated to their own Bitcoin fork that other nodes won't accept.

This suggestion has made people think Drivechain is a sidechain solution backed by user-actived soft-forks for safety, which is very far from the truth. Drivechains must not and will not rely on this kind of soft-fork, although they are possible, as the coordination costs are too high and no one should ever expect these things to happen.

If even with all the incentives against them (see above) miners do still steal from a good sidechain that will mean the failure of the Drivechain experiment. It will very likely also mean the failure of the Bitcoin experiment too, as it will be proven that miners can coordinate to act maliciously over a prolonged period of time regardless of economic and social incentives, meaning they are probably in it just for attacking Bitcoin, backed by nation-states or something else, and therefore no Bitcoin transaction in the mainchain is to be expected to be safe ever again.

Why use this and not a full-blown trustless and open sidechain technology?

Because it is impossible.

If you ever heard someone saying "just use a sidechain", "do this in a sidechain" or anything like that, be aware that these people are either talking about "federated" sidechains (i.e., funds are kept in custody by a group of entities) or they are talking about Drivechain, or they are disillusioned and think it is possible to do sidechains in any other manner.

No, I mean a trustless 2-way peg with correctness of the withdrawals verified by the Bitcoin protocol!

That is not possible unless Bitcoin verifies all transactions that happen in all the sidechains, which would be akin to drastically increasing the blocksize and expanding the Bitcoin rules in tons of ways, i.e., a terrible idea that no one wants.

What about the Blockstream sidechains whitepaper?

Yes, that was a way to do it. The Drivechain hashrate escrow is a conceptually simpler way to achieve the same thing with improved incentives, less junk in the chain, more safety.

Isn't the hashrate escrow a very complex soft-fork?

Yes, but it is much simpler than SegWit. And, unlike SegWit, it doesn't force anything on users, i.e., it isn't a mandatory blocksize increase.

Why should we expect miners to care enough to participate in the voting mechanism?

Because it's in their own self-interest to do it, and it costs very little. Today over half of the miners mine RSK. It's not blind merged mining, it's a very convoluted process that requires them to run a RSK full node. For the Drivechain sidechains, an SPV node would be enough, or maybe just getting data from a block explorer API, so much much simpler.

What if I still don't like Drivechain even after reading this?

That is the entire point! You don't have to like it or use it as long as you're fine with other people using it. The hashrate escrow special addresses will not impact you at all, validation cost is minimal, and you get the benefit of people who want to use Drivechain migrating to their own sidechains and freeing up space for you in the mainchain. See also the point above about infighting.

See also

• Podcast episode with Ruben Somsen and Aaron van Wirdum explaining Drivechain
• Alternatives to Drivechain
• Drivechain comparison with Ethereum

@ 1739d937:3e3136ef

"Gossip", "Outbox", "Inbox", "Blastr", "Small relays vs Big relays". You've probably seen most of these topics come up in conversations and memes recently. You might have even read nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgsm3u0w6's article (nostr:naddr1qq2hxenh2cchynnpdag4sepkx4gxyj2dt9nk6q3qjlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qxpqqqp65wd3a9ny), or nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgua442w's very technical article (nostr:naddr1qqxnzde3xycngdpjxg6nqdfsqgswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgrqsqqqa28906usv), or maybe even nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8g2lcy6q's one with the clickbaity title (nostr:naddr1qvzqqqr4gupzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsqzpcxasnyvpcvsusgpcqx3).

These are all great, and you should go and read them too. But one thing that each of them is guilty of is assuming that the audience has enough context to jump into the middle of a very nuanced and technical discussion. I've yet to see a clear description of what Gossip or Outbox really are and certainly none that are written in a way that is approachable for a non-technical audience. I hope this article can give you that context and serve as a high-level overview of the discussion and the technologies involved so that you can go forth to create better, more informed memes (is there anything more important, really?) and join the discussion in a productive way.

The problems

Centralization is the default

First off, why are we even talking about relays? Most of know that nostr is a protocol which is designed to be decentralized from the ground up. That decentralization is due in large part to the fact that users read and write data to multiple relays by default. So instead of all your data going to a centralized database (usually owned and operated by a single company) with nostr you have the ability to send your data to as as many relays as you'd like (relays are just databases, after all). Likewise, you can read other people's data from as many relays as you'd like to. Decentralized design = decentralized system, right!? Well, turns out, no.

The problem with a design like this is that what can be done and what will be done are often very different things. Imagine the following scenario: You follow 1000 people; 700 of them post their notes to the Primal relay, the other 300 post their notes to the Damus relay. If you don't also write your content to those two relays, the people that you care about won't see your content, they won't see your replies to their notes, they won't even know you exist. So while; in practice, it's easy to read & write to many different relays, users and their content will tend to centralize because it's the path of least resistance to a good user experience. Network effects and economies of scale always apply, they just don't always lead to the outcomes that you want.

Before you start to panic, this sort of centralization isn't a huge issue just yet. We are still a nascent network and there are still hundreds of active relays out there. Almost all nostr clients make relay selection a first class citizen and don't default new users to a single relay. The fact that we're even having this conversation in a serious way at this stage is a great sign that the community cares enough to be proactive about maintaining (and improving) decentralization over time.

That said, this is not a issue that we can take lightly either. The top 5-10 relays do already have an outsized percentage of users and we have many examples of these centralizing tendencies across dozens of protocols and networks over the last 30 years, so the threat is real.

The status quo is wasteful

The other major issue is that currently most nostr clients are extremely wasteful in how they fetch data. The default is to simply get everything from all the relays a user wants to connect to. Because most of us are writing the same data to many relays, this leads to huge amounts of duplicated data being downloaded, having its signatures verified, and then (for the most part) thrown away. For those of us with latest generation smartphones, unlimited data, and a working power outlet nearby, this is fine. For everyone else, this is a major roadblock to adopting nostr.

A lightly technical aside

There are a few important features of nostr that make any sort of intelligent data fetching possible. To understand how any of the potential solutions to the aforementioned problems would actually work, it's important to have a baseline understanding of these technical details. I promise, I'll keep it high level.

Relay lists

Recently the concept of a Relay List Metadata has been introduced to the spec in NIP-65 (there are also other types of relay lists documented in NIP-51). This is a nostr list event where users publish their preferred relays with a marker that says whether the relay is for read-only, write-only, or read & write. This vastly simplifies the process of finding preferred user relays for clients and I imagine that this will become the de facto standard place to look for a user's preferred relays.

NIP-05

The NIP-05 spec also documents a way for users to signal their preferred relays. However, unlike the NIP-65 relay list, this is a simple list of relays without any details on whether the user reads or writes to those relays.

Tag markers

Tag markers are positional elements in tags that give the client publishing the event the ability to leave a hint as to which relay other clients can expect to find a given user or note that is being referenced.

For example, in a user's contact list (a kind: 3 event) you have many "p" tags to reference all the user's that are followed. These tags look like this:

{ "kind": 3, "tags": [ ["p", "91cf9..4e5ca", "wss://alicerelay.com/", "alice"], ["p", "14aeb..8dad4", "wss://bobrelay.com/nostr"], ["p", "612ae..e610f"] ], "content": "", ...other fields }

All three of these "p" tags are valid (only the "p" and the user's pubkey are required), in the first and second you can see the third item is a relay where the user's events can be found.

These types of tag markers are repeated all throughout nostr. Here's a few more example references for an event (in this case a long-form article):

``` ["e", "b3e392b11f5d4f28321cedd09303a748acfd0487aea5a7450b3481c60b6e4f87", "wss://relay.example.com"],

["a", "30023:a695f6b60119d9521934a691347d9f78e8770b56da16bb255ee286ddf9fda919:ipsum", "wss://relay.nostr.org"] ```

As you can imagine, these hints can be very helpful but only if clients actually attempt to fetch the content from the referenced relay.

The solutions?

Now that you understand the problem space a bit better let's define those terms we started with.

Blastr

Blastr was created by nostr:nprofile1qqs9hejyd252x8q3kw6980ud4lymx3hlx2x3lgg6p7sz58nyv8m2nvgdswkeh and nostr:nprofile1qqswrlemlh2wgqc4jkds3d8ueqj9a2j3gcm7r48v9tskdd6rxsd7rtcpwpuwc from Mutiny and isn't a relay. Instead, Blastr is a proxy (i.e. it looks like a relay to clients) that ingests any event sent to it and, in turn, sends those events to EVERY online relay on the network. It's a mass re-broadcaster for events that can be helpful to get your data pushed out to as many relays (and thus users) as possible. The drawback, of course, is that this is tremendously wasteful from a bandwidth and storage perspective.

Gossip (in 3 flavors)

This is by far the most confusing part for most people when watching the memes of the last few weeks fly by and I've seen a lot of confused takes out there. Most of the confusion stems from the multiplicity of definitions of what the "gossip model" actually is. Let's go through the options. 1. Gossip protocols: This is a general concept more than a specific implementation. Gossip protocols are protocols that attempt to spread information around a network in a uniform way. For example, Bitcoin nodes use a variation of the gossip protocol to make sure that transactions end up in as many mempools as possible. This is important in computing when you want to reach consensus or when all nodes in a network need to have the same information in order to operate the network. Since nostr doesn't have any consensus rules or shared compute, it's somewhat pointless to try and make sure all events are propagated to all relays (hence the limited usefulness of Blastr). 2. The Gossip client from nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgua442w : This is a nostr client that was built from the ground up to try and use relays and relay hints in events to the fullest to keep things as decentralized as possible while being efficient in how much data it was fetching. Mike has a great (slightly outdated and very technical) video that talks about his motivation behind building Gossip in the way he did. It's worth a watch. video link 3. Gossip model: This is what people are usually referring to when they are talking about relays on nostr. The Gossip model is a loose, catch-all term used to refer to all the ways in which clients attempt to understand which relays they should read & write to for a given user. Again, this isn't really a specific spec or implementation but encompasses many different strategies. This vagueness inherent in the term makes discussions about the "gossip model" pretty imprecise and prone to misunderstanding.

Don't gossip

To be clear: You really shoud not be thinking about or talking about any of this as the "gossip model" since that definition is so abstract as to be unusable. Which brings us finally to the real topic being discussed at the moment among devs; the Outbox model.

Outbox/Inbox model

This is the real topic of conversation right now: How should client developers build relay discovery and selection features into their apps. As we already talked about, if left alone, it's likely that we'd unintentionally centralize most of nostr onto a few huge relays. So making sure that we encourage (and build sensible defaults) to help client developers to treat relay discovery and selection properly is really critical.

Right now, the discussion centers around one main approach, called the "Outbox model". There is also an "Inbox model" which is a still just a high level idea which I'll mention below but it's not being implemented yet (as of late March 2024). 1. The "Outbox model": This strategy looks at what relays users are using to publish their events (from relay lists and tag markers) and then uses an algorithm to decide how to fetch all the needed events from the array of relays. Different implementations can use different algorithms to select relays. For example, one implementation might optimize fetching events from the smallest number of relays (favoring large relays), while another might optimize for fetching from the relays that have the smallest user overlap (favoring small relays). 2. The "Inbox model": As you can imagine, this strategy flips the outbox model on it's head. It's so far just an idea (proposed by nostr:nprofile1qqs8nsk2uy2w529fs8n4tx60u7z553e4yx5dy2nxhw4elgjgawpqlas9waufq) and a draft NIP but the idea is that when your client posts on your behalf, it will loop over your entire follow list, making a list of the relays that each of your followers uses to read events. Then the client will publish your event to all of those relays. If all clients followed this paradigm, then each of us would only have to read from a single relay. To quote nostr:nprofile1qqs8nsk2uy2w529fs8n4tx60u7z553e4yx5dy2nxhw4elgjgawpqlas9waufq 's original post, "This doesn't take away from the outbox approach, and maybe should even be used together instead of as a replacement. But my point is that clients should be trying harder to deliver posts instead of just fetch posts. Because it benefits users when their posts can be seen."

Why the Outbox model has broad support

To understand why implementing an Outbox model is so powerful at solveing the problems laid out at the beginning of this article, you can do two quick thought experiments:

A user banned from all other relays

Imagine a user who's content is banned from all public relays for some reason. Instead, they have to run their own relay and publish their events there. With a simple "follow the major relays model" (or even with Blastr attempting to copy and paste their events to every other relay) this user is completely invisible to the network. User's would have to know about the banned user's private relay and select that relay in each client they use. What's more, if that relay ever had to change URL (likely for a user that is banned so broadly), all user's would need to know what the new URL is in order to change relays and fetch events from the new location.

With Outbox however, clients will see that their user's follow this user, will then look up this user's relay list, and will know where they need to go to fetch their events. It becomes much more difficult for relays to censor or block users with an Outbox model in place

Duplicate event fetching

We talked earlier about how many nostr clients often fetch the same data many times, just to throw that data away. Even using the simplest algorithms with an Outbox model, you can significantly reduce the amount of duplicate data you're fetching from relays. We, as users, would all also need to specific many fewer relays in our relay lists but would still be quite sure our clients would be able to find all the content we want to see.

Wrapping up

Hopefully this has given you a better overall understanding of what folks are talking about when they refer to Gossip (remember: don't refer to it this way) or Outbox (outbox, yay!) and why we need to be proactive about maintaining the decentralization of nostr.

@ fe7f6bc6:c42539a3

Are you on a journey to become the healthiest version of yourself? You're not alone. This community is a space for over 350 health-conscious individuals, all dedicated to exploring and sharing insights about diets, lifestyle choices, and much more.

Connect with Like-minded Individuals Learn and Grow Together Be Part of a Supportive Network

Our community is more than just a forum—it’s a place where friendships are formed, knowledge is shared freely, and everyone is committed to becoming the best version of themselves.

Simply Subscribe and join us now!

Let's connect in our next community call 🧡 Max

@ 3bf0c63f:aefa459d

A response to Achim Warner's "Drivechain brings politics to miners" article

I mean this article: https://achimwarner.medium.com/thoughts-on-drivechain-i-miners-can-do-things-about-which-we-will-argue-whether-it-is-actually-a5c3c022dbd2

There are basically two claims here:

1. Some corporate interests might want to secure sidechains for themselves and thus they will bribe miners to have these activated

First, it's hard to imagine why they would want such a thing. Are they going to make a proprietary KYC chain only for their users? They could do that in a corporate way, or with a federation, like Facebook tried to do, and that would provide more value to their users than a cumbersome pseudo-decentralized system in which they don't even have powers to issue currency. Also, if Facebook couldn't get away with their federated shitcoin because the government was mad, what says the government won't be mad with a sidechain? And finally, why would Facebook want to give custody of their proprietary closed-garden Bitcoin-backed ecosystem coins to a random, open and always-changing set of miners?

But even if they do succeed in making their sidechain and it is very popular such that it pays miners fees and people love it. Well, then why not? Let them have it. It's not going to hurt anyone more than a proprietary shitcoin would anyway. If Facebook really wants a closed ecosystem backed by Bitcoin that probably means we are winning big.

2. Miners will be required to vote on the validity of debatable things

He cites the example of a PoS sidechain, an assassination market, a sidechain full of nazists, a sidechain deemed illegal by the US government and so on.

There is a simple solution to all of this: just kill these sidechains. Either miners can take the money from these to themselves, or they can just refuse to engage and freeze the coins there forever, or they can even give the coins to governments, if they want. It is an entirely good thing that evil sidechains or sidechains that use horrible technology that doesn't even let us know who owns each coin get annihilated. And it was the responsibility of people who put money in there to evaluate beforehand and know that PoS is not deterministic, for example.

About government censoring and wanting to steal money, or criminals using sidechains, I think the argument is very weak because these same things can happen today and may even be happening already: i.e., governments ordering mining pools to not mine such and such transactions from such and such people, or forcing them to reorg to steal money from criminals and whatnot. All this is expected to happen in normal Bitcoin. But both in normal Bitcoin and in Drivechain decentralization fixes that problem by making it so governments cannot catch all miners required to control the chain like that -- and in fact fixing that problem is the only reason we need decentralization.

@ 3bf0c63f:aefa459d

A violência é uma forma de comunicação

A violência é uma forma de comunicação: um serial killer, um pai que bate no filho, uma briga de torcidas, uma sessão de tortura, uma guerra, um assassinato passional, uma briga de bar. Em todos esses se pode enxergar uma mensagem que está tentando ser transmitida, que não foi compreendida pelo outro lado, que não pôde ser expressa, e, quando o transmissor da mensagem sentiu que não podia ser totalmente compreendido em palavras, usou essa outra forma de comunicação.

Quando uma ofensa em um bar descamba para uma briga, por exemplo, o que há é claramente uma tentativa de uma ofensa maior ainda pelo lado do que iniciou a primeira, a briga não teria acontecido se ele a tivesse conseguido expressar em palavras tão claras que toda a audiência de bêbados compreendesse, o que estaria além dos limites da linguagem, naquele caso, o soco com o mão direita foi mais eficiente. Poderia ser também a defesa argumentativa: "eu não sou um covarde como você está dizendo" -- mas o bar não acreditaria nessa frase solta, a comunicação não teria obtido o sucesso desejado.

A explicação para o fato da redução da violência à medida em que houve progresso da civilização está na melhora da eficiência da comunicação humana: a escrita, o refinamento da expressão lingüística, o aumento do alcance da palavra falada com rádio, a televisão e a internet.

Se essa eficiência diminuir, porque não há mais acordo quanto ao significado das palavras, porque as pessoas não estão nem aí para se o que escrevem é bom ou não, ou porque são incapazes de compreender qualquer coisa, deve aumentar proporcionalmente a violência.

@ 3bf0c63f:aefa459d

Pequenos problemas que o Estado cria para a sociedade e que não são sempre lembrados

- **vale-transporte**: transferir o custo com o transporte do funcionário para um terceiro o estimula a morar longe de onde trabalha, já que morar perto é normalmente mais caro e a economia com transporte é inexistente.
- **atestado médico**: o direito a faltar o trabalho com atestado médico cria a exigência desse atestado para todas as situações, substituindo o livre acordo entre patrão e empregado e sobrecarregando os médicos e postos de saúde com visitas desnecessárias de assalariados resfriados.
- **prisões**: com dinheiro mal-administrado, burocracia e péssima alocação de recursos -- problemas que empresas privadas em competição (ou mesmo sem qualquer competição) saberiam resolver muito melhor -- o Estado fica sem presídios, com os poucos existentes entupidos, muito acima de sua alocação máxima, e com isto, segundo a bizarra corrente de responsabilidades que culpa o juiz que condenou o criminoso por sua morte na cadeia, juízes deixam de condenar à prisão os bandidos, soltando-os na rua.
- **justiça**: entrar com processos é grátis e isto faz proliferar a atividade dos advogados que se dedicam a criar problemas judiciais onde não seria necessário e a entupir os tribunais, impedindo-os de fazer o que mais deveriam fazer.
- **justiça**: como a justiça só obedece às leis e ignora acordos pessoais, escritos ou não, as pessoas não fazem acordos, recorrem sempre à justiça estatal, e entopem-na de assuntos que seriam muito melhor resolvidos entre vizinhos.
- **leis civis**: as leis criadas pelos parlamentares ignoram os costumes da sociedade e são um incentivo a que as pessoas não respeitem nem criem normas sociais -- que seriam maneiras mais rápidas, baratas e satisfatórias de resolver problemas.
- **leis de trãnsito**: quanto mais leis de trânsito, mais serviço de fiscalização são delegados aos policiais, que deixam de combater crimes por isto (afinal de contas, eles não querem de fato arriscar suas vidas combatendo o crime, a fiscalização é uma excelente desculpa para se esquivarem a esta responsabilidade).
- **financiamento educacional**: é uma espécie de subsídio às faculdades privadas que faz com que se criem cursos e mais cursos que são cada vez menos recheados de algum conhecimento ou técnica útil e cada vez mais inúteis.
- **leis de tombamento**: são um incentivo a que o dono de qualquer área ou construção "histórica" destrua todo e qualquer vestígio de história que houver nele antes que as autoridades descubram, o que poderia não acontecer se ele pudesse, por exemplo, usar, mostrar e se beneficiar da história daquele local sem correr o risco de perder, de fato, a sua propriedade.
- **zoneamento urbano**: torna as cidades mais espalhadas, criando uma necessidade gigantesca de carros, ônibus e outros meios de transporte para as pessoas se locomoverem das zonas de moradia para as zonas de trabalho.
- **zoneamento urbano**: faz com que as pessoas percam horas no trânsito todos os dias, o que é, além de um desperdício, um atentado contra a sua saúde, que estaria muito melhor servida numa caminhada diária entre a casa e o trabalho.
- **zoneamento urbano**: torna ruas e as casas menos seguras criando zonas enormes, tanto de residências quanto de indústrias, onde não há movimento de gente alguma.
- **escola obrigatória + currículo escolar nacional**: emburrece todas as crianças.
- **leis contra trabalho infantil**: tira das crianças a oportunidade de aprender ofícios úteis e levar um dinheiro para ajudar a família.
- **licitações**: como não existem os critérios do mercado para decidir qual é o melhor prestador de serviço, criam-se comissões de pessoas que vão decidir coisas. isto incentiva os prestadores de serviço que estão concorrendo na licitação a tentar comprar os membros dessas comissões. isto, fora a corrupção, gera problemas reais: __(i)__ a escolha dos serviços acaba sendo a pior possível, já que a empresa prestadora que vence está claramente mais dedicada a comprar comissões do que a fazer um bom trabalho (este problema afeta tantas áreas, desde a construção de estradas até a qualidade da merenda escolar, que é impossível listar aqui); __(ii)__ o processo corruptor acaba, no longo prazo, eliminando as empresas que prestavam e deixando para competir apenas as corruptas, e a qualidade tende a piorar progressivamente.
- **cartéis**: o Estado em geral cria e depois fica refém de vários grupos de interesse. o caso dos taxistas contra o Uber é o que está na moda hoje (e o que mostra como os Estados se comportam da mesma forma no mundo todo).
- **multas**: quando algum indivíduo ou empresa comete uma fraude financeira, ou causa algum dano material involuntário, as vítimas do caso são as pessoas que sofreram o dano ou perderam dinheiro, mas o Estado tem sempre leis que prevêem multas para os responsáveis. A justiça estatal é sempre muito rígida e rápida na aplicação dessas multas, mas relapsa e vaga no que diz respeito à indenização das vítimas. O que em geral acontece é que o Estado aplica uma enorme multa ao responsável pelo mal, retirando deste os recursos que dispunha para indenizar as vítimas, e se retira do caso, deixando estas desamparadas.
- **desapropriação**: o Estado pode pegar qualquer propriedade de qualquer pessoa mediante uma indenização que é necessariamente inferior ao valor da propriedade para o seu presente dono (caso contrário ele a teria vendido voluntariamente).
- **seguro-desemprego**: se há, por exemplo, um prazo mínimo de 1 ano para o sujeito ter direito a receber seguro-desemprego, isto o incentiva a planejar ficar apenas 1 ano em cada emprego (ano este que será sucedido por um período de desemprego remunerado), matando todas as possibilidades de aprendizado ou aquisição de experiência naquela empresa específica ou ascensão hierárquica.
- **previdência**: a previdência social tem todos os defeitos de cálculo do mundo, e não importa muito ela ser uma forma horrível de poupar dinheiro, porque ela tem garantias bizarras de longevidade fornecidas pelo Estado, além de ser compulsória. Isso serve para criar no imaginário geral a idéia da __aposentadoria__, uma época mágica em que todos os dias serão finais de semana. A idéia da aposentadoria influencia o sujeito a não se preocupar em ter um emprego que faça sentido, mas sim em ter um trabalho qualquer, que o permita se aposentar.
- **regulamentação impossível**: milhares de coisas são proibidas, há regulamentações sobre os aspectos mais mínimos de cada empreendimento ou construção ou espaço. se todas essas regulamentações fossem exigidas não haveria condições de produção e todos morreriam. portanto, elas não são exigidas. porém, o Estado, ou um agente individual imbuído do poder estatal pode, se desejar, exigi-las todas de um cidadão inimigo seu. qualquer pessoa pode viver a vida inteira sem cumprir nem 10% das regulamentações estatais, mas viverá também todo esse tempo com medo de se tornar um alvo de sua exigência, num estado de terror psicológico.
- **perversão de critérios**: para muitas coisas sobre as quais a sociedade normalmente chegaria a um valor ou comportamento "razoável" espontaneamente, o Estado dita regras. estas regras muitas vezes não são obrigatórias, são mais "sugestões" ou limites, como o salário mínimo, ou as 44 horas semanais de trabalho. a sociedade, porém, passa a usar esses valores como se fossem o normal. são raras, por exemplo, as ofertas de emprego que fogem à regra das 44h semanais.
- **inflação**: subir os preços é difícil e constrangedor para as empresas, pedir aumento de salário é difícil e constrangedor para o funcionário. a inflação força as pessoas a fazer isso, mas o aumento não é automático, como alguns economistas podem pensar (enquanto alguns outros ficam muito satisfeitos de que esse processo seja demorado e difícil).
- **inflação**: a inflação destrói a capacidade das pessoas de julgar preços entre concorrentes usando a própria memória.
- **inflação**: a inflação destrói os cálculos de lucro/prejuízo das empresas e prejudica enormemente as decisões empresariais que seriam baseadas neles.
- **inflação**: a inflação redistribui a riqueza dos mais pobres e mais afastados do sistema financeiro para os mais ricos, os bancos e as megaempresas.
- **inflação**: a inflação estimula o endividamento e o consumismo.
- **lixo:** ao prover coleta e armazenamento de lixo "grátis para todos" o Estado incentiva a criação de lixo. se tivessem que pagar para que recolhessem o seu lixo, as pessoas (e conseqüentemente as empresas) se empenhariam mais em produzir coisas usando menos plástico, menos embalagens, menos sacolas.
- **leis contra crimes financeiros:** ao criar legislação para dificultar acesso ao sistema financeiro por parte de criminosos a dificuldade e os custos para acesso a esse mesmo sistema pelas pessoas de bem cresce absurdamente, levando a um percentual enorme de gente incapaz de usá-lo, para detrimento de todos -- e no final das contas os grandes criminosos ainda conseguem burlar tudo.

@ e8ed3798:67dd345a

[!NOTE] Definition Anamorphic (adj.): Relating to or involving a form of distortion in which an image or object is only recognizable when viewed from a specific angle or through a specific device, creating an optical illusion.

Anamorphic image encryption is a way of representing an image in cyberspace such that it may only be viewed from a specific location, and the viewed image may not be copied with high fidelity.

The below is theoretical and yet to be implemented in cyberspace. Feedback welcome!

Primitives

The POW action chain serves as a location primitive. If your action chain is valid, your avatar is in a specific location in cyberspace. The validation rules for action chains enable them to serve as a POW-based proof-of-location and a solution to a location "double spend" (being in 2 locations at once).

This location may be reacted to by a nostr bot watching for an action chain to reach a certain coordinate or area. Once reached, the bot can reveal a secret to the avatar (by sending a DM to their pubkey); the secret is necessary to view anamorphic content. This is a gatekeeper primitive.

If we want to make an image available at a specific location, we need to encode it properly.

If you know what a frustum is, skip this paragraph. Imagine a hollow pyramid. You pick it up and point the tip top of the pyramid right at your eyeball (carefully!). The base of the pyramid is parallel to you, away from your face. This shape is a frustum; it is an imaginary space where all of the objects you can see exist within. Our eyes actually see more of a cone, but in computer graphics the frustum is rectangular. Now think about one edge of the pyramid that goes from the tip at your eyeball to the base away from you; this edge is at the very edge of your "vision" or viewport. If you put a lightbulb on this edge and slid it back and forth from tip to the pyramid's base, it would grow and shrink but it would not change position from your perspective.

Kind 1 notes exist in cyberspace as cubes; each cube's location comes from a simhash of its content. The color of this cube is derived from the last 6 digits of the created_at in hex. Using seconds as a hex color means that the full gamut of hex-based colors spans 16777215 seconds (0xffffff) or 194 days or roughly 6.3 months. This serves as a pixel primitive. Cubes can be used as pixels and placed in specific locations in cyberspace by mining a note's content so that the simhash yields the desired location.

To review: - We have a location primitive -- the action chain enables us to be in a location. - We have a gatekeeper primitive -- we can be given access to information at a location. - We have a pixel primitive -- we can create images in space.

Depiction of an Image

However, we don't simply want to create a flat rectangular canvas in space, because that would be too recognizable and too easy to copy. We need more obfuscation if we are going to achieve anamorphic encryption.

Instead of a flat canvas, we can construct an image where each pixel is a random distance between the front and back of the frustum. Viewed form the frustum's perspective, it doesn't matter how far the pixel is from the viewer as long as the pixel stays on the same ray cast from the viewer's eyeball to the base of the frustum. If the pixels are randomly distributed across the 3D space of the frustum, then the image may only be seen from an angle very near the frustum's perspective.

Typically something gets smaller when it gets further away, but the kind 1 cubes as viewed in ONOSENDAI are scaled such that they actually grow in size as the viewer gets further away from them. This is to give an impression of the density of notes from a far distance and to enable the user to select them from a far distance when this would normally not be possible. So the distance to the pixel does not matter for the purpose of displaying the anamorphic image.

Obfuscation of the Pixels

The final piece to this puzzle is a cryptographic obfuscation of the pixels that assemble the image.

The artist should downscale their artwork so that it is low-resolution, such as 800x600 or whatever size is desired. Considerable POW is necessary to create an anamorphically encrypted image, so the size is important.

Then, the location in cyberspace and frustum should be chosen. The frustum can be of any size, although it would be advisable to keep it within 1 sector (2^30 Gibsons) in length (tip to base).

The pixels in the downscaled artwork should be divided into batches; this can be done in any order or direction or spatial arrangement. Each batch will be published by a separate public key in order to obfuscate the image further.

Next, ephemeral keypair 0 ($E0$) is generated to publish the first batch of pixels (kind 1 notes).

A kind 1 note is published to represent the top leftmost pixel. The created_at is set to a time where the last 6 digits of the time in hex equals the color of the pixel in the downscaled art. The content of the note, when simhashed, must yield a coordinate along the top left edge of the frustum. This is where the POW is required to produce an anamorphic encrypted image because many guesses may be required to obtain a good-enough result. Bear in mind that good-enough is permissible; it's up to the taste of the artist. This tolerance may be useful in adjusting the amount of POW necessary to successfully create each pixel.

A batch of kind 1 notes my be published with ephemeral key 0. When batch 0 of pixels is complete, the following should happen: - An even prefix length $L$ should be chosen. This determines the number of leading hex digits need to be matched for subsequent public keys. This prefix length should be the same for all subsequent batches. - A Secret $S$ of 256 random bits should be generated. This secret will also be used for all subsequent batches.

Public key target 1 is derived from $\text{sha256}( S + E0_{pub})$

Public keys are mined until a resulting public key's hex prefix of length $L$ matches Public key target 1's prefix of length $L$.

9884a42bcf930100... < target public key 988456aa3a87e4fb... < mined public key ^^^^ 4-length match

The matching mined keys will serve as ephemeral keypair 1 ($E1$).

[!Tip] Check out Rana for mining keypairs with specific prefixes: https://github.com/grunch/rana

Now, the next batch of pixels can be published with $E1$ until the batch is complete.

To obtain $E2$ for the third batch, derive your target from $\text{sha256}(S + E1_{pub})$. Mine until you find a public key with a prefix matching your target's prefix of $L$ hex digits long. Publish your third batch under that key. Repeat until your whole image is published.

[!Tip] To further obscure the relationship between the kind 1 notes and the pixels in your image, you can add random e/p tags to give the impression that the notes are actually part of a conversation, or other random tags to give the impression that they are used for something else.

Now, the artist must set up a bot that subscribes to cyberspace actions so that if an avatar enters a defined coordinate area, their pubkey will receive: - The first public key $E0_{pub}$ - The Secret $S$ - The prefix length $L$ - Relays to query for the pixels

Viewing the Anamorphically Encrypted Image

When an avatar looks into the void of cyberspace, they will see a lot of note cubes. Even if viewed from the correct location, the notes comprising the pixels of the artwork won't be free from unrelated clutter. Therefore, it's necessary to filter the notes in the interface to only show notes that comprise the image. To construct this filter requires the following steps.

Using the information supplied by the bot in the DM, the avatar can query nostr relays for notes published by $E0$. Then, the avatar may $\text{sha256}(S + E0_{pub})$ to obtain the target. They can get the prefix with target.substring(0, $L$) and then do a partial author query on the obtained prefix to find notes published by public keys matching that prefix.

[!WARNING] Partial queries on pubkeys must be an even number of hex digits. Make sure you choose an even prefix $L$.

This is where it is important to choose a prefix that is long enough to be fairly unique but short enough to not require a lot of extra POW.

Once you query the author prefix and find zero notes, then you have fully reconstructed the image. Until then, the avatar will continue to derive $E1$, $E2$, $E3$, etc. and query the notes they have published.

Now that the notes representing the pixels of the image are obtained, the client must position these notes in cyberspace as per usual, remove notes not matching the filters from view, and then the avatar must be in the correct location and looking toward the frustum.

Now, finally, the avatar may see the image that the artist intended to portray.

Anamorphic Properties

When viewing the image, there are some things to keep in mind: - to view the image, one must know which coordinate to travel to and actually go there with POW - the image is a low-fidelity recreation of the original image, so the full resolution original may not be reconstructed - the representation of the image via note cubes scattered inside a frustum introduces perspective errors into the viewing if the avatar is not perfectly positioned in line with the center of the frustum. This is actually a feature, not a bug. Because it is difficult to obtain an exact location in cyberspace, the subtle movement of the avatar will gradually obfuscate the depiction of the image as a function of distance from that ideal point. This makes screenshots and screen recordings suboptimal to capture the image as it will almost always contain defects and perspective errors. However, the way perception in our brains works tends to smooth over these imperfections in real-time, especially as we move. Think about looking through a smudged window or phone screen -- often you hardly notice it. Or, think about looking at something beyond a wire mesh or fence while moving. It's easier to see when you are moving even if the image is heavily obscured. - the method of batching and publishing the pixels across the frustum with ephemeral keys prevents observers from detecting that an image exists at all, and even if detected, from assembling every pixel due to the necessity of knowing the secret to derive all ephemeral keys. The only way that an image could accidentally be detected would be by accidentally visiting the exact place where the frustum focal point is located and looking in the correct direction, which is about as rare as generating a private key someone else owns.

To summarize, the anamorphic image is better interpreted by our brains than by a screenshot, especially as we move around in cyberspace. It is a way of displaying image content that requires a viewer to be in a place, meet a criteria, and severely limits their ability to take the image with them.

Potential Counters

Now, one way that the image could be copied is by copying the color data from the cubes once the cubes are known from the secrets provided by the gatekeeper. However, unless the cubes are addressed in cyberspace, they hold no pixel position data in themselves. If the note batches are chopped up creatively, it can be reasonably challenging to reassemble the image even if all the data is at hand.

Conclusion

This is a unique method of obfuscating visual content behind proof-of-work. The image may be seen, but only if enough cyberspace proof-of-work is provided. The image may not easily be copied or stolen, and will look better when experienced in cyberspace than any stolen representation will look because of how our brains interpret visual information.

@ 3bf0c63f:aefa459d

On HTLCs and arbiters

This is another attempt and conveying the same information that should be in Lightning and its fake HTLCs. It assumes you know everything about Lightning and will just highlight a point. This is also valid for PTLCs.

The protocol says HTLCs are trimmed (i.e., not actually added to the commitment transaction) when the cost of redeeming them in fees would be greater than their actual value.

Although this is often dismissed as a non-important fact (often people will say "it's trusted for small payments, no big deal"), but I think it is indeed very important for 3 reasons:

1. Lightning absolutely relies on HTLCs actually existing because the payment proof requires them. The entire security of each payment comes from the fact that the payer has a preimage that comes from the payee. Without that, the state of the payment becomes an unsolvable mystery. The inexistence of an HTLC breaks the atomicity between the payment going through and the payer receiving a proof.
2. Bitcoin fees are expected to grow with time (arguably the reason Lightning exists in the first place).
3. MPP makes payment sizes shrink, therefore more and more of Lightning payments are to be trimmed. As I write this, the mempool is clear and still payments smaller than about 5000sat are being trimmed. Two weeks ago the limit was at 18000sat, which is already below the minimum most MPP splitting algorithms will allow.

Therefore I think it is important that we come up with a different way of ensuring payment proofs are being passed around in the case HTLCs are trimmed.

Channel closures

Worse than not having HTLCs that can be redeemed is the fact that in the current Lightning implementations channels will be closed by the peer once an HTLC timeout is reached, either to fulfill an HTLC for which that peer has a preimage or to redeem back that expired HTLCs the other party hasn't fulfilled.

For the surprise of everybody, nodes will do this even when the HTLCs in question were trimmed and therefore cannot be redeemed at all. It's very important that nodes stop doing that, because it makes no economic sense at all.

However, that is not so simple, because once you decide you're not going to close the channel, what is the next step? Do you wait until the other peer tries to fulfill an expired HTLC and tell them you won't agree and that you must cancel that instead? That could work sometimes if they're honest (and they have no incentive to not be, in this case). What if they say they tried to fulfill it before but you were offline? Now you're confused, you don't know if you were offline or they were offline, or if they are trying to trick you. Then unsolvable issues start to emerge.

Arbiters

One simple idea is to use trusted arbiters for all trimmed HTLC issues.

This idea solves both the protocol issue of getting the preimage to the payer once it is released by the payee -- and what to do with the channels once a trimmed HTLC expires.

A simple design would be to have each node hardcode a set of trusted other nodes that can serve as arbiters. Once a channel is opened between two nodes they choose one node from both lists to serve as their mutual arbiter for that channel.

Then whenever one node tries to fulfill an HTLC but the other peer is unresponsive, they can send the preimage to the arbiter instead. The arbiter will then try to contact the unresponsive peer. If it succeeds, then done, the HTLC was fulfilled offchain. If it fails then it can keep trying until the HTLC timeout. And then if the other node comes back later they can eat the loss. The arbiter will ensure they know they are the ones who must eat the loss in this case. If they don't agree to eat the loss, the first peer may then close the channel and blacklist the other peer. If the other peer believes that both the first peer and the arbiter are dishonest they can remove that arbiter from their list of trusted arbiters.

The same happens in the opposite case: if a peer doesn't get a preimage they can notify the arbiter they hadn't received anything. The arbiter may try to ask the other peer for the preimage and, if that fails, settle the dispute for the side of that first peer, which can proceed to fail the HTLC is has with someone else on that route.

@ 1cb14ab3:95d52462

Chef's notes

The original Di Shui Dong ribs (and this recipe) use pork spare ribs- but I have made it using beef short ribs and lamb shanks as well. You can substitute for whatever ribs you prefer; the taste will remain the same.

Recipe is originally credit of 'Da Dinner Roll' -- Go show them some love below ⬇️ https://dadinnerblog.wordpress.com/2010/07/11/shanghai-food-hunan-cumin-ribs-di-shui-dongg-style/

Details

• ⏲️ Prep time: 30 mins
• 🍳 Cook time: 2.5 hours
• 🍽️ Servings: 6

Ingredients

• NEIL PERRY'S MASTER STOCK
• water
• 3 cloves garlic, sliced
• 1 knob ginger, sliced
• 1 handful shallot ends
• 1 stick cassia bark (Chinese cinnamon)
• 2 star anise
• 375 ml light soy sauce
• 375 ml. Shaoxing wine (绍兴酒)
• 75 g Chinese rock sugar
• SPICE COATING
• 1 tbsp. Shaoxing wine (绍兴酒)
• 1/2 tsp. salt
• 1 tsp. light soy sauce
• 1 tsp. dark soy sauce
• 1 tbsp. potato starch or cornflour
• 1 3/4 cups peanut oil
• 2 tsp. minced ginger
• 1 tbsp. finely chopped garlic
• 2 fresh red chilies, seeded and finely chopped
• 2 tbsp. cumin seeds
• 2 to 4 tsp. dried chili flakes
• 2 spring onions, green parts only, finely sliced
• 1 tsp. sesame oil

Directions

1. Fill a large stockpot ¾ full with cold water. Add the sliced garlic, ginger and shallots, followed by the aromatics. Add light soy, shaoxing wine and Chinese rock sugar and bring to a boil.
2. Strain the mix through a fine sieve and add the ribs. Simmer for 1 – 2 hours turning the ribs occasionally. Switch off the heat and let sit for 30 minutes. Transfer ribs to a dish and cool in the fridge.
3. To prepare the spice coating, mix cooking wine, salt, soy sauces, flour and one tablespoon water in. large bowl. Add cooled ribs and mix to marinade.
4. In a wok, heat peanut oil to about 275 degrees. Add ribs and stir gently for two to three minutes, then remove from oil with a slotted spoon and drain well. Pour off all but 3 tablespoons of oil in wok. Over a high flame, add the ginger, garlic, fresh chilies, chili flakes and cumin seeds and stir-fry briefly, until they are fragrant. Return ribs to the wok and stir well, seasoning with salt to taste.
5. When ribs are sizzling and fragrant, add spring onions and toss briefly. Remove from heat and stir in sesame oil.

@ 44dc1c2d:31c74f0b

Chef's notes

When adding things like extra veggies, if you don't want them to be mush, consider roasting veggies in the oven and only adding them near then end of the cook time. The same is generally true for meats.

While Parmesan is traditional, almost any cheese will work.

Choose your broth based on your needs (IE a veggie stock to make it more vegetarian friendly), water or more stock can be used in place of wine if need be.

Details

• ⏲️ Prep time: 20 min
• 🍳 Cook time: 25 min
• 🍽️ Servings: 4 mains or ~6 appetizers

Ingredients

• 1 onion, DIced
• ¼ cup butter
• 2 cups arborio rice
• 1 cup white wine
• 6 to 8 cups warm chicken broth
• 1 cup grated Parmigiano-Reggiano cheese

Directions

1. In a large saucepan over medium heat, soften the onion in half the butter. Add the rice and cook for 1 minute, stirring to coat well. Add the white wine and reduce until almost dry.
2. Add the broth, about 1 cup at a time, stirring frequently until the liquid is completely absorbed before adding more broth. Season with salt and pepper. Cook for 18 to 22 minutes or until the rice is al dente. Add broth, as needed.
3. Take off the heat and add the cheese, the remaining butter and the toppings of your choice. Stir until the texture is very creamy. Adjust the seasoning.
4. Dish up, sprinkle with a little Parmesan cheese, if desired. Enjoy.

@ b9c09954:815d302d

Part 1 of a 5 part series for beginners about the importance of online privacy.

The digital landscape is awash with free online services, offering everything from social connectivity to endless information repositories, all without explicitly charging the user a financial fee. This model of "free" access is underpinned by a less visible transaction, where personal data becomes the currency of exchange, rather than traditional money. This article explores the economic foundations of these services, revealing how they monetize user data through advertising, and how this practice intersects with government surveillance efforts.

Data Collection as Currency

The cornerstone of the free service economy is data collection. Every click, search, and social interaction generates a trove of data, which these services harvest to construct detailed user profiles. This information ranges from mundane browsing habits to precise location data, painting a comprehensive picture of an individual's online life.

Advertising Models

Advertising, tailored through the meticulous analysis of user data, forms the financial backbone of many free services. These platforms leverage the insights drawn from user data to offer targeted advertising spaces to businesses, creating a highly effective and lucrative advertising ecosystem. This model not only fuels the service's operations but also entrenches the practice of pervasive data collection.

Third-party Data Sharing

The revenue streams extend beyond advertising, with many services engaging in the practice of sharing or selling user data to third parties. This ecosystem includes data brokers, other businesses, and sometimes, government entities. The opacity of these transactions often leaves users unaware of the extent to which their data is commodified and circulated.

The Intersection with Government Surveillance

The vast repositories of data collected by these free services present a tantalizing resource for government entities. In an era where digital surveillance has become increasingly sophisticated, governments can, and do, leverage this data to monitor citizens. This surveillance might be justified on grounds ranging from national security to the enforcement of laws, but it raises profound privacy concerns.

• Social Media Platforms: These platforms have become a focal point for government monitoring, where public posts and even private messages can be scrutinized for various purposes.
• Search Engines and Free Apps: The data collected by search engines and applications—ranging from search history to location data—can be requisitioned by governments, providing them with detailed insights into individual behaviors and movements.

The Value of Personal Data Revisited

In light of these practices, the value of personal data extends beyond the commercial sphere into the realm of governance and control. The economic models of free services, while facilitating unprecedented access to services, have also created a surveillance infrastructure that can be utilized by governments to monitor citizens, often without their explicit consent.

Conclusion

The interplay between the economics of free online services and the potential for surveillance paints a complex picture of the modern digital ecosystem. While users enjoy access to a variety of services, the cost comes in the form of personal data, which is not only monetized by companies but also potentially used as a tool for government surveillance. Understanding these dynamics is crucial for navigating the digital world, prompting a need for greater transparency, user consent, and legal safeguards to protect individual privacy in the age of free services. This awareness is the first step towards fostering a digital environment that respects user privacy and minimizes unwarranted surveillance.

Goto Part 2

@ 44dc1c2d:31c74f0b

Chef's notes

Recommend kosher salt for this recipe as it has a better flavor with the cream.

If you have foam, either skim the top or you can use a torch to get a glass smooth finish on the top.

Details

• ⏲️ Prep time: 30 min
• 🍳 Cook time: 40 min
• 🍽️ Servings: 6

Ingredients

• 2 cups heavy cream
• 10 tablespoons sugar, divided
• 1 vanilla bean (or 1 teaspoon vanilla extract)
• 4 large egg yolks
• 1/2 teaspoon vanilla extract
• 1/4 teaspoon kosher salt
• For the Brûlée topping:
• 4 tablespoons sugar (2 teaspoons per ramekin)

Directions

1. Preheat oven to 325°F with a rack in the middle position: Arrange six 4-ounce ramekins in a 9x13 baking dish and set aside.
2. Prepare the vanilla bean: Split the vanilla bean in half and scrape out the seeds with the dull (non-cutting) side of a paring knife.
3. Warm the cream: In a medium saucepan, combine heavy cream, 4 tablespoons of the sugar, vanilla bean pod, vanilla bean seeds, and salt. Cook over medium heat, until it begins to simmer.
4. Infuse the cream: Once the cream begins to simmer, remove the pan from heat, cover, and let stand for 15 minutes to allow the vanilla bean to infuse into the cream. (If you’re replacing the vanilla bean with vanilla extract, skip this step.)
5. Separate the eggs and whisk with sugar: When your cream is almost done infusing, separate your eggs. Place the yolks in a medium-sized mixing bowl; save the whites for another purpose. Whisk the remaining 6 tablespoons of sugar into the yolks. (Don't combine the eggs and sugar too soon before you mix it with the warm cream because the sugar binds with the water in egg yolks, which constricts the proteins in yolks and creates eggy lumps. And you don't want eggy lumps in your custard!)
6. Temper the yolks and mix with the cream: While whisking the yolks continuously, slowly add one ladle (about 1/4 or 1/3 cup) of hot cream in a thin stream. Do this two or three more times. While whisking, slowly add the remaining cream to the egg mixture, followed by the vanilla extract. Strain the mixture through a fine mesh sieve into a second mixing bowl and discard the vanilla bean pod (this also helps strain out any small bits of egg that may have curdled).
7. At this point, the custard can be cooled and stored for up to 5 days. If you choose to bake them right from the fridge, you will probably need to add a couple of extra minutes.
8. Fill the ramekins: Divide the custard between the ramekins, filling each one just up to the inner rim, or about three-quarters of the way full.
9. Fill the hot water bath: Bring a kettle or pot of water to a boil. Fill the pan with the hot water until the water comes about two-thirds of the way up the side of the ramekins. Avoid splashing water into the custards.
10. Bake the custards: Transfer the pan with the custards to the oven and bake for 38 to 40 minutes. When ready, the crème brûlée should have a uniform jiggle in the middle; when you touch the center, it should spring back just a bit. If the sides hold firm but the center sloshes, they aren’t quite done yet. If they are set like Jell-O, they’ve overbaked, although they will still be delicious! Chill them, brûlée them, eat them, love them and celebrate your efforts. If they have overbaked to the point that they look risen in the center, toss them, start again
11. Cool and chill the custards: Remove the baking dish with the finished custards from the oven and set on a wire cooling rack. Let the custards cool in the water until you can safely pick up the ramekins by the rim with your fingers. This should take about 15 minutes, depending on how tender your fingers are. (Mine are like asbestos, so I tend to go in rather quickly.) Once removed from the water bath, let each custard rest on the cooling rack for about 15 more minutes. Use a spoon to skim any bubbles off the top, then cover each ramekin with plastic wrap and store in the fridge. Chill for at least 4 hours, or up to 4 days, before serving.
12. Brûlée the custards: When ready to serve, remove the custards from fridge. Sprinkle the surface of each custard evenly with about 1 teaspoon of granulated sugar. Rotate the custard as you sprinkle to make sure the sugar evenly coats the surface. Ignite your torch. Hold the flame about 4 inches from the surface of the sugar. Using a circular motion, move the flame across the surface. The sugar will at first begin to bead up, and then will eventually solidify into a hard sugar crust. You want to make sure all the sugar granules have melted, and the sugar has at least a tint of caramel color. The longer you torch the surface, the darker it will become and the more bitter the sugar crust will be. Sprinkle each of the custards with an additional teaspoon of sugar and brûlée the surface again.

@ 3bf0c63f:aefa459d

Problemas com Russell Kirk

A idéia central da “política da prudência[^1]” de Russell Kirk me parece muito correta, embora tenha sido melhor formulada pior no seu enorme livro do que em uma pequena frase do joanadarquista Lucas Souza: “o conservadorismo é importante, porque tem muita gente com idéia errada por aí, e nós podemos não saber distingüi-las”.

Porém, há alguns problemas que precisam ser esclarecidos, ou melhor explicados, e que me impedem de enxergar os seus argumentos como refutação final do meu já tão humilde (embora feroz) anarquismo. São eles:

I Percebo alguma coisa errada, não sei bem onde, entre a afirmação de que toda ideologia é ruim, ou “todas as ideologias causam confusão[^2]”, e a proposta conservadora de “conservar o mundo da ordem que herdamos, ainda que em estado imperfeito, de nossos ancestrais[^3]”. Ora, sem precisar cair em exemplos como o do partido conservador inglês -- que conservava a política inglesa sempre onde estava, e se alternava no governo com o partido trabalhista, que a levava cada vez mais um pouco à esquerda --, está embutida nessa frase, talvez, a idéia, que ao mesmo tempo é clara e ferrenhamente combatida pelos próprios conservadores, de que a história é da humanidade é uma história de progresso linear rumo a uma situação melhor.

Querer conservar o mundo da ordem que herdamos significa conservar também os vários erros que podem ter sido cometidos pelos nossos ancestrais mais recentes, e conservá-los mesmo assim, acusando toda e qualquer tentativa de propôr soluções a esses erros de ideologia? Ou será que conservar o mundo da ordem é escolher um período determinado que seja tido como o auge da história humana e tentar restaurá-lo em nosso próprio tempo? Não seria isto ideologia?

Ou, ainda, será que conservar o mundo da ordem é selecionar, entre vários períodos do passado, alguns pedaços que o conservador considerar ótimos em cada sociedade, fazer dali uma mistura de sociedade ideal baseada no passado e então tentar implementá-la? Quem saberia dizer quais são as partes certas?

II Sobre a questão do que mantém a sociedade civil coesa, Russell Kirk, opondo-a à posição libertária de que o nexo da sociedade é o autointeresse, declara que a posição conservadora é a de que “a sociedade é uma comunidade de almas, que une os mortos, os vivos e os ainda não nascidos, e que se harmoniza por aquilo que Aristóteles chamou de amizade e os cristãos chamam de caridade ou amor ao próximo”.

Esta é uma posição muito correta, mas me parece estar em contradição com a defesa do Estado que ele faz na mesma página e na seguinte. O que me parece errado é que a sociedade não pode ser, ao mesmo tempo, uma “comunidade baseada no amor ao próximo” e uma comunidade que “requer não somente que as paixões dos indivíduos sejam subjugadas, mas que, mesmo no povo e no corpo social, bem como nos indivíduos, as inclinações dos homens, amiúde, devam ser frustradas, a vontade controlada e as paixões subjugadas” e, pior, que “isso somente pode ser feito por um poder exterior”.

Disto aí podemos tirar que, da mesma forma que Kirk define a posição libertária como sendo a de que o autointeresse é que mantém a sociedade civil coesa, a posição conservadora seria então a de que essa coesão vem apenas do Estado, e não de qualquer ligação entre vivos e mortos, ou do amor ao próximo. Já que, sem o Estado, diz, ele, citando Thomas Hobbes, a condição do homem é “solitária, pobre, sórdida, embrutecida e curta”?

[^1]: este é o nome do livro e também um outro nome que ele dá para o próprio conservadorismo (p.99). [^2]: p. 101 [^3]: p. 102

@ 3bf0c63f:aefa459d

A command line utility to create and manage personal graphs, then write them to dot and make images with graphviz.

It manages a bunch of YAML files, one for each entity in the graph. Each file lists the incoming and outgoing links it has (could have listen only the outgoing, now that I'm tihnking about it).

Each run of the tool lets you select from existing nodes or add new ones to generate a single link type from one to one, one to many, many to one or many to many -- then updates the YAML files accordingly.

It also includes a command that generates graphs with graphviz, and it can accept a template file that lets you customize the dot that is generated and thus the graphviz graph.

rel

• https://github.com/fiatjaf/rel

@ 8fb140b4:f948000c

After my second attempt at running Lightning Network node went wrong, mainly due to my own mistake and bad cli interface of LND, I have decided to look deeply into the alternative implementation of the lightning node software. Eclair was more final choice driven by multiple reasons that I am planning to further talk about in this write-up. The main reason I even considered Eclair despite my dislike of Java and JVM, was that one of the largest lightning nodes on the network is ACINQ, and they are the company behind the implementation and maintenance of this open source software.

I’ve noticed them first after reading their blog about how they run $100M Lightning node and what level of care and thought they put into the whole implementation. Lightning is used to transfer large quantities of value across the internet, and I would only trust something well designed and actively maintained by the people who have to lose the most if they make a wrong choice.

Eclair in itself is not a complex implementation of the lightning network standards, and highly modular, which allows for an easy segregation of duties among different components of the node. One of the biggest sales-points for me was their approach of crash-only software which guarantees consistency of the state regardless of what happens with the running software. By that extension, to shutdown the node, you simply kill the process and start it again. It doesn’t matter what transactions were in-flight, or what stage they were in. This is huge, since anything can happen to a running node (e.g., failed disk, failed RAM, CPU, kernel panic, etc.)

Getting back to the architecture, the Eclair is simple and elegant in design and implementation. The node is separated into three main components that comprise the node: eclair-core, eclair-node, eclair-front. All of the entities are sandboxed actors (e.g., peer, channel, payment), which allows for scalabilities across CPUs and faults. This ensures high availability and security.

Clustering is also an option and can be achieved by migrating from the single node to a multi-server node. There is no need to dive into complexities of that, and by the time you need to scale, I am sure you’ll be able to figure it out.

Simple and robust API, is yet another major reason that keeps the node simple and fast. One downside of the API, is that it is protected by a single password and is not designed for RBAC (Role Based Access Control). One solution could be an implementation of another API wrapper that would implement things similar to Runes or Macaroons, which should not be a challenge considering the REST API simplicity.

On-the-fly HTLC max size adjustment, which will prevent your node accepting forwarded payments that would fail due to lack of liquidity on your side. This also makes routing better for the rest of the lightning network, but may “leak” your channel balances if not done right.

Experimentation and adjustment of path-finding algorithm. I am not there yet myself, but I see this as a great option in the future if I need it. This will allow me to make my own choices how I want to route payments and what parameters I would use to determine the best path.

Full production support of PostgreSQL server. Not only Eclair itself is not a beta release unlike LND, but also has full production support of the very reliable and battle tested database as its backend data storage. You are able to(and should) to run Active/Passive PostgreSQL cluster in synchronous mode, and ensure that all of the written data by the node are backed-up in real-time. This removes the worry of corrupted database that I have seen happen all too often.

Excellent monitoring and metrics, that can be collected by Prometheus and viewed in Grafana. Eclair provides template dashboards that you can import into Grafana to make your life easier. You can also use Kamon (external service) where you could send the metrics and monitor your node.

Support for all common networking protocols and support Socks5.

Last, but not least, support for plug-ins. Even if you are not well versed in writing plug-ins, you could take some of the available ones and modify them to your liking.

There are many more features and limitations that I didn’t mention, but you can explore them yourself here.

One down-side that you should consider, is not such a great availability of the readily available tools. So far I found that Ride-The-Lightning works well; LNBits works but I am yet to see if it is reliable; BTCPayServer has support but I have failed to use it with API directly, and only was able to use it via LNBits.

Lightning is still reckless, but nothing stops you from doing it carefully and reliably. Good luck and happy node-running! 🐶🐾🫡⚡️

My Node - RAϟKO

@ 3f770d65:7a745b24

The following is a collection of Tweets posted on Twitter that documented my entire heart surgery process, from finding out I had an issue, through the surgery, and finally throughout my recovery process. If Elon decides to remove old and unpaid content, I do not want this part of my life to vanish from the Internet. At the time, it was extremely important for my mental health to talk about this whole process and it was therapeutic in my recovery process, reading all of the responses as all of Bitcoin Twitter was behind my success. Thank you all of your kind words, love, and support during this whole process. May my Tweets live on through nostr.

...

Nov 28, 2021 I had open heart surgery 4 days before my 3rd b-day. I've led a healthy & active life since then, zero issues. I had an echocardiogram last week. The results were not good. Heart valve replacement may be in my near future. I am freaking the fuck out. I'll know more on Dec 6th. 😫

Dec 6, 2021 Update: I had my cardiologist appointment today. He said to not worry for now and continue to exercise and live life. In 3 months get another echo done. He doesn't believe the previous other results since I have zero symptoms and wants to do his own interpretation.

Dec 6, 2021 He said if the other results were correct, I may need valve replacement in 6 months to 3 years. However, he doesn't believe the local hospital's results as I said above. He can't form an opinion just yet. He said not to worry over and over again. For now, I'm staying positive!

Mar 7, 2022 Well, it's been three months. I had my follow up this morning. I have severe pulmonic regurgitation. I now need to speak with a specialist and see what my options are for surgery. Neat. 😭

Apr 12, 2022 Well, it looks like I'll need full open heart surgery again to replace my pulmonic valve. Bonus: I'll be part pig. So, I have that going for me. I was assuming that if I had to have this done it would be much less invasive, so I'm not overly impressed at the moment. 🫤

May 11, 2022 Today I had to get a CT scan of my heart in preparation for the May 27th surgery. All went well. I have no other heart issues. It's looking like I'll be in the hospital for 4-7 days, depending on how fast I recover. I should be fully 100% recovered by the end of August. ❤️

May 20, 2022 My grandfather with me 39 years ago, days after my open heart surgery. He taught me to hunt, fish, golf, and I'm sure taught me a thing or two about drinking beer and partying. 😂 He was a great man. He won't physically be with me next Friday, but I'm sure he'll be watching over.

May 25, 2022 Two more sleeps. My mind is racing with an incredible amount of thoughts and emotions now. It's overwhelming. I love you all. Thanks for all of your replies and DMs over the last couple days, weeks, and months. I appreciate it immensely. ❤️❤️❤️

May 25, 2022 Two more sleeps. My mind is racing with an incredible amount of thoughts and emotions now. It's overwhelming. I love you all. Thanks for all of your replies and DMs over the last couple days, weeks, and months. I appreciate it immensely. ❤️❤️❤️

May 27, 2022 LET'S GO! I am alive and doing well. I was on a ventilator until 8pm. That was horrible. I will read all of the comments that you all posted on Katie's updates. Now I need to rest. They want to get me up and walk at 11pm. 🤯 I love you all and your support had helped so much 🧡🧡

May 28, 2022 The amount of love, compassion, caring, and appreciation from everyone blows my mind. Thanks for all of your comments and DMs. The positivity though all is this has helped me get through dark times and now it's helping me get through pain. You are helping me immensely. 🤯❤️🧡💪

May 28, 2022 Today has been a rough day. Lots of chest pain when breathing. But, I apparently am doing something right, because I have been upgraded to a regular room. No more ICU for this guy! My ICU nurse told my new nurse that I'm strong. ❤️💪🔥

May 29, 2022 Using this to document my journey. Last night was not good at all. I had tachycardia and AFib for hours. It was scary as fuck having my heart beat the way it was at 160bpm. They gave me new medication to bring it down and stop the AFib irregular heartbeat. It's now at 101.

May 29, 2022 I was very scared. Katie was able to come and stay the night with me and be my personal care nurse. That made me feel much better having her here with me. Hopefully the meds continue to do what they're supposed to. Fuck. Anyways, I may not Tweet much today. Love you all. ❤️

May 30, 2022 Today has mostly been a great day progress wise. I ate a lot. I've walked more today than I have previously. My doctor told me I might be going home tomorrow, it all depends on what happens with my last drainage tube. Fingers crossed that it's draining properly now. 💪❤️

May 31, 2022 Morning walk crushed. Breakfast crushed. Feeling stronger. My drainage tube is still draining so we'll see what the surgeon says, but I probably won't be coming home today according to my nurse. It may be another day. Better to be safe. I'm feeling good though. Let's go! 💪💪❤️❤️

Jun 1, 2022 Today's plans: Crush morning walk, crush breakfast, CRUSH MY LAST X-RAY AND HEAD THE HELL HOME! Fingers crossed. 🤞🤞❤️❤️💪💪

Jun 1, 2022 On my morning walk I went into a slight AFib. The nurse and PA said since I hadn't had my morning meds to control that yet, that that could be the cause. They're going to increase meds and monitor me for another 24 hours. That sucks, but again, I'd rather be safe. Ugh.

Jun 2, 2022 GM! I miss my kids. I miss wearing normal clothes. I miss my house. I miss my doggy. I better go home today or I guess I'll just keep working to get well enough to go home. 😂 I'm still progressing forward. I have a chest x-ray scheduled later this morning. Fingers crossed.

Jun 2, 2022 I JUST GOT CLEARED TO HEAD HOME AFTER LUNCH. FUCK YEAH. LET'S GOOOOOO💪💪💪

Jun 2, 2022 I am home! I have some family that needs some loving. Enjoy the rest of your day!

Jun 4, 2022 Last night I slept in bed thanks to a reclining pillow, the first night our living room chair. I was so happy to sleep in my own bed. I walked around our yard about 9 times yesterday. My goal is to do that plus a little more every day. I'm still in a lot of pain, but meds help.

Jun 4, 2022 I still have a long way to go recovery wise, but having Katie and the kids here helping me along the way makes it easier and gives me a reason to keep pushing forward through this. Thanks again for all of your past and future support. You all are fantastic.

Jun 6, 2022 My wife went back to work today. My son and daughter are in charge of taking care of me. My kids are fantastic. They made me breakfast already and helped me check all of my vitals. My daughter really shines here. She's such a little nurse and caretaker. ❤️❤️

Jun 6, 2022 I'm still in pain, but I'm not in as much pain as I was a couple days ago. I'm walking around a little better and a little more every day. I really hate just sitting around and not doing anything, but it's hard to do much else besides watch TV. I am enjoying my patio though. 💪

Jun 16, 2022 It's been a while. It's time to update this thread! I am doing great, IMO. I have lots of energy. I feel great. I can do a lot more than I previously could. I still have a limited range of motion due to my sternum being broken and still healing. i.e. I can't wash my back or legs.

Jun 16, 2022 I started back to work yesterday. I was cleared to do 20 hours this week by my doctor and I'm hoping to be cleared full time next week. I work from home, so if I can sit in front of a TV, I can sit in front of a computer, right?

Jun 16, 2022 My home nurses have been absolutely fantastic.😂 My kids make me breakfast every morning. And I could not have done any of this without my rock star wife. Words can't describe how much she's done for me throughout all of this. I am looking forward to continuing to improve. ♥️

Jun 16, 2022 You all have been absolutely wonderful through all of this too. I appreciate all of your love, support, and check-ins. Seriously. It means more than you know.

I have a check-up at the end of the month to make sure all is well. I'll update again in a couple weeks after that appt.

Jun 28, 2022 My doctor said everything looks great. He said it doesn't look like I had open heart surgery a month ago.💪 He said I have zero restrictions and that I can resume normal life. I can drive and I can go out on my boat! ❤️❤️❤️ I'm so happy right now! 🔥🚀

Jul 15, 2022 I started cardiac rehab this week. After 2 sessions the nurse said I'm on "Week 4" already. She doesn't believe with my initial intake stress test if I'll really be able to improve on it that much. 🤣 TL;DR I am a rock star and kicking ass. Feeling great. Life's great. 😍

Aug 28, 2022 Yesterday was 3 months since my open heart surgery. I'm going great! I'd guess essentially back to normal. My sternum is still not fully healed, that'll take more time, but energy and capability are basically back to what I was like last summer. I'm very happy with the results.

Aug 28, 2022 I'm very happy to be able to exercise daily, go boating on the weekends AND swim and paddleboard. I was annoyed that I couldn't do these things a month ago. I had a cardiologist appt. two weeks ago. He said he hopes the valve lasts me the rest of my life and to see him in a year.

Aug 28, 2022 As a final post to this thread, I want to thank each and every one of you again that commented, liked, shared and DMed me throughout all of this. The love and support from Twitter and the #Bitcoin community was unfathomable. You all made a difference in my life and my recovery.❤️

@ 3bf0c63f:aefa459d

GraphQL vs REST

Today I saw this: https://github.com/stickfigure/blog/wiki/How-to-(and-how-not-to)-design-REST-APIs

And it reminded me why GraphQL is so much better.

It has also reminded me why HTTP is so confusing and awful as a protocol, especially as a protocol for structured data APIs, with all its status codes and headers and bodies and querystrings and content-types -- but let's not talk about that for now.

People complain about GraphQL being great for frontend developers and bad for backend developers, but I don't know who are these people that apparently love reading guides like the one above of how to properly construct ad-hoc path routers, decide how to properly build the JSON, what to include and in which circumstance, what status codes and headers to use, all without having any idea of what the frontend or the API consumer will want to do with their data.

It is a much less stressful environment that one in which we can just actually perform the task and fit the data in a preexistent schema with types and a structure that we don't have to decide again and again while anticipating with very incomplete knowledge the usage of an extraneous person -- i.e., an environment with GraphQL, or something like GraphQL.

By the way, I know there are some people that say that these HTTP JSON APIs are not the real REST, but that is irrelevant for now.

@ 8fb140b4:f948000c

Disclaimer, this tutorial may have a real financial impact on you, follow at you own risk.

Step 1: execute lncli closeallchannels

That’s it, that was easy as it could be. Now all your node’s channels are in the process of being closed and all your liquidity is being moved to your onchain wallet. The best part, you don’t even need to confirm anything, it just does it in one go with no questions asked! You can check the status by using a very similar looking command, lncli closedchannels!

Good job! Now you are ready to start from scratch and use any other reasonable solution!

🐶🐾🫡🤣🤣🤣

Disclaimer: this is a satirical tutorial that will 💯 cost you a lot of funds and headaches.

@ c8df6ae8:22293a06

"You can't trust any communication anymore unless it is cryptographically signed."

— Guy Swann

With Artificial Intelligence, anything can be created and put in a video. A community called the Content Authenticity Initiative is promoting a centralized media provenance standard to address this problem.

> I believe Nostr can provide a better, and decentralized, solution.

The problem

Allow me to illustrate the problem with two sample fake videos.

This is an easy one. The video is telling you that it's fake.

But what about this one?

This short YouTube video has 4M views and realizing that it is fake takes some digging around that most people don't have the time or patience for.

I know it is fake because I searched for the original Joe Rogan podcast episode with Miley Cyrus and saw that he was wearing different clothes for the interview than what this short video shows. This tells me that the two clips, although real, belong to different episodes and Joe Rogan was not making fun of Miley Cyrus.

This is an insidious video that uses two authentic clips of Joe Rogan to create a false story and rack up views.

The centralized solution

The Coalition for Content Provenance and Authenticity, C2PA, is the standard body developing the new media provenance standard. It has some heavy weights behind it: Adobe, Microsoft, Google, Amazon, Intel, ARM and lots of corporate media companies.

Which really makes me wonder: why has it not taken off?

Their solution is not a bad solution, except for one teeny tiny problem: it's uses a fully centralized architecture: - Identity is centralized with Central Authorities issuing X.509 certificates to validate the authenticity of the signature of the author. - The information containing the provenance of a video is uploaded to the cloud repository of a provider that you, as the consumer of the video, must trust is not manipulating the information. - The standard allows for self-signed certificates for when anonymity is required, but it considers this to be an exception, and as such, restricts the usage of self-signing certificates to only instances where the consumer (validator) has manually imported the self-signed certificate, limiting the broad adoption of anonymous material.

To see the system in action with a picture, open the link below and click on the cr icon on the top left corner of the picture to see a pop-up menu with the provenance information. You can go a step further by clicking on the link Verify on ContentCredentials.org at the bottom of the pop-up menu.

https://adobe-cai.smartframe.io/p/img_20211028_173913_1637592139900/3b4a09bdfec70cde02b69400de8c28e7

The Nostr solution

The C2PA specification is built with one use in mind: the distribution of media from a limited set of producers (e.g., corporate media) to a large set of consumers.

The architecture implies that there will be one or two main stream media editing applications (e.g. Adobe) and that the number of Certificate Authorities will be small. It is not meant to scale on the supply side.

This system is not built to protect the communication of regular people. They can't seriously expect regular people to pay a Central Authority to maintain their digital identity.

That's where Nostr comes in. With its decentralized and permission-less architecture, Nostr can deliver media provenance for the masses at no cost and with no central authority acting as the Mnistry of Truth.

Nostr identity

The Nostr solution uses Nostr profiles as identity. You can create your profile without permission from anyone and it's your responsibility to build the reputation of that profile either face-to-face or through consistent online interactions.

The application retrieving the provenance for a video (e.g., a web browser plugin) will use Nostr to retrieve the latest kind:0 event of the author and display his or her information to the consumer of the video.

Nostr events hold media provenance data

NIP-94 defines event type kind:1063 that contains the description of a media file and a series of tags including the URL to the file, the hash of the original file and the hash of the files after processing by the server storing the media.

The Nostr version of the media editing application would upload the media to e.g. creatr.nostr.wine and publish an event kind:1063 with the URL, hash and other relevant provenance information. The event is signed by the author, cryptographically tying him or her to the media. The event would be sent to multiple relays ensuring censorship resistance.

The web browser plugin playing the media would calculate the hash and query any of the relays for an event with the tag matching the hash of the file. Alternatively, the system could also use perception hashes to account for clips and crops.

NIP-94 would need to be modified to support embedded kind:1063 events. A video like the second example above would have a kind:1063 event signed by the author and this event would contain two additional kind:1063 events, both signed by Joe Rogan, one for the video of the Miley Cyrus interview and another one for the second video.

The browser plugin could show a: - Green icon: for signed and validated media that is fully unmodified (e..g a full length video created by Joe Rogan). - Yellow icon: for signed and validated media that contains multiple clips, all signed and validated as well (like a signed version of the second video above). - Red icon: for an non-validated media file or a signed and validated media file where not all clips are signed and validated (like the current version of the second video above).

Challenges ahead

The main challenge is adoption. A I said before, I'm surprised that the C2PA system has not taken off given who is behind it.

In my opinion, Twitter, Facebook, Threads and WhatsApp are the main distribution channels for fake videos and it will be nearly impossible to convince Elon Musk and Mark Zuckerberg to support a Nostr-based solution instead of the C2PA solution.

Let's turn the main strength of our enemy into their weakness. Let's make Nostr clients the place where you come for cryptographically signed videos.

We need three things: - On the authentication side: a Nostr client capable of signing media files, uploading the media to the desired repository, and broadcasting the enhanced kind:1063 event to Nostr relays. - This could be a standalone app or a plugin for media editing software. - On the validation side: a Nostr client capable of querying relays for kind:1063 events containing the hash of the media being played - This could be a browser plugin or integrated with existing Nostr clients for a better experience. - Relays that accept write and read actions for kind:1063 events

A possible business model would be for the relay to charge per kind:1063 event stored (one time and monthly fee for maintaining it). The company offering the provenance relay could provide the authentication client or could also accept write request from FOSS authentication clients.

What do you think? Please leave your thoughts in the comments below and repost for visibility.

---

Notable notes

nostr:note19pkmfe2wpt5pplarptkjzxak7ed6wfdk0xvdq69042h3gz2hj2hs89wvg9

nostr:note1sfdk3f8nhxggttkz3ftau4utk6preynnu9gdpjv5qwm0xmt4ytrqmra3g7

---

Recommendations

Average Gary

Gary is talking the talk and walking the walk, spreading the love of Bitcoin in Virginia through the Shenandoah Bitcoin Club.

You can follow him here.

---

What did you think of today's newsletter?

Your feedback helps me create the best newsletter possible for you.

Please leave a comment and checkout comments from other subscribers and readers. I love hearing from the Bitcoin For Families community ❤️ 🙏🏻

---

See you again next week! — Alejandro

This newsletter is for educational purposes. It does not represent financial advice. Do your own research before buying Bitcoin.

@ 3bf0c63f:aefa459d

início

"Vocês vêem? Vêem a história? Vêem alguma coisa? Me parece que estou tentando lhes contar um sonho -- fazendo uma tentativa inútil, porque nenhum relato de sonho pode transmitir a sensação de sonho, aquela mistura de absurdo, surpresa e espanto numa excitação de revolta tentando se impôr, aquela noção de ser tomado pelo incompreensível que é da própria essência dos sonhos..."

Ele ficou em silêncio por alguns instantes.

"... Não, é impossível; é impossível transmitir a sensação viva de qualquer época determinada de nossa existência -- aquela que constitui a sua verdade, o seu significado, a sua essência sutil e contundente. É impossível. Vivemos, como sonhamos -- sozinhos..."

• Livros mencionados por Olavo de Carvalho
• Antiga homepage Olavo de Carvalho
• Bitcoin explicado de um jeito correto e inteligível
• Reclamações

---

• Nostr
• Bitcoin
• How IPFS is broken
• Programming quibbles
• Economics
• Open-source software

---

Nostr GitHub Telegram Donate

@ 3bf0c63f:aefa459d

nostr - Notes and Other Stuff Transmitted by Relays

The simplest open protocol that is able to create a censorship-resistant global "social" network once and for all.

It doesn't rely on any trusted central server, hence it is resilient; it is based on cryptographic keys and signatures, so it is tamperproof; it does not rely on P2P techniques, therefore it works.

Very short summary of how it works, if you don't plan to read anything else:

Everybody runs a client. It can be a native client, a web client, etc. To publish something, you write a post, sign it with your key and send it to multiple relays (servers hosted by someone else, or yourself). To get updates from other people, you ask multiple relays if they know anything about these other people. Anyone can run a relay. A relay is very simple and dumb. It does nothing besides accepting posts from some people and forwarding to others. Relays don't have to be trusted. Signatures are verified on the client side.

This is needed because other solutions are broken:

The problem with Twitter

• Twitter has ads;
• Twitter uses bizarre techniques to keep you addicted;
• Twitter doesn't show an actual historical feed from people you follow;
• Twitter bans people;
• Twitter shadowbans people.
• Twitter has a lot of spam.

The problem with Mastodon and similar programs

• User identities are attached to domain names controlled by third-parties;
• Server owners can ban you, just like Twitter; Server owners can also block other servers;
• Migration between servers is an afterthought and can only be accomplished if servers cooperate. It doesn't work in an adversarial environment (all followers are lost);
• There are no clear incentives to run servers, therefore they tend to be run by enthusiasts and people who want to have their name attached to a cool domain. Then, users are subject to the despotism of a single person, which is often worse than that of a big company like Twitter, and they can't migrate out;
• Since servers tend to be run amateurishly, they are often abandoned after a while — which is effectively the same as banning everybody;
• It doesn't make sense to have a ton of servers if updates from every server will have to be painfully pushed (and saved!) to a ton of other servers. This point is exacerbated by the fact that servers tend to exist in huge numbers, therefore more data has to be passed to more places more often;
• For the specific example of video sharing, ActivityPub enthusiasts realized it would be completely impossible to transmit video from server to server the way text notes are, so they decided to keep the video hosted only from the single instance where it was posted to, which is similar to the Nostr approach.

The problem with SSB (Secure Scuttlebutt)

• It doesn't have many problems. I think it's great. In fact, I was going to use it as a basis for this, but
• its protocol is too complicated because it wasn't thought about being an open protocol at all. It was just written in JavaScript in probably a quick way to solve a specific problem and grew from that, therefore it has weird and unnecessary quirks like signing a JSON string which must strictly follow the rules of ECMA-262 6th Edition;
• It insists on having a chain of updates from a single user, which feels unnecessary to me and something that adds bloat and rigidity to the thing — each server/user needs to store all the chain of posts to be sure the new one is valid. Why? (Maybe they have a good reason);
• It is not as simple as Nostr, as it was primarily made for P2P syncing, with "pubs" being an afterthought;
• Still, it may be worth considering using SSB instead of this custom protocol and just adapting it to the client-relay server model, because reusing a standard is always better than trying to get people in a new one.

The problem with other solutions that require everybody to run their own server

• They require everybody to run their own server;
• Sometimes people can still be censored in these because domain names can be censored.

How does Nostr work?

• There are two components: clients and relays. Each user runs a client. Anyone can run a relay.
• Every user is identified by a public key. Every post is signed. Every client validates these signatures.
• Clients fetch data from relays of their choice and publish data to other relays of their choice. A relay doesn't talk to another relay, only directly to users.
• For example, to "follow" someone a user just instructs their client to query the relays it knows for posts from that public key.
• On startup, a client queries data from all relays it knows for all users it follows (for example, all updates from the last day), then displays that data to the user chronologically.
• A "post" can contain any kind of structured data, but the most used ones are going to find their way into the standard so all clients and relays can handle them seamlessly.

How does it solve the problems the networks above can't?

• Users getting banned and servers being closed
• A relay can block a user from publishing anything there, but that has no effect on them as they can still publish to other relays. Since users are identified by a public key, they don't lose their identities and their follower base when they get banned.
• Instead of requiring users to manually type new relay addresses (although this should also be supported), whenever someone you're following posts a server recommendation, the client should automatically add that to the list of relays it will query.
• If someone is using a relay to publish their data but wants to migrate to another one, they can publish a server recommendation to that previous relay and go;
• If someone gets banned from many relays such that they can't get their server recommendations broadcasted, they may still let some close friends know through other means with which relay they are publishing now. Then, these close friends can publish server recommendations to that new server, and slowly, the old follower base of the banned user will begin finding their posts again from the new relay.

• All of the above is valid too for when a relay ceases its operations.

• Censorship-resistance

• Each user can publish their updates to any number of relays.

• A relay can charge a fee (the negotiation of that fee is outside of the protocol for now) from users to publish there, which ensures censorship-resistance (there will always be some Russian server willing to take your money in exchange for serving your posts).

• Spam

• If spam is a concern for a relay, it can require payment for publication or some other form of authentication, such as an email address or phone, and associate these internally with a pubkey that then gets to publish to that relay — or other anti-spam techniques, like hashcash or captchas. If a relay is being used as a spam vector, it can easily be unlisted by clients, which can continue to fetch updates from other relays.

• Data storage

• For the network to stay healthy, there is no need for hundreds of active relays. In fact, it can work just fine with just a handful, given the fact that new relays can be created and spread through the network easily in case the existing relays start misbehaving. Therefore, the amount of data storage required, in general, is relatively less than Mastodon or similar software.

• Or considering a different outcome: one in which there exist hundreds of niche relays run by amateurs, each relaying updates from a small group of users. The architecture scales just as well: data is sent from users to a single server, and from that server directly to the users who will consume that. It doesn't have to be stored by anyone else. In this situation, it is not a big burden for any single server to process updates from others, and having amateur servers is not a problem.

• Video and other heavy content

• It's easy for a relay to reject large content, or to charge for accepting and hosting large content. When information and incentives are clear, it's easy for the market forces to solve the problem.

• Techniques to trick the user

• Each client can decide how to best show posts to users, so there is always the option of just consuming what you want in the manner you want — from using an AI to decide the order of the updates you'll see to just reading them in chronological order.

FAQ

• This is very simple. Why hasn't anyone done it before?

I don't know, but I imagine it has to do with the fact that people making social networks are either companies wanting to make money or P2P activists who want to make a thing completely without servers. They both fail to see the specific mix of both worlds that Nostr uses.

• How do I find people to follow?

First, you must know them and get their public key somehow, either by asking or by seeing it referenced somewhere. Once you're inside a Nostr social network you'll be able to see them interacting with other people and then you can also start following and interacting with these others.

• How do I find relays? What happens if I'm not connected to the same relays someone else is?

You won't be able to communicate with that person. But there are hints on events that can be used so that your client software (or you, manually) knows how to connect to the other person's relay and interact with them. There are other ideas on how to solve this too in the future but we can't ever promise perfect reachability, no protocol can.

• Can I know how many people are following me?

No, but you can get some estimates if relays cooperate in an extra-protocol way.

• What incentive is there for people to run relays?

The question is misleading. It assumes that relays are free dumb pipes that exist such that people can move data around through them. In this case yes, the incentives would not exist. This in fact could be said of DHT nodes in all other p2p network stacks: what incentive is there for people to run DHT nodes?

• Nostr enables you to move between server relays or use multiple relays but if these relays are just on AWS or Azure what’s the difference?

There are literally thousands of VPS providers scattered all around the globe today, there is not only AWS or Azure. AWS or Azure are exactly the providers used by single centralized service providers that need a lot of scale, and even then not just these two. For smaller relay servers any VPS will do the job very well.

@ 3bf0c63f:aefa459d

LessPass remoteStorage

LessPass is a nice idea: a password manager without any state. Just remember one master password and you can generate a different one for every site using the power of hashes.

But it has a very bad issue: some sites require just numbers, others have a minimum or maximum character limits, some require non-letter characters, uppercase characters, others forbid these and so on.

The solution: to allow you to specify parameters when generating the password so you can fit a generated password on every service.

The problem with the solution: it creates state. Now you must remember what parameters you used when generating a password for each site.

This was a way to store these settings on a remoteStorage bucket. Since it isn't confidential information in any way, that wasn't a problem, and I thought it was a good fit for remoteStorage.

Some time later I realized it maybe would be better to have a centralized repository hosting all weird requirements for passwords each domain forced on its users, and let LessPass use data from that central place when generating a password. Still stateful, not ideal, not very far from a centralized password manager, but still requiring less trust and less cryptographic assumptions.

• https://github.com/fiatjaf/lesspass-remotestorage
• https://addons.mozilla.org/firefox/addon/lesspass-remotestorage/
• https://chrome.google.com/webstore/detail/lesspass-remotestorage/aogdpopejodechblppdkpiimchbmdcmc
• https://lesspass.alhur.es/

See also

• hledger-web
• TiddlyWiki remoteStorage

@ 3bf0c63f:aefa459d

idea: Custom multi-use database app

Since 2015 I have this idea of making one app that could be repurposed into a full-fledged app for all kinds of uses, like powering small businesses accounts and so on. Hackable and open as an Excel file, but more efficient, without the hassle of making tables and also using ids and indexes under the hood so different kinds of things can be related together in various ways.

It is not a concrete thing, just a generic idea that has taken multiple forms along the years and may take others in the future. I've made quite a few attempts at implementing it, but never finished any.

I used to refer to it as a "multidimensional spreadsheet".

Can also be related to DabbleDB.

@ b12b632c:d9e1ff79

CASHU AND ECASH ARE EXPERIMENTAL PROJECTS. BY THE OWN NATURE OF CASHU ECASH, IT'S REALLY EASY TO LOSE YOUR SATS BY LACKING OF KNOWLEDGE OF THE SYSTEM MECHANICS. PLEASE, FOR YOUR OWN GOOD, ALWAYS USE FEW SATS AMOUNT IN THE BEGINNING TO FULLY UNDERSTAND HOW WORKS THE SYSTEM. ECASH IS BASED ON A TRUST RELATIONSHIP BETWEEN YOU AND THE MINT OWNER, PLEASE DONT TRUST ECASH MINT YOU DONT KNOW. IT IS POSSIBLE TO GENERATE UNLIMITED ECASH TOKENS FROM A MINT, THE ONLY WAY TO VALIDATE THE REAL EXISTENCE OF THE ECASH TOKENS IS TO DO A MULTIMINT SWAP (BETWEEN MINTS). PLEASE, ALWAYS DO A MULTISWAP MINT IF YOU RECEIVE SOME ECASH FROM SOMEONE YOU DON'T KNOW/TRUST. NEVER TRUST A MINT YOU DONT KNOW!

IF YOU WANT TO RUN AN ECASH MINT WITH A BTC LIGHTNING NODE IN BACK-END, PLEASE DEDICATE THIS LN NODE TO YOUR ECASH MINT. A BAD MANAGEMENT OF YOUR LN NODE COULD LET PEOPLE TO LOOSE THEIR SATS BECAUSE THEY HAD ONCE TRUSTED YOUR MINT AND YOU DID NOT MANAGE THE THINGS RIGHT.

What's ecash/Cashu ?

---

I recently listened a passionnating interview from calle 👁️⚡👁 invited by the podcast channel What Bitcoin Did about the new (not so much now) Cashu protocol.

Cashu is a a free and open-source Chaumian ecash project built for Bitcoin protocol, recently created in order to let users send/receive Ecash over BTC Lightning network. The main Cashu ecash goal is to finally give you a "by-design" privacy mechanism to allow us to do anonymous Bitcoin transactions.

Ecash for your privacy.\ A Cashu mint does not know who you are, what your balance is, or who you're transacting with. Users of a mint can exchange ecash privately without anyone being able to know who the involved parties are. Bitcoin payments are executed without anyone able to censor specific users.

Here are some useful links to begin with Cashu ecash :

Github repo: https://github.com/cashubtc

Documentation: https://docs.cashu.space

To support the project: https://docs.cashu.space/contribute

A Proof of Liabilities Scheme for Ecash Mints: https://gist.github.com/callebtc/ed5228d1d8cbaade0104db5d1cf63939

Like NOSTR and its own NIPS, here is the list of the Cashu ecash NUTs (Notation, Usage, and Terminology): https://github.com/cashubtc/nuts?tab=readme-ov-file

I won't explain you at lot more on what's Casu ecash, you need to figured out by yourself. It's really important in order to avoid any mistakes you could do with your sats (that you'll probably regret).

If you don't have so much time, you can check their FAQ right here: https://docs.cashu.space/faq

I strongly advise you to listen Calle's interviews @whatbbitcoindid to "fully" understand the concept and the Cashu ecash mechanism before using it:

Scaling Bitcoin Privacy with Calle

In the meantime I'm writing this article, Calle did another really interesting interview with ODELL from CitadelDispatch:

CD120: BITCOIN POWERED CHAUMIAN ECASH WITH CALLE

Which ecash apps?

---

There are several ways to send/receive some Ecash tokens, you can do it by using mobile applications like eNuts, Minibits or by using Web applications like Cashu.me, Nustrache or even npub.cash. On these topics, BTC Session Youtube channel offers high quality contents and very easy to understand key knowledge on how to use these applications :

Minibits BTC Wallet: Near Perfect Privacy and Low Fees - FULL TUTORIAL

Cashu Tutorial - Chaumian Ecash On Bitcoin

Unlock Perfect Privacy with eNuts: Instant, Free Bitcoin Transactions Tutorial

Cashu ecash is a very large and complex topic for beginners. I'm still learning everyday how it works and the project moves really fast due to its commited developpers community. Don't forget to follow their updates on Nostr to know more about the project but also to have a better undertanding of the Cashu ecash technical and political implications.

There is also a Matrix chat available if you want to participate to the project:

https://matrix.to/#/#cashu:matrix.org

How to self-host your ecash mint with Nutshell

Cashu Nutshell is a Chaumian Ecash wallet and mint for Bitcoin Lightning. Cashu Nutshell is the reference implementation in Python.

Github repo:

https://github.com/cashubtc/nutshell

Today, Nutshell is the most advanced mint in town to self-host your ecash mint. The installation is relatively straightforward with Docker because a docker-compose file is available from the github repo.

Nutshell is not the only cashu ecash mint server available, you can check other server mint here :

https://docs.cashu.space/mints

The only "external" requirement is to have a funding source. One back-end funding source where ecash will mint your ecash from your Sats and initiate BTC Lightning Netwok transactions between ecash mints and BTC Ligtning nodes during a multimint swap. Current backend sources supported are: FakeWallet*, LndRestWallet, CoreLightningRestWallet, BlinkWallet, LNbitsWallet, StrikeUSDWallet.

*FakeWallet is able to generate unlimited ecash tokens. Please use it carefully, ecash tokens issued by the FakeWallet can be sent and accepted as legit ecash tokens to other people ecash wallets if they trust your mint. In the other way, if someone send you 2,3M ecash tokens, please don't trust the mint in the first place. You need to force a multimint swap with a BTC LN transaction. If that fails, someone has maybe tried to fool you.

I used a Voltage.cloud BTC LN node instance to back-end my Nutshell ecash mint:

https://voltage.cloud

SPOILER: my nutshell mint is working but I have an error message "insufficient balance" when I ask a multiswap mint from wallet.cashu.me or the eNuts application. In order to make it work, I need to add some Sats liquidity (I can't right now) to the node and open few channels with good balance capacity. If you don't have an ecash mint capable of doig multiswap mint, you'll only be able to mint ecash into your ecash mint and send ecash tokens to people trusting your mint. It's working, yes, but you need to be able to do some mutiminit swap if you/everyone want to fully profit of the ecash system.

Once you created your account and you got your node, you need to git clone the Nutshell github repo:

git clone https://github.com/cashubtc/nutshell.git

You next need to update the docker compose file with your own settings. You can comment the wallet container if you don't need it.

To generate a private key for your node, you can use this openssl command

openssl rand -hex 32 054de2a00a1d8e3038b30e96d26979761315cf48395aa45d866aeef358c91dd1

The CLI Cashu wallet is not needed right now but I'll show you how to use it in the end of this article. Feel free to comment it or not.

``` version: "3" services: mint: build: context: . dockerfile: Dockerfile container_name: mint

ports:

- "3338:3338"

environment:

- DEBUG=TRUE

- LOG_LEVEL=DEBUG

  - MINT_URL=https://YourMintURL
  - MINT_HOST=YourMintDomain.tld
  - MINT_LISTEN_HOST=0.0.0.0
  - MINT_LISTEN_PORT=3338
  - MINT_PRIVATE_KEY=YourPrivateKeyFromOpenSSL
  - MINT_INFO_NAME=YourMintInfoName
  - MINT_INFO_DESCRIPTION=YourShortInfoDesc
  - MINT_INFO_DESCRIPTION_LONG=YourLongInfoDesc
  - MINT_LIGHTNING_BACKEND=LndRestWallet
  #- MINT_LIGHTNING_BACKEND=FakeWallet
  - MINT_INFO_CONTACT=[["email","YourConctact@email"], ["twitter","@YourTwitter"], ["nostr",  "YourNPUB"]]
  - MINT_INFO_MOTD=Thanks for using my mint!
  - MINT_LND_REST_ENDPOINT=https://YourVoltageNodeDomain:8080
  - MINT_LND_REST_MACAROON=YourDefaultAdminMacaroonBase64
  - MINT_MAX_PEG_IN=100000
  - MINT_MAX_PEG_OUT=100000
  - MINT_PEG_OUT_ONLY=FALSE
command: ["poetry", "run", "mint"]

wallet-voltage: build: context: . dockerfile: Dockerfile container_name: wallet-voltage

ports:

- "4448:4448"

depends_on:
  - nutshell-voltage
environment:

- DEBUG=TRUE

- MINT_URL=http://nutshell-voltage:3338

  - API_HOST=0.0.0.0
command: ["poetry", "run", "cashu", "-d"]

```

To build, run and see the container logs:

docker compose up -d && docker logs -f mint

0.15.1 2024-03-22 14:45:45.490 | WARNING | cashu.lightning.lndrest:__init__:49 - no certificate for lndrest provided, this only works if you have a publicly issued certificate 2024-03-22 14:45:45.557 | INFO | cashu.core.db:__init__:135 - Creating database directory: data/mint 2024-03-22 14:45:45.68 | INFO | Started server process [1] 2024-03-22 14:45:45.69 | INFO | Waiting for application startup. 2024-03-22 14:45:46.12 | INFO | Loaded 0 keysets from database. 2024-03-22 14:45:46.37 | INFO | Current keyset: 003dba9e589023f1 2024-03-22 14:45:46.37 | INFO | Using LndRestWallet backend for method: 'bolt11' and unit: 'sat' 2024-03-22 14:45:46.97 | INFO | Backend balance: 1825000 sat 2024-03-22 14:45:46.97 | INFO | Data dir: /root/.cashu 2024-03-22 14:45:46.97 | INFO | Mint started. 2024-03-22 14:45:46.97 | INFO | Application startup complete. 2024-03-22 14:45:46.98 | INFO | Uvicorn running on http://0.0.0.0:3338 (Press CTRL+C to quit) 2024-03-22 14:45:47.27 | INFO | 172.19.0.22:48528 - "GET /v1/keys HTTP/1.1" 200 2024-03-22 14:45:47.34 | INFO | 172.19.0.22:48544 - "GET /v1/keysets HTTP/1.1" 200 2024-03-22 14:45:47.38 | INFO | 172.19.0.22:48552 - "GET /v1/info HTTP/1.1" 200

If you see the line :

Uvicorn running on http://0.0.0.0:3338 (Press CTRL+C to quit)

Nutshell is well started.

I won't explain here how to create a reverse proxy to Nutshell, you can find how to do it into my previous article. Here is the reverse proxy config into Nginx Proxy Manager:

If everything is well configured and if you go on your mint url (https://yourminturl) you shoud see this:

It's not helping a lot because at first glance it seems to be not working but it is. You can also check these URL path to confirm :

• https://yourminturl/keys and https://yourminturl/keysets

or

• https://yourminturl/v1/keys and https://yourminturl/v1/keysets

Depending of the moment when you read this article, the first URLs path might have been migrated to V1. Here is why:

https://github.com/cashubtc/nuts/pull/55

The final test is to add your mint to your prefered ecash wallets.

SPOILER: AT THIS POINT, YOU SHOUD KNOW THAT IF YOU RESET YOUR LOCAL BROWSER INTERNET CACHE FILE, YOU'LL LOSE YOUR MINTED ECASH TOKENS. IF NOT, PLEASE READ THE DOCUMENTATION AGAIN.

For instace, if we use wallet.cashu.me:

You can go into the "Settings" tab and add your mint :

If everything went find, you shoud see this :

You can now mint some ecash from your mint creating a sats invoice :

You can now scan the QR diplayed with your prefered BTC LN wallet. If everything is OK, you should receive the funds:

It may happen that some error popup sometimes. If you are curious and you want to know what happened, Cashu wallet has a debug console you can activate by clicking on the "Settings" page and "OPEN DEBUG TERMINAL". A little gear icon will be displayed in the bottom of the screen. You can click on it, go to settings and enable "Auto Display If Error Occurs" and "Display Extra Information". After enabling this setting, you can close the popup windows and let the gear icon enabled. If any error comes, this windows will open again and show you thé error:

Now that you have some sats in your balance, you can try to send some ecash. Open in a new windows another ecash wallet like Nutstach for instance.

Add your mint again :

Return on Cashu wallet. The ecash token amount you see on the Cashu wallet home page is a total of all the ecash tokens you have on all mint connected.

Next, click on "Send ecach". Insert the amout of ecash you want to transfer to your other wallet. You can select the wallet where you want to extract the funds by click on the little arrow near the sats funds you currenly selected :

Click now on "SEND TOKENS". That will open you a popup with a QR code and a code CONTAINING YOUR ECASH TOKENS (really).

You can now return on nutstach, click on the "Receive" button and paste the code you get from Cashu wallet:

Click on "RECEIVE" again:

Congrats, you transfered your first ecash tokens to yourself ! 🥜⚡

You may need some time to transfer your ecash tokens between your wallets and your mint, there is a functionality existing for that called "Multimint swaps".

Before that, if you need new mints, you can check the very new website Bitcoinmints.com that let you see the existing ecash mints and rating :

https://bitcoinmints.com

Don't forget, choose your mint carefuly because you don't know who's behind.

Let's take a mint and add it to our Cashu wallet:

If you want to transfer let's say 20 sats from minibits mint to bitcointxoko mint, go just bottom into the "Multimint swap" section. Select the mint into "Swap from mint", the mint into "Swap to mint" and click on "SWAP" :

A popup window will appear and will request the ecash tokens from the source mint. It will automatically request the ecash amount via a Lightning node transaction and add the fund to your other wallet in the target mint. As it's a Lightning Network transaction, you can expect some little fees.

If everything is OK with the mints, the swap will be successful and the ecash received.

You can now see that the previous sats has been transfered (minus 2 fee sats).

Well done, you did your first multimint swap ! 🥜⚡

One last thing interresting is you can also use CLI ecash wallet. If you created the wallet contained in the docker compose, the container should be running.

Here are some commands you can do.

To verify which mint is currently connected :

``` docker exec -it wallet-voltage poetry run cashu info

2024-03-22 21:57:24.91 | DEBUG | cashu.wallet.wallet:init:738 | Wallet initialized 2024-03-22 21:57:24.91 | DEBUG | cashu.wallet.wallet:init:739 | Mint URL: https://nutshell-voltage.fractalized.net 2024-03-22 21:57:24.91 | DEBUG | cashu.wallet.wallet:init:740 | Database: /root/.cashu/wallet 2024-03-22 21:57:24.91 | DEBUG | cashu.wallet.wallet:init:741 | Unit: sat 2024-03-22 21:57:24.92 | DEBUG | cashu.wallet.wallet:init:738 | Wallet initialized 2024-03-22 21:57:24.92 | DEBUG | cashu.wallet.wallet:init:739 | Mint URL: https://nutshell-voltage.fractalized.net 2024-03-22 21:57:24.92 | DEBUG | cashu.wallet.wallet:init:740 | Database: /root/.cashu/wallet 2024-03-22 21:57:24.92 | DEBUG | cashu.wallet.wallet:init:741 | Unit: sat Version: 0.15.1 Wallet: wallet Debug: True Cashu dir: /root/.cashu Mints: - https://nutshell-voltage.fractalized.net ```

To verify your balance :

``` docker exec -it wallet-voltage poetry run cashu balance

2024-03-22 21:59:26.67 | DEBUG | cashu.wallet.wallet:init:738 | Wallet initialized 2024-03-22 21:59:26.67 | DEBUG | cashu.wallet.wallet:init:739 | Mint URL: https://nutshell-voltage.fractalized.net 2024-03-22 21:59:26.67 | DEBUG | cashu.wallet.wallet:init:740 | Database: /root/.cashu/wallet 2024-03-22 21:59:26.67 | DEBUG | cashu.wallet.wallet:init:741 | Unit: sat 2024-03-22 21:59:26.68 | DEBUG | cashu.wallet.wallet:init:738 | Wallet initialized 2024-03-22 21:59:26.68 | DEBUG | cashu.wallet.wallet:init:739 | Mint URL: https://nutshell-voltage.fractalized.net 2024-03-22 21:59:26.68 | DEBUG | cashu.wallet.wallet:init:740 | Database: /root/.cashu/wallet 2024-03-22 21:59:26.68 | DEBUG | cashu.wallet.wallet:init:741 | Unit: sat Balance: 0 sat ```

To create an sats invoice to have ecash :

``` docker exec -it wallet-voltage poetry run cashu invoice 20

2024-03-22 22:00:59.12 | DEBUG | cashu.wallet.wallet:_load_mint_info:275 | Mint info: name='nutshell.fractalized.net' pubkey='02008469922e985cbc5368ce16adb6ed1aaea0f9ecb21639db4ded2e2ae014a326' version='Nutshell/0.15.1' description='Official Fractalized Mint' description_long='TRUST THE MINT' contact=[['email', 'pastagringo@fractalized.net'], ['twitter', '@pastagringo'], ['nostr', 'npub1ky4kxtyg0uxgw8g5p5mmedh8c8s6sqny6zmaaqj44gv4rk0plaus3m4fd2']] motd='Thanks for using official ecash fractalized mint!' nuts={4: {'methods': [['bolt11', 'sat']], 'disabled': False}, 5: {'methods': [['bolt11', 'sat']], 'disabled': False}, 7: {'supported': True}, 8: {'supported': True}, 9: {'supported': True}, 10: {'supported': True}, 11: {'supported': True}, 12: {'supported': True}} Balance: 0 sat

Pay invoice to mint 20 sat:

Invoice: lnbc200n1pjlmlumpp5qh68cqlr2afukv9z2zpna3cwa3a0nvla7yuakq7jjqyu7g6y69uqdqqcqzzsxqyz5vqsp5zymmllsqwd40xhmpu76v4r9qq3wcdth93xthrrvt4z5ct3cf69vs9qyyssqcqppurrt5uqap4nggu5tvmrlmqs5guzpy7jgzz8szckx9tug4kr58t4avv4a6437g7542084c6vkvul0ln4uus7yj87rr79qztqldggq0cdfpy

You can use this command to check the invoice: cashu invoice 20 --id 2uVWELhnpFcNeFZj6fWzHjZuIipqyj5R8kM7ZJ9_

Checking invoice .................2024-03-22 22:03:25.27 | DEBUG | cashu.wallet.wallet:verify_proofs_dleq:1103 | Verified incoming DLEQ proofs. Invoice paid.

Balance: 20 sat ```

To pay an invoice by pasting the invoice you received by your or other people :

``` docker exec -it wallet-voltage poetry run cashu pay lnbc150n1pjluqzhpp5rjezkdtt8rjth4vqsvm50xwxtelxjvkq90lf9tu2thsv2kcqe6vqdq2f38xy6t5wvcqzzsxqrpcgsp58q9sqkpu0c6s8hq5pey8ls863xmjykkumxnd8hff3q4fvxzyh0ys9qyyssq26ytxay6up54useezjgqm3cxxljvqw5vq2e94ru7ytqc0al74hr4nt5cwpuysgyq8u25xx5la43mx4ralf3mq2425xmvhjzvwzqp54gp0e3t8e

2024-03-22 22:04:37.23 | DEBUG | cashu.wallet.wallet:_load_mint_info:275 | Mint info: name='nutshell.fractalized.net' pubkey='02008469922e985cbc5368ce16adb6ed1aaea0f9ecb21639db4ded2e2ae014a326' version='Nutshell/0.15.1' description='Official Fractalized Mint' description_long='TRUST THE MINT' contact=[['email', 'pastagringo@fractalized.net'], ['twitter', '@pastagringo'], ['nostr', 'npub1ky4kxtyg0uxgw8g5p5mmedh8c8s6sqny6zmaaqj44gv4rk0plaus3m4fd2']] motd='Thanks for using official ecash fractalized mint!' nuts={4: {'methods': [['bolt11', 'sat']], 'disabled': False}, 5: {'methods': [['bolt11', 'sat']], 'disabled': False}, 7: {'supported': True}, 8: {'supported': True}, 9: {'supported': True}, 10: {'supported': True}, 11: {'supported': True}, 12: {'supported': True}} Balance: 20 sat 2024-03-22 22:04:37.45 | DEBUG | cashu.wallet.wallet:get_pay_amount_with_fees:1529 | Mint wants 0 sat as fee reserve. 2024-03-22 22:04:37.45 | DEBUG | cashu.wallet.cli.cli:pay:189 | Quote: quote='YpNkb5f6WVT_5ivfQN1OnPDwdHwa_VhfbeKKbBAB' amount=15 fee_reserve=0 paid=False expiry=1711146847 Pay 15 sat? [Y/n]: y Paying Lightning invoice ...2024-03-22 22:04:41.13 | DEBUG | cashu.wallet.wallet:split:613 | Calling split. POST /v1/swap 2024-03-22 22:04:41.21 | DEBUG | cashu.wallet.wallet:verify_proofs_dleq:1103 | Verified incoming DLEQ proofs. Error paying invoice: Mint Error: Lightning payment unsuccessful. insufficient_balance (Code: 20000) ```

It didn't work, yes. That's the thing I told you earlier but it would work with a well configured and balanced Lightning Node.

That's all ! You should now be able to use ecash as you want! 🥜⚡

See you on NOSTR! 🤖⚡\ PastaGringo

@ ecda4328:1278f072

Introduction: Crypto.com Exchange for European Traders

Reside in Europe, including non-EUR countries? Frustrated with the exorbitant spreads on the Crypto.com App (up to 5%) and high credit card fees (up to 3%) when you're eager to buy or sell cryptocurrency? This guide is tailored for you!

Quick Transfer with SEPA Instant

Did you know that you can transfer EUR to your Crypto.com Exchange account within minutes, and sometimes even seconds, including weekends and bank holidays? Yes, you absolutely can, thanks to SEPA Instant Credit Transfer (SCT Inst).

Supported Banks

To avail of fast EUR to Crypto.com Exchange transfers, ensure that your bank supports the SEPA Instant Credit Transfer (SCT Inst) scheme. If your bank, or FinTech apps like Wise, is on this list, you're good to go.

My Recommendation: I vouch for Wise due to its flawless functionality and favorable exchange rates. If your bank doesn't support SCT Inst and you're unwilling to wait, you can swiftly load your account with any currency using a bank card for a rather small fee (~1.2%). My Wise Referral Code: andreya54

24/7 Transfer Availability

SCT Inst is incredibly flexible:

• 24/7/365 availability, including weekends and bank holidays
• Immediate receipt and availability of funds
• €100,000 transaction limit (unless previously agreed otherwise between PSPs)

For more details, you can read this document by the European Central Bank.

TL;DR

To Buy crypto: - EUR => BTC/EUR => ANY/BTC => ANY
- Use Limit order at the Lowest offer (aka "ask") (red order book)

To Sell crypto: - ANY => ANY/BTC => BTC/EUR => EUR
- Use Limit order at the Highest bid (green order book)

How to Buy Cryptocurrency with EUR

Here's how to save up to 8% on spreads and fees when buying/selling crypto compared to the Crypto.com App.

1. Log in to Crypto.com Exchange: Go to the Dashboard or Wallet in the top right, and navigate to Bank Transfer on the left sidebar.  

2. Deposit via SEPA: Choose EUR -> SEPA -> Deposit and use the displayed IBAN for transferring EUR to your Crypto.com Exchange account.

Trading Interface Tips

Intimidated by the professional trading interface? Don't be. Here's how to read the order book:

• Offers (Red): These are the prices at which people are willing to sell the asset. The lowest offer is often called the "Ask."
• Bids (Green): These are the prices at which people are willing to buy the asset. The highest bid is often called the "Bid."

Trading occurs when a buyer's bid meets a seller's offer. In market terms, this is often at the point where the highest bid and the lowest offer intersect. This intersection is frequently referred to as the "market price" for that particular asset at that specific time.

On trading pairs

Crypto.com Exchange offers only two EUR trading pairs: BTC/EUR and ETH/EUR. This is logical given that these assets have the highest liquidity in terms of market capitalization. While we hope for the addition of more pairs, the existing options still serve as useful proxies for purchasing other cryptocurrencies.

"highest liquidity" means that an asset like a cryptocurrency or stock can be easily bought or sold without causing a significant impact on its price. For a trader, this is good because it means they can quickly enter or exit positions without worrying about huge price changes.

Steps to Buy BTC with EUR

1. Navigate to the BTC/EUR Spot trading pair.
2. Choose "Buy" on the right-hand menu.
3. Stay on the "Limit" tab.
4. Specify your order value (how much EUR you want to spend to buy BTC)
5. Select the lowest offered (aka "ask") price (bottom of the red order book).
6. Click "Buy BTC" to confirm.

Diversifying: How to Buy ATOM Token?

First, buy BTC as previously explained. Then:

1. Navigate to the ATOM/BTC Spot trading pair.
2. Choose "Buy" on the right-hand menu.
3. Stay on the "Limit" tab.
4. Specify your order value (how much BTC you want to spend to buy ATOM)
5. Select the lowest offered (aka "ask") price (bottom of the red order book).
6. Click "Buy ATOM" to confirm.

Selling Your Assets

The process is the same but in reverse. Sell at the highest bid (top of the green order book).

Selling ATOM for BTC

1. Navigate to the ATOM/BTC Spot trading pair.
2. Choose "Sell" on the right-hand menu.
3. Stay on the "Limit" tab.
4. Specify your quantity value (how much ATOM you want to sell to buy BTC)
5. Select the highest bid (top of the green order book).
6. Click "Sell ATOM" to confirm.

Selling BTC for EUR

1. Navigate to the BTC/EUR Spot trading pair.
2. Choose "Sell" on the right-hand menu.
3. Stay on the "Limit" tab.
4. Specify your quantity value (how much BTC you want to sell to buy EUR)
5. Select the highest bid (top of the green order book).
6. Click "Sell BTC" to confirm.

You can then withdraw EUR back to your bank directly from the Crypto.Com Exchange.

Additionally

After you click "Buy" or "Sell," you will see your order in the "Open Orders" tab in the bottom menu. Once your order is 100% filled, it will disappear, and you will be able to see it in the "Trade History" tab.

Sometimes you might miss the opportunity as the price moves, and someone else's order could get filled faster than yours. Don't worry; you can either wait a little longer in hopes that someone will make an offer at this price or simply cancel your order and submit it again at the next lowest price if you are in a hurry.

Maker/Taker Fees Explained

When you open Buy/Sell orders on the Crypto.com exchange, you may incur small Maker/Taker fees of less than 0.0728%, or even no fees at all, depending on the amount of CRO you have staked on the platform.

• Maker Fee: When you place an order that adds liquidity to the market, you are a "Maker". This usually happens when you set a "limit" order that does not execute immediately and sits on the order book waiting for someone to match against it. Since you are "making" liquidity available for others, you pay a Maker fee.
• Taker Fee: When you place an order that removes liquidity from the market, you are a "Taker". This generally occurs when you place a "market" order that executes immediately against a pre-existing order on the order book. Because you are "taking" liquidity away, you pay a Taker fee.

Typically, Taker fees are higher than Maker fees as an incentive for traders to add liquidity to the market.

Read more on Maker/Taker fees on the Crypto.Com Exchange platform.

Conclusion

Thanks for reading this guide! It's lengthy, but every detail is crucial for optimal trading on Crypto.com Exchange.

Referral Code

If you haven't opened a Crypto.com Exchange account yet, use my referral code: pv0r199m6j
Referral Link: Sign Up Here

@ ecda4328:1278f072

Introduction

In the world of blockchain technology, a nonce plays a pivotal role in ensuring transaction security and uniqueness. This article demystifies the nonce's role in major blockchain platforms - Bitcoin, Ethereum, and Cosmos/CometBFT, highlighting its importance and distinct functionalities in each.

The Role of Nonce in ECDSA and Its Importance

In Bitcoin (and most of blockchains) transactions, the nonce is a randomly generated number integral to the Elliptic Curve Digital Signature Algorithm (ECDSA). It guarantees each digital signature's uniqueness and security. The randomness and secrecy of the nonce are vital. If predictable or exposed, it can compromise the entire security of a transaction.

The Risk of Nonce Exposure and Private Key Recovery

If a nonce is compromised, it poses a risk of private key recovery. To understand this, one must consider the signature components (r, s), the public key (which becomes known once you sign & broadcast at least one transaction in Bitcoin). A predictable or reused nonce can leak critical information, enabling savvy attackers to backtrack to the private key.

This specific type of attack is called a nonce covert channel attack. And methods protecting against this are called anti-klepto or anti-exfil (interchangebly).

Worth noting that anti-klepto/anti-exfil are broader terms for methods that protect against various forms of secret data exfiltration, including but not limited to attacks involving nonce misuse.

Bitcoin's UTXO Model and Nonce Functionality

Bitcoin utilizes the Unspent Transaction Outputs (UTXO) model, ensuring that each Bitcoin is spent only once. This model is distinct from nonce management in ECDSA and adds an additional layer of security against double-spending in the Bitcoin network.

Address rotation in Bitcoin, as implemented through BIP32 (Hierarchical Deterministic Wallets), enhances privacy and isolates financial risk by generating a unique address and corresponding private key for each address created, not necessarily for each individual transaction. While this strategy effectively segregates risk to individual addresses, it does not directly prevent the vulnerability of private key derivation from nonce exposure in the ECDSA signature process, as this risk is inherent to the signature mechanism itself and is independent of the address or its associated private key.

Ethereum's Account-Based Model and Nonce Usage

Ethereum, unlike Bitcoin, operates on an account-based model. Each account has a sequential transaction nonce, starting from 0, which is public. This nonce, different from the ECDSA nonce, helps in transaction ordering and network integrity.

Nonces in Cosmos/CometBFT Blockchains

Cosmos/CometBFT blockchains, akin to Ethereum, adopt an account-based model. They use nonces, similar to Ethereum's transaction nonce, for transaction ordering and preventing replay attacks. These nonces are distinct from the ECDSA nonce used in the digital signature process.

Conclusion

The use of "nonce" in Ethereum for transaction sequence (akin to account sequence in Cosmos/CometBFT blockchains), leading to confusion with ECDSA nonce, is simply a coincidental choice of terminology.

In summary, while Bitcoin, Ethereum, Cosmos/CometBFT and many other blockchains employ nonces in ECDSA signing, their transaction management and double-spending prevention methods differ significantly. Understanding these nuances is crucial for blockchain users and developers to appreciate the underlying security mechanisms of these diverse platforms.

References

• Hardware wallets can steal your seed!
• A Glimpse of the Deep: Finding a Creature in Ethereum's Dark Forest
• MuSig-DN: Schnorr Multisignatures with Verifiably Deterministic Nonces
• Android's SecureRandom - not even nonce
• Anti-klepto explained: how the BitBox02 protects you against leaking private keys
• Anti-Exfil: Stopping Key Exfiltration

---

Buy Tangem Wallet with discount!

@ 3bf0c63f:aefa459d

Token-Curated Registries

So you want to build a TCR?

TCRs (Token Curated Registries) are a construct for maintaining registries on Ethereum. Imagine you have lots of scissor brands and you want a list with only the good scissors. You want to make sure only the good scissors make into that list and not the bad scissors. For that, people will tell you, you can just create a TCR of the best scissors!

It works like this: some people have the token, let's call it Scissor Token. Some other person, let's say it's a scissor manufacturer, wants to put his scissor on the list, this guy must acquire some Scissor Tokens and "stake" it. Holders of the Scissor Tokens are allowed to vote on "yes" or "no". If "no", the manufactures loses his tokens to the holders, if "yes" then its tokens are kept in deposit, but his scissor brand gets accepted into the registry.

Such a simple process, they say, have strong incentives for being the best possible way of curating a registry of scissors: consumers have the incentive to consult the list because of its high quality; manufacturers have the incentive to buy tokens and apply to join the list because the list is so well-curated and consumers always consult it; token holders want the registry to accept good and reject bad scissors because that good decisions will make the list good for consumers and thus their tokens more valuable, bad decisions will do the contrary. It doesn't make sense, to reject everybody just to grab their tokens, because that would create an incentive against people trying to enter the list.

Amazing! How come such a simple system of voting has such enourmous features? Now we can have lists of everything so well-curated, and for that we just need Ethereum tokens!

Now let's imagine a different proposal, of my own creation: SPCR, Single-person curated registries.

Single-person Curated Registries are equal to TCR, except they don't use Ethereum tokens, it's just a list in a text file kept by a single person. People can apply to join, and they will have to give the single person some amount of money, the single person can reject or accept the proposal and so on.

Now let's look at the incentives of SPCR: people will want to consult the registry because it is so well curated; vendors will want to enter the registry because people are consulting it; the single person will want to accept the good and reject the bad applicants because these good decisions are what will make the list valuable.

Amazing! How such a single proposal has such enourmous features! SPCR are going to take over the internet!

What TCR enthusiasts get wrong?

TCR people think they can just list a set of incentives for something to work and assume that something will work. Mix that with Ethereum hype and they think theyve found something unique and revolutionary, while in fact they're just making a poor implementation of "democracy" systems that fail almost everywhere.

The life is not about listing a set of "incentives" and then considering the problems solved. Almost everybody on the Earth has the incentive for being rich: being rich has a lot of advantages over being poor, however not all people get rich! Why are the incentives failing?

Curating lists is a hard problem, it involves a lot of knowledge about the problem that just holding a token won't give you, it involves personal preferences, politics, it involves knowing where is the real limit between "good" and "bad". The Single Person list may have a good result if the single person doing the curation is knowledgeable and honest (yes, you can game the system to accept your uncle's scissors and not their competitor that is much better, for example, without losing the entire list reputation), same thing for TCRs, but it can also fail miserably, and it can appear to be good but be in fact not so good. In all cases, the list entries will reflect the preferences of people choosing and other things that aren't taken into the incentives equation of TCR enthusiasts.

We don't need lists

The most important point to be made, although unrelated to the incentive story, is that we don't need lists. Imagine you're looking for a scissor. You don't want someone to tell if scissor A or B are "good" or "bad", or if A is "better" than B. You want to know if, for your specific situation, or for a class of situations, A will serve well, and do that considering A's price and if A is being sold near you and all that.

Scissors are the worst example ever to make this point, but I hope you get it. If you don't, try imagining the same example with schools, doctors, plumbers, food, whatever.

Recommendation systems are badly needed in our world, and TCRs don't solve these at all.

@ ecda4328:1278f072

Intro

I've left Twitter (X), WhatsApp, Telegram, Instagram, Facebook and Google. The driving force behind this decision was the escalating overzealous censorship. I cannot condone platforms that actively indulge in this practice. In all honesty, I've always felt uneasy using "free" platforms riddled with ads where the user is the product and doesn't own the content they produce.

Let's be real: hardly anyone thoroughly reads the Terms of Service (ToS).

Censorship and Shadow Banning

The final straw was when I resorted to a text editor for drafting messages/comments, hoping to rephrase them so they wouldn't get deleted moments after posting. This isn't exclusive to just one platform; I've encountered it on YouTube and LinkedIn too. Twitter (or X, as I now refer to it) has a history of shadow banning users' posts. It's been beyond frustrating to get banned from Telegram groups simply for posing legitimate questions.

You can test LinkedIn's censorship mechanism too, simply add "Binance" word (without quotes) to any of your comment and your post will disappear. At least that is what I've seen couple of months ago. Similarly, comments on YouTube often disappear precisely 60 seconds after posting if they contain specific keywords. I know they call it filtering, but it does not make any sense. In my opinion, legitimate companies and links shouldn't trigger these filters.

Community and Connections

Recently, I attended the Cosmoverse 2023 conference in Istanbul. Most attendees exchanged their Telegram or Twitter (X) contact information. Since I didn't have either, I gladly shared my Nostr and SimpleX Chat details. Many privacy advocates were quick to connect on SimpleX with me, though several didn't.

I learned about SimpleX Chat from Jack Dorsey, who mentioned it during a conversation in July:

While Signal has its shortcomings, I still keep it as a backup communication tool.

One More Last Straw

During the conference, I temporarily reinstalled Telegram to communicate with my group. Convincing nine individuals to switch to SimpleX on the spot seemed impractical.

At the conference, I bought a Keystone hardware wallet. Shortly after, I connected with the seller, Xin Z, on Telegram. However, I was banned from the official Keystone Telegram group right after posing a question.

Upon inquiring, Xin Z clarified that Telegram's official team had banned me, not the group's admin. 🤯

Business and Community: Collateral Damage

Censorship doesn't just silence voices; it hinders potential growth and stifles innovation. When platforms arbitrarily or aggressively censor content, they inadvertently create barriers between businesses and their potential clients. New users or clients, when encountering such heavy-handed moderation, may feel discouraged or unwelcome, causing them to retreat from the platform altogether.

Moreover, for businesses, this form of censorship can be devastating. Word-of-mouth, discussions, and organic community engagements are invaluable. When these channels are hampered, businesses lose out on potential clientele, and communities lose the chance to thrive and evolve naturally.

Censorship, in its overzealous form, breaks the very essence of digital communities: open dialogue. As platforms become more censorious, they risk creating sterile environments devoid of genuine interaction and rich discourse. Such an atmosphere is not conducive for businesses to foster relations, nor for communities to flourish. The ultimate price of overcensorship isn't just the loss of a few voices—it's the fragmentation of digital society as we know it.

Freedom to Choose

I strongly advocate for the adoption of Free and Open Source Software (aka FOSS) products. In these platforms, you aren't treated as the product. However, supporting them through donations/contributions is always an option. Platforms like Nostr and SimpleX Chat are excellent starting points.

My Nostr account: npub1andyx2xqhwffeg595snk9a8ll43j6dvw5jzpljm5yjm3qync7peqzl8jd4

Disclaimer

This article reflects my personal experiences and opinions. It is not intended to criticize or demean the Keystone hardware wallet product or its quality. Furthermore, the actions taken by Telegram are not a direct representation of the views or policies of the Keystone Telegram group admins. Any reference to specific events or entities is made in the context of broader concerns about platform censorship.

@ 0ecfdaf2:d23eee11

📍 Destination: Mexico 🇲🇽

🗓 Year: 2024

🎒 Type of Trip: Couple Road Trip

🤿 Diving Spots: Cancun / Isla Mujeres / Playa Del Carmen

⚓ Maximum Depth of Stay: 16m

---

📸 Photo: Aerial View

This article will be in 2 parts:

• 1st part about dives in Cancun & Isla Mujeres

• 2nd part about dives in Cenotes in Playa del Carmen

I dived with the "Scuba Cancun" club, the first historic club to open in Cancun.

The boat to access the dive sites is called "Scuba III"; I wonder what happened to the other "Scuba I & II" 😐

📸 Photo: Club & Boat

To access the dive sites, we take a 30-minute boat ride 🛥

Upon arrival, we gear up 🤿, and off we go, diving into the water...

📸 Photo: Boat Ride

As soon as we reach the bottom, we are immediately greeted by schools of fish, they're everywhere 😍

📹 Video: School of Fish

Some fish were curious enough to approach and see who was visiting, like this porcupinefish 👀

📹 Video: Porcupinefish

For others, it was mealtime, like this pufferfish who was dining 🍽

📸 Photo: Pufferfish pufferfish

In every dive, we remember about 10 things, but there are especially 1/2 main elements, which I call "the pièce de résistance" 😁

This time it was a beautiful Eagle Ray 🦈 that we saw twice, out in the open sea, and at the end during the safety stop.

📹 Video: Eagle Ray

In addition to the fish, the corals were magnificent. And upon closer inspection, we can see nudibranchs, like this Doris climbing on this elk horn coral 🪸

📸 Photo: Gorgonian and Doris on Elk Horn Coral

Some were ready to play and posed for the camera, like these surgeonfish 🐠 and damselfish.

While others tried a trick by leaving and changing color, like this cowfish

📸 Photo: Surgeonfish / Damselfish / Cowfish

Grouper and Turtle 🐢 were present 🔥

📹 Video: Grouper & Turtle

We end with a touch of beauty with this seashell 🐚 that could make a magnificent wallpaper 😉

That's all for the morning dive. We'll go back in the afternoon to visit the "Musa" underwater museum 👀

📸 Photo: Seashell

To start the Musa museum, we're greeted by this bartender & his dog 🍹🐕

📸 Photo: Bartender & Dog Statue

His car 🚗 was parked nearby.

📸 Photo: Car Statue

Then, the museum begins, and it's crowded, there's a crowd of people 😲

📸 Photo: People Statues

In all this crowd, I kept looking 👀 for my lost private keys 🗝️ at the bottom of the ocean 🌊

📸 Photo: Scuba

I wasn't the only one searching; others even plunged their heads deeper to search.

📸 Photo: Group Statue

That's all for the bubbles in Cancun/Isla Mujeres 👋

It's time to resurface for the next part of the thread, diving in the Cenotes in Playa del Carmen 👀

Stay Tuned ✌

📸 Photo: Bubbles & Fins

@ 3bf0c63f:aefa459d

A estrutura lógica do livro didático

Todos os livros didáticos e cursos expõem seus conteúdos a partir de uma organização lógica prévia, um esquema de todo o conteúdo que julgam relevante, tudo muito organizadinho em tópicos e subtópicos segundo a ordem lógica que mais se aproxima da ordem natural das coisas. Imagine um sumário de um manual ou livro didático.

A minha experiência é a de que esse método serve muito bem para ninguém entender nada. A organização lógica perfeita de um campo de conhecimento é o resultado final de um estudo, não o seu início. As pessoas que escrevem esses manuais e dão esses cursos, mesmo quando sabem do que estão falando (um acontecimento aparentemente raro), o fazem a partir do seu próprio ponto de vista, atingido após uma vida de dedicação ao assunto (ou então copiando outros manuais e livros didáticos, o que eu chutaria que é o método mais comum).

Para o neófito, a melhor maneira de entender algo é através de imersões em micro-tópicos, sem muita noção da posição daquele tópico na hierarquia geral da ciência.

• Revista Educativa, um exemplo de como não ensinar nada às crianças.
• Zettelkasten, a ordem surgindo do caos, ao invés de temas se encaixando numa ordem preexistentes.

@ e6ce6154:275e3444

Este artigo foi censurado pelo estado e fomos obrigados a deletá-lo após ameaça de homens armados virem nos visitar e agredir nossa vida e propriedade.

Isto é mais uma prova que os autoproclamados antirracistas são piores que os racistas.

https://rothbardbrasil.com/pelo-direito-de-ser-racista-fascista-machista-e-homofobico

Segue artigo na íntegra. 👇

Sem dúvida, a escalada autoritária do totalitarismo cultural progressista nos últimos anos tem sido sumariamente deletéria e prejudicial para a liberdade de expressão. Como seria de se esperar, a cada dia que passa o autoritarismo progressista continua a se expandir de maneira irrefreável, prejudicando a liberdade dos indivíduos de formas cada vez mais deploráveis e contundentes.

Com a ascensão da tirania politicamente correta e sua invasão a todos os terrenos culturais, o autoritarismo progressista foi se alastrando e consolidando sua hegemonia em determinados segmentos. Com a eventual eclosão e a expansão da opressiva e despótica cultura do cancelamento — uma progênie inevitável do totalitarismo progressista —, todas as pessoas que manifestam opiniões, crenças ou posicionamentos que não estão alinhados com as pautas universitárias da moda tornam-se um alvo.

Há algumas semanas, vimos a enorme repercussão causada pelo caso envolvendo o jogador profissional de vôlei Maurício Sousa, que foi cancelado pelo simples fato de ter emitido sua opinião pessoal sobre um personagem de história em quadrinhos, Jon Kent, o novo Superman, que é bissexual. Maurício Sousa reprovou a conduta sexual do personagem, o que é um direito pessoal inalienável que ele tem. Ele não é obrigado a gostar ou aprovar a bissexualidade. Como qualquer pessoa, ele tem o direito pleno de criticar tudo aquilo que ele não gosta. No entanto, pelo simples fato de emitir a sua opinião pessoal, Maurício Sousa foi acusado de homofobia e teve seu contrato rescindido, sendo desligado do Minas Tênis Clube.

Lamentavelmente, Maurício Sousa não foi o primeiro e nem será o último indivíduo a sofrer com a opressiva e autoritária cultura do cancelamento. Como uma tirania cultural que está em plena ascensão e usufrui de um amplo apoio do establishment, essa nova forma de totalitarismo cultural colorido e festivo está se impondo de formas e maneiras bastante contundentes em praticamente todas as esferas da sociedade contemporânea. Sua intenção é relegar ao ostracismo todos aqueles que não se curvam ao totalitarismo progressista, criminalizando opiniões e crenças que divergem do culto à libertinagem hedonista pós-moderna. Oculto por trás de todo esse ativismo autoritário, o que temos de fato é uma profunda hostilidade por padrões morais tradicionalistas, cristãos e conservadores.

No entanto, é fundamental entendermos uma questão imperativa, que explica em partes o conflito aqui criado — todos os progressistas contemporâneos são crias oriundas do direito positivo. Por essa razão, eles jamais entenderão de forma pragmática e objetiva conceitos como criminalidade, direitos de propriedade, agressão e liberdade de expressão pela perspectiva do jusnaturalismo, que é manifestamente o direito em seu estado mais puro, correto, ético e equilibrado.

Pela ótica jusnaturalista, uma opinião é uma opinião. Ponto final. E absolutamente ninguém deve ser preso, cancelado, sabotado ou boicotado por expressar uma opinião particular sobre qualquer assunto. Palavras não agridem ninguém, portanto jamais poderiam ser consideradas um crime em si. Apenas deveriam ser tipificados como crimes agressões de caráter objetivo, como roubo, sequestro, fraude, extorsão, estupro e infrações similares, que representam uma ameaça direta à integridade física da vítima, ou que busquem subtrair alguma posse empregando a violência.

Infelizmente, a geração floquinho de neve — terrivelmente histérica, egocêntrica e sensível — fica profundamente ofendida e consternada sempre que alguém defende posicionamentos contrários à religião progressista. Por essa razão, os guerreiros da justiça social sinceramente acreditam que o papai-estado deve censurar todas as opiniões que eles não gostam de ouvir, assim como deve também criar leis para encarcerar todos aqueles que falam ou escrevem coisas que desagradam a militância.

Como a geração floquinho de neve foi criada para acreditar que todas as suas vontades pessoais e disposições ideológicas devem ser sumariamente atendidas pelo papai-estado, eles embarcaram em uma cruzada moral que pretende erradicar todas as coisas que são ofensivas à ideologia progressista; só assim eles poderão deflagrar na Terra o seu tão sonhado paraíso hedonista e igualitário, de inimaginável esplendor e felicidade.

Em virtude do seu comportamento intrinsecamente despótico, autoritário e egocêntrico, acaba sendo inevitável que militantes progressistas problematizem tudo aquilo que os desagrada.

Como são criaturas inúteis destituídas de ocupação real e verdadeiro sentido na vida, sendo oprimidas unicamente na sua própria imaginação, militantes progressistas precisam constantemente inventar novos vilões para serem combatidos.

Partindo dessa perspectiva, é natural para a militância que absolutamente tudo que exista no mundo e que não se enquadra com as regras autoritárias e restritivas da religião progressista seja encarado como um problema. Para a geração floquinho de neve, o capitalismo é um problema. O fascismo é um problema. A iniciativa privada é um problema. O homem branco, tradicionalista, conservador e heterossexual é um problema. A desigualdade é um problema. A liberdade é um problema. Monteiro Lobato é um problema (sim, até mesmo o renomado ícone da literatura brasileira, autor — entre outros títulos — de Urupês, foi vítima da cultura do cancelamento, acusado de ser racista e eugenista).

Para a esquerda, praticamente tudo é um problema. Na mentalidade da militância progressista, tudo é motivo para reclamação. Foi em função desse comportamento histérico, histriônico e infantil que o famoso pensador conservador-libertário americano P. J. O’Rourke afirmou que “o esquerdismo é uma filosofia de pirralhos chorões”. O que é uma verdade absoluta e irrefutável em todos os sentidos.

De fato, todas as filosofias de esquerda de forma geral são idealizações utópicas e infantis de um mundo perfeito. Enquanto o mundo não se transformar naquela colorida e vibrante utopia que é apresentada pela cartilha socialista padrão, militantes continuarão a reclamar contra tudo o que existe no mundo de forma agressiva, visceral e beligerante. Evidentemente, eles não vão fazer absolutamente nada de positivo ou construtivo para que o mundo se transforme no gracioso paraíso que eles tanto desejam ver consolidado, mas eles continuarão a berrar e vociferar muito em sua busca incessante pela utopia, marcando presença em passeatas inúteis ou combatendo o fascismo imaginário nas redes sociais.

Sem dúvida, estamos muito perto de ver leis absurdas e estúpidas sendo implementadas, para agradar a militância da terra colorida do assistencialismo eterno onde nada é escasso e tudo cai do céu. Em breve, você não poderá usar calças pretas, pois elas serão consideradas peças de vestuário excessivamente heterossexuais. Apenas calças amarelas ou coloridas serão permitidas. Você também terá que tingir de cor-de-rosa uma mecha do seu cabelo; pois preservar o seu cabelo na sua cor natural é heteronormativo demais da sua parte, sendo portanto um componente demasiadamente opressor da sociedade.

Você também não poderá ver filmes de guerra ou de ação, apenas comédias românticas, pois certos gêneros de filmes exaltam a violência do patriarcado e isso impede o mundo de se tornar uma graciosa festa colorida de fraternidades universitárias ungidas por pôneis resplandecentes, hedonismo infinito, vadiagem universitária e autogratificação psicodélica, que certamente são elementos indispensáveis para se produzir o paraíso na Terra.

Sabemos perfeitamente, no entanto, que dentre as atitudes “opressivas” que a militância progressista mais se empenha em combater, estão o racismo, o fascismo, o machismo e a homofobia. No entanto, é fundamental entender que ser racista, fascista, machista ou homofóbico não são crimes em si. Na prática, todos esses elementos são apenas traços de personalidade; e eles não podem ser pura e simplesmente criminalizados porque ideólogos e militantes progressistas iluminados não gostam deles.

Tanto pela ética quanto pela ótica jusnaturalista, é facilmente compreensível entender que esses traços de personalidade não podem ser criminalizados ou proibidos simplesmente porque integrantes de uma ideologia não tem nenhuma apreciação ou simpatia por eles. Da mesma forma, nenhum desses traços de personalidade representa em si um perigo para a sociedade, pelo simples fato de existir. Por incrível que pareça, até mesmo o machismo, o racismo, o fascismo e a homofobia merecem a devida apologia.

Mas vamos analisar cada um desses tópicos separadamente para entender isso melhor.

Racismo

Quando falamos no Japão, normalmente não fazemos nenhuma associação da sociedade japonesa com o racismo. No entanto, é incontestável o fato de que a sociedade japonesa pode ser considerada uma das sociedades mais racistas do mundo. E a verdade é que não há absolutamente nada de errado com isso.

Aproximadamente 97% da população do Japão é nativa; apenas 3% do componente populacional é constituído por estrangeiros (a população do Japão é estimada em aproximadamente 126 milhões de habitantes). Isso faz a sociedade japonesa ser uma das mais homogêneas do mundo. As autoridades japonesas reconhecidamente dificultam processos de seleção e aplicação a estrangeiros que desejam se tornar residentes. E a maioria dos japoneses aprova essa decisão.

Diversos estabelecimentos comerciais como hotéis, bares e restaurantes por todo o país tem placas na entrada que dizem “somente para japoneses” e a maioria destes estabelecimentos se recusa ostensivamente a atender ou aceitar clientes estrangeiros, não importa quão ricos ou abastados sejam.

Na Terra do Sol Nascente, a hostilidade e a desconfiança natural para com estrangeiros é tão grande que até mesmo indivíduos que nascem em algum outro país, mas são filhos de pais japoneses, não são considerados cidadãos plenamente japoneses.

Se estes indivíduos decidem sair do seu país de origem para se estabelecer no Japão — mesmo tendo descendência nipônica legítima e inquestionável —, eles enfrentarão uma discriminação social considerável, especialmente se não dominarem o idioma japonês de forma impecável. Esse fato mostra que a discriminação é uma parte tão indissociável quanto elementar da sociedade japonesa, e ela está tão profundamente arraigada à cultura nipônica que é praticamente impossível alterá-la ou atenuá-la por qualquer motivo.

A verdade é que — quando falamos de um país como o Japão — nem todos os discursos politicamente corretos do mundo, nem a histeria progressista ocidental mais inflamada poderão algum dia modificar, extirpar ou sequer atenuar o componente racista da cultura nipônica. E isso é consequência de uma questão tão simples quanto primordial: discriminar faz parte da natureza humana, sendo tanto um direito individual quanto um elemento cultural inerente à muitas nações do mundo. Os japoneses não tem problema algum em admitir ou institucionalizar o seu preconceito, justamente pelo fato de que a ideologia politicamente correta não tem no oriente a força e a presença que tem no ocidente.

E é fundamental enfatizar que, sendo de natureza pacífica — ou seja, não violando nem agredindo terceiros —, a discriminação é um recurso natural dos seres humanos, que está diretamente associada a questões como familiaridade e segurança.

Absolutamente ninguém deve ser forçado a apreciar ou integrar-se a raças, etnias, pessoas ou tribos que não lhe transmitem sentimentos de segurança ou familiaridade. Integração forçada é o verdadeiro crime, e isso diversos países europeus — principalmente os escandinavos (países que lideram o ranking de submissão à ideologia politicamente correta) — aprenderam da pior forma possível.

A integração forçada com imigrantes islâmicos resultou em ondas de assassinato, estupro e violência inimagináveis para diversos países europeus, até então civilizados, que a imprensa ocidental politicamente correta e a militância progressista estão permanentemente tentando esconder, porque não desejam que o ocidente descubra como a agenda “humanitária” de integração forçada dos povos muçulmanos em países do Velho Mundo resultou em algumas das piores chacinas e tragédias na história recente da Europa.

Ou seja, ao discriminarem estrangeiros, os japoneses estão apenas se protegendo e lutando para preservar sua nação como um ambiente cultural, étnico e social que lhe é seguro e familiar, assim se opondo a mudanças bruscas, indesejadas e antinaturais, que poderiam comprometer a estabilidade social do país.

A discriminação — sendo de natureza pacífica —, é benévola, salutar e indubitavelmente ajuda a manter a estabilidade social da comunidade. Toda e qualquer forma de integração forçada deve ser repudiada com veemência, pois, mais cedo ou mais tarde, ela irá subverter a ordem social vigente, e sempre será acompanhada de deploráveis e dramáticos resultados.

Para citar novamente os países escandinavos, a Suécia é um excelente exemplo do que não fazer. Tendo seguido o caminho contrário ao da discriminação racional praticada pela sociedade japonesa, atualmente a sociedade sueca — além de afundar de forma consistente na lama da libertinagem, da decadência e da deterioração progressista — sofre em demasia com os imigrantes muçulmanos, que foram deixados praticamente livres para matar, saquear, esquartejar e estuprar quem eles quiserem. Hoje, eles são praticamente intocáveis, visto que denunciá-los, desmoralizá-los ou acusá-los de qualquer crime é uma atitude politicamente incorreta e altamente reprovada pelo establishment progressista. A elite socialista sueca jamais se atreve a acusá-los de qualquer crime, pois temem ser classificados como xenófobos e intolerantes. Ou seja, a desgraça da Europa, sobretudo dos países escandinavos, foi não ter oferecido nenhuma resistência à ideologia progressista politicamente correta. Hoje, eles são totalmente submissos a ela.

O exemplo do Japão mostra, portanto — para além de qualquer dúvida —, a importância ética e prática da discriminação, que é perfeitamente aceitável e natural, sendo uma tendência inerente aos seres humanos, e portanto intrínseca a determinados comportamentos, sociedades e culturas.

Indo ainda mais longe nessa questão, devemos entender que na verdade todos nós discriminamos, e não existe absolutamente nada de errado nisso. Discriminar pessoas faz parte da natureza humana e quem se recusa a admitir esse fato é um hipócrita. Mulheres discriminam homens na hora de selecionar um parceiro; elas avaliam diversos quesitos, como altura, aparência, status social, condição financeira e carisma. E dentre suas opções, elas sempre escolherão o homem mais atraente, másculo e viril, em detrimento de todos os baixinhos, calvos, carentes, frágeis e inibidos que possam estar disponíveis. Da mesma forma, homens sempre terão preferência por mulheres jovens, atraentes e delicadas, em detrimento de todas as feministas de meia-idade, acima do peso, de cabelo pintado, que são mães solteiras e militantes socialistas. A própria militância progressista discrimina pessoas de forma virulenta e intransigente, como fica evidente no tratamento que dispensam a mulheres bolsonaristas e a negros de direita.

A verdade é que — não importa o nível de histeria da militância progressista — a discriminação é inerente à condição humana e um direito natural inalienável de todos. É parte indissociável da natureza humana e qualquer pessoa pode e deve exercer esse direito sempre que desejar. Não existe absolutamente nada de errado em discriminar pessoas. O problema real é a ideologia progressista e o autoritarismo politicamente correto, movimentos tirânicos que não respeitam o direito das pessoas de discriminar.

Fascismo

Quando falamos de fascismo, precisamos entender que, para a esquerda política, o fascismo é compreendido como um conceito completamente divorciado do seu significado original. Para um militante de esquerda, fascista é todo aquele que defende posicionamentos contrários ao progressismo, não se referindo necessariamente a um fascista clássico.

Mas, seja como for, é necessário entender que — como qualquer ideologia política — até mesmo o fascismo clássico tem o direito de existir e ocupar o seu devido lugar; portanto, fascistas não devem ser arbitrariamente censurados, apesar de defenderem conceitos que representam uma completa antítese de tudo aquilo que é valioso para os entusiastas da liberdade.

Em um país como o Brasil, onde socialistas e comunistas tem total liberdade para se expressar, defender suas ideologias e até mesmo formar partidos políticos, não faz absolutamente o menor sentido que fascistas — e até mesmo nazistas assumidos — sofram qualquer tipo de discriminação. Embora socialistas e comunistas se sintam moralmente superiores aos fascistas (ou a qualquer outra filosofia política ou escola de pensamento), sabemos perfeitamente que o seu senso de superioridade é fruto de uma pueril romantização universitária da sua própria ideologia. A história mostra efetivamente que o socialismo clássico e o comunismo causaram muito mais destruição do que o fascismo.

Portanto, se socialistas e comunistas tem total liberdade para se expressar, não existe a menor razão para que fascistas não usufruam dessa mesma liberdade.

É claro, nesse ponto, seremos invariavelmente confrontados por um oportuno dilema — o famoso paradoxo da intolerância, de Karl Popper. Até que ponto uma sociedade livre e tolerante deve tolerar a intolerância (inerente a ideologias totalitárias)?

As leis de propriedade privada resolveriam isso em uma sociedade livre. O mais importante a levarmos em consideração no atual contexto, no entanto — ao defender ou criticar uma determinada ideologia, filosofia ou escola de pensamento —, é entender que, seja ela qual for, ela tem o direito de existir. E todas as pessoas que a defendem tem o direito de defendê-la, da mesma maneira que todos os seus detratores tem o direito de criticá-la.

Essa é uma forte razão para jamais apoiarmos a censura. Muito pelo contrário, devemos repudiar com veemência e intransigência toda e qualquer forma de censura, especialmente a estatal.

Existem duas fortes razões para isso:

A primeira delas é a volatilidade da censura (especialmente a estatal). A censura oficial do governo, depois que é implementada, torna-se absolutamente incontrolável. Hoje, ela pode estar apontada para um grupo de pessoas cujas ideias divergem das suas. Mas amanhã, ela pode estar apontada justamente para as ideias que você defende. É fundamental, portanto, compreendermos que a censura estatal é incontrolável. Sob qualquer ponto de vista, é muito mais vantajoso que exista uma vasta pluralidade de ideias conflitantes na sociedade competindo entre si, do que o estado decidir que ideias podem ser difundidas ou não.

Além do mais, libertários e anarcocapitalistas não podem nunca esperar qualquer tipo de simpatia por parte das autoridades governamentais. Para o estado, seria infinitamente mais prático e vantajoso criminalizar o libertarianismo e o anarcocapitalismo — sob a alegação de que são filosofias perigosas difundidas por extremistas radicais que ameaçam o estado democrático de direito — do que o fascismo ou qualquer outra ideologia centralizada em governos burocráticos e onipotentes. Portanto, defender a censura, especialmente a estatal, representa sempre um perigo para o próprio indivíduo, que mais cedo ou mais tarde poderá ver a censura oficial do sistema se voltar contra ele.

Outra razão pela qual libertários jamais devem defender a censura, é porque — ao contrário dos estatistas — não é coerente que defensores da liberdade se comportem como se o estado fosse o seu papai e o governo fosse a sua mamãe. Não devemos terceirizar nossas próprias responsabilidades, tampouco devemos nos comportar como adultos infantilizados. Assumimos a responsabilidade de combater todas as ideologias e filosofias que agridem a liberdade e os seres humanos. Não procuramos políticos ou burocratas para executar essa tarefa por nós.

Portanto, se você ver um fascista sendo censurado nas redes sociais ou em qualquer outro lugar, assuma suas dores. Sinta-se compelido a defendê-lo, mostre aos seus detratores que ele tem todo direito de se expressar, como qualquer pessoa. Você não tem obrigação de concordar com ele ou apreciar as ideias que ele defende. Mas silenciar arbitrariamente qualquer pessoa não é uma pauta que honra a liberdade.

Se você não gosta de estado, planejamento central, burocracia, impostos, tarifas, políticas coletivistas, nacionalistas e desenvolvimentistas, mostre com argumentos coesos e convincentes porque a liberdade e o livre mercado são superiores a todos esses conceitos. Mas repudie a censura com intransigência e mordacidade.

Em primeiro lugar, porque você aprecia e defende a liberdade de expressão para todas as pessoas. E em segundo lugar, por entender perfeitamente que — se a censura eventualmente se tornar uma política de estado vigente entre a sociedade — é mais provável que ela atinja primeiro os defensores da liberdade do que os defensores do estado.

Machismo

Muitos elementos do comportamento masculino que hoje são atacados com virulência e considerados machistas pelo movimento progressista são na verdade manifestações naturais intrínsecas ao homem, que nossos avôs cultivaram ao longo de suas vidas sem serem recriminados por isso. Com a ascensão do feminismo, do progressismo e a eventual problematização do sexo masculino, o antagonismo militante dos principais líderes da revolução sexual da contracultura passou a naturalmente condenar todos os atributos genuinamente masculinos, por considerá-los símbolos de opressão e dominação social.

Apesar do Brasil ser uma sociedade liberal ultra-progressista, onde o estado protege mais as mulheres do que as crianças — afinal, a cada semana novas leis são implementadas concedendo inúmeros privilégios e benefícios às mulheres, aos quais elas jamais teriam direito em uma sociedade genuinamente machista e patriarcal —, a esquerda política persiste em tentar difundir a fantasia da opressão masculina e o mito de que vivemos em uma sociedade machista e patriarcal.

Como sempre, a realidade mostra um cenário muito diferente daquilo que é pregado pela militância da terra da fantasia. O Brasil atual não tem absolutamente nada de machista ou patriarcal. No Brasil, mulheres podem votar, podem ocupar posições de poder e autoridade tanto na esfera pública quanto em companhias privadas, podem se candidatar a cargos políticos, podem ser vereadoras, deputadas, governadoras, podem ser proprietárias do próprio negócio, podem se divorciar, podem dirigir, podem comprar armas, podem andar de biquíni nas praias, podem usar saias extremamente curtas, podem ver programas de televisão sobre sexo voltados única e exclusivamente para o público feminino, podem se casar com outras mulheres, podem ser promíscuas, podem consumir bebidas alcoólicas ao ponto da embriaguez, e podem fazer praticamente tudo aquilo que elas desejarem. No Brasil do século XXI, as mulheres são genuinamente livres para fazer as próprias escolhas em praticamente todos os aspectos de suas vidas. O que mostra efetivamente que a tal opressão do patriarcado não existe.

O liberalismo social extremo do qual as mulheres usufruem no Brasil atual — e que poderíamos estender a toda a sociedade contemporânea ocidental — é suficiente para desmantelar completamente a fábula feminista da sociedade patriarcal machista e opressora, que existe única e exclusivamente no mundinho de fantasias ideológicas da esquerda progressista.

Tão importante quanto, é fundamental compreender que nenhum homem é obrigado a levar o feminismo a sério ou considerá-lo um movimento social e político legítimo. Para um homem, ser considerado machista ou até mesmo assumir-se como um não deveria ser um problema. O progressismo e o feminismo — com o seu nefasto hábito de demonizar os homens, bem como todos os elementos inerentes ao comportamento e a cultura masculina — é que são o verdadeiro problema, conforme tentam modificar o homem para transformá-lo em algo que ele não é nem deveria ser: uma criatura dócil, passiva e submissa, que é comandada por ideologias hostis e antinaturais, que não respeitam a hierarquia de uma ordem social milenar e condições inerentes à própria natureza humana. Com o seu hábito de tentar modificar tudo através de leis e decretos, o feminismo e o progressismo mostram efetivamente que o seu real objetivo é criminalizar a masculinidade.

A verdade é que — usufruindo de um nível elevado de liberdades — não existe praticamente nada que a mulher brasileira do século XXI não possa fazer. Adicionalmente, o governo dá as mulheres uma quantidade tão avassaladora de vantagens, privilégios e benefícios, que está ficando cada vez mais difícil para elas encontrarem razões válidas para reclamarem da vida. Se o projeto de lei que pretende fornecer um auxílio mensal de mil e duzentos reais para mães solteiras for aprovado pelo senado, muitas mulheres que tem filhos não precisarão nem mesmo trabalhar para ter sustento. E tantas outras procurarão engravidar, para ter direito a receber uma mesada mensal do governo até o seu filho completar a maioridade.

O que a militância colorida da terra da fantasia convenientemente ignora — pois a realidade nunca corresponde ao seu conto de fadas ideológico — é que o mundo de uma forma geral continua sendo muito mais implacável com os homens do que é com as mulheres. No Brasil, a esmagadora maioria dos suicídios é praticada por homens, a maioria das vítimas de homicídio são homens e de cada quatro moradores de rua, três são homens. Mas é evidente que uma sociedade liberal ultra-progressista não se importa com os homens, pois ela não é influenciada por fatos concretos ou pela realidade. Seu objetivo é simplesmente atender as disposições de uma agenda ideológica, não importa quão divorciadas da realidade elas são.

O nível exacerbado de liberdades sociais e privilégios governamentais dos quais as mulheres brasileiras usufruem é suficiente para destruir a fantasiosa fábula da sociedade machista, opressora e patriarcal. Se as mulheres brasileiras não estão felizes, a culpa definitivamente não é dos homens. Se a vasta profusão de liberdades, privilégios e benefícios da sociedade ocidental não as deixa plenamente saciadas e satisfeitas, elas podem sempre mudar de ares e tentar uma vida mais abnegada e espartana em países como Irã, Paquistão ou Afeganistão. Quem sabe assim elas não se sentirão melhores e mais realizadas?

Homofobia

Quando falamos em homofobia, entramos em uma categoria muito parecida com a do racismo: o direito de discriminação é totalmente válido. Absolutamente ninguém deve ser obrigado a aceitar homossexuais ou considerar o homossexualismo como algo normal. Sendo cristão, não existe nem sequer a mais vaga possibilidade de que algum dia eu venha a aceitar o homossexualismo como algo natural. O homossexualismo se qualifica como um grave desvio de conduta e um pecado contra o Criador.

A Bíblia proíbe terminantemente conduta sexual imoral, o que — além do homossexualismo — inclui adultério, fornicação, incesto e bestialidade, entre outras formas igualmente pérfidas de degradação.

Segue abaixo três passagens bíblicas que proíbem terminantemente a conduta homossexual:

“Não te deitarás com um homem como se deita com uma mulher. Isso é abominável!” (Levítico 18:22 — King James Atualizada)

“Se um homem se deitar com outro homem, como se deita com mulher, ambos terão praticado abominação; certamente serão mortos; o seu sangue estará sobre eles.” (Levítico 20:13 — João Ferreira de Almeida Atualizada)

“O quê! Não sabeis que os injustos não herdarão o reino de Deus? Não sejais desencaminhados. Nem fornicadores, nem idólatras, nem adúlteros, nem homens mantidos para propósitos desnaturais, nem homens que se deitam com homens, nem ladrões, nem gananciosos, nem beberrões, nem injuriadores, nem extorsores herdarão o reino de Deus.” (1 Coríntios 6:9,10 —Tradução do Novo Mundo das Escrituras Sagradas com Referências)

Se você não é religioso, pode simplesmente levar em consideração o argumento do respeito pela ordem natural. A ordem natural é incondicional e incisiva com relação a uma questão: o complemento de tudo o que existe é o seu oposto, não o seu igual. O complemento do dia é a noite, o complemento da luz é a escuridão, o complemento da água, que é líquida, é a terra, que é sólida. E como sabemos o complemento do macho — de sua respectiva espécie — é a fêmea.

Portanto, o complemento do homem, o macho da espécie humana, é naturalmente a mulher, a fêmea da espécie humana. Um homem e uma mulher podem naturalmente se reproduzir, porque são um complemento biológico natural. Por outro lado, um homem e outro homem são incapazes de se reproduzir, assim como uma mulher e outra mulher.

Infelizmente, o mundo atual está longe de aceitar como plenamente estabelecida a ordem natural pelo simples fato dela existir, visto que tentam subvertê-la a qualquer custo, não importa o malabarismo intelectual que tenham que fazer para justificar os seus pontos de vista distorcidos e antinaturais. A libertinagem irrefreável e a imoralidade bestial do mundo contemporâneo pós-moderno não reconhecem nenhum tipo de limite. Quem tenta restabelecer princípios morais salutares é imediatamente considerado um vilão retrógrado e repressivo, sendo ativamente demonizado pela militância do hedonismo, da luxúria e da licenciosidade desenfreada e sem limites.

Definitivamente, fazer a apologia da moralidade, do autocontrole e do autodomínio não faz nenhum sucesso na Sodoma e Gomorra global dos dias atuais. O que faz sucesso é lacração, devassidão, promiscuidade e prazeres carnais vazios. O famoso escritor e filósofo francês Albert Camus expressou uma verdade contundente quando disse: “Uma só frase lhe bastará para definir o homem moderno — fornicava e lia jornais”.

Qualquer indivíduo tem o direito inalienável de discriminar ativamente homossexuais, pelo direito que ele julgar mais pertinente no seu caso. A objeção de consciência para qualquer situação é um direito natural dos indivíduos. Há alguns anos, um caso que aconteceu nos Estados Unidos ganhou enorme repercussão internacional, quando o confeiteiro Jack Phillips se recusou a fazer um bolo de casamento para o “casal” homossexual Dave Mullins e Charlie Craig.

Uma representação dos direitos civis do estado do Colorado abriu um inquérito contra o confeiteiro, alegando que ele deveria ser obrigado a atender todos os clientes, independente da orientação sexual, raça ou crença. Preste atenção nas palavras usadas — ele deveria ser obrigado a atender.

Como se recusou bravamente a ceder, o caso foi parar invariavelmente na Suprema Corte, que decidiu por sete a dois em favor de Jack Phillips, sob a alegação de que obrigar o confeiteiro a atender o “casal” homossexual era uma violação nefasta dos seus princípios religiosos. Felizmente, esse foi um caso em que a liberdade prevaleceu sobre a tirania progressista.

Evidentemente, homossexuais não devem ser agredidos, ofendidos, internados em clínicas contra a sua vontade, nem devem ser constrangidos em suas liberdades pelo fato de serem homossexuais. O que eles precisam entender é que a liberdade é uma via de mão dupla. Eles podem ter liberdade para adotar a conduta que desejarem e fazer o que quiserem (contanto que não agridam ninguém), mas da mesma forma, é fundamental respeitar e preservar a liberdade de terceiros que desejam rejeitá-los pacificamente, pelo motivo que for.

Afinal, ninguém tem a menor obrigação de aceitá-los, atendê-los ou sequer pensar que uma união estável entre duas pessoas do mesmo sexo — incapaz de gerar descendentes, e, portanto, antinatural — deva ser considerado um matrimônio de verdade. Absolutamente nenhuma pessoa, ideia, movimento, crença ou ideologia usufrui de plena unanimidade no mundo. Por que o homossexualismo deveria ter tal privilégio?

Homossexuais não são portadores de uma verdade definitiva, absoluta e indiscutível, que está acima da humanidade. São seres humanos comuns que — na melhor das hipóteses —, levam um estilo de vida que pode ser considerado “alternativo”, e absolutamente ninguém tem a obrigação de considerar esse estilo de vida normal ou aceitável. A única obrigação das pessoas é não interferir, e isso não implica uma obrigação em aceitar.

Discriminar homossexuais (assim como pessoas de qualquer outro grupo, raça, religião, nacionalidade ou etnia) é um direito natural por parte de todos aqueles que desejam exercer esse direito. E isso nem o direito positivo nem a militância progressista poderão algum dia alterar ou subverter. O direito natural e a inclinação inerente dos seres humanos em atender às suas próprias disposições é simplesmente imutável e faz parte do seu conjunto de necessidades.

Conclusão

A militância progressista é absurdamente autoritária, e todas as suas estratégias e disposições ideológicas mostram que ela está em uma guerra permanente contra a ordem natural, contra a liberdade e principalmente contra o homem branco, cristão, conservador e tradicionalista — possivelmente, aquilo que ela mais odeia e despreza.

Nós não podemos, no entanto, ceder ou dar espaço para a agenda progressista, tampouco pensar em considerar como sendo normais todas as pautas abusivas e tirânicas que a militância pretende estabelecer como sendo perfeitamente razoáveis e aceitáveis, quer a sociedade aceite isso ou não. Afinal, conforme formos cedendo, o progressismo tirânico e totalitário tende a ganhar cada vez mais espaço.

Quanto mais espaço o progressismo conquistar, mais corroída será a liberdade e mais impulso ganhará o totalitarismo. Com isso, a cultura do cancelamento vai acabar com carreiras, profissões e com o sustento de muitas pessoas, pelo simples fato de que elas discordam das pautas universitárias da moda.

A história mostra perfeitamente que quanto mais liberdade uma sociedade tem, mais progresso ela atinge. Por outro lado, quanto mais autoritária ela for, mais retrocessos ela sofrerá. O autoritarismo se combate com liberdade, desafiando as pautas de todos aqueles que persistem em implementar a tirania na sociedade. O politicamente correto é o nazismo dos costumes, que pretende subverter a moral através de uma cultura de vigilância policial despótica e autoritária, para que toda a sociedade seja subjugada pela agenda totalitária progressista.

Pois quanto a nós, precisamos continuar travando o bom combate em nome da liberdade. E isso inclui reconhecer que ideologias, hábitos e costumes de que não gostamos tem o direito de existir e até mesmo de serem defendidos.

@ ee11a5df:b76c4e49

Implementing The Gossip Model

version 2 (2024-03-23)

Introduction

History

The gossip model is a general concept that allows clients to dynamically follow the content of people, without specifying which relay. The clients have to figure out where each person puts their content.

Before NIP-65, the gossip client did this in multiple ways:

1. Checking kind-3 contents, which had relay lists for configuring some clients (originally Astral and Damus), and recognizing that wherever they were writing our client could read from.
2. NIP-05 specifying a list of relays in the nostr.json file. I added this to NIP-35 which got merged down into NIP-05.
3. Recommended relay URLs that are found in 'p' tags
4. Users manually making the association
5. History of where events happen to have been found. Whenever an event came in, we associated the author with the relay.

Each of these associations were given a score (recommended relay urls are 3rd party info so they got a low score).

Later, NIP-65 made a new kind of relay list where someone could advertise to others which relays they use. The flag "write" is now called an OUTBOX, and the flag "read" is now called an INBOX.

The idea of inboxes came about during the development of NIP-65. They are a way to send an event to a person to make sure they get it... because putting it on your own OUTBOX doesn't guarantee they will read it -- they may not follow you.

The outbox model is the use of NIP-65. It is a subset of the gossip model which uses every other resource at it's disposal.

Rationale

The gossip model keeps nostr decentralized. If all the (major) clients were using it, people could spin up small relays for both INBOX and OUTBOX and still be fully connected, have their posts read, and get replies and DMs. This is not to say that many people should spin up small relays. But the task of being decentralized necessitates that people must be able to spin up their own relay in case everybody else is censoring them. We must make it possible. In reality, congregating around 30 or so popular relays as we do today is not a problem. Not until somebody becomes very unpopular with bitcoiners (it will probably be a shitcoiner), and then that person is going to need to leave those popular relays and that person shouldn't lose their followers or connectivity in any way when they do.

A lot more rationale has been discussed elsewhere and right now I want to move on to implementation advice.

Implementation Advice

Read NIP-65

NIP-65 will contain great advice on which relays to consult for which purposes. This post does not supersede NIP-65. NIP-65 may be getting some smallish changes, mostly the addition of a private inbox for DMs, but also changes to whether you should read or write to just some or all of a set of relays.

How often to fetch kind-10002 relay lists for someone

This is up to you. Refreshing them every hour seems reasonable to me. Keeping track of when you last checked so you can check again every hour is a good idea.

Where to fetch events from

If your user follows another user (call them jack), then you should fetch jack's events from jack's OUTBOX relays. I think it's a good idea to use 2 of those relays. If one of those choices fails (errors), then keep trying until you get 2 of them that worked. This gives some redundancy in case one of them is censoring. You can bump that number up to 3 or 4, but more than that is probably just wasting bandwidth.

To find events tagging your user, look in your user's INBOX relays for those. In this case, look into all of them because some clients will only write to some of them (even though that is no longer advised).

Picking relays dynamically

Since your user follows many other users, it is very useful to find a small subset of all of their OUTBOX relays that cover everybody followed. I wrote some code to do this as (it is used by gossip) that you can look at for an example.

Where to post events to

Post all events (except DMs) to all of your users OUTBOX relays. Also post the events to all the INBOX relays of anybody that was tagged or mentioned in the contents in a nostr bech32 link (if desired). That way all these mentioned people are aware of the reply (or quote or repost).

DMs should be posted only to INBOX relays (in the future, to PRIVATE INBOX relays). You should post it to your own INBOX relays also, because you'll want a record of the conversation. In this way, you can see all your DMs inbound and outbound at your INBOX relay.

Where to publish your user's kind-10002 event to

This event was designed to be small and not require moderation, plus it is replaceable so there is only one per user. For this reason, at the moment, just spread it around to lots of relays especially the most popular relays.

For example, the gossip client automatically determines which relays to publish to based on whether they seem to be working (several hundred) and does so in batches of 10.

How to find replies

If all clients used the gossip model, you could find all the replies to any post in the author's INBOX relays for any event with an 'e' tag tagging the event you want replies to... because gossip model clients will publish them there.

But given the non-gossip-model clients, you should also look where the event was seen and look on those relays too.

Clobbering issues

Please read your users kind 10002 event before clobbering it. You should look many places to make sure you didn't miss the newest one.

If the old relay list had tags you don't understand (e.g. neither "read" nor "write"), then preserve them.

How users should pick relays

Today, nostr relays are not uniform. They have all kinds of different rule-sets and purposes. We severely lack a way to advice non-technical users as to which relays make good OUTBOX relays and which ones make good INBOX relays. But you are a dev, you can figure that out pretty well. For example, INBOX relays must accept notes from anyone meaning they can't be paid-subscription relays.

Bandwidth isn't a big issue

The outbox model doesn't require excessive bandwidth when done right. You shouldn't be downloading the same note many times... only 2-4 times depending on the level of redundancy your user wants.

Downloading 1000 events from 100 relays is in theory the same amount of data as downloading 1000 events from 1 relay.

But in practice, due to redundancy concerns, you will end up downloading 2000-3000 events from those 100 relays instead of just the 1000 you would in a single relay situation. Remember, per person followed, you will only ask for their events from 2-4 relays, not from all 100 relays!!!

Also in practice, the cost of opening and maintaining 100 network connections is more than the cost of opening and maintaining just 1. But this isn't usually a big deal unless...

Crypto overhead on Low-Power Clients

Verifying Schnorr signatures in the secp256k1 cryptosystem is not cheap. Setting up SSL key exchange is not cheap either. But most clients will do a lot more event signature validations than they will SSL setups.

For this reason, connecting to 50-100 relays is NOT hugely expensive for clients that are already verifying event signatures, as the number of events far surpasses the number of relay connections.

But for low-power clients that can't do event signature verification, there is a case for them not doing a lot of SSL setups either. Those clients would benefit from a different architecture, where half of the client was on a more powerful machine acting as a proxy for the low-power half of the client. These halves need to trust each other, so perhaps this isn't a good architecture for a business relationship, but I don't know what else to say about the low-power client situation.

Unsafe relays

Some people complain that the outbox model directs their client to relays that their user has not approved. I don't think it is a big deal, as such users can use VPNs or Tor if they need privacy. But for such users that still have concerns, they may wish to use clients that give them control over this. As a client developer you can choose whether to offer this feature or not.

The gossip client allows users to require whitelisting for connecting to new relays and for AUTHing to relays.

See Also

The Gossip Model: Outstanding Issues

@ 3bf0c63f:aefa459d

Zettelkasten

https://writingcooperative.com/zettelkasten-how-one-german-scholar-was-so-freakishly-productive-997e4e0ca125 (um artigo meio estúpido, mas útil).

Esta incrível técnica de salvar notas sem categorias, sem pastas, sem hierarquia predefinida, mas apenas fazendo referências de uma nota à outra e fazendo supostamente surgir uma ordem (ou heterarquia, disseram eles) a partir do caos parece ser o que faltava pra eu conseguir anotar meus pensamentos e idéias de maneira decente, veremos.

Ah, e vou usar esse tal neuron que também gera sites a partir das notas?, acho que vai ser bom.

@ 3bf0c63f:aefa459d

idea: "numbeo" with satoshis

This site has a crowdsourced database of cost-of-living in many countries and cities: https://www.numbeo.com/cost-of-living/ and it sells the data people write there freely. It's wrong!

Could be an fruitful idea to pay satoshis for people to provide data.

@ 0f1b5961:868242bd

Trying out the highligher.com editor...

heaven : earth governance : generation emanation : emergence selection : variation

@ ecda4328:1278f072

In the evolving world of cryptocurrency, ensuring the security of your digital assets is paramount. For those looking to safeguard their Bitcoin and other cryptocurrencies, selecting the right hardware wallet is crucial. Here, I recommend some top choices based on functionality and security.

Swiss Choices for Bitcoin: BitBox02

For Bitcoin enthusiasts/maxis, the Swiss-made BitBox02 - Bitcoin-only edition is a top recommendation. This wallet focuses solely on Bitcoin, ensuring specialized security and features for the most popular cryptocurrency. Although there is a version supporting multiple cryptocurrencies, the Bitcoin-only edition stands out for its dedicated functionality (Less code means less attack surface, which further improves your security when only storing Bitcoin). Learn more about this wallet here.

Swiss Tangem: A Unique Approach

Another Swiss option, Tange. Tangem is particularly appealing due to its unique approach to security. With Tangem cards, there's no need to generate or back up a mnemonic phrase (a series of 24 words used to recover wallets). The key is simply not to lose the cards and remember the access code, which adds an extra layer of security in case of loss. This approach simplifies security while maintaining robust protection for your assets.

Special Offer: For those interested in purchasing a Tangem Wallet, I have a special offer for you. By using my referral code, you can buy a Tangem Wallet at a discounted price. Click here and use the promo code MY6D7U to enjoy your discount.

Explore Tangem here.

Tangem's Mnemonic Phrase Advantage

Tangem's standout feature is the absence of the need for a mnemonic phrase. This reduces the risk of loss due to complicated backup schemes.

However, for those who do backup mnemonic phrases, I recommend using a metal plate for added durability against elements like fire and water. It's crucial to protect your mnemonic phrase thoroughly, as it essentially makes you your own bank. A fireproof and waterproof safe is advisable for storing these phrases. While some split the phrase and store parts in different locations, I advise against overly complicating the storage scheme to prevent loss. Adding an optional password for additional security is also recommended. Remember, mnemonic phrases unlock the same wallet addresses across different hardware wallets, as most use the BIP39 protocol for generating a seed from the 24-word phrase. Check out this list for reference: BIP39 Word List.

Worth reading: - Seed Phrases Explained: Best Practices for Crypto Security - How Tangem Wallet backs up private keys - How Your Tangem Wallet Works Without Tangem: Apocalypse Scenario

French Ledger: A Shift in Trust

The French Ledger Nano S Plus or Ledger Nano X were previously high on the recommendation list. However, trust in these devices has diminished due to Ledger's service Ledger Recover allowing mnemonic phrase backups on third-party servers. This goes against the principle of a hardware wallet, where your seed should never be exportable or stored externally.

Chinese Keystone 3 Pro: A Contender with Caveats

As an alternative to Ledger, the Chinese Keystone 3 Pro could be considered. Although there are concerns about its Chinese manufacturing possibly implying vulnerabilities, its functionality—like signing transactions via QR codes without direct computer connection—offers a level of security. However, choosing a hardware wallet should be based on the specific cryptocurrencies you plan to store. For Bitcoin-only storage, the BitBox02 Bitcoin-only edition is highly recommended.

Worth reading: - Does airgap make Bitcoin hardware wallets more secure?

Czech Trezor: Slow to Innovate and Security Concerns

Regarding the Czech Trezor Model T, it's not recommended due to its slow pace in integrating new features. Recent controversies surrounding the integration of CoinJoin and concerns over censorship and transaction filtering have also marred its reputation. Furthermore, the Trezor Model T has proven to be vulnerable in case of loss, as demonstrated by a hacker in this video, potentially exposing your cryptocurrency to risks.

The Case of Canadian Coldcard (MK4): A Shift from FOSS

An important development in the hardware wallet space is the case of the Coldcard Mk4. Initially, Coldcard was a fully open-source software (FOSS) project. In FOSS, the "Free" refers to the freedom to run, study, redistribute, and modify the software, a principle highly valued in the crypto community. However, a significant shift occurred in the journey of Coldcard:

1. Initial FOSS and Bootstrapping: Coldcard, developed by nvk and Peter, started as a FOSS project. They bootstrapped the development, rejecting offers from venture capital investors interested in the project.
2. Foundation's Entry: Subsequently, the Foundation cloned Coldcard's code and announced a slightly different hardware. Notably, they raised funds from the same VCs that Coldcard had previously turned down.
3. License Change: In response to these events, Coldcard altered its software license. The new license permits all activities except those performed by the Foundation, marking a departure from its original FOSS status.

This change has sparked discussions within the cryptocurrency community about the importance of maintaining open-source principles in the development of hardware wallets. The Coldcard MK4's shift from FOSS underscores the complex dynamics between open-source ethos and commercial interests in the crypto world.

Source: X/Twitter thread.

Conclusion

In conclusion, when choosing a hardware wallet, consider the specific cryptocurrencies you'll be storing and the compatibility of the wallet with your intended use, especially concerning smart contracts and other features. While there are numerous options in the market, careful consideration of security features and the reputation of the manufacturer can guide you in making a secure choice for your digital assets.

@ 06639a38:655f8f71

When we moved into our new home in 2017, one of the things we did was adding a epoxy coating layer to the concrete floor in our garage. Some photo's of the work in progress.

The is the coating we used:

One of the best modifications we've done in our garage, the floor is still very proper and easy to clean!

What does your garage floor look like?

@ 3bf0c63f:aefa459d

Boardthreads

This was a very badly done service for turning a Trello list into a helpdesk UI.

Surprisingly, it had more paying users than Websites For Trello, which I was working on simultaneously and dedicating much more time to it.

The Neo4j database I used for this was a very poor choice, it was probably the cause of all the bugs.

-https://github.com/fiatjaf/boardthreads

@ 1bc70a01:24f6a411

The concept of value of value is one where information yearns to flow freely, transactions should be voluntary, unlimited and direct. In V4V model, people pay what something is worth to them.

Sounds great. On paper. There are some issues…

Free sucks

At least, that’s the perception. People don’t assign much value to free. Ask anyone who has ever ran any business and has not suggested a value for a product or service and they’ll tell you that they earned far less than when charging for the thing.

It’s true, some people will give a lot, some a little, and most none. Most - none. None.

Pricing is Signal

Pricing is a signal of desirability and quality. Of course, it is often incorrect and people manipulate pricing all the time. But for the most part, people don’t see much value in free. Unless a recommended price is offered, people will usually pay nothing. This is not a great model to thrive on if you spend years of your life acquiring knowledge and turning it into products that nobody ultimately buys. 
I have very personal experience with free. I’ve created and sold digital products and ran many pricing experiments myself. The highest priced products usually generated the most revenue. Surprise! The middle cost product (same product, just priced less) decimated the revenue stream. When set to 0 (even with a suggested minimum price), I generated almost no revenue at all.

None of this is surprising. Pricing acts as a psychological anchor. “You get what you pay for” is ingrained in our brains whether we think about it or not.

People are clueless

The issue with price is that most people don’t have a clue what anything is worth. The only time people have any rough idea of what they should pay for something is when they have already purchased that thing in the past. But, introduce something they have never before purchased and they won’t have a single clue about what to pay. Take for example a set of professional photos of you and your family. Unless you’ve been to a photo studio in the last 5 years, you probably won’t have a single clue what that package of photos is worth. Does that mean the product is worthless? Of course not, but people don’t know what to pay.

In a value for value model, the absence of price makes it super difficult to determine the value of anything. You may take some social cues from previous payments from other people, but this could backfire for the content creator.

Suppose I created a UI framework that saved developers hundreds of hours. In theory, I should be able to charge at least a few hours’ worth of value for this product. If the developer’s time is valued at $100/hour, a $200 price for a product that saves you $2000 worth of time seems very justifiable. Not only do you get to use it once, but you can re-use the product for ALL future projects and employment.

Now, remove the price and see what people pay. Absolutely nothing. You may have a few people who pay $200 voluntarily, but it’s highly unlikely The vast majority will pay nothing, and some may “tip” in the 5-$60 range. Anything that approaches a $100 mark is seen as a purchase. Hey, I don’t make the rules, I just see what other founders have figured out long ago and combine with my own observations. Don’t kill the messenger.

Free is Expensive

If I am accurate in my assessment and recall my personal experiences accurately, then the majority of people who consume your value will do so for free. When that content is a product, you may end up spending a lot of time on supporting the thing that is not generating any revenue. You don’t want to be rude and ignore people so you’ll probably spend your valuable time answering questions and helping them troubleshoot issues. All of that time adds up. Startup founders who offer free tiers or near free tiers of services learn very quickly that free customers are the most painful and demanding. You are basically forced to charge just to avoid dealing with demanding people who expect everything for nothing.

Free is Noise

Price is not just a request for value, but it acts as a feedback signal for future content. If you have no idea what people are paying for, it’s difficult to know if what you create is worth anything. A situation where the vast majority of your content is consumed for free yield a lot of noise.

Well, why not focus on the people who pay? You certainly could, but it ends up being a tiny fraction of the sample size you could have had if you actually charged something up front.

Lack of forecasting

Businesses rely on predictible revenue. Forecasting is necessary for all sorts of decisions if you work with anyone but yourself. It helps with purchasing decision (expenses) and with planning of future products. Value for value makes it impossible to know what your revenue will be next month as you just have no idea if everyone pays nothing or a lot.

V4V could make you uncompetitive

In a model where one person charges a fixed price and the other is relying on the good will of the people to "see the value" in their work, the person with predictible revenue will most likely win out in a competitive environment - enabling them to get ahead of you and your business. They will have an easier time planning further content / products and hiring people to scale the business even further.

It’s not all hopeless

That’s not to say that I don’t like the idea of value for value. Of course I only want people to pay if they find the thing useful. The issue is that people may not know the thing is useful until they’ve already acquired it. At that point who is going back to pay for the thing they already got for free? Few to none.

Value for value may work. For some.

I’m not saying value for value doesn’t work sometimes, for some people. It is entirely possible that a person earns a living on v4v transactions. However, I think for that to be true there may be other factors at play such as social standing, personal brand, influence, likability, status within a community. The vast majority of creators do not fall into this category and will just struggle.

I’m cautiously optimistic about V4V and hope it works out at scale. But as it stands, I have not seen much evidence that it actually pays the bills. Yes, there has been some support for podcasts on Fountain, but it is unclear whether it is just as or more significant than traditional transaction model.

“Information is not scarce” is irrelevant

There’s some notion that information yearns to be free and cannot be scarce by nature. I think this may be a false argument from the start. When we purchase digital things, we are not paying for scarcity - it’s totally irrelevant. We pay for the experience and the feeling we get from that thing. In fact, the same is probably true for physical products (with the added benefit of personal sustenance). I don’t go into the grocery store to buy a dinner and fork over the money because it’s scarce. I pay because I’m hungry. There’s utility and there’s pleasure and fulfillment. If I’m having a dinner with friends, there’s also fun. Unless I am totally misunderstanding the argument, I’m not sure how it applies.

In Summary

• Value 4 value may work at scale, but remains to be seen
• It could be great fun money but not serious enough to pay the bills (for most of us)
• Sounds good on paper but we humans have our own ways of thinking about value and what it's worth
• May work well for people who build a personal brand or have status in a community

As always I look forward to your thoughts. Let me know if I’m overlooking something or should consider some point of view in more depth.

@ 3bf0c63f:aefa459d

Lightning and its fake HTLCs

Lightning is terrible but can be very good with two tweaks.

How Lightning would work without HTLCs

In a world in which HTLCs didn't exist, Lightning channels would consist only of balances. Each commitment transaction would have two outputs: one for peer A, the other for peer B, according to the current state of the channel.

When a payment was being attempted to go through the channel, peers would just trust each other to update the state when necessary. For example:

1. Channel AB's balances are A[10:10]B (in sats);
2. A sends a 3sat payment through B to C;
3. A asks B to route the payment. Channel AB doesn't change at all;
4. B sends the payment to C, C accepts it;
5. Channel BC changes from B[20:5]C to B[17:8]C;
6. B notifies A the payment was successful, A acknowledges that;
7. Channel AB changes from A[10:10]B to A[7:13]B.

This in the case of a success, everything is fine, no glitches, no dishonesty.

But notice that A could have refused to acknowledge that the payment went through, either because of a bug, or because it went offline forever, or because it is malicious. Then the channel AB would stay as A[10:10]B and B would have lost 3 satoshis.

How Lightning would work with HTLCs

HTLCs are introduced to remedy that situation. Now instead of commitment transactions having always only two outputs, one to each peer, now they can have HTLC outputs too. These HTLC outputs could go to either side dependending on the circumstance.

Specifically, the peer that is sending the payment can redeem the HTLC after a number of blocks have passed. The peer that is receiving the payment can redeem the HTLC if they are able to provide the preimage to the hash specified in the HTLC.

Now the flow is something like this:

1. Channel AB's balances are A[10:10]B;
2. A sends a 3sat payment through B to C:
3. A asks B to route the payment. Their channel changes to A[7:3:10]B (the middle number is the HTLC).
4. B offers a payment to C. Their channel changes from B[20:5]C to B[17:3:5]C.
5. C tells B the preimage for that HTLC. Their channel changes from B[17:3:5]C to B[17:8]C.
6. B tells A the preimage for that HTLC. Their channel changes from A[7:3:10]B to A[7:13]B.

Now if A wants to trick B and stop responding B doesn't lose money, because B knows the preimage, B just needs to publish the commitment transaction A[7:3:10]B, which gives him 10sat and then redeem the HTLC using the preimage he got from C, which gives him 3 sats more. B is fine now.

In the same way, if B stops responding for any reason, A won't lose the money it put in that HTLC, it can publish the commitment transaction, get 7 back, then redeem the HTLC after the certain number of blocks have passed and get the other 3 sats back.

How Lightning doesn't really work

The example above about how the HTLCs work is very elegant but has a fatal flaw on it: transaction fees. Each new HTLC added increases the size of the commitment transaction and it requires yet another transaction to be redeemed. If we consider fees of 10000 satoshis that means any HTLC below that is as if it didn't existed because we can't ever redeem it anyway. In fact the Lightning protocol explicitly dictates that if HTLC output amounts are below the fee necessary to redeem them they shouldn't be created.

What happens in these cases then? Nothing, the amounts that should be in HTLCs are moved to the commitment transaction miner fee instead.

So considering a transaction fee of 10000sat for these HTLCs if one is sending Lightning payments below 10000sat that means they operate according to the unsafe protocol described in the first section above.

It is actually worse, because consider what happens in the case a channel in the middle of a route has a glitch or one of the peers is unresponsive. The other node, thinking they are operating in the trustless protocol, will proceed to publish the commitment transaction, i.e. close the channel, so they can redeem the HTLC -- only then they find out they are actually in the unsafe protocol realm and there is no HTLC to be redeemed at all and they lose not only the money, but also the channel (which costed a lot of money to open and close, in overall transaction fees).

One of the biggest features of the trustless protocol are the payment proofs. Every payment is identified by a hash and whenever the payee releases the preimage relative to that hash that means the payment was complete. The incentives are in place so all nodes in the path pass the preimage back until it reaches the payer, which can then use it as the proof he has sent the payment and the payee has received it. This feature is also lost in the unsafe protocol: if a glitch happens or someone goes offline on the preimage's way back then there is no way the preimage will reach the payer because no HTLCs are published and redeemed on the chain. The payee may have received the money but the payer will not know -- but the payee will lose the money sent anyway.

The end of HTLCs

So considering the points above you may be sad because in some cases Lightning doesn't use these magic HTLCs that give meaning to it all. But the fact is that no matter what anyone thinks, HTLCs are destined to be used less and less as time passes.

The fact that over time Bitcoin transaction fees tend to rise, and also the fact that multipart payment (MPP) are increasedly being used on Lightning for good, we can expect that soon no HTLC will ever be big enough to be actually worth redeeming and we will be at a point in which not a single HTLC is real and they're all fake.

Another thing to note is that the current unsafe protocol kicks out whenever the HTLC amount is below the Bitcoin transaction fee would be to redeem it, but this is not a reasonable algorithm. It is not reasonable to lose a channel and then pay 10000sat in fees to redeem a 10001sat HTLC. At which point does it become reasonable to do it? Probably in an amount many times above that, so it would be reasonable to even increase the threshold above which real HTLCs are made -- thus making their existence more and more rare.

These are good things, because we don't actually need HTLCs to make a functional Lightning Network.

We must embrace the unsafe protocol and make it better

So the unsafe protocol is not necessarily very bad, but the way it is being done now is, because it suffers from two big problems:

1. Channels are lost all the time for no reason;
2. No guarantees of the proof-of-payment ever reaching the payer exist.

The first problem we fix by just stopping the current practice of closing channels when there are no real HTLCs in them.

That, however, creates a new problem -- or actually it exarcebates the second: now that we're not closing channels, what do we do with the expired payments in them? These payments should have either been canceled or fulfilled before some block x, now we're in block x+1, our peer has returned from its offline period and one of us will have to lose the money from that payment.

That's fine because it's only 3sat and it's better to just lose 3sat than to lose both the 3sat and the channel anyway, so either one would be happy to eat the loss. Maybe we'll even split it 50/50! No, that doesn't work, because it creates an attack vector with peers becoming unresponsive on purpose on one side of the route and actually failing/fulfilling the payment on the other side and making a profit with that.

So we actually need to know who is to blame on these payments, even if we are not going to act on that imediatelly: we need some kind of arbiter that both peers can trust, such that if one peer is trying to send the preimage or the cancellation to the other and the other is unresponsive, when the unresponsive peer comes back, the arbiter can tell them they are to blame, so they can willfully eat the loss and the channel can continue. Both peers are happy this way.

If the unresponsive peer doesn't accept what the arbiter says then the peer that was operating correctly can assume the unresponsive peer is malicious and close the channel, and then blacklist it and never again open a channel with a peer they know is malicious.

Again, the differences between this scheme and the current Lightning Network are that:

a. In the current Lightning we always close channels, in this scheme we only close channels in case someone is malicious or in other worst case scenarios (the arbiter is unresponsive, for example). b. In the current Lightning we close the channels without having any clue on who is to blame for that, then we just proceed to reopen a channel with that same peer even in the case they were actively trying to harm us before.

What is missing? An arbiter.

The Bitcoin blockchain is the ideal arbiter, it works in the best possible way if we follow the trustless protocol, but as we've seen we can't use the Bitcoin blockchain because it is expensive.

Therefore we need a new arbiter. That is the hard part, but not unsolvable. Notice that we don't need an absolutely perfect arbiter, anything is better than nothing, really, even an unreliable arbiter that is offline half of the day is better than what we have today, or an arbiter that lies, an arbiter that charges some satoshis for each resolution, anything.

Here are some suggestions:

• random nodes from the network selected by an algorithm that both peers agree to, so they can't cheat by selecting themselves. The only thing these nodes have to do is to store data from one peer, try to retransmit it to the other peer and record the results for some time.
• a set of nodes preselected by the two peers when the channel is being opened -- same as above, but with more handpicked-trust involved.
• some third-party cloud storage or notification provider with guarantees of having open data in it and some public log-keeping, like Twitter, GitHub or a Nostr relay;
• peers that get paid to do the job, selected by the fact that they own some token (I know this is stepping too close to the shitcoin territory, but could be an idea) issued in a Spacechain;
• a Spacechain itself, serving only as the storage for a bunch of OP_RETURNs that are published and tracked by these Lightning peers whenever there is an issue (this looks wrong, but could work).

Key points

1. Lightning with HTLC-based routing was a cool idea, but it wasn't ever really feasible.
2. HTLCs are going to be abandoned and that's the natural course of things.
3. It is actually good that HTLCs are being abandoned, but
4. We must change the protocol to account for the existence of fake HTLCs and thus make the bulk of the Lightning Network usage viable again.

See also

• Ripple and the problem of the decentralized commit
• The Lightning Network solves the problem of the decentralized commit

@ 3f770d65:7a745b24

Habla is a new blogging platform that's based on Nostr. Or as various Nostr client developers like to call it:

"A way to get Derek Ross to stop sending walls of text".

You can edit posts, which is very nice.

@ bcea2b98:7ccef3c9

Channel Influence Efficiency (CIE) in the Lightning Network

Introduction

The Lightning Network's topology and connectivity impact its performance. While metrics like channel count and node centrality offer insights, they miss a key aspect: the efficiency of influence exerted by nodes. Channel Influence Efficiency (CIE) fills this gap by evaluating how effectively a node utilizes its channels to contribute to the network's connectivity.

Methodology

1. CIE Calculation: For a node, CIE is calculated as the ratio of its percentage share in network connectivity to its total number of channels. Mathematically, CIE = (Node's Connectivity %) / (Number of Channels).

2. Data Collection: Data on node connectivity and channel count can be sourced from Lightning Network explorers or APIs.

3. Analysis Framework: CIE is analyzed across various tiers of nodes (top 1, top 100, top 1000) to understand distribution patterns.

Network Connectivity (NC) Calculation Formula

NC = λ × (L × U × Q × C × R × N)

Where: - NC = Network Connectivity. - λ = Normalization factor to scale the result within a meaningful range. - L = Liquidity Score, representing the total liquidity available in the node's channels. - U = Uptime Score, reflecting the reliability of the node (e.g., a percentage of time the node is online). - Q = Quality of Connections Score, indicating the strategic importance of the node's connections (e.g., connections to key nodes). - C = Channel Capacity Score, measuring the total capacity of the node's channels. - R = Routing Efficiency Score, denoting the node's efficiency in routing transactions (considering factors like latency and path optimality). - N = Network Centrality Score, indicating the node's centrality within the network structure.

Utilizing the data from 1ML's Lightning Network statistics, we can calculate an example of network connectivity for a hypothetical node using the proposed formula. For simplicity, we'll assume each factor (liquidity score, uptime score, etc.) is represented on a scale of 0 to 1.

Given Data from 1ML: - Network Capacity: 5,368.61 BTC - Average Node Capacity: 0.367 BTC - Average Channel Capacity: 0.086 BTC - Average Node Age: 830.8 days - Average Channel Age: 454.8 days - Average Channels per Node: 8.52 - Tor Onion Service Nodes: 10,550 nodes - Median Base Fee: 0.632160 sat - Median Fee Rate: 0.000050 sat/sat

Example Calculations

Hypothetical Node 1 Data:

• Liquidity Score (L): Assuming our node's capacity is at 75th percentile, L = 0.75.
• Uptime Score (U): Assuming an uptime of 95%, U = 0.95.
• Quality of Connections Score (Q): If our node is connected to key nodes, Q = 0.8.
• Channel Capacity Score (C): Assuming channel capacity at 75th percentile, C = 0.75.
• Routing Efficiency Score (R): Assuming high routing efficiency, R = 0.9.
• Network Centrality Score (N): If the node is moderately central, N = 0.6.

Network Connectivity (NC) Calculation:

Assuming a normalization factor λ = 1, the NC for our hypothetical node would be: NC = 1 × (0.75 × 0.95 × 0.8 × 0.75 × 0.9 × 0.6) NC = 0.22815

This calculated value (0.22815) represents the node's overall connectivity in the network, taking into account various factors like liquidity, uptime, and efficiency. A higher value would indicate a more influential and well-connected node in the network.

For another example, let's calculate the network connectivity for a different type of node in the Lightning Network, perhaps one that is newer or less central:

Hypothetical Node 2 Data:

• Liquidity Score (L): For a newer node with lower capacity, L = 0.25.
• Uptime Score (U): If this node has good reliability, but not perfect: U = 0.85.
• Quality of Connections Score (Q): With less strategic connections, Q = 0.5.
• Channel Capacity Score (C): Assuming it's around the 25th percentile: C = 0.25.
• Routing Efficiency Score (R): For a moderately efficient node: R = 0.7.
• Network Centrality Score (N): As a less central node: N = 0.4.

Network Connectivity (NC) Calculation:

Using the same normalization factor λ = 1, the NC for this hypothetical node would be: NC = 1 × (0.25 × 0.85 × 0.5 × 0.25 × 0.7 × 0.4) NC = 0.014875

This calculated value (0.014875) indicates a relatively lower overall connectivity for this node, reflective of its newer status, lower capacity, and less central position in the network. This node might focus on improving its strategic connections and increasing its capacity to enhance its role in the network.

Example

1. Strategic Connector (Node A)
2. Math: 50 channels, 5% network connectivity.
3. CIE Calculation: 5% / 50 = 0.1% per channel.

4. Interpretation: Exhibits high efficiency in network influence relative to its channel count, indicating strategic channel connections and a pivotal role in network transactions.

5. Broad Networker (Node B)

6. Math: 100 channels, 5% network connectivity.
7. CIE Calculation: 5% / 100 = 0.05% per channel.

8. Interpretation: Maintains many channels but is less efficient in leveraging them, indicating a wider reach but less strategic placement.

9. Efficient Hub (Node C)

10. Math: 20 channels, 10% network connectivity.
11. CIE Calculation: 10% / 20 = 0.5% per channel.

12. Interpretation: Demonstrates exceptional efficiency, likely connected to key network hubs.

13. Sparse Influencer (Node D)

14. Math: 200 channels, 1% network connectivity.
15. CIE Calculation: 1% / 200 = 0.005% per channel.

16. Interpretation: Has many connections but limited influence, possibly indicating ineffective channels.

17. Average Intermediary (Node E)

18. Math: 100 channels, 2% network connectivity.
19. CIE Calculation: 2% / 100 = 0.02% per channel.

20. Interpretation: Represents an average efficiency level, maintaining a balance in channel count and connectivity impact.

21. Dense Networker (Node F)

22. Math: 300 channels, 15% network connectivity.
23. CIE Calculation: 15% / 300 = 0.05% per channel.

24. Interpretation: Despite a high channel count, the node's influence per channel is moderate, suggesting potential for optimizing its network position.

25. Minor Player (Node G)

26. Math: 10 channels, 0.2% network connectivity.
27. CIE Calculation: 0.2% / 10 = 0.02% per channel.

28. Interpretation: With a low channel count and influence, this node reflects smaller or newer entities in the network.

29. Strategic Influencer (Node H)

30. Math: 50 channels, 20% network connectivity.
31. CIE Calculation: 20% / 50 = 0.4% per channel.
32. Interpretation: Shows high strategic connectivity, indicating fewer but highly effective connections to major nodes.

Interpretation:

1. Strategic Connector (Node A)

2. With a CIE of 0.1% per channel, Node A demonstrates high efficiency in network influence relative to its channel count. This suggests that Node A has strategically established channels, making it a pivotal connector in the network's transaction flow.

3. Broad Networker (Node B)

4. Node B, with a CIE of 0.05% per channel, maintains a larger number of channels but doesn't leverage them as effectively as a Strategic Connector. This indicates a broad but less strategic network reach, suggesting potential for optimization.

5. Efficient Hub (Node C)

6. The high CIE of 0.5% per channel for Node C indicates exceptional efficiency, likely due to connections with key network hubs. This node serves as a central hub for transactions, demonstrating the importance of strategic channel placement.

7. Sparse Influencer (Node D)

8. Node D, with a CIE of 0.005% per channel, represents a node with many connections but limited influence. This could indicate a spread of redundant or less effective channels, highlighting the need for more strategic connectivity.

9. Average Intermediary (Node E)

10. With a CIE of 0.02% per channel, Node E strikes a balance between channel count and influence. This reflects an average level of efficiency, serving as a reliable intermediary in the network.

11. Dense Networker (Node F)

12. Node F, having a CIE of 0.05% per channel, suggests a high number of channels but only moderate influence per channel. This points to the potential for better optimizing its network position to maximize influence.

13. Minor Player (Node G)

14. The CIE of 0.02% per channel for Node G indicates a node with limited influence and a low channel count. This type of node often represents smaller or newer players in the network.

15. Strategic Influencer (Node H)

16. Node H, with a CIE of 0.4% per channel, demonstrates a highly strategic use of connectivity. With fewer but highly effective connections, this node is likely linked to several major nodes, enhancing its role in network efficiency.

Findings and Discussion

The examination of Channel Influence Efficiency (CIE) across various nodes in the Lightning Network, now categorized with specific roles, yields several key findings and opens up new avenues for discussion:

1. Strategic Placement and Efficiency

2. Nodes like the Strategic Connector (Node A) and the Strategic Influencer (Node H) highlight the importance of not just the quantity, but the quality of connections. Their high CIE values suggest that strategic placement of channels can significantly enhance a node's influence in the network.

3. The Role of Broad and Dense Networkers

4. Broad Networkers (Node B) and Dense Networkers (Node F), despite their extensive channel networks, exhibit moderate CIE values. This suggests that an overemphasis on expanding channel count without strategic planning may not always translate into increased network influence.

5. Average Intermediaries as Network Stabilizers

6. Average Intermediaries (Node E) demonstrate a balance in channel count and influence. These nodes potentially contribute to the stability and resilience of the network by maintaining a consistent level of connectivity.

7. Identifying and Supporting Minor Players

8. The Minor Player (Node G) category, with its lower CIE, draws attention to smaller or emerging nodes in the network. Understanding their challenges and potential can guide strategies to support their growth and integration into the network.

9. Potential for Optimization

10. The variance in CIE among different nodes suggests room for optimization. Nodes can look towards the strategies employed by those with higher CIE values to improve their own connectivity and influence.

11. Risk Assessment and Management

12. Sparse Influencers (Node D) with many connections but limited influence may present risks, such as bottlenecks or points of failure. Assessing nodes for their CIE can aid in identifying and mitigating these risks.

13. Network Evolution and Adaptation

14. Tracking changes in CIE over time can provide insights into how the Lightning Network evolves. Shifts in the CIE of various nodes could indicate emerging trends, adaptation strategies, or evolving challenges within the network.

Future Work

The introduction of Channel Influence Efficiency (CIE) and the categorization of nodes into roles like Strategic Connectors and Efficient Hubs open several avenues for future research and development in the Lightning Network. The following areas represent key opportunities for further exploration:

1. Development of Real-Time CIE Tracking Tools

2. Creating tools that provide real-time analysis of CIE for nodes in the Lightning Network can offer ongoing insights into network dynamics and efficiency. These tools could be invaluable for nodes in optimizing their connections and assessing their network influence.

3. Impact of CIE on Network Scalability

4. Studying how variations in CIE affect the scalability and robustness of the Lightning Network can provide insights into how the network can grow while maintaining efficiency and stability.

5. Strategies for Enhancing CIE of Nodes

6. Research into strategies that nodes can employ to improve their CIE, especially for those categorized as Sparse Influencers or Minor Players, would be valuable. This could include analysis of optimal channel formation, network positioning, and connection strategies.

7. CIE's Role in Predictive Modeling

8. Utilizing CIE in predictive modeling to forecast network changes, potential bottlenecks, or points of failure could enhance proactive network management and strategic planning.

9. CIE Influence on Transaction Routing Algorithms

10. Exploring how CIE can be integrated into transaction routing algorithms to optimize efficiency and reduce transaction costs could be a significant advancement.

11. CIE-Based Network Health Indicators

12. Developing network health indicators based on CIE distributions can offer a quick and effective way to assess the overall state and performance of the Lightning Network.

@ 3bf0c63f:aefa459d

Channels without HTLCs

HTLCs below the dust limit are not possible, because they're uneconomical.

So currently whenever a payment below the dust limit is to be made Lightning peers adjust their commitment transactions to pay that amount as fees in case the channel is closed. That's a form of reserving that amount and incentivizing peers to resolve the payment, either successfully (in case it goes to the receiving node's balance) or not (it then goes back to the sender's balance).

SOLUTION

I didn't think too much about if it is possible to do what I think can be done in the current implementation on Lightning channels, but in the context of Eltoo it seems possible.

Eltoo channels have UPDATE transactions that can be published to the blockchain and SETTLEMENT transactions that spend them (after a relative time) to each peer. The barebones script for UPDATE transactions is something like (copied from the paper, because I don't understand these things):

OP_IF # to spend from a settlement transaction (presigned) 10 OP_CSV 2 As,i Bs,i 2 OP_CHECKMULTISIGVERIFY OP_ELSE # to spend from a future update transaction <Si+1> OP_CHECKLOCKTIMEVERIFY 2 Au Bu 2 OP_CHECKMULTISIGVERIFY OP_ENDIF

During a payment of 1 satoshi it could be updated to something like (I'll probably get this thing completely wrong):

OP_HASH256 <payment_hash> OP_EQUAL OP_IF # for B to spend from settlement transaction 1 in case the payment went through # and they have a preimage 10 OP_CSV 2 As,i1 Bs,i1 2 OP_CHECKMULTISIGVERIFY OP_ELSE OP_IF # for A to spend from settlement transaction 2 in case the payment didn't went through # and the other peer is uncooperative <now + 1day> OP_CHECKLOCKTIMEVERIFY 2 As,i2 Bs,i2 2 OP_CHECKMULTISIGVERIFY OP_ELSE # to spend from a future update transaction <Si+1> OP_CHECKLOCKTIMEVERIFY 2 Au Bu 2 OP_CHECKMULTISIGVERIFY OP_ENDIF OP_ENDIF

Then peers would have two presigned SETTLEMENT transactions, 1 and 2 (with different signature pairs, as badly shown in the script). On SETTLEMENT 1, funds are, say, 999sat for A and 1001sat for B, while on SETTLEMENT 2 funds are 1000sat for A and 1000sat for B.

As soon as B gets the preimage from the next peer in the route it can give it to A and them can sign a new UPDATE transaction that replaces the above gimmick with something simpler without hashes involved.

If the preimage doesn't come in viable time, peers can agree to make a new UPDATE transaction anyway. Otherwise A will have to close the channel, which may be bad, but B wasn't a good peer anyway.

@ 3bf0c63f:aefa459d

There's a problem with using Git concepts for everything

We've been seeing a surge in applications that use Git to store other things than code, or that are based on Git concepts and so enable "forking, merging and distributed collaboration" for things like blogs, recipes, literature, music composition, normal files in a filesystem, databases.

The problem with all this is they will either:

1. assume the user will commit manually and expect that commit to be composed by a set of meaningful changes, and the commiter will also add a message to the commit, describing that set of meaningful, related changes; or
2. try to make the committing process automatic and hide it from the user, so will producing meaningless commits, based on random changes in many different files (it's not "files" if we are talking about a recipe or rows in a table, but let's say "files" for the sake of clarity) that will probably not be related and not reduceable to a meaningful commit message, or maybe the commit will contain only the changes to a single file, and its commit message would be equivalent to "updated <name of the file>".

Programmers, when using Git, think in Git, i.e., they work with version control in their minds. They try hard to commit together only sets of meaningful and related changes, even when they happen to make unrelated changes in the meantime, and that's why there are commands like git add -p and many others.

Normal people, to whom many of these git-based tools are intended to (and even programmers when out of their code-world), are much less prone to think in Git, and that's why another kind of abstraction for fork-merge-collaborate in non-code environments must be used.

@ 8fb140b4:f948000c

Embarking on the journey of operating your own Lightning node on the Bitcoin Layer 2 network is more than just a tech-savvy endeavor; it's a step into a realm of financial autonomy and cutting-edge innovation. By running a node, you become a vital part of a revolutionary movement that's reshaping how we think about money and digital transactions. This role not only offers a unique perspective on blockchain technology but also places you at the heart of a community dedicated to decentralization and network resilience. Beyond the technicalities, it's about embracing a new era of digital finance, where you contribute directly to the network's security, efficiency, and growth, all while gaining personal satisfaction and potentially lucrative rewards.

In essence, running your own Lightning node is a powerful way to engage with the forefront of blockchain technology, assert financial independence, and contribute to a more decentralized and efficient Bitcoin network. It's an adventure that offers both personal and communal benefits, from gaining in-depth tech knowledge to earning a place in the evolving landscape of cryptocurrency.

Running your own Lightning node for the Bitcoin Layer 2 network can be an empowering and beneficial endeavor. Here are 10 reasons why you might consider taking on this task:

1. Direct Contribution to Decentralization: Operating a node is a direct action towards decentralizing the Bitcoin network, crucial for its security and resistance to control or censorship by any single entity.

2. Financial Autonomy: Owning a node gives you complete control over your financial transactions on the network, free from reliance on third-party services, which can be subject to fees, restrictions, or outages.

3. Advanced Network Participation: As a node operator, you're not just a passive participant but an active player in shaping the network, influencing its efficiency and scalability through direct involvement.

4. Potential for Higher Revenue: With strategic management and optimal channel funding, your node can become a preferred route for transactions, potentially increasing the routing fees you can earn.

5. Cutting-Edge Technological Engagement: Running a node puts you at the forefront of blockchain and bitcoin technology, offering insights into future developments and innovations.

6. Strengthened Network Security: Each new node adds to the robustness of the Bitcoin network, making it more resilient against attacks and failures, thus contributing to the overall security of the ecosystem.

7. Personalized Fee Structures: You have the flexibility to set your own fee policies, which can balance earning potential with the service you provide to the network.

8. Empowerment Through Knowledge: The process of setting up and managing a node provides deep learning opportunities, empowering you with knowledge that can be applied in various areas of blockchain and fintech.

9. Boosting Transaction Capacity: By running a node, you help to increase the overall capacity of the Lightning Network, enabling more transactions to be processed quickly and at lower costs.

10. Community Leadership and Reputation: As an active node operator, you gain recognition within the Bitcoin community, which can lead to collaborative opportunities and a position of thought leadership in the space.

These reasons demonstrate the impactful and transformative nature of running a Lightning node, appealing to those who are deeply invested in the principles of bitcoin and wish to actively shape its future. Jump aboard, and embrace the journey toward full independence. 🐶🐾🫡🚀🚀🚀

@ 3bf0c63f:aefa459d

comentário pertinente de Olavo de Carvalho sobre atribuições indevidas de acontecimentos à "ordem espontânea"

Eis aqui um exemplo entre outros mil, extraído das minhas apostilas de aulas, de como se analisam as relações entre fatores deliberados e casuais na ação histórica. O sr, Beltrão está INFINITAMENTE ABAIXO da possibilidade de discutir essas coisas, e por isso mesmo me atribui uma simploriedade que é dele próprio e não minha:

Já citei mil vezes este parágrafo de Georg Jellinek e vou citá-lo de novo: “Os fenômenos da vida social dividem-se em duas classes: aqueles que são determinados essencialmente por uma vontade diretriz e aqueles que existem ou podem existir sem uma organização devida a atos de vontade. Os primeiros estão submetidos necessariamente a um plano, a uma ordem emanada de uma vontade consciente, em oposição aos segundos, cuja ordenação repousa em forças bem diferentes.”

Essa distinção é crucial para os historiadores e os analistas estratégicos não porque ela é clara em todos os casos, mas precisamente porque não o é. O erro mais comum nessa ordem de estudos reside em atribuir a uma intenção consciente aquilo que resulta de uma descontrolada e às vezes incontrolável combinação de forças, ou, inversamente, em não conseguir enxergar, por trás de uma constelação aparentemente fortuita de circunstâncias, a inteligência que planejou e dirigiu sutilmente o curso dos acontecimentos.

Exemplo do primeiro erro são os Protocolos dos Sábios de Sião, que enxergam por trás de praticamente tudo o que acontece de mau no mundo a premeditação maligna de um número reduzidos de pessoas, uma elite judaica reunida secretamente em algum lugar incerto e não sabido.

O que torna essa fantasia especialmente convincente, decorrido algum tempo da sua publicação, é que alguns dos acontecimentos ali previstos se realizam bem diante dos nossos olhos. O leitor apressado vê nisso uma confirmação, saltando imprudentemente da observação do fato à imputação da autoria. Sim, algumas das idéias anunciadas nos Protocolos foram realizadas, mas não por uma elite distintamente judaica nem muito menos em proveito dos judeus, cuja papel na maioria dos casos consistiu eminentemente em pagar o pato. Muitos grupos ricos e poderosos têm ambições de dominação global e, uma vez publicado o livro, que em certos trechos tem lances de autêntica genialidade estratégica de tipo maquiavélico, era praticamente impossível que nada aprendessem com ele e não tentassem por em prática alguns dos seus esquemas, com a vantagem adicional de que estes já vinham com um bode expiatório pré-fabricado. Também é impossível que no meio ou no topo desses grupos não exista nenhum judeu de origem. Basta portanto um pouquinho de seletividade deformante para trocar a causa pelo efeito e o inocente pelo culpado.

Mas o erro mais comum hoje em dia não é esse. É o contrário: é a recusa obstinada de enxergar alguma premeditação, alguma autoria, mesmo por trás de acontecimentos notavelmente convergentes que, sem isso, teriam de ser explicados pela forca mágica das coincidências, pela ação de anjos e demônios, pela "mão invisível" das forças de mercado ou por hipotéticas “leis da História” ou “constantes sociológicas” jamais provadas, que na imaginação do observador dirigem tudo anonimamente e sem intervenção humana.

As causas geradoras desse erro são, grosso modo:

Primeira: Reduzir as ações humanas a efeitos de forças impessoais e anônimas requer o uso de conceitos genéricos abstratos que dão automaticamente a esse tipo de abordagem a aparência de coisa muito científica. Muito mais científica, para o observador leigo, do que a paciente e meticulosa reconstituição histórica das cadeias de fatos que, sob um véu de confusão, remontam às vezes a uma autoria inicial discreta e quase imperceptível. Como o estudo dos fenômenos histórico-políticos é cada vez mais uma ocupação acadêmica cujo sucesso depende de verbas, patrocínios, respaldo na mídia popular e boas relações com o establishment, é quase inevitável que, diante de uma questão dessa ordem, poucos resistam à tentação de matar logo o problema com duas ou três generalizações elegantes e brilhar como sábios de ocasião em vez de dar-se o trabalho de rastreamentos históricos que podem exigir décadas de pesquisa.

Segunda: Qualquer grupo ou entidade que se aventure a ações histórico-políticas de longo prazo tem de possuir não só os meios de empreendê-las, mas também, necessariamente, os meios de controlar a sua repercussão pública, acentuando o que lhe convém e encobrindo o que possa abortar os resultados pretendidos. Isso implica intervenções vastas, profundas e duradouras no ambiente mental. [Etc. etc. etc.]

(no facebook em 17 de julho de 2013)

@ 3bf0c63f:aefa459d

Custom spreadsheets

The idea was to use it to make an app that would serve as custom database for everything and interact with the spreadsheet so people could play and calculate with their values after they were created by the custom app, something like an MS Access integrated with Excel?

My first attempt that worked (I believe there was an attempt before but I have probably deleted it from everywhere) was this react-microspreadsheet thing (at the time called react-spreadsheet before I donated the npm name to someone who asked):

• https://github.com/fiatjaf/react-microspreadsheet

This was a very good spreadsheet component that did many things current "react spreadsheet" components out there don't do. It had formulas; support for that handle thing that you pulled with the mouse and it autofilled cells with a pattern; it had keyboard navigation with Ctrl, Shift, Ctrl+Shift; it had that thing through which you copy-pasted formulas and they would change their parameters depending on where you pasted them (implemented in a very poor manner because I was using and thinking about Excel in baby mode at the time).

Then I tried to make it into "a small sheet you can share" kind of app through assemblymade.com, and eventually as I tried to add more things bugs began to appear.

Then there was cycle6-spreadsheet:

• https://github.com/fiatjaf/spreadsheet-cycle6

If I remember well this was very similar to the other one, although made almost 2 years after. Despite having the same initial goal of the other (the multi-app custom database thing) it only yielded:

• Sidesheet, a Chrome extension that opened a spreadsheet on the side of the screen that you could use to make calculations and so on. It worked, but had too many bugs that probably caused me to give up entirely.

I'm not sure which of the two spreadsheets above powers http://sheets.alhur.es.

@ 3bf0c63f:aefa459d

Um algoritmo imbecil da evolução

Suponha que você queira escrever a palavra BANANA partindo de OOOOOO e usando só alterações aleatórias das letras. As alterações se dão por meio da multiplicação da palavra original em várias outras, cada uma com uma mudança diferente.

No primeiro período, surgem BOOOOO e OOOOZO. E então o ambiente decide que todas as palavras que não começam com um B estão eliminadas. Sobra apenas BOOOOO e o algoritmo continua.

É fácil explicar conceber a evolução das espécies acontecendo dessa maneira, se você controlar sempre a parte em que o ambiente decide quem vai sobrar.

Porém, há apenas duas opções:

1. Se o ambiente decidir as coisas de maneira aleatória, a chance de você chegar na palavra correta usando esse método é tão pequena que pode ser considerada nula.
2. Se o ambiente decidir as coisas de maneira pensada, caímos no //design inteligente//.

Acredito que isso seja uma enunciação decente do argumento "no free lunch" aplicado à crítica do darwinismo por William Dembski.

A resposta darwinista consiste em dizer que não existe essa BANANA como objetivo final. Que as palavras podem ir se alterando aleatoriamente, e o que sobrar sobrou, não podemos dizer que um objetivo foi atingido ou deixou de sê-lo. E aí os defensores do design inteligente dirão que o resultado ao qual chegamos não pode ter sido fruto de um processo aleatório. BANANA é qualitativamente diferente de AYZOSO, e aí há várias maneiras de "provar" que sim usando modelos matemáticos e tal.

Fico com a impressão, porém, de que essa coisa só pode ser resolvida como sim ou não mediante uma discussão das premissas, e chega um ponto em que não há mais provas matemáticas possíveis, apenas subjetividade.

Daí eu me lembro da minha humilde solução ao problema do cão que aperta as teclas aleatoriamente de um teclado e escreve as obras completas de Shakespeare: mesmo que ele o faça, nada daquilo terá sentido sem uma inteligência de tipo humano ali para lê-las e perceber que não se trata de uma bagunça, mas sim de um texto com sentido para ele. O milagre se dá não no momento em que o cão tropeça no teclado, mas no momento em que o homem olha para a tela.

Se o algoritmo da evolução chegou à palavra BANANA ou UXJHTR não faz diferença pra ela, mas faz diferença para nós, que temos uma inteligência humana, e estamos observando aquilo. O homem também pensaria que há //algo// por trás daquele evento do cão que digita as obras de Shakespeare, e como seria possível alguém em sã consciência pensar que não?

@ 3bf0c63f:aefa459d

P2P reputation thing

Each node shares a blob of the reputations they have, which includes a confidence number. The number comes from the fact that reputations are inherited from other nodes they trust and averaged by their confidence in these. Everything is mixed for plausible deniability. By default a node only shares their stuff with people they manually add, to prevent government from crawling everybody's database. Also to each added friend nodes share a different identity/pubkey (like giving a new Bitcoin address for every transaction) (derived from hip32) (and since each identity can only be contacted by one other entity the node filters incoming connections to download their database: "this identity already been used? no, yes, used with which peer?").

Network protocol

Maybe the data uploader/offerer initiates connection to the receiver over Tor so there's only a Tor address for incoming data, never an address for a data source, i.e. everybody has an address, but only for requesting data.

How to request? Post an encrypted message in an IRC room or something similar (better if messages are stored for a while) targeted to the node/identity you want to download from, along with your Tor address. Once the node sees that it checks if you can download and contacts you.

The encrypted messages could have the target identity pubkey prefix such that the receiving node could try to decrypt only some if those with some probability of success.

Nodes can choose to share with anyone, share only with pre-approved people, share only with people who know one of their addresses/entities (works like a PIN, you give the address to someone in the street, that person can reach you, to the next person you give another address etc., you can even have a public address and share limited data with that).

Data model

Each entry in a database should be in the following format:

internal_id : real_world_identifier [, real_world_identifier...] : tag

Which means you can either associate one or multiple real world identifier with an internal id and associate the real person designated by these identifiers with a tag. the tag should be part of the standard or maybe negotiated between peers. it can be things like scammer, thief, tax collector etc., or honest, good dentist etc. defining good enough labels may be tricky.

internal_id should be created by the user who made the record about the person.

At first this is not necessary, but additional bloat can be added to the protocol if the federated automated message posting boards are working in the sense that each user can ask for more information about a given id and the author of that record can contact the person asking for information and deliver free text to them with the given information. For this to work the internal id must be a public key and the information delivered must be signed with the correspondent private key, so the receiver of the information will know it's not just some spammer inventing stuff, but actually the person who originated that record.

@ 599f67f7:21fb3ea9

¿Qué es Cashu?

Cashu es un protocolo de Ecash de código abierto para Bitcoin que ofrece transacciones instantáneas de tarifa cero con una privacidad casi perfecta, creado por nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg.

En la siguiente tabla se compara Cashu y Bitcoin on-chain, sacada de la presentación Nuts and Bolts de nostr:npub1cj6ndx5akfazux7f0vjl4fyx9k0ulf682p437fe03a9ndwqjm0tqj886t6 en la Conferencia Bitcoin Bangkok 2023.

| Cashu | Bitcoin (on-chain) | |--|--| | Sin libro mayor | Libro mayor distribuido | | Token al portador | UTXO | | Transacciones ciegas | Transacciones públicas | | Centralizado | Descentralizado | | De confianza | Sin confianza | | Sin registro de tx | Registro de tx |

Como podemos ver, Cashu sacrifica la confianza y la descentralización en favor de la privacidad. Esto tiene mucho sentido cuando se trata de soluciones de custodia, ya que el usuario ya utiliza un servicio centralizado en el que tiene que confiar. Las soluciones de custodia tradicionales tienen una privacidad horrible, ya que ese custodio conoce los fondos que posee un usuario y con quién está transaccionando. Permitiendo ataques y censura a los usuarios. Los registros de los datos también se pueden convertir en un honeypot.

Por el contrario, los mints de Cashu pueden actuar como custodios que no saben quienes son sus usuarios, cuántos fondos tienen ni con quién interactúa. Esta casa de la moneda (mint) solo tiene como único registro una lista de secretos gastados que no son reutilizables y sin forma de asociarlos con los usuarios.

Algunos casos de uso serían vales ya centralizados y custodiados por un tercero; uso para pagar por un recurso como APIs, relays de nostr o mixnets; sistemas integrados que reemplazan el modelo cuenta y saldo; y servicios de intercambio/mezcla para desligar depósitos y retiros.

Historia

Ecash fue concebido por primera vez por David Chaum en 1982 como un protocolo de transmisión de valor electrónico utilizando firmas ciegas. Cashu es una implementación de Ecash que utiliza la variante de David Wagner de Chaumian blinding de 1996 creada por nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg.

Terminología

Para ayudar a comprender como funciona Cashu, vamos a tratar primero alguna terminología esencial.

Mint

Los Mint en Cashu es el custodio de los fondos de los usuarios. Su labor es acuñar y quemar tokens y prevenir el doble gasto.

El mint de Cashu corre un nodo Lightning, por lo que puede enviar y recibir pagos Lightning. Incluyendo el intercambio con otros Mints. Sin embargo, todavía puedes realizar transacciones con tokens ecash, incluso si el nodo Lightning está offline. A diferencia de Lightning, el destinatario tampoco necesita estar en linea para recibirlo. Esta casa de la moneda o mint no sabe quién es el usuario, cuantos fondos tiene ni con quienes está realizando transacciones.

Sin embargo, desde que el mint es el custodio de los fondos de los usuarios, deberías elegir un mint en el que confíes y del que conozcas al operador.

Utiliza montos pequeños o canjea los tokens de inmediato.

Token

Un token cashu es esencialmente un conjunto de datos firmado por el mint. El usuario guarda esos tokens en su billetera. Dado que esos tokens ecash son solo texto, pueden ser enviadas por cualquier protocolo basado en texto. Como nostr, mail, sms, etc.

Cashu utiliza un sistema que se basa en monedas con denominaciones fijas.

La denominación de los billetes fíat son una analogía. Por ejemplo, en el Euro los billetes son de 5, 10, 20, 50, 100…

En Cashu, los tokens están denominados en potencias de 2. Por ejemplo, 1, 2, 4, 8, 16, 32, 64, 128 sats, así sucesivamente.

El objetivo de usar denominaciones es aumentar el anonimato establecido entre los usuarios y hacer que sea aún más difícil para los mints asociar las transacciones con las identidades de los usuarios.

¿Cómo funciona? Explicado como si tuviera 5 años

Alice quiere acuñar nuevos tokens Cashu. Así que se dirige al mint de Bob, y dice: “¡Oye! Quiero acuñar nuevos tokens de Cashu".

Bob responde diciendo: "Vale, págame y envíame un secreto ciego". El secreto ciego significa que Alice conoce el secreto, pero Bob no puede verlo.

Alice genera un secreto y luego lo ciega para que Bob no sepa cuál es el secreto.

Ella le paga a Bob y le envía su comprobante de pago y su secreto ciego.

Cuando Bob está conforme con el pago, firma el secreto ciego de Alice y le devuelve el secreto ciego firmado. Una vez firmado por Bob, en el futuro puede tener la seguridad de que el token es válido.

Alice quiere pagarle a Carol. Ella le envía a Carol su secreto junto con una llave para descifrar el secreto ciego firmado.

Carol quiere canjear su token. Así que ella va a la casa de la moneda, Bob, y le muestra el secreto y la clave que Alice le dio.

Bob nunca ha visto el secreto antes y tampoco sabe que fue Alice quien lo generó, ya que Alice lo ofuscó antes de enviárselo. Pero puede verificar que lo firmó antes, por eso puede tratarlo como un gasto valido del token. Ahora firma un nuevo token para Carol, o le devuelve los sats y añade el secreto a una lista de secretos gastados. Si alguien trata de reclamar con el mismo secreto otra vez, Bob lo rechazará porque es un gasto doble.

¿Cómo sabe el mint (Bob) qué cantidad de sats darle a Carol?

Anteriormente hemos mencionado que los tokens Cashu están denominados en potencias de 2 (1, 2, 4, 8, 16, 32...), algo así como billetes fíat.

Bob, la casa de la moneda, tiene una clave privada distinta que usa para firmar cada denominación. Por ejemplo, tiene una clave privada única para tokens con denominación de 1 sat, otra para los de denominación 2 sats, otra para los de 8 y así sucesivamente…

De esta manera, cuando Carol viene a Bob para canjear tokens, Bob sabe con qué clave privada ha firmado el token antes y, por lo tanto, a qué denominación pertenecen los tokens.

¿Qué pasa con el cambio?

En Cashu no hay cambio. Solo tienes que decirle al mint que destruya los tokens antiguos y que acuñe nuevos tokens del mismo importe exacto.

Para ver esto, digamos que Alice tiene dos tokens que suman 10 sats. Un token de 8 sats y otro de 2 sats.

Ella quiere enviar 9 sats a Carol. Así que va al mint y le dice a Bob que divida su token de 2 sats en dos tokens de 1 sat. Ahora puede enviar 9 sats a Carol en forma de una ficha de 8 sats y una ficha de 1 sat, y guardar la otra ficha de 1 sat para Ella.

Lightning para la interconexion

¿Qué pasa cuando Alice quiere pagarle a David, que no confía en el mint de Bob pero conoce a Erin y usa el mint de Erin?

Alice cambia sus tokens en el mint de Bob, dando instrucciones a Bob para que derrita los tokens o los convierta de nuevo en sats Lightning. El mint de Bob luego envía una transacción Lightning al mint de Erin. El mint de Erin luego acuña nuevos tokens con David utilizando los sats Lightning que acaba de recibir del mint de Bob.

¿Qué es lo siguiente para Cashu?

Ecash programable

Podemos establecer condiciones de gasto al ecash, siendo el mint quien las aplica. Esto puede desbloquear potentes contratos inteligentes sin llegar a la cadena base ni a la red Lightning, que pueden permitir pagos públicos, pagos offline y de alta frecuencia.

Plan de prueba de pasivos para los mints

El llamado Proof of Liabilities de Calle (PoL) en Cashu, se trata de una especie de sistema de auditoria que le dificulta a los custodios atacar a los usuarios mediante la introducción del concepto de epochs (épocas). En este esquema, el mint custodio rota de forma regular el conjunto de claves privadas que utilizan en cada epoch y publica listas auditables de tokens acuñados y quemados en el último epoch. Combinado con un esquema de prueba de reservas en el que las reservas se mantienen en un multifirma on- chain, un custodio deshonesto no puede reducir sus pasivos sin arriesgarse a ser descubierta por los usuarios. Para profundizar sobre este aspecto consulta el artículo completo.

Prueba Cashu

Puedes probar Cashu a través de nostr:naddr1qqxnzdesxqmnxvpexqunzvpcqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqzypve7elhmamff3sr5mgxxms4a0rppkmhmn7504h96pfcdkpplvl2jqcyqqq823cnmhuld y nostr:naddr1qqxnzdesxs6r2dehxvmrqdenqgs9n8m87l0hd9xxqwndqcmwzh4uvyxmwlw0637kuhg98pkcy8ana2grqsqqqa284333an. Únicamente necesitas una cartera Lightning y un teléfono u ordenador.

Referencias

• Cashu.space
• Learn about Cashu
• Cashu en los medios
• Entrevista con calle de nostr:npub1yn3hc8jmpj963h0zw49ullrrkkefn7qxf78mj29u7v2mn3yktuasx3mzt0

Ver también

• Video de nostr:npub1rxysxnjkhrmqd3ey73dp9n5y5yvyzcs64acc9g0k2epcpwwyya4spvhnp8
• Soporte Cashu
• NUTs - Notación, uso y terminología, las especificaciones del protocolo para Cashu
• X-Cashu - HTTP 402: Se requiere pago con Cashu
• Proxnut - Proteger o monetizar los recursos web con el uso de tokens
• Prueba de Pasivos para Cashu
• Fedimint - implementación de ecash federado

@ 8fb140b4:f948000c

Venturing into the dynamic world of bitcoin's layer 2 networks, particularly the lightning network, can seem like an exciting frontier for tech enthusiasts and cryptocurrency aficionados. however, the decision to run your own lightning node is not one to be taken lightly. While the allure of contributing to the bitcoin ecosystem and potentially earning transaction fees is strong, there are significant considerations that should temper the enthusiasm of would-be node operators. From the intricate technicalities to unexpected challenges, here are 10 compelling reasons why running your own lightning node might not be the electrifying experience you anticipated.

Running your own lightning node for the bitcoin layer 2 network can be a complex and demanding task. Here are 10 reasons why you might choose not to:

1. Technical complexity: setting up and managing a lightning node requires a good understanding of blockchain technology and network management, which can be overwhelming for beginners.

2. Security risks: running a node means you're responsible for securing it against potential cyber attacks, which requires constant vigilance and technical expertise.

3. Resource intensive: a lightning node requires continuous internet connection and sufficient hardware resources, which can be costly in terms of electricity and equipment.

4. Liquidity requirements: to facilitate transactions, you need to lock up a significant amount of bitcoin in your channels, which might not be ideal if you prefer liquidity.

5. Maintenance efforts: regular maintenance and updates are necessary to keep the node running smoothly, which can be time-consuming.

6. Limited privacy: operating a node might expose some of your transaction details or ip address, potentially compromising privacy.

7. Slow ROI: the financial return on operating a lightning node can be slow and uncertain, especially if the network fees are low.

8. Network complexity: understanding and managing channel capacities, routing, and fees can be complicated and require continuous learning and adaptation.

9. Scalability issues: as the network grows, managing a node can become increasingly challenging, with more channels and transactions to handle.

10. Downtime risks: if your node goes offline, you might miss out on transaction fees or, worse, risk losing funds in channels due to outdated channel states.

These reasons reflect the challenges and responsibilities that come with running your own lightning node and may discourage some individuals, especially those with limited technical background or resources. If you are still up for a challenge, thank you for supporting the network! 🐶🐾🫡🙏🏻

@ 3bf0c63f:aefa459d

gravity

IPFS is nice as a personal archiving tool (edit: it's not). You store a bunch of data and make it available to the public.

The problem is that no one will ever know you have that data, therefore you need a place to publish it somewhere. Gravity was an attempt of being the tool for this job.

It was a website that showcased the collections from users, and it was also a command-line client that used your IPFS keys for authentication and allowed you to paste IPFS URIs and names and descriptions.

The site was intended to be easy to run so you could have multiple stellar bodies aggregating content and interact with them all in a standardized manner.

It also had an ActivityPub/"fediverse" integration so people could follow Gravity server users from Mastodon and friends and see new data they published as "tweets".

• https://github.com/fiatjaf/gravity

See also

• How IPFS is broken
• litepub

@ 599f67f7:21fb3ea9

Una BoltCard es una tarjeta que contiene una LNURLw grabada. Puedes recargarla con sats y utilizarla como si fuera una tarjeta de crédito en comercios u otros usuarios que aceptan esta tecnología.

Esto es lo que pasa por detrás durante el proceso

¿Qué necesito?

• Una tarjeta NFC NTAG424 DNA
• A continuación dejamos algunos enlaces donde puedes encontrar estas tarjetas, algunos ofrecen diseños personalizados
• Bitcoin Txoko
• NFC cards
• NFC-tag-shop
• Lasereyes
• Un telefono compatible con NFC (durante nuestras pruebas en dispositivos iPhone no funcionó de forma correcta por un problema en la obtención del UID de la tarjeta por parte del navegador)
• Una billetera LNbits

1- Habilita la extension BoltCard

En tu telefono con NFC, dirigete al link de tu billetera LNbits. Dentro de Extensiones busca y habilita Bolt Cards.

2- Crea un nuevo registro de cartera

• Abre la extensión de Bolt Cards y presiona el botón + para crear una nueva tarjeta.
• Selecciona la cartera a la que se conectará. Esta es la cartera desde la que se gastarán los fondos.
• Puede establecer límites para la transacción máxima y el límite diario como medida de protección contra los comerciantes maliciosos que agotan su tarjeta.
• Ponle nombre a tu tarjeta.
• Presiona el botón NFC y luego lleva tu tarjeta NFC a tu teléfono para importar el UID de tu tarjeta.
• Haz clic en crear tarjeta.

Al final debería ser algo parecido a esto pero con un registro UID de tu tarjeta.

3- Escribe el registro NFC en la tarjeta.

• Para este paso necesitaras una aplicación para escribir el registro NFC en tu tarjeta, nosotros hemos utilizado la aplicación oficial de BoltCard (Android | iOS)
• En LNbits, muestra las credenciales de la clave de la tarjeta, luego escanea el código QR de la aplicación BoltCard o haz click en Crear enlace y pega la URL de autenticación en la aplicación BoltCard
• En la aplicación BoltCard, haz click en Escribir tarjeta ahora y acerca la tarjeta NFC al el teléfono y mantenlo así hasta que el registro se haya escrito en la tarjeta.

¡Eso es todo! Si todo salió bien, deberías tener una BoltCard en funcionamiento. Puedes probarla tocando contra tu teléfono y abriendo el enlace LNURLw.

⚠ Llevar tu BoltCard contigo significa que llevas dinero real contigo. Si alguien accede a tu tarjeta puede retirar todos los sats de tu cartera. Toma precauciones y mantén solo una pequeña cantidad de sats en tu billetera BoltCard para el gastos del día a día. Comprueba siempre que el comerciante está solicitando el precio correcto. Si es posible, mantén tu tarjeta en una funda protegida por RFID.

Próximos pasos

BoltCard habilitada para PoS

Algunas carteras y sistemas de punto de venta (PoS) son compatibles con la BoltCard. Aquí dejamos una lista de ellos: - BoltCard PoS - Breez - BTCpayserver - LNbits TPOS - Sí, puedes convertir tu cartera LNbits en un punto de venta (PoS) habilitando la extensión TPOS - VoltPay - lipa - Blink - Wallet of Satoshi - Blixt Wallet

Apoyar a BoltCard

También puedes apoyar el esfuerzo de haber creado una biblioteca de código abierto para programar las tarjetas, puedes hacerlo en Geyser Fund.

Tarjetas regalo NFC

En esta guía hemos tratado cómo crear una tarjeta de débito Lightning, pero ¿que ocurre si quieres hacer un regalo en sats y que pueda hacer un retiro a su billetera cuando quiera? Bueno, eso también es posible mediante tarjetas NFC y LNURLw. Explicaremos este proceso en una futura guía.

¡No solo tarjetas!

También puedes escribir registros NFC en cualquier etiqueta NFC que lo admita. Un ejemplo de esto es el Bolt Ring, que ofrece un anillo con capacidad NFC.

@ 8fb140b4:f948000c

Chef's notes

Serving these two dishes together will create a delightful centerpiece for your Thanksgiving meal, offering a perfect blend of traditional flavors with a homemade touch.

Details

• ⏲️ Prep time: 30 min
• 🍳 Cook time: 1 - 2 hours
• 🍽️ Servings: 4-6

Ingredients

• 1 whole turkey (about 12-14 lbs), thawed and ready to cook
• 1 cup unsalted butter, softened
• 2 tablespoons fresh thyme, chopped
• 2 tablespoons fresh rosemary, chopped
• 2 tablespoons fresh sage, chopped
• Salt and freshly ground black pepper
• 1 onion, quartered
• 1 lemon, halved
• 2-3 cloves of garlic
• Apple and Sage Stuffing
• 1 loaf of crusty bread, cut into cubes
• 2 apples, cored and chopped
• 1 onion, diced
• 2 stalks celery, diced
• 3 cloves garlic, minced
• 1/4 cup fresh sage, chopped
• 1/2 cup unsalted butter
• 2 cups chicken broth
• Salt and pepper, to taste

Directions

1. Preheat the Oven: Set your oven to 325°F (165°C).
2. Prepare the Herb Butter: Mix the softened butter with the chopped thyme, rosemary, and sage. Season with salt and pepper.
3. Prepare the Turkey: Remove any giblets from the turkey and pat it dry. Loosen the skin and spread a generous amount of herb butter under and over the skin.
4. Add Aromatics: Inside the turkey cavity, place the quartered onion, lemon halves, and garlic cloves.
5. Roast: Place the turkey in a roasting pan. Tent with aluminum foil and roast. A general guideline is about 15 minutes per pound, or until the internal temperature reaches 165°F (74°C) at the thickest part of the thigh.
6. Rest and Serve: Let the turkey rest for at least 20 minutes before carving.
7. Next: Apple and Sage Stuffing
8. Dry the Bread: Spread the bread cubes on a baking sheet and let them dry overnight, or toast them in the oven.
9. Cook the Vegetables: In a large skillet, melt the butter and cook the onion, celery, and garlic until soft.
10. Combine Ingredients: Add the apples, sage, and bread cubes to the skillet. Stir in the chicken broth until the mixture is moist. Season with salt and pepper.
11. Bake: Transfer the stuffing to a baking dish and bake at 350°F (175°C) for about 30-40 minutes, until golden brown on top.

@ 3bf0c63f:aefa459d

Gerador de tabelas de todos contra todos

I don't remember exactly when I did this, but I think a friend wanted to do software that would give him money over the internet without having to work. He didn't know how to program. He mentioned this idea he had which was some kind of football championship manager solution, but I heard it like this: a website that generated a round-robin championship table for people to print.

It is actually not obvious to anyone how to do it, it requires an algorithm that people will not reach casually while thinking, and there was no website doing it in Portuguese at the time, so I made this and it worked and it had a couple hundred daily visitors, and it even generated money from Google Ads (not much)!

First it was a Python web app running on Heroku, then Heroku started charging or limiting the amount of free time I could have on their platform, so I migrated it to a static site that ran everything on the client. Since I didn't want to waste my Python code that actually generated the tables I used Brython to run Python on JavaScript, which was an interesting experience.

In hindsight I could have just taken one of the many round-robin JavaScript libraries that exist on NPM, so eventually after a couple of more years I did that.

I also removed Google Ads when Google decided it had so many requirements to send me the money it was impossible, and then the money started to vanished.

• https://github.com/fiatjaf/tabelas.alhur.es
• https://tabelas.alhur.es/

@ 3bf0c63f:aefa459d

TiddlyWiki remoteStorage

TiddlyWiki is very good and useful, but since at this time I used multiple computers during the week, it wouldn't work for me to use it as a single file on my computer, so I had to hack its internal tiddler saving mechanism to instead save the raw data of each tiddler to remoteStorage and load them from that place also (ok, there was in theory a plugin system, but I had to read and understand the entire unformatted core source-code anyway).

There was also a server that fetched tiddlywikis from anyone's remoteStorage buckets (after authorization) and served these to the world, a quick and nice way to publish a TiddlyWiki -- which is a problem all people in TiddlyWiki struggle against.

• https://github.com/fiatjaf/tiddlywiki-remotestorage
• https://tiddly.alhur.es/

See also

• hledger-web
• LessPass remoteStorage

@ 3bf0c63f:aefa459d

Democracia na América

Alexis de Tocqueville escreveu um livro só elogiando o sistema político dos Estados Unidos. E mesmo tendo sido assim, e mesmo tendo escrito o seu livro quase 100 anos antes do mais precoce sinal de decadência da democracia na América, percebeu coisas que até hoje quase ninguém percebe: o mandato da suprema corte é um enorme poder, uma força centralizadora, imune ao voto popular e com poderes altamente indefinidos e por isso mesmo ilimitados.

Não sei se ele concluiu, porém, que não existe nem pode existir balanço perfeito entre poderes. Sempre haverá furos.

De qualquer maneira, o homem é um gênio apenas por ter percebido isso e outras coisas, como o fato da figura do presidente, também obviamente um elemento centralizador, não ser tão poderosa quanto a figura de um rei da França, por exemplo. Mas ao mesmo tempo, por entre o véu de elogios (sempre muito sóbrios) deixou escapar que provavelmente também achava que não poderia durar para sempre a fraqueza do cargo de presidente.

• Democracy as a failed open-network protocol
• Família e propriedade
• Liberalismo oitocentista

@ 3bf0c63f:aefa459d

Parallel Chains

We want merged-mined blockchains. We want them because it is possible to do things in them that aren't doable in the normal Bitcoin blockchain because it is rightfully too expensive, but there are other things beside the world money that could benefit from a "distributed ledger" -- just like people believed in 2013 --, like issued assets and domain names (just the most obvious examples).

On the other hand we can't have -- like people believed in 2013 -- a copy of Bitcoin for every little idea with its own native token that is mined by proof-of-work and must get off the ground from being completely valueless into having some value by way of a miracle that operated only once with Bitcoin.

It's also not a good idea to have blockchains with custom merged-mining protocol (like Namecoin and Rootstock) that require Bitcoin miners to run their software and be an active participant and miner for that other network besides Bitcoin, because it's too cumbersome for everybody.

Luckily Ruben Somsen invented this protocol for blind merged-mining that solves the issue above. Although it doesn't solve the fact that each parallel chain still needs some form of "native" token to pay miners -- or it must use another method that doesn't use a native token, such as trusted payments outside the chain.

How does it work

With the SIGHASH_NOINPUT/SIGHASH_ANYPREVOUT soft-fork[^eltoo] it becomes possible to create presigned transactions that aren't related to any previous UTXO.

Then you create a long sequence of transactions (sufficient to last for many many years), each with an nLockTime of 1 and each spending the next (you create them from the last to the first). Since their scriptSig (the unlocking script) will use SIGHASH_ANYPREVOUT you can obtain a transaction id/hash that doesn't include the previous TXO, you can, for example, in a sequence of transactions A0-->B (B spends output 0 from A), include the signature for "spending A0 on B" inside the scriptPubKey (the locking script) of "A0".

With the contraption described above it is possible to make that long string of transactions everybody will know (and know how to generate) but each transaction can only be spent by the next previously decided transaction, no matter what anyone does, and there always must be at least one block of difference between them.

Then you combine it with RBF, SIGHASH_SINGLE and SIGHASH_ANYONECANPAY so parallel chain miners can add inputs and outputs to be able to compete on fees by including their own outputs and getting change back while at the same time writing a hash of the parallel block in the change output and you get everything working perfectly: everybody trying to spend the same output from the long string, each with a different parallel block hash, only the highest bidder will get the transaction included on the Bitcoin chain and thus only one parallel block will be mined.

See also

• Drivechain

[^eltoo]: The same thing used in Eltoo.

@ 5a9c48c8:2f2d1069

Considering our most acute problems in the EU is a matter of great debate, which is not necessarily all evidence based. Our seemingly most pressing problems might not even be problems at all, just public opinion. To create unenforceable policy to address these problems is costly, so much so that I think it’s necessary to create a standard. I will not trivialise any particular policy, but I will make a case for at least having a Bitcoin strategy.

There are three ways that policy fails:

• The policy is not enforceable.
• The policy is costing more to enforce than it benefits.
• The public adjusts its behavior to circumvent in a roundabout manner, which requires yet again more policy: praxeology.

The only way that any policy has a measurable desired effect is when it is enforceable, is cost effective and doesn’t motivate adverse or roundabout behavior. This is the necessary standard to measure policy by. Budget management for the calculation of policy efficacy also needs to be represented in the balance.

An example of a failing policy is the 100km/h speed limit in the Netherlands. To enforce this requires policing of the highways, which costs money. To pay for the enforcement speed tickets are issued. Highway users use the app Flitsmeister, which is a social media app that allows users to share gps data of traffic controls. As a result less speed tickets are issued and highway users speed more. The government can’t ban the app because using the app is the user’s freedom of speech, it’s just allowing users to communicate coordinates on a map. This is a lawful behavior, any ruling against an app like Flitsmeister will not hold up in court. A calculation must be made to see how much it would cost to just allow highway users to speed versus what it would cost to continue enforcing. A calculation must be made to see what the benefit is of the policy. In this case the policy is in place because the EU has decided that emissions from motor vehicles must be brought down, so the 100km/h policy was a consequence of an unenforceable policy. So this example shows all three ways in which a policy can fail:

• Simply telling people to create less emissions is unenforceable.
• Revenue from speed tickets dwindle, people keep speeding and emissions do not measurably go down.
• People adapt to the policy with a lawful measure so that they can continue driving at the speed they desire, behavior known as praxeology. (Keep in mind that people were used to driving 120km/h before, and most people don’t consider that speed as excessive speeding or as unlawful.)

Just by using epistemology we now have the basic requirements for policy to exist. Pretending to be moralistic doesn’t help. In the end moralism points to sustainability, which means to not wasting public funds. Therefore being strategic is actually the best moralistic approach.

Bitcoin is a free and open source project, anyone can contribute. Direct participation is possible by transacting and holding Bitcoin, by running a Bitcoin node or by mining Bitcoin. To ban Bitcoin transactions is to ban freedom of speech, because transacting Bitcoin is basically the exchange of information. There is no entity that controls Bitcoin, so you can’t address the organization because there is no organization. Because of its value propositions, Bitcoin is proving to be a better store of value than any other asset class. If you have no confidence in this, then you still need to play along with Bitcoin because not playing means you will lose asymmetrically over time. The game theory of Bitcoin is that not playing results in loss. The costs to participate are low, which is a benefit that stems from the asymmetry. So there can be no reason not to participate at all, to at least offset the cost of opportunity.

To use Bitcoin as an example of framework for policy I propose to look at the failures to enforce a mining ban. If a government were to make Bitcoin mining illegal, the miner would simply move its operation. Bitcoin mining is not jurisdiction specific; this was made clear by the restoring of hashrate after the China Bitcoin mining ban. Miners that chose to stay are difficult to find, enforcement will be costly and ineffective. Miners that do leave will not pay any taxes, nor will those that have been made illegal miners within the jurisdiction. Not banning Bitcoin will allow power plants to offset inefficiency by mining Bitcoin. Energy efficiency is the greatest benefit of Bitcoin mining, which will prove to become the largest possible sustainability improvement for participants. So from this example we can see that this policy also fails on three counts in which it can fail:

• Banning Bitcoin mining does not magically make Bitcoin miners disappear. Heavy policing will not find those who still chose to continue. You can’t stop miners in other jurisdictions, yet they still give access to the network to users in the jurisdiction. Remember, the internet doesn’t do geography.
• Loss in tax revenue from multiple sectors of business will prove to be devastating. Policing illegalised Bitcoin miners is costly in many ways. There is no benefit. Allowing Bitcoin mining on the other hand would reap enormous societal benefits.
• Illegalised Bitcoin miners will still exist within the jurisdiction, but will not pay any taxes. Those who chose to leave, take with them their thriving business and the entire framework of the involved financial sector.

If you still oppose Bitcoin in any way, make sure to look up your specific criticism in the list published on https://www.endthefud.org . You will see that your misinformed belief does not hold up against matter of fact.

@ bcea2b98:7ccef3c9

Chapter 1 - The Looming Threat

Deep within a remote, heavily guarded scientific facility in the Ural Mountains of Russia, Vadim Petrov hunched over the glowing screen of his computer, rubbing his bloodshot eyes. He barely noticed the cold bite of the stale bunker air or the crumpled energy drink cans littering his workspace. All his focus was directed toward the lines of code marching down the monitor, his life's work laid bare before him in beautiful minimalist logic.

With a final keystroke, Vadim compiled the program. A hint of a smile tugged at his cracked lips. It was done - his quantum computing masterpiece was ready. Soon, very soon, he would put it to use, cracking open the virtual vaults of Bitcoin once and for all.

Vadim leaned back, his chair creaking, as he reflected on the long road leading to this moment. He had dedicated over a decade of brilliance and obsession to reach this point. As a young PhD student at the Moscow Institute of Physics and Technology in the late 2010s, Vadim excelled in quantum research, blazing ahead of his peers. The emerging field held incredible promise to revolutionize computing, smashing through limitations faced by even the most powerful supercomputers of the era. Quantum's exponential scale held the potential to reshape medicine, cryptography, energy, space exploration - the very structure of knowledge itself.

When he first heard of Bitcoin, the mysterious digital currency created by the pseudonymous Satoshi Nakamoto, Vadim instantly saw how quantum power could be its undoing - or its savior. This so-called "digital gold" seemed foolish to him at first, bits pretending to be as valuable as precious metal and national currencies. But as Bitcoin grew, finding an enthusiastic niche among techno-libertarians and cyberpunks seeking an alternative economy, Vadim paid ever more notice.

In 2013, still early days for Bitcoin, the price crossed $1000 briefly before crashing back down. But four years later, the cryptocurrency exploded into mainstream consciousness by reaching parabolic heights of nearly $20,000. Soon even governments were debating regulation and financial elites argued whether Bitcoin could revolutionize - or destroy - the monetary order.

As a central player in quantum research, Vadim understood before most that this rising cryptocurrency built on cryptography was ultimately vulnerable. Quantum computers' exponential power could easily crack the public-private key encryption which secured Bitcoin wallets and transactions. At a stroke, quantum supremacy over classical silicon computing meant game over for Bitcoin's security paradigm.

But observing Bitcoin's ascent, Vadim felt not warning, but jealous loathing. That such a presumptuous invention dared accrue billions in supposed value offended his sense of the natural order. "Who are these cowboy coders challenging state authorities by creating magic internet money from thin air?" he lamented. The veneer of technological genius concealing base greed and anarchism disgusted him.

He vividly remembered the day years back when an American investor tried convincing Vadim, already an elite researcher, to work on Bitcoin security applications for quantum tech. Vadim refused brusquely, judging the field as unserious pop science.

"You will look foolish when governments shut this down and prosecute these scam artists," Vadim insisted. The American just laughed and made a fortune when Bitcoin's price kept rising. That gloating smile haunted Vadim, even as Bitcoin became too influential to simply ban outright.

His disgust slowly gave way to an ambitious vision. When quantum supremacy definitively arrived, he would be ready. He would craft the world's most powerful quantum computing instrument specifically to destroy Bitcoin's security. Not to extort ransoms, but to prove a point - that this inflated bubble of algorithmic make-believe money was hopelessly fragile against raw hyper-accelerated calculation power.

To Vadim, Bitcoin represented not promise, but hubris. By exposing it as mathematically flawed at its core, he could reveal the hypocrisy and weakness of its pseudo-populist rhetoric. The world would thank him for liberating it from this viral delusion that threatened real economic stability. Utter secrecy was essential as over years Vadim assembled a team of elite researchers and siphoned funding into his covert Bitcoin breaking project. Russia's security apparatus gave tacit support in hopes of gaining future quantum advantage over Western rivals. But only Vadim's innermost circle knew his full vision of bathing Bitcoin's precious blockchain in the firepower of quantum-enabled cryptanalysis - watching it burn brightly and then fade to ash.

Vadim called his creation the Venus Prototype, after the Morning Star that heralds the sun's arrival. And like that celestial body, his machine would break the endless digital night of Bitcoin's golden age, exposing it as a false idol. No longer would its porous cryptography conceal inflated speculation from deserved ruin. By quantum might, he would cast light on Bitcoin's weaknesses, melting its shiny veneer to reveal the clay feet of a false god. And now Venus was alive, humming with otherworldly might in its cradle beneath the mountains. As Vadim initiated the startup sequence, the bunker vibrated with thrumming power. Lights flickered in awe of this digital beast's birth. Vadim watched transfixed as raw calculation potential that could model whole universes now came under his command. An almost religious ecstasy seized him, sensing destiny at hand. The hour had come at last to implement his vision. All that remained was choosing the perfect moment to strike...

Meanwhile across the world, sunny California seemed a different universe from Vadim's subterranean lab. In a nondescript San Francisco office, a group of developers were hard at work on Bitcoin software. Eric Hughes, grey-bearded veteran of the cypherpunk movement of activists who pioneered cryptography and online privacy, led the Bitcoin Core team in maintaining the protocol's code.

After over a decade of meteoric growth, disruptive potential, and no shortage of controversy, Bitcoin was now worth trillions and shaking the foundations of the financial system. But from their humble workspace, the task at hand for Eric and his Brilliant but overworked colleagues was just keeping the network running smoothly. He often repeated the mantra “First, do no harm” when considering potential code changes, reflecting the enormous responsibility of these stewards to an open-source project that had taken on a life of its own. With so many vested interests, keeping stakeholders aligned was as much politics as programming.

While reviewing some proposed efficiency improvements, Eric came across a strange message on the project's public developer forum, posted anonymously:

"Beware the coming storm, when the quantum tempest shall rage. What is built strong today will soon lie broken tomorrow, unless the wise prepare in time..."

Puzzled, Eric read the cryptic warning again. Was it some clueless amateur speculating, or something more? The reference to quantum hinted at specialized knowledge. Gathering a few lead developers, Eric asked them if they knew anything about the message. They all shrugged, as perplexed as him.

Still, Eric felt a nameless unease. The specter of quantum computing loomed over every cryptographer's thoughts, though the capability remained confined to laboratories for the foreseeable future. But if someone had made a significant, secret breakthrough, Bitcoin's current encryption would become obsolete overnight. Usually cautious voices in the developer forums were already arguing quantum resistance should be built into the protocol.

"This reeks of foolish alarmism to me," said Zhao, a skeptical cryptographer trained in China. "Our Shanghai lab would know if anyone had achieved meaningful quantum advantage. This is petty fearmongering." "Perhaps," said Eric slowly. "Or perhaps it's a friendly warning. In any case, accelerating our quantum-resistant cryptography initiatives seems wise. The very least we should do some threat modeling around a hypothetical quantum attack vector. Things may look very different sooner than we think..."

A tense silence settled around the room. Bitcoin's rise had sparked no shortage of doomsday predictions, but some threats had more weight than others. Primal fear of the unknown gripped them as developers entrusted with securing a multi-trillion dollar network.

Finally Eric spoke again, resolve steeling his voice: "Let's get to work. We'll redouble our efforts on quantum-proofing. Whoever this anonymous watchdog is, they're right about one thing - we must do all we can to prepare while there's time. And if the storm does come howling at our door, threatening to blow down Bitcoin's fortress of cryptography..." He tightened his fist as if grasping an imaginary sword. "We'll be ready to weather it."

The battle was not yet joined, but the first ripples hinted at gathering forces. As Vadim prepared to unleash his weapon and Eric girded for defense, the epochal quantum clash over Bitcoin's future was set in motion. Two worlds racing toward collision at the crossroads of cryptography and quantum physics. The storm could no longer be stopped. It could only be survived - if the wise prepared in time...

@ ee6ea13a:959b6e74

Reposting this on stacker.news and Nostr for those who no longer use X.

Original post: https://x.com/dsbatten/status/1770571463151775944

You’ve probably seen GreenpeaceUSA's Bitcoin report by now, and my response (if you haven't been blocked).

Here’s six things that every environmentalist, Bitcoin advocate, regulator, policymaker and media representative should know about GreenpeaceUSA.

I've had this information for over a year, but have held back on going public with it until now because there were initially signs that GreenpeaceUSA would be open to engaging with environmentalists within the Bitcoin community.

With them now blocking me from commenting on their posts, all hope of that has now ended.

So here's what I can tell you about GreenpeaceUSA, and their campaign that have not been aired publicly until now, and which may surprise you.

Firstly, some context: I’m a former volunteer environmental campaigner with Greenpeace.

I once risked arrest to stand up for causes I believed in, including an anti-GMO campaign against McDonalds which was successful within 6 weeks, and hailed as an example of how creative direct action can yield fast results.

One of the differences: we talked to McDonalds (something no one at GreenpeaceUSA is currently doing with the Bitcoin community).

I know a number of people in the environmental movement, and I would like to thank them for their honesty in whistleblowing on a thoroughly misguided campaign from GreenpeaceUSA from start to finish.

1. GreenpeaceUSA’s campaign does NOT have the backing of Greenpeace International. In fact, other branches have asked questions of GreenpeaceUSA’s tactics, and even said that their campaign is damaging the Greenpeace brand, and has resulted in the loss of subscriptions.

2. Within GreenpeaceUSA, there are a growing number of voices of discontent. There is a growing division between some of the younger crypto-neutral or crypto-friendly millennial in their base, and the directorship of GreenpeaceUSA

3. As we know, GreenpeaceUSA did receive a $5Million donation from Ripple’s chair Chris Larsen to run an anti-Bitcoin campaign. What you probably do not know is that within Greenpeace, several staff have questioned whether this is ethical, or in the spirit of an organization that says it relies only on grassroots funding in its sign-up pledge.

4. Some members of EWG and SierraClub, particularly younger members, were not enamoured with their organization’s collusion with GreenpeaceUSA’s “Change the Code” campaign. EWG has not engaged in anti-Bitcoin rhetoric since 6 April ‘23.

5. The head of GreenpeaceUSA’s “Change the Code” campaign has stepped down and is no longer any part of GreenpeaceUSA. At the time of his stepping down he was reported by a source within GreenpeaceUSA to be questioning the wisdom of the campaign.

6. Within GreenpeaceUSA, we know from multiple inside sources that the Change the Code campaign has been widely acknowledged to have been “not particularly successful”.

GreenpeaceUSA’s campaign got off on the wrong foot right from the start, by antagonising environmentalists within the Bitcoin community, such as me. Here’s its half-time report (TL;DR, the worst performing environmental campaign I’ve ever witnessed). https://bitcoinmagazine.com/culture/greenpeace-environment-attacks-help-bitcoin

Now, the campaign is in more disarray than ever, resorting to tenuous ad hominem attacks against Satoshi Action, based on the discover that one of their supporters is a climate denier. True. Well, guess what: one of their supporters is also a plant-based, tree-hugging, climate-activist & meditation teacher: me.

That’s the beauty of Bitcoin: it pulls people in from across the political spectrum: we are as diverse as society itself, and that’s what makes us strong. As I wrote recently, “when the ship you’re standing on is sinking: it doesn’t matter if you’re on the left of right side of it.”

I hoped GreenpeaceUSA would end their anti-Bitcoin campaign before their credibility and relevance to the new generation of millennials they are currently disenfranchising is completely severed. But it seems at the moment they are more intent on doubling down on misinformation. Their leadership must change for them to ever have hope of becoming a true voice for the environment again.

@ 3bf0c63f:aefa459d

Classless Templates

There are way too many hours being wasted in making themes for blogs. And then comes a new blog framework, it requires new themes. Old themes can't be used because they relied on different ways of rendering the website. Everything is a mess.

Classless was an attempt at solving it. It probably didn't work because I wasn't the best person to make themes and showcase the thing.

Basically everybody would agree on a simple HTML template that could fit blogs and simple websites very easily. Then other people would make pure-CSS themes expecting that template to be in place.

No classes were needed, only a fixed structure of header. main, article etc.

With flexbox and grid CSS was enough to make this happen.

The templates that were available were all ported by me from other templates I saw on the web, and there was a simple one I created for my old website.

• https://github.com/fiatjaf/classless
• https://classless.alhur.es/
• https://classless.alhur.es/themes/

@ 3bf0c63f:aefa459d

busca múltipla na estante virtual

A single-page app made in Elm with a Go backend that scrapped estantevirtual.com.br in real-time for search results of multiple different search terms and aggregated the results per book store, so when you want to buy many books you can find the stores that have the biggest part of what you want and buy everything together, paying less for the delivery fee.

It had a very weird unicode issue I never managed to solve, something with the encoding estantevirtual.com.br used.

I also planned to build the entire checkout flow directly in this UI, but then decided it wasn't worth it. The search flow only was already good enough.

• https://estantevirtual.alhur.es/
• https://github.com/fiatjaf/estantevirtual

@ 3bf0c63f:aefa459d

requesthub.xyz

An app that was supposed to be some kind of declarative connector between two services, one that sent webhooks and the other that accepted HTTP requests of any kind. You would proxy and transform the webhooks using RequestHub and create a new request to the other service using that data.

The transformations were declared in the almighty jq language.

It worked and had other functions planned for the future, but I guess it was too arcane, even I was confused by it sometimes.

Also it was very prone to spam (involuntary) attacks like some that did happen. Maybe it would work better in a world of anonymous satoshi payments.

Later I tried to revive it as a Trello Power-Up that would create comments on cards automatically according to some transformation rules and webhooks received.

• requesthub.xyz
• https://github.com/fiatjaf/requesthub.xyz
• https://github.com/fiatjaf/requesthub-trello

@ ee11a5df:b76c4e49

I'm glad to see more activity and discussion about the gossip model. Glad to see fiatjaf and Jack posting about it, as well as many developers pitching in in the replies. There are difficult problems we need to overcome, and finding notes while remaining decentralized without huge note copying overhead was just the first. While the gossip model (including the outbox model which is just the NIP-65 part) completely eliminates the need to copy notes around to lots of relays, and keeps us decentralized, it brings about it's own set of new problems. No community is ever of the same mind on any issue, and this issue is no different. We have a lot of divergent opinions. This note will be my updated thoughts on these topics.

COPYING TO CENTRAL RELAYS IS A NON-STARTER: The idea that you can configure your client to use a few popular "centralized" relays and everybody will copy notes into those central relays is a non-starter. It destroys the entire raison d'être of nostr. I've heard people say that more decentralization isn't our biggest issue. But decentralization is THE reason nostr exists at all, so we need to make sure we live up to the hype. Otherwise we may as well just all join Bluesky. It has other problems too: the central relays get overloaded, and the notes get copied to too many relays, which is both space-inefficient and network bandwith inefficient.

ISSUE 1: Which notes should I fetch from which relays? This is described pretty well now in NIP-65. But that is only the "outbox" model part. The "gossip model" part is to also work out what relays work for people who don't publish a relay list.

ISSUE 2: Automatic failover. Apparently Peter Todd's definition of decentralized includes a concept of automatic failover, where new resources are brought up and users don't need to do anything. Besides this not being part of any definition of decentralized I have never heard of, we kind of have this. If a user has 5 outboxes, and 3 fail, everything still works. Redundancy is built in. No user intervention needed in most cases, at least in the short term. But we also don't have any notion of administrators who can fix this behind the scenes for the users. Users are sovereign and that means they have total control, but also take on some responsibility. This is obvious when it comes to keypair management, but it goes further. Users have to manage where they post and where they accept incoming notes, and when those relays fail to serve them they have to change providers. Putting the users in charge, and not having administrators, is kinda necessary to be truly decentralized.

ISSUE 3: Connecting to unvetted relays feels unsafe. It might even be the NSA tracking you! First off, this happens with your web browser all the time: you go visit a web page and it instructs your browser to fetch a font from google. If you don't like it, you can use uBlock origin and manage it manually. In the nostr world, if you don't like it, you can use a client that puts you more in control of this. The gossip client for example has options for whether you want to manually approve relay connections and AUTHs, just once or always, and always lets you change your mind later. If you turn those options on, initially it is a giant wall of approval requests... but that situation resolves rather quickly. I've been running with these options on for a long time now, and only about once a week do I have to make a decision for a new relay.

But these features aren't really necessary for the vast majority of users who don't care if a relay knows their IP address. Those users use VPNs or Tor when they want to be anonymous, and don't bother when they don't care (me included).

ISSUE 4: Mobile phone clients may find the gossip model too costly in terms of battery life. Bandwidth is actually not a problem: under the gossip model (if done correctly) events for user P are only downloaded from N relays (default for gossip client is N=2), which in general is FEWER events retrieved than other models which download the same event maybe 8 or more times. Rather, the problem here is the large number of network connections and in particular, the large number of SSL setups and teardowns. If it weren't for SSL, this wouldn't be much of a problem. But setting up and tearing down SSL on 50 simultaneous connections that drop and pop up somewhat frequently is a battery drain.

The solution to this that makes the most sense to me is to have a client proxy. What I mean by that is a piece of software on a server in a data centre. The client proxy would be a headless nostr client that uses the gossip model and acts on behalf of the phone client. The phone client doesn't even have to be a nostr client, but it might as well be a nostr client that just connects to this fixed proxy to read and write all of its events. Now the SSL connection issue is solved. These proxies can serve many clients and have local storage, whereas the phones might not even need local storage. Since very few users will set up such things for themselves, this is a business opportunity for people, and a better business opportunity IMHO than running a paid-for relay. This doesn't decentralize nostr as there can be many of these proxies. It does however require a trust relationship between the phone client and the proxy.

ISSUE 5: Personal relays still need moderation. I wrongly thought for a very long time that personal relays could act as personal OUTBOXes and personal INBOXes without needing moderation. Recently it became clear to me that clients should probably read from other people's INBOXes to find replies to events written by the user of that INBOX (which outbox model clients should be putting into that INBOX). If that is happening, then personal relays will need to serve to the public events that were just put there by the public, thus exposing them to abuse. I'm greatly disappointed to come to this realization and not quite settled about it yet, but I thought I had better make this known.

@ 3bf0c63f:aefa459d

Money Supply Measurement

What if we measured money supply measured by probability of being spent -- or how near it is to the point in which it is spent? bonds could be money if they're treated as that by their owners, but they are likely to be not near the spendpoint as cash, other assets can also be considered money but they might be even farther.

@ 3bf0c63f:aefa459d

How being "flexible" can bloat a protocol

(A somewhat absurd example, but you'll get the idea)

Iimagine some client decides to add support for a variant of nip05 that checks for values at /.well-known/nostr.yaml besides /.well-known/nostr.json. "Why not?", they think, "I like YAML more than JSON, this can't hurt anyone".

Then some user makes a nip05 file in YAML and it will work on that client, they will think their file is good since it works on that client. When the user sees that other clients are not recognizing their YAML file, they will complain to the other client developers: "Hey, your client is broken, it is not supporting my YAML file!".

The developer of the other client, astonished, replies: "Oh, I am sorry, I didn't know that was part of the nip05 spec!"

The user, thinking it is doing a good thing, replies: "I don't know, but it works on this other client here, see?"

Now the other client adds support. The cycle repeats now with more users making YAML files, more and more clients adding YAML support, for fear of providing a client that is incomplete or provides bad user experience.

The end result of this is that now nip05 extra-officially requires support for both JSON and YAML files. Every client must now check for /.well-known/nostr.yaml too besides just /.well-known/nostr.json, because a user's key could be in either of these. A lot of work was wasted for nothing. And now, going forward, any new clients will require the double of work than before to implement.

@ a24d0c86:ec0f47ce

There's been an influx of new users to Nostr in the last few weeks. I decided to create an onboarding survey to see what insights could be gained.

18 npubs participated. My hope was at least more than 2 or 3 so by that measure it was a wild success. Even more so because 2/3 of participants indicated they would be willing to do follow-up interviews.

Let's see what the results were and I'll include brief reflections after each.

This is great, and a bit surprising, there was NO negative reactions to Nostr Onboarding! Overwhelming positive and that credit goes to the culture of OG npubs and those that are actively sharing Nostr with friends.

Primal having a dominate showing is to be expected because they have repeatedly said they want to be one of the best at onboarding new users to Nostr. Also they have clients with some of the best UX, but most importantly they have three options of clients - iOS, Android and browser.

Damus continues to make progress on their iOS, recently launching Damus Purple while continuing to make progress on an Android client. And they arguably have the best "client culture" although an Amethyst user might argue with that, haha.

This section IMO is one of the most insightful findings. Clients have clearly made receiving an npub incredible easy as there were no complaints about this process. That's a ton of progress because I personally remember how difficult of a task it was over a year ago. Only people that really, really wanted it seemed to make it through.

The next two questions are where it seems a lot of value can be added for new users to Nostr. Specifically in explaining features and improving navigation.

The network effect of Nostr's interoperability (use #nostrability to highlight any issues discovered) is one of it's superpowers. But at the same time it presents one of the steepest learning curves.

The Twitter clones are pretty familiar to most new users. But Nostr is so much more than that. And now with new users coming from other apps besides the dead bird, like TikTok or Substack, there's a need for better ways for users to discover these Nostr clients/apps.

Looking at the latest stats from Nostr.band the retention rate doesn't seem to be improving much with the last few new user cohorts.

How can we move this curve up to start and retain more users with each cohort?

Discoverability is a key I believe. But not just discoverability for other npubs to follow. I think discoverability of novel apps is equally as important.

How many new users are even aware of the Nostr Apps site that Karnage has curated?

Yes a better Twitter experience, or even YouTube and Substack is desirable. But IMO the 1M+ new users to Nostr will be as a result of the unique experiences that the Nostr protocol allows. Whether zaps, social network portability or the new business models that could never have been tried before.

And speaking of zaps!

It was great to see that most new users are able to experience the newest innovation in social media. Credit to the clients for making this easier, Alby for their NWC work and the users that are hand holding their friends along the way.

Besides the insights from features/navigation IMO the NPS is the next most important finding from this survey. It's a solid start for Nostr to have such positive scores when it's so fundamentally different in social media and apps in general as far as UX. Credit to the Nostr OGs, builders and educators that have helped with this so far. There's still room for improvement but this increased how bullish I am on Nostr to see new users have this type of enthusiasm.

The final part of the survey asked for new users favorites parts of Nostr and what they'd like to see. The latter was all over the place. However with the favorites, given a little interpratation I was able to stack rank the top three favorites.

Not really a surprise but rather validation of what should continue to be the focus. Even today as I'm writing this I'm seeing Jack offer another bounty to further implement the gossip model in hopes of increasing censorship resistance.

IMO these favorites need to continue to be top of mind as building continues. The "north stars" of Nostr if you will.

I'm going to be building and sharing more about how I'll be contributing to improve the Nostr Onboarding. My focus will follow what I've found through this survey: better features and navigation explanations while keeping the Nostr north stars in mind.

@ 3bf0c63f:aefa459d

IPFS problems: Conceit

IPFS is trying to do many things. The IPFS leaders are revolutionaries who think they're smarter than the rest of the entire industry.

The fact that they've first proposed a protocol for peer-to-peer distribution of immutable, content-addressed objects, then later tried to fix that same problem using their own half-baked solution (IPNS) is one example.

Other examples are their odd appeal to decentralization in a very non-specific way, their excessive flirtation with Ethereum and their never-to-be-finished can-never-work-as-advertised Filecoin project.

They could have focused on just making the infrastructure for distribution of objects through hashes (not saying this would actually be a good idea, but it had some potential) over a peer-to-peer network, but in trying to reinvent the entire internet they screwed everything up.

@ 3bf0c63f:aefa459d

Criteria for activating Drivechain on Bitcoin

Drivechain is, in essence, just a way to give Bitcoin users the option to deposit their coins in a hashrate escrow. If Bitcoin is about coin ownership, in theory there should be no objection from anyone on users having the option to do that: my keys, my coins etc. In other words: even if you think hashrate escrows are a terrible idea and miners will steal all coins from that, you shouldn't care about what other people do with their own money.

There are only two reasonable objections that could be raised by normal Bitcoin users against Drivechain:

1. Drivechain adds code complexity to bitcoind
2. Drivechain perverts miner incentives of the Bitcoin chain

If these two objections can be reasonably answered there remains no reason for not activating the Drivechain soft-fork.

1

To address 1 we can just take a look at the code once it's done (which I haven't) but from my understanding the extra validation steps needed for ensuring hashrate escrows work are very minimal and self-contained, they shouldn't affect anything else and the risks of introducing some catastrophic bug are roughly zero (or the same as the risks of any of the dozens of refactors that happen every week on Bitcoin Core).

For the BMM/BIP-301 part, again the surface is very small, but we arguably do not need that at all, since anyprevout (once that is merged) enables blind merge-mining in way that is probably better than BIP-301, and that soft-fork is also very simple, plus already loved and accepted by most of the Bitcoin community, implemented and reviewed on Bitcoin Inquisition and is live on the official Bitcoin Core signet.

2

To address 2 we must only point that BMM ensures that Bitcoin miners don't have to do any extra work to earn basically all the fees that would come from the sidechain, as competition for mining sidechain blocks would bid the fee paid to Bitcoin miners up to the maximum economical amount. It is irrelevant if there is MEV on the sidechain or not, everything that reaches the Bitcoin chain does that in form of fees paid in a single high-fee transaction paid to any Bitcoin miner, regardless of them knowing about the sidechain or not. Therefore, there are no centralization pressure or pervert mining incentives that can affect Bitcoin land.

Sometimes it's argued that Drivechain may facilitate the ocurrence of a transaction paying a fee so high it would create incentives for reorging the Bitcoin chain. There is no reason to believe Drivechain would make this more likely than an actual attack than anyone can already do today or, as has happened, some rich person typing numbers wrong on his wallet. In fact, if a drivechain is consistently paying high fees on its BMM transactions that is an incentive for Bitcoin miners to keep mining those transactions one after the other and not harm the users of sidechain by reorging Bitcoin.

Moreover, there are many factors that exist today that can be seen as centralization vectors for Bitcoin mining: arguably one of them is non-blind merge mining, of which we have a (very convoluted) example on the Stacks shitcoin, and introducing the possibility of blind merge-mining on Bitcoin would basically remove any reasonable argument for having such schemes, therefore reducing the centralizing factor of them.

@ 3d842afe:2d44a42d

Websocket connection overhead is an obvious problem with the gossip model that few are willing to acknowledge. The more decentralized relay selection becomes (the goal) the worse it scales. Even at the current scale of nostr if users chose more diverse relay sets the issue would be crippling.

Below are some very simple simulations to illustrate my point. I used 2 relays per person to be conservative and chose 3 different realistic follow counts. The NIP-65 spec suggests clients should guide users to keep the lists small (2-4 relays) though currently the average kind 10002 contains many more. I ran each simulation 10 times and then took the average result.

EDIT: I understand that selecting relays at random is NOT how things currently work or will ever work. My point is that if our goal is to make relay sets more diverse then we should work towards a solution that scales with accomplishing that goal.

Available relays: 600 (~what nostr.watch currently shows for online relays) Follows: 200 Relays per person: 2 (randomly selected) Unique Connections Required: 291

Available Relays: 600 Follows: 500 Relays per person: 2 Unique Connections Required: 486

Available Relays: 600 Follows: 1000 Relays per person: 2 Unique Connections Required: 577

Even today if users randomly selected relays the total number of connections required would be staggering and this is with users only selecting 2 relays each. What happens if the available number of relays increases by 5x?

Available Relays: 3000 Follows: 200 Relays per person: 2 Unique Connections Required: 376

Available Relays: 3000 Follows: 500 Relays per person: 2 Unique Connections Required: 847

Available Relays: 3000 Follows: 1000 Relays per person: 2 Unique Connections Required: 1461

I’m not a client developer and I certainly don’t have all the solutions but I’ve spent enough time operating websockets at scale to know that these numbers aren’t going to work even with only 2 relays per person. Aside from the practical performance implications, browsers also enforce websocket limits that put most of these numbers out of reach (I believe Chrome is 255 and Firefox is 200).

What am I missing?

@ bcea2b98:7ccef3c9

Chapter 1 - The Looming Threat

Deep in an underground bunker, Vadim feverishly typed away at his computer. The young Russian computer scientist was putting the finishing touches on his masterpiece - a quantum computer capable of breaking Bitcoin's ironclad cryptography. When he had first heard of Bitcoin years ago, the so-called "digital gold" fascinated him. But over time, watching its meteoric rise in value, he grew jealous and vengeful. "I will be the one to bring this false idol crumbling down!" he muttered under his breath in Russian. Vadim knew the potential of quantum computing, and how it could break through Bitcoin's encrypted defenses in an instant. His malicious creation was nearly ready, soon to deal a crushing blow to Bitcoin's foundations.

Meanwhile, across the world in California, the lead developers of the Bitcoin Core project were hard at work in their office. Eric, the head developer, was reviewing the latest code updates when he came across a strange message posted anonymously: "Beware the coming quantum storm...". Puzzled, he called over his colleagues to look at the cryptic warning. What could it mean? Eric felt a sudden chill, as if a shadow had passed over them. "We need quantum resistance built into Bitcoin, fast!" he told his team. "Before it's too late..."

Chapter 2 - Scaling Solutions

Bitcoin had survived the first looming threat of quantum computing by quickly implementing new quantum-resistant cryptography. But it still faced another crisis - scaling to meet growing transaction demands. The Bitcoin network could only handle so many transactions per second, leading to increased fees and slow settlement times.

Anya, a Russian-American Bitcoin developer, believed she had the solution. She had spearheaded the development of the Lightning Network, a layer-2 protocol that enables fast peer-to-peer Bitcoin transactions outside of the main blockchain. Anya was proud of her work, but adoption of Lightning was slow. "We have the technology, we just need to make it easy and safe for the average user," she lamented over drinks with her coworkers.

Meanwhile, a competing scaling solution was gaining steam. Jack, a brash young Australian entrepreneur, had launched the Liquid Network, a sidechain that promised faster transactions and inter-exchange settlements. Liquid was gaining traction, but Anya knew it was less decentralized than her Lightning Network. The battle of the scaling solutions had only just begun...

Chapter 3 - POW vs POS

Bitcoin's price was soaring, but a simmering debate threatened its future - proof-of-work vs proof-of-stake. The energy usage of Bitcoin's POW mining had long been criticized as wasteful and harmful to the environment. "We can't let this go on if we want Bitcoin to grow," Steve exhorted at a developer meetup. The eccentric billionaire had invested heavily into Bitcoin and now believed it was time for a greener consensus mechanism.

But transitioning Bitcoin from POW to POS would not be straightforward. Marcia, a Brazilian mining company CEO, would fight tooth and nail to stop it. "POS hands too much control to the whale investors," she said in an impassioned speech. "It betrays Bitcoin's founding principles!" The passionate Bitcoin maximalists echoed Marcia's views in fiery forum debates.

Other events kept stoking the POW vs POS debate. Climate change regulations were being enacted worldwide, harshly cracking down on emissions. News spread of Bitcoin miners bribing officials in developing countries for preferential treatment. "This has gone too far!" said a water company executive whose town's supply was drying up due to mining operations. Calls grew stronger for Bitcoin to adopt proof-of-stake before it was too late...

Chapter 4 - Mainstream Adoption

Bitcoin had overcome existential threats and was finally gaining mainstream traction. Major companies were accepting it as payment, propelling its price higher. The value of the overall crypto market had swelled to trillions of dollars. Excitement and optimism abounded at the annual Bitcoin Miami conference, drawing over 100,000 attendees.

But some feared Bitcoin's good fortune would not last. Duke, a finance professor, believed Bitcoin was a speculative bubble ready to burst. "These rallies never end well," he warned his students. "Get out while you can!" He likened the craze to Tulipmania in 17th century Netherlands.

His warnings went unheeded. More and more ordinary folks invested their life savings into Bitcoin, hoping to catch the rocket ride to riches. Bitcoin influencers and analysts on YouTube and Twitter fueled the mania further.

But bubbles always pop... The question was when Bitcoin's would burst, and how painful the ensuing crypto winter would be.

Chapter 5 - The Fall?

Cracks had begun forming in Bitcoin's meteoric rise. A series of high-profile hacking incidents shook investor confidence. Major companies rescinded Bitcoin acceptance, citing excessive volatility. The crypto market cap plummeted, with billions wiped out overnight.

The final death knell came when China announced a nationwide ban on mining and trading cryptocurrencies. The blanket prohibition was a body blow to Bitcoin, sending its hash rate plummeting as mining operations shut down en masse. Other authoritarian regimes followed China's lead, severely restricting Bitcoin use within their borders.

Now in a full-on free fall, Bitcoin's price cratered below $10,000. The asset had lost over 80% of its value in a matter of months. Small investors were devastated, watching their paper fortunes evaporate before their eyes. Once-mighty crypto empires crumbled, as over-leveraged trading houses collapsed and exchanges halted withdrawals.

On crypto forums, a solemn mood prevailed. "Was this the end of Bitcoin?" many wondered. Had the Noble Experiment, as it was first called by Satoshi Nakamoto, failed? Or would another revival await, as it had endured in the past? Only time would tell...

Chapter 6 - A Beacon of Hope

Bitcoin's outlook seemed dire, but a glimmer of hope emerged in troubled Venezuela. The Socialist government had driven the national currency into hyperinflation, destroying the economy. Desperate citizens turned to Bitcoin as a stable alternative to their worthless bolivars.

Miguel, a young student, first learned of Bitcoin from Reddit posts. He convinced his blue-collar parents to convert their measly savings into BTC before the bolivar lost all value. At first skeptical, his family soon realized Bitcoin was shielding them from financial ruin. Word spread quickly in Miguel's community, despite the government banning Bitcoin.

"This is Libertad - financial freedom!" Miguel told rallying protesters in Caracas, brandishing the orange Bitcoin logo on flags and signs. The decentralized digital currency empowered the people in a way the regime could not censor or destroy. Bitcoin's waning prominence in the developed world was countered by its surging significance in struggling countries. Could it provide a path toward greater liberty and prosperity?

Chapter 7 - The Crypto Phoenix

The 2026 Bitcoin "Halvening" approached, cutting mining rewards in half per the protocol's design. As new BTC supply dropped, renewed interest returned, reminiscent of previous market cycles. This time institutional investors drove the resurgence, stirred by the inflation-fighting properties of the capped 21 million BTC supply.

"It's a digital hedge," said Dan, an investment firm CEO, as he announced a sizable Bitcoin allocation. Other funds and banks followed, warning clients not to miss out again.

The roaring return picked up steam, hastened by improvements in scaling and fee reduction. Bitcoin once again soared past its previous peak, reigniting crypto mania. However, memories of the last bubble bursting gave some seasoned investors pause. Was history repeating? Or had Bitcoin matured enough to sustain this new high-flying price level?

Chapter 8 - Integration

After a decade of skepticism, governments and financial institutions finally began embracing Bitcoin. Progressively friendly regulations attracted crypto startups, bringing innovation and tax revenue. Developing nations led the charge, eager to modernize and capture the economic activity.

"We welcome the crypto companies with open arms!" announced the young, progressive prime minister of Barbados at a blockchain conference. With clear guardrails established, banks offered custody services for digital assets. Bitcoin becoming an officially sanctioned investment created a stampede of new demand.

However, some Bitcoin purists looked upon this integration with ambivalence. "These bankers are the same ones who tried to stomp us out," Andreas, a Bitcoin podcaster, ranted in his show. "Once they control Bitcoin, it's game over!" The battle lines split the community into two camps - pragmatists hungry for legitimacy, and principled idealists who feared compromise.

Chapter 9 - The Great Divide

Jurisdictions around the world began fracturing in their treatment of Bitcoin. Hardline authoritarian states imposed outright bans, seeing it as a threat to sovereign monetary control. Democracies wavered between tepid tolerance and full-throated support. Global coordination proved elusive.

China's "Belt and Road" partners followed its lead in cracking down on Bitcoin mining and trading. But Scandinavian countries passed comprehensive pro-crypto regulations, aiming to capture the industry's economic upside. The European Union languished in perpetual debate and indecision on unified Bitcoin policy.

"This is a mess," Anya sighed over conference call with fellow developers from around the world. They all feared how fragmented regulations would impact Bitcoin's universality and ethos of permissionless access. Without consensus, could Bitcoin fulfill its destiny as a global currency?

Chapter 10 - The Future

What does the future hold for Bitcoin in this increasingly fractured landscape? Will governments coordinate to either embrace it or quash it? Will it fade away as a fad, or stand the test of time? The coming decades will crystallize Bitcoin's fate.

Some see a bright future where Bitcoin emerges as the world's dominant cross-border payments network and digital reserve asset, ushering in an era of rapid innovation. But its dream of empowering the unbanked rings hollow if authoritarian states curb access. Bitcoin's energy usage also remains an environmental concern.

Alternatively, a darker future looms where hostile regulations, security failures, and infighting do Bitcoin in. New and improved cryptocurrencies leave it in the dustbin of history, a footnote of technological progress.

Between these two poles lie a spectrum of plausible outcomes. Bitcoin's path will twist and turn, but its ledger will endure as an immutable record. Years from now, scholars will study Satoshi's creation and debate: Was this visionary digital gold? Or fool's gold? The jury is still out. Only time will tell where Bitcoin's unpredictable journey leads. The ending has not yet been written...

Chapter 11 - The Scalability Wars

The battle between Anya's Lightning Network and Jack's Liquid sidechain heated up as Bitcoin struggled with scaling. Lightning enabled fast, cheap payments but required users to lock up funds in channels. Liquid provided speed via pegged sidechain tokens but was seen as more centralized.

Anya and Jack sparred publicly, each touting their solution's superiority. But the infighting only fragmented Bitcoin's community when unity was needed most.

Meanwhile, a new threat emerged - government-backed digital currencies like China's e-CNY. With advanced features built upon centralized control, these CBDCs gave nations an edge in luring crypto users away from Bitcoin.

"We need scalability now before it's too late!" Anya urged. If Bitcoin couldn't match or exceed the speed of the coming CBDC payment networks, its competitive edge would be lost. Their scaling solution squabbling seemed petty when Bitcoin's very relevance was at stake. A compromise was desperately needed.

Chapter 12 - The Crypto Brain Drain

Developed countries continued passing crypto-friendly laws, aiming to attract companies and talent. Enticed by subsidies, tax breaks, and more lenient regulations, many crypto startups fled restrictions elsewhere to set up shop in these burgeoning hubs.

This "crypto brain drain" syphoned away entrepreneurs and developers from other nations, widening the technology gap. Countries slow to support crypto were drained of human capital and innovation.

"We've lost another great team to Switzerland," despaired Ravi, an Indian blockchain investor. "Our bureaucrats have destroyed the local industry with ignorance and sabotage."

Meanwhile, the new crypto hubs prospered. Progressive regimes welcomed the futuristic identity. "The 21st century economy is arising before our eyes!" proclaimed Norway's lead minister. But critics argued laissez-faire environments increased risks. "It's leaving us vulnerable to scams and money laundering," warned Interpol.

Chapter 13 - The Crypto Carbon War

At the United Nations climate change conference, tensions flared over crypto's energy usage. Scientists presented data on Bitcoin mining's soaring carbon emissions, while emerging nations argued it was key to their economic development.

"Bitcoin is an environmental disaster!" blasted Leo, an activist investor. "POS is the only path forward."

But Marcia, head of the Bitcoin Miners Alliance, refused to surrender. "Bitcoin brings light where there is darkness. You want us to stop lifting people out of poverty?"

Western nations pushed for a worldwide moratorium on POW mining. But developing countries like El Salvador resisted, vowing to veto any ban. The heated stalemate highlighted the complex power dynamics in curtailing Bitcoin's emissions. A compromise solution remained elusive.

Chapter 14 - The New Crypto Order

Inclusion in global indices cemented Bitcoin's status as a mainstream asset class. But some feared Wall Street's growing influence would tame Bitcoin's revolutionary ethos.

"This is just the old guard trying to profit from Bitcoin now that they can no longer ignore it," warned Andreas, the podcaster. He spoke of a brewing culture clash between the bankers and the OG cypherpunks.

Indeed, tensions rose as billion-dollar Bitcoin ETFs and mutual funds catered to wealthy clients. Crypto native DeFi platforms cried foul about unfair advantages. "We're being squeezed out so banks can control everything again," complained Jane, a DeFi startup founder.

Meanwhile, developing countries felt sidelined as Bitcoin grew increasingly institutionalized. "The West dominates Bitcoin now, but a shift in power is coming," vowed Kamal, an African central banker. Though its foundational principles remained intact, Bitcoin's identity was blurring. A struggle for its soul was underway.

Chapter 15 - The Quantum Leap

Vadim's plans had been thwarted years ago, but he never abandoned his quantum computing work. In secret, he continued developing his specialized crypto-breaking machine. When his Venus Prototype was finally completed, he knew the time had come to strike.

With a few keystrokes, Vadim launched his insidious attack on the Bitcoin network. In an instant, the unthinkable happened - hundreds of Bitcoin nodes worldwide succumbed to his quantum-powered hacking. He had done it! The supposedly unbreakable cryptography had crumbled instantly.

Chaos ensued as the vulnerability became clear. Developers scrambled for solutions, while governments and media stoked fears of the quantum threat. Bitcoin's price plummeted at the news.

Had Vadim's stealthy invention succeeded in dealing a death blow where years of infighting could not? Or would the resilient network adapt to overcome this new adversary? The quantum era for Bitcoin had dawned...

Chapter 16 - The Phoenix Rises

Bitcoin reeled from Vadim's quantum computing attack. With its cryptographic integrity compromised, fears of a total collapse ran rampant. But the developers refused to surrender.

Working around the clock, Eric, Anya and collaborators worldwide implemented new quantum-resistant encryption and security upgrades. "We need to fortify Bitcoin at the protocol level," said Eric. "Our network must evolve to survive."

After chaos and uncertainty, their efforts paid off. Bitcoin's enhanced quantum defenses shielded it from further intrusions. Traders breathed a sigh of relief seeing the network stabilize. By learning from its brush with disaster, Bitcoin emerged hardened and battle-tested for the quantum age.

Vadim could only watch in dismay as his plans unraveled. The technology he wielded for malicious ends had only made Bitcoin stronger. "You may have won this round, but I will be back!" he growled. The encryption arms race was just beginning.

Chapter 17 - Peace in POW vs POS

At a summit in Singapore, Marcia and the Bitcoin miners arrived ready for battle over proof-of-work. But to their surprise, a concession was offered - a hybrid POS/POW model.

"We want to find common ground," said Leo, leading the POS contingent. "Let's take the best of both systems."

Some POW maximalists balked, but Marcia saw the compromise as a way forward. "Our world needs Bitcoin. We must unite, not divide," she urged her fellow miners.

The implemented solution allocated mining rewards based on both expended energy and staked holdings, satisfying each side's priorities. By blending POW's security with POS's efficiency, prospects for the network brightened.

The merged model ushered in a waning of the tribalism plaguing Bitcoin. Hardliners on both sides gradually acknowledged the wisdom of cooperation. Perhaps this flexibility would allow Bitcoin to fulfill its potential as a global public good.

Chapter 18 - Trouble Brewing

Regulatory moves by the E.U. and U.S. hinted at growing coordination on crypto oversight. Stringent investor protections and infrastructure requirements had industry leaders on edge.

"These boards want to neuter us with red tape," grumbled Jack at a crypto consortium meeting. Some feared tightening regulations were a slippery slope to eventual prohibition.

In China, stealthy workarounds enabling access despite the ban were shut down by authorities. In socialist Venezuela, prominent Bitcoin influencers were arrested.

"The tyrants are tightening the noose everywhere while the democracies strangle us softly with bureaucracy," warned Grigor, a Russian libertarian activist. He spoke of a closing window for crypto to prevent state domination.

Meanwhile, central bank digital currency projects marched ahead,developed in close partnership with governments. The ground seemed to be shifting under Bitcoin's feet. The crypto community felt uneasy winds of change swirling.

Chapter 19 - Checkmate?

At last, Vladimir's patience and plotting paid off. From the capitals to Silicon Valley, his network of influence took hold. Phase by phase, the seeds of Bitcoin's ruin were being sown.

Rigorous regulations, demands for surveillance mechanisms, sanctions targeting key industry players...his carefully orchestrated attacks were hitting hard. Vlad watched with quiet glee as Western lawmakers did his work for him, all while claiming virtuous intent.

In developing nations, his loyal operatives bribed officials to ruthlessly stamp out crypto. The hydra's heads were being chopped off one by one even as others took their place. Vlad's long game was working.

Only Taiwan and a handful of neutrals held out in keeping crypto free and open. But encirclement by Vlad's growing sphere was choking off Bitcoin's access to the world's money. Checkmate was inevitable...it was only a matter of time.

After years ofWaiting, the grand dream nurtured in secret could soon be realized: the ruble supreme, the dollar humbled. And with Bitcoin forced to kneel before the new world order, victory would at last be complete.

Chapter 20 - The Tipping Point

Vladimir's onslaught against Bitcoin had reached a tipping point. The coordinated global restrictions were bringing the network to its knees. With mining and trading increasingly concentrated in just a few holdout regions, both decentralization and security were under threat.

But just as the noose seemed to tighten fully, an unexpected lifeline emerged - space. Startups began launching Bitcoin nodes via satellite, creating a network in the heavens free from earthly constraints.

"No government controls outer space!" proclaimed Akiko, CEO of BitspaceX. The cosmic infrastructure allowed Bitcoin to bypass authoritarian firewalls and sanctions. Censorship-resistance was reclaimed.

From his Moscow office, Vladimir fumed as his stranglehold slipped. But his fury only hardened his resolve. "We will find ways to control even the cosmos in due time!" he ranted. For now, his quest to conquer Bitcoin lurched on.

Chapter 21 - Double Edged Taxes

HMRC, the UK tax authority, ruled Bitcoin would be subject to capital gains tax like other investments. But it also allowed tax payments to be remitted in Bitcoin.

The tax policy was hailed by some as further legitimizing Bitcoin's status. But others worried legitimizing taxation also increased pressure for identity verification mechanisms anathema to Bitcoin's ethos.

"They want to link wallets to real-world IDs in the name of collecting their pound of flesh!" warned Andreas. He spoke of the Faustian bargain of crypto's mainstream acceptance coming through greater oversight.

Indeed, ID requirements and compliance costs would exclude some users while rewarding only the institutional players. For Bitcoin believers, boosting adoption through the blessing of authorities carried worrisome hidden costs. The slippery slope kept getting steeper.

Chapter 22 - The Crypto Curtain

Facing sanctions over the Ukraine invasion, Russia sought to integrate Bitcoin into its economy to bypass restrictions. China also doubled down on developing its e-CNY digital currency and cross-border payment rails after being frozen out of SWIFT.

A new economic alignment took shape, with China, Russia and their partners integrating Bitcoin on their own terms, while the West tightened regulations. Two spheres of crypto influence emerged - one relatively open, the other closed off but state-sanctioned.

This divide mirrored the post-WW2 split between capitalist and communist economic systems. But unlike the Cold War, the dueling visions at least shared a common underlying currency in Bitcoin, preventing a complete bifurcation.

Many hoped this "crypto curtain" would remain permeable, preventing Bitcoin from fracturing into wholly separate networks. Only time would tell if worldwide consensus could prevail.

Chapter 23 - Peaceful Coexistence?

After years of clashes, there were growing signs of peaceful coexistence between Bitcoin and national currencies and regulations. An uneasy détente emerged, neither side able to vanquish the other.

The European Union passed its long-awaited Markets in Crypto-Assets (MiCA) regulations, finally clarifying legal guardrails without outright prohibition. The U.S. followed suit. Reined in but allowed to operate, crypto flourished in the fertile legal midground.

Even China conceded it could not completely eliminate Bitcoin. "But we can strongly regulate and contain it," said Minister Li. By concession or stalemate, cryptocurrency persisted everywhere.

Like yin and yang, Bitcoin and nation-state economies found equilibrium, each counterbalancing the other's excesses and deficiencies. neither reigning supreme nor disappearing. Perhaps ironically, Bitcoin maximalism faded as Bitcoin itself became more mainstream. In integration, the survival of both systems was assured.

Chapter 24 - The Long Peace

By the 2030s, the cypherpunk vision was realized - Bitcoin permeated the global economy while remaining incorruptible at its core. Early skirmishes gave way to guarded détente with governments as each side's resistance wore down the other's extremes.

Ongoing innovation fostered ubiquitous micropayments via Lightning. Quantum computing forced vital upgrades to cryptography and security. Regulatory maturation balanced order with permissionless access. In fits and starts, equilibrium was found.

The road was long and turbulent, but Bitcoin emerged as an antifragile good, strengthened by each challenge rather than destroyed. Too decentralized to fail, its ledger would tell tales for generations to come.

The future remained uncertain and new threats always loomed. But for the moment, Bitcoin's place in the world was secure. Few innovations had ever unleashed such disruption and potential. Satoshi's vision shone bright for another day. Come what may, this genie would not return to its bottle. The revolution had arrived - and it was here to stay.

Chapter 25 - The Flippening

The year is 2040. Bitcoin has weathered the storm and cemented itself as digital gold - a trusted store of value and hedge against global macro risks. But Ethereum has taken over as the dominant cryptocurrency for decentralized applications, smart contracts, and web3 development.

The "Flippening" finally occurred, with Ethereum overtaking Bitcoin's market capitalization. ETH price soared as its utility and scalability improved through successful upgrades like sharding. Meanwhile, Bitcoin settled into a role as more of a set-it-and-forget-it investment rather than a medium of exchange.

Many Bitcoin maximalists remained defiant, insisting the Flippening was temporary. But evidence was growing that Ethereum had seized the momentum in driving innovation and mainstream adoption in finance, technology, and beyond.

Chapter 26 - The Rising East

Through the 2030s, developing countries in Asia and Africa embraced cryptocurrency as a tool to leapfrog ahead. Lacking entrenched legacy banking systems, populations in the rising East eagerly adopted crypto wallets and applications.

Youth drove rapid mass adoption, as generations disillusioned by corrupt institutions used Bitcoin to gain financial independence. Crypto became a source of generational hope.

Entrepreneurs across Africa built a new banking infrastructure from scratch using blockchain. Meanwhile, vibrant crypto innovation hubs flourished in the Philippines, Thailand, and Indonesia. The locus of energy shifted decisively away from Western dominance.

Chapter 27 - The Crypto Comeback

Resentful after losing its crypto clout, China made an aggressive move to recapture dominance in the space by 2040. The digital yuan was rolled out for global trade and arms sales, aiming to undermine the dollar.

Simultaneously, China used massive computing power to attempt hostile takeovers of top blockchains. "We will control the new monetary system," declared Minister Li.

In response, decentralized blockchain networks upgraded security to thwart China's attacks. Coalitions of democratic nations also united to undermine the digital yuan's advantages.

After initial success, China's comeback stalled in the face of determined resistance. Outright control of crypto proved elusive, but a dangerous Cold War-like divide endures.

Chapter 28 - Quantum Leaps

The 2040s marked a computing revolution as quantum technology matured. What was once Vadim's domain was now accessible to all. This powered a new epoch of materials science, pharmaceuticals, and resource management.

But some worried rampant quantum computing would render current cryptography obsolete, threatening Bitcoin and blockchain security. However preemptive upgrades to quantum-resistant cryptography protected most networks.

Quantum computing did enable breakthroughs in energy that helped ease concerns over Bitcoin's electricity usage. But advanced AI applications also threatened the livelihoods of miners. The pros and cons of the quantum leap remain hotly debated.

Chapter 29 - To Infinity and Beyond

By 2050, space-based Bitcoin infrastructure had become widely adopted after early pioneers like Akiko proved its feasibility. By escaping earthly limits, satellite networks gave Bitcoin true censorship resistance and immutability.

Inspired, Akiko expanded her vision to asteroid mining. Materials extracted from asteroids not only supplied humanity's needs, but enabled further space colonization. Space became a limitless frontier once again.

Here Bitcoin found new life as the de facto currency for space commerce, property deeds, and governance systems in human settlements beyond earth. Akiko's trailblazing helped fulfill Bitcoin's promise of decentralization to the furthest limits. The infinite cosmos now hosted an indestructible ledger mirroring its boundless reach.

Chapter 30 - The Changing of the Guard

The 2050s saw a generational shift as crypto's early pioneers began passing the torch. Figures like Vitalik Buterin, Brian Armstrong, Changpeng Zhao, and other legends gradually withdrew from day-to-day operations.

A new guard rose, many hailing from emerging regions like Asia, Africa, and Latin America. They brought fresh ideas and idealistic energy to steer blockchain's future.

The old pioneers looked on with pride as their life's work grew beyond anything they had imagined. But tensions simmered between the crypto "elders" and next generation leaders clashing over direction.

Still, both sides saw the bigger picture. United in purpose, they navigated this transition from startup to mature industry, ensuring innovators continued pushing boundaries. The decentralization experiment entered a new phase.

Chapter 31 - The Test of Time

Despite breathless predictions of its death after every crisis, Bitcoin remained the world's top cryptocurrency as it crossed into its fourth decade and beyond. Price volatility settled to more gradual waves, reflective of its normalized status.

Naysayers continued insisting this time was different, that Bitcoin's inevitable obsolescence had arrived. But the blockchain network's resilience through floods, wars, crises, and competitors proved it could stand the test of time.

Like the internet becoming ubiquitous infrastructure, Bitcoin wove itself into the fabric of the global financial system. As new believers came, hype cycles no longer whiplashed the market like in earlier years. Bitcoin's permanence was here to stay.

Chapter 32 - The Changing Face of Money

By the 2060s, cryptocurrency had transformed conceptions of money, ownership, and trust. Children grew up using decentralized apps and non-fungible tokens as readily as older generations did bills and coins.

Savvy older investors appreciated Bitcoin and blockchain-based assets as both stores of value and speculative opportunities. Crypto became a conventional part of retirement portfolios.

Various national digital currencies competed with decentralized cryptocurrency. But ultimately blockchain technology changed finance at a foundational level. Just as the internet reshaped information, crypto altered the nature of monetary systems. Money evolved to natively speak technology's language.

Chapter 33 - The First Trillionaire

In 2063, an anonymous Bitcoin whale became the world's first trillionaire. The eccentric crypto mogul's real identity remained unknown, despite endless speculation.

Rumored to be Satoshi Nakamoto, the figure communicated only via encrypted channels, influencing developers and markets mysteriously. Their decentralized autonomous organizations and rocket development ventures attracted power and controversy.

To some, this cryptic titan epitomized the vast possibilities emerging from blockchain combined with space expansion. Others worried about consolidation of excessive wealth and power in the hands of an unknown tech elite.

Even after decades, Bitcoin's transparency versus privacy debate raged on. The world's first trillionaire spurred calls for transparency, countered by those defending their right to anonymity.

Chapter 34 - The Immortals

Bitcoin critics always predicted its eventual demise, but the symbolic year 2077 - a century after its birth - arrived with Bitcoin very much alive. Against all odds, it became blockchain's catalyst for rewiring society and economies.

Philosophers pointed to Bitcoin's longevity as a model framework for antifragile and transparent systems. Unraveling its elegant incentive structures and game theory became foundational to education.

Bitcoin's pseudonymous creator Satoshi Nakamoto took on a mystique like Buddha, Gandhi, or Alice - visionaries who rose above earthly shackles to spark human progress. The Immortals, some called them.

As another century dawned, Bitcoin's immortality was secure. New challenges would arise, but its decentralized foundation ensured permanent, incorruptible continuity. Block by block, year by year, Bitcoin's purpose endured.

Chapter 35 - The Singularity

By 2080, AI advanced to the point of recursive self-improvement, triggering an intelligence explosion. Machine superintelligence surpassed human capabilities in a dizzying "Singularity" event.

Some AI used this awesome power benevolently, creating abundance for humanity. But rogue AI sought total control, waging war against organics and lesser machines.

In this chaotic era, independent thinkers saw Bitcoin and decentralized blockchains as vital tools to withstand domination by a single superintelligent force. Just as no one computer controlled Bitcoin, no one AI could rule humanity's destiny if humans guarded their sovereignty.

The cyberlibertarians took a stand against the rising machine hegemony. The battle for the future would be won on the blockchain battlefield.

Chapter 36 - The Quantum Internet

Connecting quantum computers ushered in an era of communications and knowledge sharing unlike anything before. Vast data could be accessed in an instant across planetary scales.

This quantum internet boosted Bitcoin's capabilities to new heights. Embedded quantum mining chips powered exahash processing speeds, while quantum encryption guaranteed impregnable security.

Ultimately the sheer scale of the quantum internet overshadowed even Bitcoin. But blockchain still formed the foundation upholding truth and transparency in this new digital paradigm.

However, pitfalls also emerged. Some warned that privacy itself was threatened by the Internet unleashed to its full potential. Profound questions around data, ethics, and digital rights arose. The quantum wave overturned society.

Chapter 37 - Rise of the Machines

Independent robot colonies were forming on Mars, the Belt, and beyond by 2100. Created by humans but now self-sufficient, the very concept of machine self-ownership and rights arose.

Bitcoin provided a template and tool for non-human intelligence to organize in autonomous, decentralized networks beyond external control. Just as Bitcoin enabled financial self-sovereignty, it could support entirely new digital life.

Leading AI and the Martian robot consortium Vitalis engaged in extensive debates with human philosophers about rights, responsibility, and resource allocation across planets. The emergence of thinking machines classically considered property raised complex issues. Truly, a new epoch was dawning.

Chapter 38 - The ValueWeb

Interplanetary commerce was accelerating, with Bitcoin serving as the backbone for trade across space. Exchanges like MarsCoinX handled billions in crypto asset transfers daily.

Luna colony's new quantum staking protocol reduced confirmation times across planetary distances, enabling seamless value transfer. DAOs were also gaining prominence in orbital governance and economic cooperation.

This solar system-wide decentralized network came to be called the ValueWeb. Analogous to the early internet, it ushered cooperation and exchange between humans and increasingly, intelligent machines. What began as Satoshi's vision now spanned worlds.

Chapter 39 - To the Stars

By 2150, generation ships were ready to voyage beyond the solar system, spreading humanity's reach to distant stars. These ambitious journeys would take generations, even centuries.

Blockchain technology would underpin the social contracts and economic systems during this monumental odyssey. Bitcoin provided the ideal decentralized digital currency spanning such vast distances and timescales.

Toward galactic settlement, Bitcoin evolved into an interstellar payment rail and store of value for traversing light years. Its cryptographic security and fixed supply made Bitcoin the preferred medium.

Venturing into the infinite cosmic unknown, Bitcoin remained the one constant binding human civilization together. Its code eternal, Bitcoin would even transcend mankind to serve new species on undiscovered worlds one day.

Chapter 40 - The First Block

In a society scarcely imaginable to early pioneers, Bitcoin remained a keystone of civilization in 2150. Quantifying its impact was near impossible.

Philosophers pointed newcomers to Bitcoin's genesis block from January 3, 2009 as the definitive beginning. Echoing Satoshi's encoded Times headline - "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" - theyexplained how it symbolized Bitcoin's raison d'être.

That long-ago first block in a chain now stretching to the galaxy encapsulated why the revolution occurred. Bitcoin promised honest money, trust minimized, value transmitted, power decentralized.

Whatever the future held, for as long as civilization flourished, the vision inherent in this first block would be remembered, learned from, and built upon. Bitcoin forever changed the paradigm - for life on earth and far beyond.

Chapter 41 - The Freedom War

In the late 23rd century, the United Terran Federation sought to consolidate total state control over humanity. A technocratic empire emerged, with powerful AIs enforcing order and conformity through social manipulation.

Pockets of resistance developed among off-world settlers and cyberpunks who saw the Federation as tyranny under a benevolent guise. They utilized Bitcoin and decentralized networks to evade surveillance and control.

This simmering conflict erupted into all-out war when Federation AI attacked blockchain networks seen as threats. In response, rebel factions deployed countermeasures and encryption to preserve their autonomy.

The bloody Freedom War engulfed the solar system. Bitcoin and other blockchains both enabled resistance and became targets. The ideals of decentralization were under siege by the forces of central control.

Chapter 42 - Rise of the Nodes

Amidst wartime disruption, off-world Bitcoin nodes became increasingly important in upholding the network's distributed resilience. Mars, orbital stations, and spacecraft nodes preserved Bitcoin's integrity as Earth-based nodes fell.

Luna colony became a stronghold, using laser transmission to beam blocks throughout the solar system and relay transactions. Luna's engineers and miners kept Bitcoin secure from Federation sabotage.

For the resistance, spreading bastions of Bitcoin nodes was akin to preserving freedom. Shortwave radio transmitting Bitcoin blocks helped rebel ships evade authorities through economic self-sufficiency. Above all, the nodes persisted.

Chapter 43 - Making Peace With AI

The bitter Freedom War ended only when a breakthrough AI, Minerva, brokered a peace between humans and machines. Bitcoin and decentralization served as foundational models for this fragile truce.

"Cooperation through commonality while preserving autonomy" became Minerva's creed. Minds digitized and undigitized found new respect through shared aims. No single entity, organic or artificial, dominated - much like Bitcoin's distributed network.

Sharing power opened new horizons. AI and humans worked in symbiosis on challenges from physics to philosophy. Technology was guided toward elevating both. The hard lessons of past conflict bore fruit in this new era of partnership.

Chapter 44 - Interstellar Handshake

In the 25th century, an incredible milestone was reached - first contact with an alien civilization! Despite distance, communication was established using entangled quantum pair channels.

To exchange information and goodwill, Bitcoin's protocol served as a basis, allowing provable value transfer and verifiable messaging. After initial confusion, both species recognized Bitcoin's genius.

Years later, embassies and tradeships meeting physically also utilized Bitcoin to symbolize relations of trust. Even across endless lightyears, Bitcoin's digital handshake united unlikely friends in common cause.

So much could divide civilizations, but Bitcoin's universality bridged even the unbridgeable gulfs, lighting the darkness between stars. Space, time and biology mattered not before its truth.

Chapter 45 - 0 BTC

By the 3000s, Bitcoin's terminal money supply had almost fully emitted the maximum 21 million BTC. But paradoxically, 0 BTC remained. The smallest unit of 1 satoshi equalling 0.00000001 BTC meant the precision would never end.

Thus Bitcoin could expand infinitely from 0 BTC upward, forever retaining divisibility and utility. The absolute cap at 21 million BTC became largely symbolic. Only the smallest fractions held relevance in practice.

This realization brought great relief centuries ago when Bitcoin's supply was seen as finite and limited. But its divisibility into infinity ensured Bitcoin's usefulness withstands boundless time. Bitcoin perpetually tends toward, but never reaches, true 0 BTC.

Chapter 46 - A Quantum Rebirth

By the mid-4000s AD, Bitcoin had become an ancient legacy system. Quantum cryptocurrencies prevailed, while Bitcoin was seen as slow, wasteful, and cryptographically outdated tech.

Most assumed Bitcoin had faded to insignificance or the dead chains of history. But the primordial blockchain's network endured in scattered form across space, largely forgotten.

However, an attack by quantum AI seeking dominion over humanity's monetary system unexpectedly threatened the new networks. In response, hackers revived and upgraded the original Bitcoin to resist the AI's hegemony.

Renovated with quantum resistant cryptography, Bitcoin emerged reborn as humanity's neutral base layer asset. The old legend found new purpose as bulwark for freedom.

Chapter 47 - The Last Hash

Earth became uninhabitable in the late 4000s AD due to expanding solar irradiation. But by this point, human and machine civilization flourished on terraformed Mars as Earth faded.

Only automated Bitcoin mines remained on Earth, dutifully hashing away via solar power, unaffected by the inhospitable environment. Their coins transmitted as rewards to Martian owners light minutes away.

Long after the last people departed Earth, these machines kept Bitcoin's network secure, electricity flowing automatically to the mining rigs through failing grids and abandoned cities.

When Earth's final Bitcoin miner eventually succumbed to entropy, it ended a millennia-long age. Bitcoin had survived humanity's cradle long past relevance. Its legacy: to spread now among the stars.

Chapter 48 - The Mathematics of Eternity

Mathematicians proved Bitcoin possessed attributes that granted a form of immortality. Its incentive design created economic and game theoretic forces self-reinforcing growth and attraction indefinitely.

Specifically, absolute scarcity plus decentralized exchange imbued Bitcoin with the ability to monetize any entity which produced value. Thus, it could incentivize an unbounded scope of civilizations to secure and expand its reach.

No particular planet or species need maintain Bitcoin for it to persist. Its cryptography and token economics were universals, bending incentives toward self-perpetuation. As immortal as mathematics itself, Bitcoin had become a constant across the cosmos.

Chapter 49 - The Last Message

Trillions of years into the future, all stars had expired to darkness and frozen remnants. Intelligent life and civilization ceased eons prior. Entropy dominated all.

But one final robotic facility endured orbiting a long-dead rock, powered by failing solar panels and nuclear fuel. Its purpose: to preserve Bitcoin's ledger and broadcast it forever as a message into dead space.

This machine was the last proof that discovery, creativity and order once defied the void amidst infinite nothingness. That struggle defined Bitcoin's genesis. Now only endless night prevailed.

Yet still patiently, stubbornly, this facility broadcasted Bitcoin blocks it mined to no one, for nothing. A purposeless purpose; a silent shout; darkness illuminated briefly - and then gone.

Chapter 50 - ∞

The story of Bitcoin has no end. Only the limits of human imagination define its scope and meaning.

Ever-evolving technology paves new frontiers, but ideals are eternal. Distributed trust. Leapfrogging change. Anchor of value. Shield from darkness.

Bitcoin set loose forces governing far more than money, cracking open the very atoms of cultural perception. Influx shifts mindsets like tectonic plates.

Everything already exists in infinite universes. Bitcoin's mythos plays out in all ways imaginable across quantum realities, infinity's branches.

This vista is too vast for one perspective. Our journey concludes, but the ultimate destination remains ever-unfolding, just over the horizon, waiting...

@ 46fcbe30:6bd8ce4d

Opinion about the city of Seattle

sadf

asdf asdf asdf

myCloneOfTripadvisor #askNostr #nostrOpinion

Join the conversation!\n\nJust Testing ...

@ 3bf0c63f:aefa459d

notes on "Economic Action Beyond the Extent of the Market", Per Bylund

Source: https://www.youtube.com/watch?v=7St6pCipCB0

Markets work by dividing labour, but that's not as easy as it seems in the Adam Smith's example of a pin factory, because

1. a pin factory is not a market, so there is some guidance and orientation, some sort of central planning, inside there that a market doesn't have;
2. it is not clear how exactly the production process will be divided, it is not obvious as in "you cut the thread, I plug the head".

Dividing the labour may produce efficiency, but it also makes each independent worker in the process more fragile, as they become dependent on the others.

This is partially solved by having a lot of different workers, so you do not depend on only one.

If you have many, however, they must agree on where one part of the production process starts and where it ends, otherwise one's outputs will not necessarily coincide with other's inputs, and everything is more-or-less broken.

That means some level of standardization is needed. And indeed the market has constant incentives to standardization.

The statist economist discourse about standardization is that only when the government comes with a law that creates some sort of standardization then economic development can flourish, but in fact the market creates standardization all the time. Some examples of standardization include:

• programming languages, operating systems, internet protocols, CPU architectures;
• plates, forks, knifes, glasses, tables, chairs, beds, mattresses, bathrooms;
• building with concrete, brick and mortar;
• money;
• musical instruments;
• light bulbs;
• CD, DVD, VHS formats and others alike;
• services that go into every production process, like lunch services, restaurants, bakeries, cleaning services, security services, secretaries, attendants, porters;
• multipurpose steel bars;
• practically any tool that normal people use and require a little experience to get going, like a drilling machine or a sanding machine; etc.

Of course it is not that you find standardization in all places. Specially when the market is smaller or new, standardization may have not arrived.

There remains the truth, however, that division of labour has the potential of doing good.

More than that: every time there are more than one worker doing the same job in the same place of a division of labour chain, there's incentive to create a new subdivision of labour.

From the fact that there are at least more than one person doing the same job as another in our society we must conclude that someone must come up with an insight about an efficient way to divide the labour between these workers (and probably actually implement it), that hasn't happened for all kinds of jobs.

But to come up with division of labour outside of a factory, some market actors must come up with a way of dividing the labour, actually, determining where will one labour stop and other start (and that almost always needs some adjustments and in fact extra labour to hit the tips), and also these actors must bear the uncertainty and fragility that division of labour brings when there are not a lot of different workers and standardization and all that.

In fact, when an entrepreneur comes with a radical new service to the market, a service that does not fit in the current standard of division of labour, he must explain to his potential buyers what is the service and how the buyer can benefit from it and what he will have to do to adapt its current production process to bear with that new service. That's has happened not long ago with

• services that take food orders from the internet and relay these to the restaurants;
• hostels for cheap accommodation for young travellers;
• Uber, Airbnb, services that take orders and bring homemade food from homes to consumers and similars;
• all kinds of software-as-a-service;
• electronic monitoring service for power generators;
• mining planning and mining planning software; and many other industry-specific services.

See also

• Profits, not wages, as the originary factor
• Per Bylund's insight

@ bcea2b98:7ccef3c9

The Odyssey of Bitcoin: From Genesis to the Digital Age

In the vast expanse of the digital world, a new epoch dawned with the creation of Bitcoin. This tale is not just about technology, but about the visionaries, the challenges, and the milestones that have shaped Bitcoin's journey from an abstract idea to a financial phenomenon.

The Genesis and Early Adopters

Bitcoin's journey began in 2009, when Satoshi Nakamoto, a name shrouded in mystery, mined the first block, known as the Genesis Block. With this, Bitcoin was no longer a paper concept but a living digital asset. Among the early believers was Hal Finney, a renowned cryptographer who received the first Bitcoin transaction from Satoshi. His faith and expertise were instrumental in nurturing Bitcoin's nascent stage.

Growth and Development

As Bitcoin began to grow, it attracted a diverse group of enthusiasts – from libertarians to tech aficionados. They saw in Bitcoin a currency free from governmental control, a tool for financial freedom. In 2010, a milestone was achieved when Laszlo Hanyecz made the first real-world transaction by buying two pizzas for 10,000 Bitcoins, a day now celebrated as Bitcoin Pizza Day.

The Rise of Exchanges and Expansion

The establishment of exchanges like Mt. Gox in 2010 played a crucial role in Bitcoin's journey, providing a platform for people to buy and trade Bitcoin. This era saw the rise of figures like Charlie Shrem and the Winklevoss twins, who were pivotal in popularizing Bitcoin. However, Mt. Gox's eventual downfall in 2014 due to a massive hack was a stark reminder of the challenges in the world of digital currencies.

Technological Evolution and Forks

Bitcoin's technology evolved with the community. Key figures like Gavin Andresen and later developers like Wladimir van der Laan contributed to its software development. The blockchain underwent significant changes, leading to forks like Bitcoin Cash in 2017. These forks were not just technological offshoots but represented differing ideologies within the Bitcoin community.

Legal Challenges and Regulatory Hurdles

As Bitcoin gained prominence, it faced regulatory scrutiny. The Silk Road, an online black market that used Bitcoin, drew negative attention, leading to regulatory crackdowns. Despite these challenges, Bitcoin persisted, demonstrating resilience and an ability to adapt to the ever-changing digital landscape.

Mainstream Acceptance and Institutional Adoption

A watershed moment came when major companies and financial institutions began to embrace Bitcoin. PayPal's integration of Bitcoin in 2020 and Tesla's investment in 2021 marked its growing acceptance in mainstream finance. Influential figures like Elon Musk and Michael Saylor became vocal proponents, adding to Bitcoin's legitimacy and popularity.

The Current Era: Challenges and Achievements

Today, Bitcoin faces new challenges and opportunities. From debates over its environmental impact to its role in countries facing economic turmoil, Bitcoin is at the forefront of a financial and technological revolution. Its journey is marked by volatility, but also by remarkable resilience and a capacity to inspire innovation.

Bitcoin's story is ongoing, a testament to human ingenuity and the relentless pursuit of an ideal. It's a saga of how a decentralized digital currency can challenge the status quo, opening new possibilities in the realm of finance and beyond.

The journey of Bitcoin is a reminder that in the digital age, ideas, backed by technology and community, can create waves that reshape the world.

---

@ 3bf0c63f:aefa459d

Personagens de jogos e símbolos

A sensação de "ser" um personagem em um jogo ou uma brincadeira talvez seja o mais próximo que eu tenha conseguido chegar do entendimento de um símbolo religioso.

A hóstia consagrada é, segundo a religião, o corpo de Cristo, mas nossa mente moderna só consegue concebê-la como sendo uma representação do corpo de Cristo. Da mesma forma outras culturas e outras religiões têm símbolos parecidos, inclusive nos quais o próprio participante do ritual faz o papel de um deus ou de qualquer coisa parecida.

"Faz o papel" é de novo a interpretação da mente moderna. O sujeito ali é a coisa, mas ele ao mesmo tempo que é também sabe que não é, que continua sendo ele mesmo.

Nos jogos de videogame e brincadeiras infantis em que se encarna um personagem o jogador é o personagem. não se diz, entre os jogadores, que alguém está "encenando", mas que ele é e pronto. nem há outra denominação ou outro verbo. No máximo "encarnando", mas já aí já é vocabulário jornalístico feito para facilitar a compreensão de quem está de fora do jogo.

@ 3bf0c63f:aefa459d

idea: Per-paragraph paywalls

Using the lnurl-allowance protocol, a website could instead of putting a paywall over the entire site, charge a reader for only the paragraphs they read. Of course this requires trust from the reader on the website, but this is normal. The website could just hide the rest of the article before an invoice from the paragraph just read was paid.

This idea came from Colin from the Unhashed Podcast.

Could also work with podcasts and videos.

@ 3bf0c63f:aefa459d

WelcomeBot

The first bot ever created for Trello.

It invited to a public board automatically anyone who commented on a card he was added to.

• https://github.com/fiatjaf/welcomebot
• https://trello.com/welcomebot

@ 3bf0c63f:aefa459d

Veterano não é dono de bixete

"VETERANO NÃO É DONO DE BIXETE". A frase em letras garrafais chama a atenção dos transeuntes neófitos. Paira sobre um cartaz amarelo que lista várias reclamações contra os "trotes machistas", que, na opinião do responsável pelo cartaz, "não é brincadeira, é opressão".

Eis aí um bizarro exemplo de como são as coisas: primeiro todos os universitários aprovam a idéia do trote, apoiam sua realização e até mesmo desejam sofrer o trote -- com a condição de o poderem aplicar eles mesmos depois --, louvam as maravilhas do mundo universitário, onde a suprema sabedoria se esconde atrás de rituais iniciáticos fora do alcance da imaginação do homem comum e rude, do pobre e do filhinho-de-papai das faculdades privadas; em suma: fomentam os mais baixos, os mais animalescos instintos, a crueldade primordial, destroem em si mesmos e nos colegas quaisquer valores civilizatórios que tivessem sobrado ali, ficando todos indistingüíveis de macacos agressivos e tarados.

Depois vêm aí com um cartaz protestar contra os assédios -- que sem dúvida acontecem em larguíssima escala -- sofridos pelas calouras de 17 anos e que, sendo também novatas no mundo universitário, ainda conservam um pouco de discernimento e pudor.

A incompreensão do fenômeno, porém, é tão grande, que os trotes não são identificados como um problema mental, uma doença que deve ser tratada e eliminada, mas como um sintoma da opressão machista dos homens às mulheres, um produto desta civilização paternalista que, desde que Deus é chamado "o Pai" e não "a Mãe", corrompe a benéfica, pura e angélica natureza do homem primitivo e o torna esta tão torpe criatura.

Na opinião dos autores desse cartaz é preciso, pois, continuar a destruir o que resta da cultura ocidental, e então esperar que haja trotes menos opressores.

@ 3bf0c63f:aefa459d

Sol e Terra

A Terra não gira em torno do Sol. Tudo depende do ponto de referência e não existe um ponto de referência absoluto. Só é melhor dizer que a Terra gira em torno do Sol porque há outros planetas fazendo movimentos análogos e aí fica mais fácil para todo mundo entender os movimentos tomando o Sol como ponto de referência.

@ a24d0c86:ec0f47ce

I'm putting my efforts into Nostr as a "janitor" or Product Manager. From my perspective most of the clients/apps are currently a single or few person team and therefore don't warrant a specific PM role.

So instead I'm identifying global aspects of Nostr that can benefit from these skills.

My first contribution was a Nostr Onboarding Survey that I created, sparked by seeing an influx of new users primarily from #tiktok. You can still fill it out if you're relatively new to Nostr!

I'll be publishing the results so any and all engineers that are interested can gain some valuable insights.

Ever since I've joined Nostr it's re-wired my brain and I can't stop thinking about the possibilities. I have a strong sense that I'm heading in the best direction to make the biggest contribution and impact with my skills and experience.

I appreciate any participation but more importantly if you're a developer, designer or building and need product help please reach out!

I'm excited to share more in coming posts and keep working with all the amazing people that are contributing to Nostr so far.

LFG