Bitcoin just crashed $1,700 !

For 20,000 sats, I will call you a dumb fuck, and sign it with my pgp key. LIMITED! First 10 people only.

When someone asks me to be their Bitcoin mentor, the relationship is for life. The is the way of the Force.

I have ParmAirGaps available worldwide - Dismembered Thinkpad Laptops without WiFi or BlueTooth cards, Electrum & Sparrow Wallets installed, and a webcam for QR signing transactions, fully encrypted. Let me tell you what they are for... 1) Make seeds You can use it to verify checksums of bespoke seeds that you roll yourself - I have guides for that. 2) Verify the honesty of HWWs You can use it to verify the addresses of wallets made by hardware wallets. How do you know they are not using parallel seeds and pretending to use the seed you created or entered? Even if you use some dice roll feature, you can't know if the addresses truly belong to the seed you think you're using. Even if you have a passphrase, this risk exists. If you're paranoid enough, you can enter the seed into the ParmAirGap's Electrum/Sparrow wallet (don't use a regular computer, that's bloody dangerous), then check that the addresses generated are the same as the ones from the hardware wallet. Then you're good, and you can delete the ParmAirGap wallet you just created (if you want). 3) Storage & Encryption It's up to you if you want to use the device as a stateless machine (store keys on it or not). It is safe because the drive is encrypted. Air-gapped computers with encrypted drives are still vulnerable because an attacker can remove the drive and attach it to their computer, then explore the file system without needing to enter a password. In addition to the drive being encrypted, you can encrypt any wallet files you create - the software offers that. Even if you forget the password, you've learned from Parman and you know to have backup redundancy. 4) Inheritance On this computer it is safe to generate letters with high detail about bitcoin recovery. You can then encrypt the file and put it on a USB device. Ideally, put it on a Tails USB drive. Available on request, or make your own. To get assistance with inheritance planning, BetterCallParman (TM). 5) Signing It can be used as a signing device - partially signed transactions can be passed around by QR code for extra safety. Even safer is to have multiple devices geographically separated with each device only ever having knowledge of one key. Then you pass the transaction around until it is fully signed. BetterCallParman to learn how (mentorship or individual lesson). 6) Uncle Jim like a champ. With one of these it's easy to create keys for your family, and even store and encrypt keys for them as their backup. FUD Note that there is FUD going around that these can be hacked, but c'mon, these are laboratory condition attacks AND at the very least the device needs to be tampered by an attacker and then put back without you noticing. If it truly is a concern, get 2 or 3 of them and do multisig. You can get one here...

ParmAirGap™

And it nicely pairs with a ParmanodL transaction computer, just saying...

ParmanodL™

Today I noticed that when playing #piano, the vectors of force through and across the fingers at impact, are very similar to the force vectors across my well balanced and securely held chopstick. In conclusion, this is why that 4 yo Asian kid is crazy good at piano 🤣 #pianostr

Compiling Knots building a ParmanodL

Beautiful day to roast coffee #Coffeestr

I am building ParmanodLs and ParmAirGaps. Who wants yuan?

Parman's Bearnaise Sauce. Instructions with secret tips (on special request). Ingredients... 1 tbsp diced shallot (red onion or even brown onion is acceptable) ¼ cup any vinegar ¼ cup white wine (or dry vermouth better) 1/8 tsp cracked pepper 1.5 tbs tarragon (dried is fine) ¼ tsp salt (adjust later if using unsalted butter) - Quality of the butter matters immensely Method... Cook down to 2 tablespoons liquid to concentrate - strain. (Don't over do it) 3 egg yolks in a pan Beat them up first, for a minute to thicken Beat a tablespoon of butter and the vinegar reduction together Beat eggs over heat to a custard. Approx 58 to 60 deg C. You'll notice the thickness and won't need a thermometer when you're an expert. Tips... Exact amounts don't matter, these decimals are just the result of scaling the recipe… 28.35g butter per yolk max, but 18.9g per yolk better tasting If it splits, a drop of vinegar on the edge, and mix it in, it should re-emulsify. Otherwise beat an egg yolk and add the broken sauce bit by bit as you stir. Do make sure you get the salt right, depends in your butter, taste as you go. Pepper to taste. Add more tarragon leaves again to the sauce at some point (after they've been strained from the cooked liquid). #foodstr #Bearnaisestr

For mini GPG (PGP) tutorial number 2 in the #gpgparman series, we're going to import Parman's public gpg key into the computer's key ring. Easy AF and quick (I'll link episode 1 in the thread). Preamble: The keyring is just an abstract concept - it's a list of stored public keys (of other people). The public keys are sort of like Bitcoin addresses with identity information embedded. That person has the private key and can sign with it. You, and anyone, have the public key. The owner would usually widely publish their public key, or share it personally with anyone who requests it. You (the public) do signature checks for validity with the public key, the same way your Bitcoin node checks the validity of Bitcoin transactions and signatures. A discussion about Bitcoin signing another time. For now, let's just do the acquisition and importing of a public key. Step 1 - get gpg, the program Step 2 - get a key Step 3 - import key Step 4 - Another time; verify Parman's signature. STEP 1: First, you need to have gpg installed. Linux has it by default. For Mac, download and install GPGsuite, gpgtools.org, click the friendly red download button, install, and uncheck all the bloat, just get a minimal installation. For Windows, download and install gpg4win - gpg4win.org STEP 2: Next, let's get my public key. There are many ways, and for something you're super paranoid about, you could check different sources to make sure you're getting the right key and not an imposter's. I'll show you the way from a "keyserver" which is analogous to a Bitcoin node that shares data with other nodes and stays in sync, like mempool.space. Here, keyserver.ubuntu.com, you can enter names or emails and get lists of keys that hit your match. Go there and enter "armatheparman". (IMAGE below) You'll see a database entry for my key. Click the link that starts with "(4) rsa..." - it might open in the browser, or it might download. If it opens in the browser, right-click and save the page to the downloads directory. If it opens in a browser, you can copy all the text and paste it into a text file - save it in the downloads directory for now. There are other ways to acquire the key, but let's keep it simple. To look at the key, in the terminal (cmd for Windows), navigate to the downloads directory: cd ~/Downloads (For Windows, do cd \users\username\downloads , or if you open a fresh window, simply cd downloads should work) (~ is a shortcut to /home/username/ on Linux and /Users/username/ on Macs) Whatever the key file is called, probably "a5613b1902a4e2973f23fc67e7c061d4c5e5bc98.asc", then type cat a567 <tab> (for windows replace "cat" with "type") Don't type out <tab> ; that part means after the first few characters of the target filename (a567 for example), hit the <tab> key and the file name will autocomplete - don't type that long file name all out manually - ain't nobody got time for dat. When you hit enter, the cat program will print the contents of the file. Cat will do that for anything, it's handy. STEP 3: Now we import the key to the computer's "key ring", giving it access when needed for verifying signatures. In the terminal, go to where the file is, presumably downloads. (You can alternatively be anywhere in the file system, but then you have to type the full path of the file, not just its name) cd ~/Downloads then gpg --import thefilename Alternatively, from anywhere not just where the file is.... gpg --import /home/username/downloads/thefilename OBVIOUSLY, type in the actual filename not "thefilename" as written (and use the <tab> autocomplete nearly always). It should print some sort of success command. Nice. STEP 4: Verifying my signature using the public key. Stay tuned for episode 3.

Going for 2 in a row...

I'm going to do a public tutorial series in stages, where you can follow along and learn gpg and sha256 verification skills. Lessons in small manageable chunks. Use #gpgparman to find related posts, and bookmark this one as I'll add subsequent tutorials in replies. Let's begin... You can follow along with a computer (not a phone), Mac, Windows, or Linux. Today, let's just do a basic sha256 hash of a file with some explanations. Step 1: Download my free pdf book (why not make a smol plug?) from this website, click the download button on the page...

The Orange Pill Book &#8211; Bitcoin Guides

Alternatively, the direct link to the file is... https://armantheparman.com/wp-content/uploads/2022/10/The-Orange-Pill-Book.pdf It should download to your downloads directory. The size is 32.52 MB, but how can you be sure you truly downloaded the correct file, and where does the trust start and end? This is where hashing comes in. (It doesn't matter much for a PDF, but it's crucial for a Bitcoin Wallet!) A hash is a computer function that takes data and produces a numerical fingerprint of fixed value - a random-looking big number. There are many properties to hashes, the relevant thing here is that if you repeatedly hash the same data, you'll always get the same fingerprint. If you want a detailed explanation of mining, I have an essay,

SHA256 and Bitcoin Mining Walkthrough &#8211; Bitcoin Guides

Anyway, if I hash my PDF file, and report the result to you, then when you hash it and get the same value, you know we have identical copies. If you get a different result, it's likely you did something wrong, downloaded the wrong file, or the file got modified from what I originally published. While you still trust I'm giving you a friendly product, you're no longer trusting the delivery system (the internet and anyone trying to trick your computer), ie the file hasn't been tampered with because the hashes are identical. Step 2: This is the hash of my file, make a note of it: 23cd0813cc811d8cf11995335ca6c74825e9b97b4571f80f4d99abe5aa81bdd1 Step 3: For Mac and Linux, open the terminal and find your file. If it's in the downloads directory, you can get there by typing: cd ~/Downloads <enter>Windows ls <enter> For Windows, open cmd and type cd downloads <enter> dir <enter> For Parmanode computers, I have included a shortcut as part of 'ParmaShell', just type dl <enter> The above instructions will list everything in the downloads directory (A text-based version of exploring files). You should see the pdf file in there and the spelling of the filename. The-Orange-Pill-Book.pdf Make sure the file has finished downloading before attempting the next step, it's possible to hash an incompletely downloaded file and then you'll get a hash value mismatch. Detour: A common reason why people get the wrong hash values on Macs is because they might download a zipped file, and once downloaded, the Mac operating system automatically unzips the file and throws the original in the trash! Without asking - Yes. Why? I don't know, it's dumb. Then, people hash the extracted file, get a mismatch and wonder what's going on. They need to remove the file from the trash and hash that file, not the extracted file. Moving on... have Now we hash the file. For Linux and Mac, type this in the terminal: shasum -a 256 The-Orange-Pill-Book.pdf For Windows: certutil -hashfile The-Orange-Pill-Book.pdf sha256 You should then get exactly the same hash as what I attest: 23cd0813cc811d8cf11995335ca6c74825e9b97b4571f80f4d99abe5aa81bdd1 Step 5: Now repeat the above command and hash any other file for practice. Then do the same file again and see that you get an identical result. That's it for now, I hope it was fun. I'll write more to build from this in a little while.

Give me your retarded, your poor, Your subscribed masses yearning to trade charts, The wretched refuse of your teeming engagement farm. Send these, the chairless, tempest-toss to me, I lift my lamp beside the orange door!

Yesterday, I "custom" brute forced a passphrase recovery for a pleb. Then a few hours later I cracked another one. Two in one day is a nice record.

New insight to me while thinking about theoretical #physics ... Firstly, what many physics enthusiasts already know ... There is a boundary around a point in space that beyond which, it is impossible for any information to reach the central point. The "cosmic boundary" I think it's called. This is because space is expanding in such a way that every point is moving away from every other point (like ink dots on an expanding balloon all move away from each other). Because of this, cumulatively over enough distance, two points in space are moving away from each other faster than the speed of light (this doesn't break the speed of light limit btw, because the limit is on masses (and information) moving THROUGH space, not a limit of universe expansion). So as the universe keeps expanding, more and more points in space can never communicate with other points, eventually everything in the universe become isolated and alone. This is my new idea/concept (idk if it's well described, probably already is) ... Say there are two giant masses moving away from each other, and then after some time they are too far apart, such that light/information from one can't ever travel to the other because the universe space between is inflating too fast. What happens to the gravitational force between them? The natural thought might be to ask if the force disappears. But force itself isn't information that travels and limited by the speed of light. It's the CHANGE to the gravitational force that is information limited by the speed of light. My thought is that the mass will perceive the other as a static mass. Eg if it implodes and radiates its mass to zero, none of that change will be "felt" and the original gravitational force remains. More interestingly, what if the object is moving, does its gravitational field just stop moving once a cosmic barrier exists? Well, no, the "perceived" speed of the other object actually approaches zero naturally because light/gravitational_waves have further and further to travel as the cosmic boundary conditions come closer to existence. I'm not a theoretical physicist, yet, so please correct any errors in my thinking.

Embarking on a 5 hr series of physics lectures by Richard Feynman, "The character of physical law", 1964, because why not? Later, I might tackle the mysteries of the universe, IDK.

Bitcoin podcaster starter pack

Parman's Leverage Gets Fucked Trade ™

#Pizza night #foodstr