CandaceFoleyQBW

Music

**What is a block party?**

It's when you team up w/ folks to try and solo mine a bitcoin block.

**Upendo is a block party auction**

You bid on hashrate and mine with other bitcoiners ✅ 
We will mine with 2,100 TH/s on Saturday, November 30th ⛏️
The goal is to find a block and earn 3.125 bitcoin + tx fees 🎉

To get a spot on the party, you have to win a hashrate auction.

Hashrate will be provided via [Rigly](https://rigly.io) and we will use [CK Pool](https://solo.ckpool.org/) to solo mine.

**Bonus hashrate**

The block party earns bonus hashrate for each new bidder, and so the odds get better and better over the course of the auction ... so get your spot early!

Upendo - Mining Block Party Auction

BooksAndArticles

Jeff Booth

JorgeHaydenX2E

I kind of want to avoid artificial friendship stuff. I think it's a trap.

We don't have follower counts in real life.

bitcoin

# Will you be okay if hyperbitcoinization doesn't happen for a thousand years?

How about two thousand?

The Christians have been waiting for their Second Coming for almost that long. 

I am frequently struck by the similarities between bitcoin and religion. Most recently, I realized that many of us are expecting hyperbitconization on a snappy timeline. Like, it's okay if it doesn't happen next year, but goddammit if I'm still using fiat in 10 years.

And if you have ever had the dubious pleasure of reading the letters of the sainted Paul and friends, you get the sense that a lot of the early Christians expected a similar timeline for the return of the recently dead and risen-again Jesus Christ.[^1]

[^1]: To list off a few instances: Let your reasonableness be known to everyone. The Lord is at hand ( (Philippians 4:5)), You also, be patient. Establish your hearts, for the coming of the Lord is at hand. (James 5:8), And he said to me, “Do not seal up the words of the prophecy of this book, for the time is near. (Revelations 22:10) The end of all things is at hand.  (1 Peter 4:7)

To be fair, some transitions *are* pretty fast: hyper-internet-ization happend in a flash; [cars replaced horses in a couple decades](https://www.taketotheroad.co.uk/when-did-cars-replace-horses/); electrification took a little longer, [but still less than a human lifespan](https://mrelectric.com/blog/the-history-of-electricity-history-of-electricity-timeline).[^2]

[^2]: Not interested in nit-picking the idea that people were experimenting with electricity for centuries before electrificaiton of households took off in the 20th Century. Technology builds on past work, but I'm talking about once a product appears, how fast does it take to spread.  

So what's to say ours won't be like that? Maybe it will. but I'm more interested in what we're going to do in the mean time--because maybe it won't.

# How would you change your behavior if you were certain hyperbitcoinization wasn't going to happen this century?

Bitcoin is a tool. It has some amazing properties:

- It's internet-native money: you can send it anywhere on earth at anytime and it moves really fast.
- It's something you can truly own.
- It's transparent and you can know exactly what's happening with it.
- It doesn't require anyone else's permission.

These properties are useful today. You don't have to wait to take advantage of them. Here's a few examples of things you can do with bitcoin:

- Save up a pile because your fiat currency might devalue faster than expected.
- Learn how to coinjoin because your government might outlaw what you want to buy or sell.
- Spend it at a small-business because middle-men are getting more powerful.
- Get used to earning it because your bank might close your accounts.

The Christians have changed the world while they've been waiting for the second coming. No reason we can't do the same while we wait for hyperbitcoinization. Who knows how long we might have?

Hyperbitcoinization and the Second Coming of Our Lord Jesus Christ

devs

Don't pay now (in fiat) what you can pay later

MaureenHardyRL8

We do things a bit odd here: "MVB" minimum viable beta. Try to burn as little devel and support time while you try out ideas. These things take time to build on btc, so keep burn low and "days alive" long. We have zero W2 employees including me and no spending commitment greater than 30 days. 

Dear experienced stackers and newbies,

How are you doing? How is your experience on SN these 4-5 first days of Million Sat Madness?

How do you feel waking up in the morning and seeing no daily rewards for your posts, comments, and zaps?

Probably, the experienced stacker will answer that they are not receiving daily rewards, but they are working hard to rank higher for the winning one prex of MSM.

But I'm curious to know how newbies are going to answer this question. I mean, being aware that they cannot by no means compete with the experienced stackers for being ranked higher, how do they feel about not receiving daily rewards for the entire month?

Speaking from my perspective, I won't make it into the first 64 positions for the month-end rewards. It makes me feel uncomfortable enough.

I would also share another thought that came to my mind these days. We talk about the beauty of Bitcoin and blockchain, which are a decentralized system, while the experiment of MSM looks like an attempt to centralize the rewarding system of Stacker News.

The daily reward system is more decentralized, while the Million Sat Madness is a more centralized system. In the first one, everyone who is active by posting, commenting, and zapping has a chance to be rewarded every day, even if the rewards could be very low or very high, but all have a chance if they are active. For that reason, I consider it a decentralized system. In the second one, at the end of the month, only those ranked in the top 64 positions will be rewarded, while the rest will receive no rewards regardless of their activity. That's why this sounds like a centralized reward system to me.

I have the impression that if MSM continues in the coming months, a lot of SN users (especially newbies) will lose their interest and will leave the forum. And I'm not sure if this is a good thing for SN.

I would prefer the first one, i.e. the daily rewards, because everyone can be rewarded: newbies with small amounts and the experienced ones with high amounts.

What do you think, Stacker?

Daily Rewards vs Million Sat Madness

> **I'm not the creator of the phoenixd-lnurl project** nor affliated with it, moreover I couldn't find the creator here on Stacker News. I know that the guy can be found on Nostr behind the npub `npub1raftzmju5gq77twqxrumv5gnweew2t0p4v5upv8kku4vsz4j8jzq3tgns2` and [here is his website](https://1f52b.xyz/). He has all the credits for this. 

## Background

A few days ago I was checking my nostr feed and somehow I run into the following project:

https://github.com/AngusP/phoenixd-lnurl

that is based on the new-born phoenixd server, the new ACINQ product that basically mimics what the android phoenix wallet does, but it is deployable on a web server and potentially runs 24/7.

## The process

Since I have a VPS with some dummy services on it, I decided to try phoenixd and this wrapper, just to understand the potential of such a product.

> For simplicity I'll call the phoenixd  daemon "node" from now on.

The first thing to do is clearly to have some sort of server/VPS with a static IP and a domain. You'll need the domain to deploy the lnurl webpage that shows the  lnurl and your lnaddress.
Once you set up the VPS you can decide to follow two different paths:

1. Deploy the node using docker, which is pretty straightforward and all the information is on the README file of the project;
2. Deploy the node by installing by hand phoenixd server, the dependencies of phoenixd-lnurl and setting up manually everything.

I decided to go for the second methodology.

### Phoenixd server

Installing phoenixd server is very easy, the *get started* section of the website explains step-by-step the deploy process so [take a look at it](https://phoenix.acinq.co/server/get-started). Once you're done with the installation of phoenixd server you'll have at hand two scripts, **phoenixd** and **phoenix-cli** and if you run phoenixd for the first time it'll generate your new phoenix server node, generating  the 12 seed words and setting up everything that is needed. Just rememeber to backup the seed.dat file (containing your 12 words seed), you'll find it in the ~/.phoenix folder.

Last thing I suggest to do is to add to the path the folder containing  **phoenixd** and **phoenix-cli**.

### Phoenixd-lnurl wrapper

Once the server installation is completed and the scripts are on your path, its time to proceed with the installation of the wrapper that will enable you to have a static webpage and an lnaddress  directly linked to your new created node.

Go to the [project repository ](https://github.com/AngusP/phoenixd-lnurl) and clone the repository in your favourite folder, then `cd` into the newly created repository folder,
At this point, you need to check one thing before going ahead: you need to verify that your system has an installed python version equal or newer than the python3.10. You can check that by writing `python --version`.
This is needed because some commands included in the `run.sh` script for the wrapper need  this specific (or newer) version of python, otherwise the `run.sh` script will fail every time with an `TypeError`.

If your python version respects the requirement explained above, then you can procede with the creation of a new virtual environment, recalling to use the python3.10 version, and install the requirements as explained in the README.


### Config file 

At this point you should have the phoenixd-lnurl folder and an **activated** python environment with all the requirements. In the same folder you should create an phoenixd-lnurl.env file and copy the content of the phoenixd-lnurl.env.example. This env file is very important because in it you'll define:

- the `PHOENIXD_URL`, that is an url containing your username, the http password (that you can find in ~/.phoenix/phoenix.conf), the localhost and the port that will be used to communicate with the node instance. The final form of this parameter is `http://<username>:<http_password>@127.0.0.1:<port>`. You can check the hostname and the port number by reading the content of the `run.sh` script in the same folder;
- your username (then used for the lnaddress);
- the hostname that will serve the invoices  needed by the LNURL,   which is also the domain that will serve the webpage showing your LNURL QRcode;
- some other settings about the min and max amounts that the LNURL can receive;
- your nostr pubkey, that will appear in the same webpage.

### Nginx settings

As of now, the wrapper should be set up as intended and you can even start it by running `./run.sh` in your terminal; if you run both the phoenixd daemon and the run.sh script your lnaddress will be able to receive sats. in order to run also the LNURL webpage you'll need to tickle a bit with nginx.

If you're running already a web server you should be already aware of how to tickle with nginx, anyway I recommend to take a look at [this guide](https://landchad.net/basic/nginx/) that will easily explain to you how to edit the nginx settings. Just remember that the `server` settings that the README file recommends to use must be inserted in the file corresponding to the domain you'll use that is contained in the `/etc/nginx/sites-available/` folder. The suggested settings for nginx already include the new landing page for the LNURL QRcode, so you can simply copy-paste everything.

### Systemd services

The final thing you need to do is to create two systemd services (if you're using systemd), one for the phoenixd server daemon and one for the `run.sh` script. The project comes with a suggested systemd service template that you can easily edit according to where these files are located in your filesystem. 

## Final remarks

Now by navigating to your `https://domain.com/lnurl` you should be able to see a freshy colorful page with your LNURL QRcode in the middle and the lightning address. And this is it!

The process is fairly simple and does not require a lot of work to set this up, nonetheless you should pay attention to a few elements:

1. Phoenixd server is still a trust-minimized node that relies on ACINQ node for liquidity management and its overall functioning. As for the mobile wallet, channels are opened with ACINQ as a peer but as an additive feature phoenixd comes with the possibility of receiving some sats even without having a channel opened. This can work only for very small amounts, since phoenixd server 'understands' that the sats are not enough to open a channel with a swap and thus trusts momentarily ACINQ for holding these sats on your behalf.
2. Phoenixd is a very new product and can have bugs that could lead to loss of funds. Moreover, phoenixd-lnurl is an alpha solution **built on top of a beta product**...you can easily understand that the level of insecurity of the overall structure requires to be very careful and not going mad by using substantial bitcoin amounts.
3. As for an LN full node, phoenixd server is an hot lightning wallet running on a web server, which can possibly have a very low level of security, depending on your ability to secure linux systems.  