If you hold Ethereum, please remember to do your Christmas shopping early - you don't want a repeat of last year, disappointing your wife's lover with some lame socks. Take your time and find something special.

If Saylor buying 100,000 bitcoin doesn't move the price, will buying 22 million bitcoin move the price?

I figured out Saylor... If you had enough capital to deploy (your own money or others'), eg like MicroStrategy, why wouldn't you open long contracts, and at the same time push the price up with spot buying, then liquidate the shorts to collect even more bitcoin? I'm on to Saylor - he never quite explains it well, despite explaining literally everything else very simply. Not discouraging it BTW. How did I figure it out? Because my special move is to figure out schemes, loopholes, and weaknesses. It's possible he's not actually doing this, but he bloody should. For interest...

Liberals are not Boolish enough

I'm pleased to announce a new update to Parmanode... -Improved navigation, jump directly to desired menus, even from the command line. -BTCPay update to v2.0.3 (Mac and Linux) -Custom BTCPay backup and restore function -Custom upgrade/downgrade function for BTCPay A backup and restore feature is really important, and it's not that obvious how and what to backup. BTCPay has an official backup/restore script, but it won't work if you have a bespoke BTCPay installation like what Parmanode offers. So I had to reverse engineer their script to understand which components needed to be backed up and made a specific one for Parmanode. It's been tested on Linux and Mac and works nice.

Have you got a pair of socks that when you put on you say, "Ohh, that felt good", and you know the rest of the day is going to be great?

If you're feeling euphoria at 100k bitcoin, it's not because you stacked enough, it's because... 1) bitcoin hasn't improved you yet 2) you're probably multiplying your stack by the current price each day 3) and you're intending to buy stupid shit. Just saying. Also, if I get access to your phone's calculator, I can take a look at your history, and I'll find some number times 98,000, and I'll know your stack size.

Laser ray until you're no longer gay!

The more fucking around that happens, the more finding out that happens

Despite my mission to teach self custody, I accept that holding your own entire wealth is not for everyone - it's OK, really... I always say, expecting everyone to learn the skills of banking and security is unrealistic and goes against the benefits of having money in society. Money helps us escape the inefficiencies of barter, and allows everyone to specialise in what they are good at, rather than doing everything themselves. Banking, like baking, dentistry, or building - is just another skillset, and time drainer. The existence of Bitcoin banks will not mean that the purpose of Bitcoin has been corrupted or has failed ... Bitcoin wasn't created to end banks. It's fixing the money - so they no one can create it for free and scam humanity. Yes it means that some will engage in fractional reserve, and yes that has the*effect* of increasing the money supply, but it's acceptable... Whatever the increase, it has an anchor to the real fixed supply, and can't keep growing, because as it does, bankruptcies increase pulling it back to reality. Free markets, baby, accept it. This natural market force, with some people fucking around and finding out, doesn't mean there is any sacrifice to the main mission. We would still have sound money, and have ended central banks (yes self custody TODAY helps defeat them, but that is for the "then they fight you" stage, not the "then you win" stage). We, the earliest Bitcoiners, have the responsibility to hold our own coins, but also the opportunity to be the custodians of the future, if we so choose. There will be fierce competition, no monopolies, with a myriad of black and white market options that can't be stopped. People will have the choice to use services for convenience, and won't have to rely on a small handful of custodians to hold all their wealth, they can diversify, OR, is their wealth justifies/demands it, can call someone like me to mentor them to learn self banking skills and extreme security (excuse the smol plug). Why should the poorest people with 5 sats to their name be concerned with security or the ability to open their own lightning channels? I hope this part is obvious, not going to elaborate. Rant over. Getting up to a gorgeous day of winning.

Parman's Bitcoin Wallet fun facts, please enjoy... When you make a BIP39 wallet with no passphrase, the text "mnemonic" is used in the code under the hood. If you do have a passphrase, eg HFSP, then under the hood it becomes "mnemonicHFSP". That combined with the seed phrase (however long) goes through 2048 rounds of a HMAC function with SHA-512 at it's code - not SHA256! So the resulting output, called the seed, is a 512 bit (not 256!) binary number (or expressed as 64 bytes, or 128 hex characters) - it's not a cryptographic key! Just a big number called a seed - ie the entropy that goes into making the key. Of note, the seed/passphrase text is converted to numbers first and held as bytes, but how is it converted? It doesn't go back to the BIP 39 word list numbers which is what many people would think and what I initially thought. In fact the text is converted to ASCII, which is a completely different way to map text to numbers. So when you roll dice or toss a coin, you produce numbers which map in the BIP39 protocol to words first, but then those words are mapped to numbers again, but using ASCII, so totally different numbers. Why, IDK. Anyway so going through this elaborate process might seem completely useless, why not just start with the 512 bit number/seed? Short answer is that it's harder to write down than words. It's much easier to write down text, leaving the hard stuff to the coders to do in the background. Also interesting is that although there are protocol words used to produce the 512-bit seed, technically you can use any text you want to put into the HMAC function and produce a 512-bit seed. You still get a resulting wallet and the Bitcoin protocol will not know anything about whether your wallet is to BIP39 protocol or not (BIP 39 has nothing to do with the Bitcoin consensus rules, it's something external, for wallet generation and compatibility between hardware in software). The problem occurs when you try to input this invalid seed into a BIP39 compliant hardware wallet or software wallet. But if you write your own code, you can do whatever you want and live dangerously. You can take BIP39 non-compliant words and convert them to a BIP32 (HD wallet pritocol) 512-bit seed and from there perform the necessary cryptography to produce a wallet. But when you fuck up and lose your bitcoin, the rest of humanity will thank you for your loss. More interesting things... The hierarchical deterministic wallet BIP is number 32 and existed before BIP 39 which included words. When making a HD wallet before BIP 39, it was possible to use a 128-bit seed or 256-bit seed or 512-bit seed. The BIP39 protocol took the longest option, 512. The way I am describing all this might sound like I was around at the time, but no, I'm just interpreting things from reading the protocol, an interested latecomer, trying to build ParmaWallet.

I was asked by someone if they should wait for the price to drop to $82k before buying more bitcoin...

Hey @Lyn Alden I was halfway through your book on Spotify, enjoying it, then suddenly, "Not available in your region" (Australia) What the skibidi? 😭

There are a lot of liberal women out there completely depressed... There is the rare one that might be cute... MAGA-guys, please don't take advantage of them with your charm in this delicate moment, they can't get abortions.

Huge success today with lamb ragu gnocchi. Was like eating little clouds.

Happy Bitcoin Whitepaper Day!!

Everyone should wear a Guy Fawkes mask when they go out to vote on Nov 5.

A quick explanation of how to assess a Bitcoin miner for profitability... Let's take the S21 Pro. It has a hash rate of 234 TH/s. The world is hashing at 750M TH/s, so that machine will contribute to the following fraction of the world hash rate... 234/750,000,000 = 0.000000312 Cool. That means, if left on all day, it should generate the total world bitcoin reward for the day multiplied by that percentage... 450 bitcoin x 0.000000312 = 0.00014040 bitcoin (14,040 stats) So the S21 Pro produces 14k sats per day if left on. The next question is how much that costs per day. The machine is rated at 3510 Watts, or 3.51 kW, 3.51 kilojoules per second. Electricity prices are in $/kWhr ($/energy). BTW, Energy is kW (kJoules/second) multiplied by 1 hr (ie E / time x time) = Energy. So 3.51kW * 1hr = 3.51kWhr is the amount of energy used in 1 hour by this machine, and x 24 = 84.24 kWhr in one day. How much does 84.24 kWhr, which was used in the day to produce 14k sats, cost? If your electricity price is 0.06c per kWhr, then it costs: 84.24 kWhr x 0.06 $/kWhr = $5.05 per day. So $5.05 to produce 14k sats. At what price are you effectively "buying" bitcoin? We need the units $/bitcoin... 5.05 ÷ 0.00014040(ie 14k sats) = $35968 The current market price is $72,000 It means that if you pay full price for the s21 Pro ($6318), and have cheap electricity at 0.06c/kWhr (I pay around 20c US btw where I live), you will be mining bitcoin profitably, but... you need to recover the cost of the ASIC. $72000 x 0.0001404 bitcoin means that you're earning about $10.10 per day in bitcoin, and paying $5.05 in electricity. $5 per day profit will take a while to pay off that $6,318 miner!! (3.46 years) How can it make sense? Answer: Well, if the bitcoin price doubles, guess what happens to the value of the ASIC? That will probably roughly double also - if it doesn't many people will buy them, bid up their price, and by turning them on also make mining less profitable. For the miner who got in early, that reduction in profitability is compensated for by a capital gain on the equipment. Meanwhile, they are still mining somewhat profitably - They'll be mining less than 14k sats/day as the hashrate goes up, but those sats will be worth more. And their daily costs are static. Another way to put it... MINING COST FOLLOWS PRICE ...not the other way around as with every other commodity in nature. For everything else, the price follows the cost to produce. I like to call it "anchored" to the cost of production. For Bitcoin, the cost to produce is anchored to the price, and this is fundamentally due to the difficulty adjustment, which keeps the daily production constant regardless of price. OK, that was a long explanation, not quick, sorry, I lied. Here's the other thing that most people don't think about... That $6k miner that was bought hoping for a bitcoin price pump... what if you just bought $6k worth of bitcoin today? You probably would end up with more sats. Mining is fun but opportunity cost is a bitch.

If you're looking to learn to code for the joy and empowerment, I highly recommend bash script. It helps you to be great at maintaining your computer, and following guides to install things with Linux. Anything you might execute from the command line is code. Here's how you start (works on Linux or Mac)... 1) create a paranoid crypto anarchist directory and go into it cd ~ mkdir pca cd pca 2) make a file touch GFY.sh 3) edit it with nano (vim later when you're getting skilled and seeking efficiency). This makes step 2 redundant, everyone relax, I know. nano GFY.sh 4) on line 1, very important, put... #!/bin/bash This turns the document into a program. 5) Let's print something. Add these 3 lines echo "GFY World!" sleep 10 clear This will print to screen, wait 10 seconds, then clear the screen, then the program ends. Notice, each new line is a new command, and they can be sequentially typed in if you want. All these lines of bash code work manually too. 6) Make the program executable... sudo chmod +x ~/GFY.sh This is superuser do (elevated privileges), change mode function, add executable option, and the path to the file (~ is shorthand to the home directory of the current user). 7) now you can run the program like this... ./GFY.sh Or ~/GFY.sh In the first example the full stop stands for the current directory. So whatever your directory you're in, the computer knows to replace the full stop with the current path, and then it adds on the rest. You have to be in the same directory as your program for this work. In the second example, you don't have to be in the same directory because you're specifying the path fully, although in shorthand with ~ This might seem very trivial but it is the basic building blocks for building more and more complex things, such as Parmanode . You can actually read the Parmanode script and see what it's doing. Maybe I should do a video one day explaining the code.

Fuck you. I mean, GM 🧡