mako | bips | |
---|---|---|
13 | 1,282 | |
565 | 8,961 | |
- | 1.3% | |
0.0 | 6.8 | |
over 1 year ago | 4 days ago | |
C | Wikitext | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mako
-
what programming language is bitcoin software written in?
Mako is written in C Core and some other variants are discussed in the /u/bitusher comment
-
Who controls Bitcoin ?
There is a thread about mako, which is a new implementation, in this sub right now.
- Show HN: Mako – a full Bitcoin implementation in C
- mako - a full Bitcoin implementation in C
- An open access book on scientific visualization using python and matplotlib
-
Mako – a full Bitcoin implementation in C
Call me old school, but I like looking at the number of lines of code to get a feel for how big of a project something is. Mako[1] is 265,618 lines of code. The most widely accepted Bitcoin implementation[2] is 639,074 lines of code. The common Bitcoin implementation is 2.5x bigger and written in a slew of languages. Mako looks like a super-impressive amount of work (and by a single person no less).
[1] https://github.com/chjj/mako
[2] https://github.com/bitcoin/bitcoin
[3] How I calculated: find -type f | sed 's/.*/"&"/' | xargs wc -l
bips
-
Understanding and avoiding visually ambiguous characters in IDs
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...
-
Bitcoin Block 840000
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...
-
Generating and Working With ScriptPubKeys in Bitcoin Transactions
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.
- Blue Wallet and seed phrases
-
Nano S seed compromised?
Here’s the reference https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
-
Do you use 12 - 24 words?
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
- 24 words
- Creating a custom Bip39 brain wallet
-
SEC Charges Kraken for Operating as an Unregistered Securities Exchange
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.
-
Recover Cool Wallet seed to a Ledger?
All the seeds generated from the CoolWallet (Number / Word) adhere to the BIP-39 protocol.
What are some alternatives?
tokei - Count your code, quickly.
brainflayer - A proof-of-concept cracker for cryptocurrency brainwallets and other low entropy key algorithms.
bcoin - Javascript bitcoin library for node.js and browsers
P2P-Trading-Exchanges - Person-to-Person bitcoin Trading Exchanges
StratisFullNode
solidity - Solidity, the Smart Contract Programming Language
scc - Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go
EIPs - The Ethereum Improvement Proposal repository
NBitcoin - Comprehensive Bitcoin library for the .NET framework.
bip39 - A web tool for converting BIP39 mnemonic codes
btcd - An alternative full node bitcoin implementation written in Go (golang)
solana - Web-Scale Blockchain for fast, secure, scalable, decentralized apps and marketplaces.