sdk VS bips

Another possible aspect he could have meant is that there are some frameworks for BSV that just stash a bunch of javascript code in BSV transactions. Whoever consumes those transactions is expected to run that javascript code to put back together some state. It's what cryptofights is using, in a way that generated a silly number of transactions at one point. You can read about it at https://run.network/ for now, although the folks behind it are moving on, so it's unclear what future it will have. As I understand it, the Run sdk is not intended to run in a browser, but in a node.js environment (and all the state stashed in transactions needs to also be stored in a local database for anything non-trivial to work properly.) Still it's all javascript anyway.

Run

Thanks. I'm just trying to get my head around how diferent languages and environments communicate with eachother and work together. For example, I'm building a game using godot, and need to work with a sdk. and found this godot tutorial on how to use third party sdks. My head is spinning like crazy!

Yeah. I've got the ui and api running locally. I was just wondering if there were existing publicly accessible api services, sorta like how the run token protocol allows for purely browser js blockchain dev.

https://run.network is the SDK of the protocol

Cryptofights is using the Run framework as their underlying game engine/storage/BSV integration mechanism. It's a fun little framework. It stores large chunks of javascript source code in strange places, and expects users of the framework to load and run it in a provided sandbox, as a mean of doing smarter things with transactions. While stopping short of calling itself a smart contract platform, it nonetheless purports to let applications create "tokens, contracts, artwork, elections, games, digital pets, and more." It appears that Run is intended to allow users to use someone else's Run code and objects under some conditions, although their docs could be clearer on how and when exactly that would happen.

Whereas UTXO-based designs get parallelizability by design, creating a programming model around them has been harder, and frankly there aren't even that many people trying. Full-transparency, I've been working to solve this problem, and believe I've cracked it. Check out https://run.network if this interests you.

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

No one controls Bitcoin, because it's a protocol. Bitcoin Core is the reference implementation, but there are others, and anyone can create new implementations if they wish. Also, the Bitcoin Core maintainers can't just change something on a whim, because users would then switch to another fork. Maintainers (or miners or other groups) can't force their changes on users, because everyone can decide on their own which version they want to use.

The protocol development happens through BIPs (Bitcoin improvement proposals): https://github.com/bitcoin/bips

BIPs are discussed for years, before (and if) they are implemented, and basically everyone needs to agree on them, because no one wants to fork the blockchain, which could be devastating.

All the seeds generated from the CoolWallet (Number / Word) adhere to the BIP-39 protocol.