Bitcoin

P2P Protocol

The original peer-to-peer electronic cash protocol — a decentralized, trust-minimized ledger secured by Proof-of-Work mining, with no central issuer or validator set. Bitcoin Core is the reference implementation; independent implementations (btcd, bcoin, libbitcoin) exist and must conform to the same consensus rules. Protocol changes go through the informal Bitcoin Improvement Proposal (BIP) process — rough consensus among node operators, miners, and developers, not a formal vote.

Comunidade
Links
Visitar Website Ver Detalhe Econômico Sugerir uma correção

Detalhes

Licença MIT
Status de Dev 🟢 Ativo
Proprietário No single owner — an open-source project with a large, distributed contributor base.
Órgão de Governança None (informal rough consensus via the BIP process; no foundation or company holds authority over consensus rules).
País N/A (globally distributed, no single jurisdiction)
Ano de Início 2009
Stack C++ (Bitcoin Core); independent implementations exist in Go (btcd), JavaScript (bcoin), and C++ (libbitcoin) conforming to the same protocol.
Financiamento No formal funding entity; Bitcoin Core development is funded via a mix of individual, company (e.g. exchanges, mining firms), and grant-based sponsorship of individual contributors, not a treasury.
Última Investigação 23 de ago. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

P2P Protocol Atributos

Origins Peer-to-peer electronic cash, first described in Satoshi Nakamoto's 2008 whitepaper.
Database N/A (append-only blockchain, not a queryable database in the conventional sense)
Query Language N/A (RPC interface for node queries; no query language)
Data Formats Binary block/transaction format (custom serialization).
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Via third-party wallet apps (not part of Bitcoin Core itself).
Web Support Via third-party block explorers and web wallets; Bitcoin Core itself is not a web app.
Native Apps Yes — Bitcoin Core ships desktop node/wallet software (Windows/macOS/Linux).
Terms Free, open-source software; network transaction fees paid to miners.
Funds Not tracked as a single project treasury (see Funding).
Based On Builds on prior work in cryptographic hash functions, digital signatures, and Byzantine fault tolerance research; not itself built on another protocol.
P2P Architecture Unstructured gossip network of full nodes; each node independently validates and relays blocks/transactions; no supernodes or privileged peers.
Overlay Network Global, permissionless — any node can join by connecting to peers via DNS seeds or hardcoded IPs.
Content Addressing No (transaction/block references are by hash, but this isn't a general content-addressing system).
Local-First N/A
E2EE N/A (public ledger, not a messaging protocol)
CRDTs Lib N/A
Byzantine Fault Tolerance Yes — Nakamoto consensus (longest valid chain with most cumulative work) provides probabilistic BFT-equivalent guarantees under an honest-majority-hashpower assumption.
Signature ECDSA (secp256k1), with Schnorr signatures available since the 2021 Taproot upgrade.
Permissions Permissionless — anyone can run a node, mine, or transact without authorization.
Semantic Web Compatibility No.
Smart Contract Limited — Bitcoin Script (a non-Turing-complete stack-based language); Taproot/Tapscript extended scripting capability in 2021.
Protocol Stack Position Base-layer settlement (Layer 1); Lightning Network and other protocols build payment/state channels on top.
Asset / Value Embedding Native — BTC is the protocol's own unit of value; UTXO model.
Protocol Maturity / Standardization Mature, de facto standard — no formal standards body, but 15+ years of continuous mainnet operation and the most widely-adopted PoW blockchain protocol.