raiden VS bips

Raiden sees v0.6.0 "Metamorphosis" with an updated database format and changes to the REST API.

Raiden v0.3 is released.

The Raiden client looks almost completely ready for the Coruscant milestone. The development team created a couple more release candidates in the last 7 days, the latest one being Coruscant - mansard. All packages in the Raiden Client were updated to the latest versions and a few more optimizations were also successfully completed. Open issues section of github looks clean of any reported bugs and we can see an open task for the Release 3.0.0.

Referencing this latest release: https://github.com/raiden-network/raiden/releases/tag/v3.0.0rc3

Development progress is looking great in the past week. Release candidate for Coruscant milestone was introduced in the Raiden Client. This release candidate will help the development team in testing and debugging. For now, the open issue section looks clean of any bugs discovered.

The Raiden Testnet is launched.

Coruscant - Songpa adds support for the cooperative settlement. Furthermore it also introduces performance improvements to payments and the WebRTC transport layer. Backward compatibility with version 2.x is broken which means channels opened with older versions need to be closed, settled and re-opened.

The Raiden Client has also seen some nice progress. Progress in the Raiden Client repository can be followed here.

In the Raiden Client repository they successfully completed WebRTC integration. Also, the work in progress version of cooperative settlement feature was introduced. Cooperative settlement was also successfully completed in the Raiden smart contracts. Other work includes minor codebase cleanup and fixes.

Raiden v0.100.4 "thehighfiveghost" is out on testnet, bundled with Raiden Services, and including channel withdrawals, permissive source routing and the handling of pruned blocks.

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.