Bitcoin VS bips

Well AI is the new blockchain, but that doesn't mean blockchain is dead. Bitcoin is here with a new release of Bitcoin Core. Bitcoin Core connects to the Bitcoin network to download and fully validate blocks and transactions. The project includes a wallet and graphical user interface. The latest update includes new features such as support for Testnet4, policy changes, updates to RPCs and REST APIs, detection of wallet transactions when they conflict with the mempool, and lots more. Read up on all the changes in the Bitcoin release notes.

Ubuntu/Debian: Install LND: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#install-lnd Install Bitcoin Core: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#linux-instructions

To be able to follow along, you must have both bitcoind and lnd installed.

As mentioned previously, ScriptPubKeys are scripts that embody the locking conditions of bitcoins in a Bitcoin transaction. They are a crucial element of a Bitcoin transaction that specifies the requirements that must be met before an unspent transaction output (UTXO) is used. The ScriptPubKey, combined with the Amount, creates an output of a Bitcoin transaction. Like every other script, ScriptPubKeys are made up of operators and data. During the encoding of a transaction, both data and the operands are represented in hexadecimal format. You can find the hex representation for all operands used in Bitcoin Scripts here.

Which article? Have a look at Luke's CVE and pull request https://nvd.nist.gov/vuln/detail/CVE-2023-50428 https://github.com/bitcoin/bitcoin/pull/28408

Some years ago, I saw a wallet called [Spark](https://sparkwallet.io/) that let you generate a QR-code to view in your Apple Wallet and Apple Watch Wallet. It was for receiving over lightning, not sending.

I guess with unified [BIP21](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawi...) QR-codes, anyone can already add a RECEIVING wallet code to Apple Wallet today.

I don't think Apple want's to be the middle man in receiving Bitcoin payments though because “tainted” coins exist in the C-suite mind, and they would rather not receive and handle those.

But Jack Mallers recently told me he wants to integrate Apple Pay into [Strike](https://strike.me), so who knows, something similar will exist soon.

Anything you put elsewhere is not more secure, unless you are more secure than Apple's servers, which seems highly unlikely. If you don't have it, it can't get compromised.

The user has an iCloud account, you can write to iCloud storage without making them "sign in" to your app. It's their data, they can find it in the folder for your app in their iCloud drive on a Mac.

And see https://developer.apple.com/game-center/ for a way to let two users coordinate "play", multiplayer, turn based, achievements, etc., which cover most of the interaction you'd need.

For sharing personality test, a person can do their own and their partner's, but for a better take on the partner you and your partner can each take your own test then generate a sharable fun code that captures the "bits" of the answers without repeating the test. As partners, you could tell each other the sharable code as a NFC bump or QR code to scan, or generate one of the word based codes like bitcoin wallet passwords.

See BIP39: https://github.com/bitcoin/bips/blob/master/bip-0039.

(This passphrase would be short if the test results distill down to a smaller set of outcomes, like 64 questions give 8 results. It would be long if you need all 64 questions' answers to match with.)

Modern bitcoin addresses use a base-32 character set that leaves out some of the most ambiguous pairs and also permutes the address ordering so that the most visually similar remaining characters produce single bit errors which are better handled by the addresses error detecting (and potentially correcting) code.

https://github.com/bitcoin/bips/blob/master/bip-0173.mediawi...

Context: Bitcoin miners have just adopted a 50% pay cut for themselves. This pay cut was baked into Bitcoin protocol at the launch of the network (mostly, see "BIP 42" [1]). The OP link gives information about the block in which this pay cut was made.

I get that HN comments tend to dismiss Bitcoin. But the fact that for the fourth time this pay cut has happened without a hitch speaks volumes to what makes Bitcoin interesting: It's a rare combination of economic incentives and technology that keeps chugging. Nobody can stop it. And it's extremely resistant to change. It requires no governmental approval. All attempts at subversion or interference have failed. There aren't many things that come close to that kind of record.

[1] https://github.com/bitcoin/bips/blob/master/bip-0042.mediawi...

Bitcoin transactions involve locking funds in scripts, which can only be spent if those locking conditions are met. The part of the script that expresses these locking conditions are called ScriptPubKeys. On the other hand, the part that provides unlocking scripts to satisfy the locking conditions is referred to as ScriptSig for legacy transactions, and ScriptWitness for SegWit Transactions. These scripts are evaluated by a stack-based language called Script. This article will mainly focus on ScriptPubKeys.

Here’s the reference https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

There are 5 271 537 971 301 488 476 000 309 317 528 177 868 800 possible permutations of the bip39 wordlist found here: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt when using 12 word seeds. You probably have better change to win the lottery every week for the rest of your life than cracking a 12 word seed in correct order