Glossary · Blockchain basics
Published 23 May 2025 · Updated 9 Nov 2026 · 15 min read
A public blockchain is a shared ledger anyone can read and send transactions to, maintained by independent nodes following the same open rules. On permissionless networks, block producers need stake or mining hardware, not an operator's approval. Public access does not guarantee privacy or remove legal obligations, and some public networks restrict who validates.
A public blockchain ledger lets anyone read records and submit transactions. On a permissionless network, no administrator decides who may join, unlike a database run by one company. It is one form of distributed ledger, not a synonym for every shared database. The definitions below separate access from authority. NIST IR 8202, published in October 2018, ties permissionless participation to reading, writing and publishing blocks without authorization.
| Source | Date | Definition, in its own words | What it adds |
|---|---|---|---|
| NIST IR 8202, Blockchain Technology Overview | DateOctober 2018 | Definition, in its own words“In a permissionless blockchain network anyone can read and write to the blockchain without authorization.” | What it addsThe standard test: no one's permission to read or write |
| EDPB Guidelines 02/2025, paragraph 22 | DateFinal version 7 July 2026 | Definition, in its own words“Permissionless blockchains provide participants with equal rights and capacities: anyone can read, write, or create blocks.” | What it addsThe EU data regulators' wording, which adds creating blocks |
| ethereum.org, Networks | DateUpdated 23 September 2026 | Definition, in its own words“Anyone can read or create transactions on a public blockchain and validate the transactions being executed.” | What it addsA network's own description, with validation open to all |
| Bitcoin white paper | DateAnnounced 31 October 2008 | Definition, in its own words“nodes can leave and rejoin the network at will” | What it addsOpen joining and leaving, with no membership list |
| World Bank, FinTech Note No. 1 | Date2017 | Definition, in its own words“Distributed ledgers are categorized as public or private depending on whether the ledgers can be accessed by anyone” | What it addsSeparates who may read from who may write |
| BIS Annual Economic Report 2018, chapter V | Date24 June 2018 | Definition, in its own words“while anybody can participate, nobody has a special key to change the ledger.” | What it addsNo administrator key, changes only by consensus |
Two axes matter: who may read, and who may write and validate. Public or private describes access. Permissionless participation or a permissioned ledger describes authorization. The Bitcoin network and Ethereum network are public permissionless examples. A public permissioned network separates those choices. Hedera's consensus nodes are permissioned and operated by its council, while mirror nodes are permissionless. Public access does not guarantee decentralized block production or permission for every node to become a validator.
Bitcoin is pseudonymous, not anonymous. Its documentation says it cannot offer cash's level of privacy. A blockchain explorer can expose an address's balance and payment history without displaying a person's name. The BIS chapter published in June 2018 described cryptocurrencies as anonymous, but Bitcoin's documentation contradicts that wording. Transparent records and absent names are different properties. Anyone can see the balance and all transactions of any Bitcoin address.
Access involves different jobs, not one universal permission. The table separates reading, sending transactions, producing blocks, operating a node, building applications and changing rules. Bitcoin and Ethereum allow open participation, but each job carries different costs. Permissionless describes authorization, not free computing resources or automatic influence over upgrades.
| Anyone can | On Bitcoin | On Ethereum | What it takes |
|---|---|---|---|
| Read the ledger | On BitcoinAll transactions are public, traceable and permanently stored (bitcoin.org) | On EthereumAnyone can read transactions and verify them with their own client (ethereum.org) | What it takesA node of your own, or a provider's node or an explorer |
| Send a transaction | On BitcoinPay a fee rate that miners accept. Bitcoin Core v32.1 relays from 0.1 sat/vB by default | On EthereumPay at least the base fee, usually plus a tip. Up to 16,777,216 gas per transaction since December 2025 | What it takesCoins for the fee and a wallet |
| Produce blocks | On BitcoinMine with specialized hardware. A miner's share of blocks follows its hash power | On EthereumStake at least 32 ETH per validator, and up to 2,048 ETH | What it takesHardware and power, or stake |
| Run a full node | On BitcoinAbout 7 GB of disk when pruned, 2 GB of RAM, 400 kbit/s upload (bitcoin.org) | On Ethereum16 GB of RAM, 32 GB recommended, a 4 TB NVMe SSD and 25+ Mbit/s (ethereum.org) | What it takesA machine that stays online, at home or in the cloud |
| Build on it | On BitcoinBitcoin Core is open source under the MIT license | On EthereumNo rules on who can build an application (ethereum.org) | What it takesCode, and no approval |
| Propose rule changes | On BitcoinNobody owns the network. Changes need users to choose new software (bitcoin.org) | On EthereumGovernance happens off-chain, and node operators can decline an upgrade (ethereum.org) | What it takesPersuade users and node operators, or fork |
Reading and sending transactions need no admission approval. An Ethereum validator requires at least 32 ETH. Bitcoin block production needs specialized hardware, and share follows hash power. A full node verifies rules but needs an online machine. ethereum.org warns that cloud concentration can create a single point of failure. Users and node operators choose software, so rule changes depend on adoption. RPC provider access offers another way to read data.
A public blockchain has several points where a transaction can be refused. The interface, connection service and block producer have different powers. Censorship resistance varies by layer, since refusal at one layer does not necessarily control the network. Select Bitcoin or Ethereum to distinguish a rejected request, delayed inclusion, a token freeze and legal obligations.
A wallet, RPC provider or relay can refuse service, while other software or providers can carry the same valid transaction.
One block producer can omit a transaction from its block, while a later producer can include it.
A majority of stake or hash power could censor while it holds control, while the social layer can support a fork.
A stablecoin issuer can freeze its own token at an address, but cannot freeze BTC or ETH.
Regulators and courts bind people and firms within their reach, rather than rewriting the network's consensus rules.
This page team map traces the transaction path with dated cases and readings. It is not legal advice.
Wallets, RPC providers, builders and relays can refuse service, making network decentralization more than a protocol property. Another node can submit valid transactions. In August 2022, the Tornado Cash front end went offline. Circle froze designated USDC addresses on 8 August 2022. The next day, providers blocked API access, not RPC access. The 7 November 2026 reading shows 16.7% of MEV-Boost deliveries through relays classified as censoring. The peak was 94.8% on 26 October 2022. This is delivery share, not an exact block count.
No individual Ethereum producer can undo finality. Majority stake or hash power can censor or reorder recent blocks. Issuers control only their tokens. In Van Loon, the Fifth Circuit ruled on 26 November 2024 that Tornado Cash's immutable contracts were not property of a foreign national or entity. Treasury's delisting followed on 21 March 2025. In November 2026, draft FOCIL, EIP-7805, is scheduled for Hegotá without a mainnet date. Its proposed validator inclusion lists would require blocks to include listed mempool transactions.
A transparent ledger exposes more than a transaction amount. Bitcoin and Ethereum records differ, and privacy-focused designs expose different fields. Pseudonymous participation does not make those fields confidential. Compare six payment types, including what becomes visible in a public mempool before a swap is included in a block.
Bitcoin inputs, outputs, amounts and the fee are public and unencrypted, while common inputs reveal a shared owner.
Ethereum exposes from, to, value and fee, while the nonce links transactions originating from the same account.
The token contract's Transfer event records from, to and amount, and the log identifies which token contract emitted it.
A pending mempool swap is public before inclusion, and the recorded trade exposes both amounts and the price after execution.
Zcash shielded transfers shield addresses, amounts and memos, while the fee and value entering or leaving a shielded pool remain visible.
Only informees can decrypt Canton transfer views. The synchronizer handles encrypted messages, while sequencers see recipient lists and message sizes.
Example values are made up. The visibility assigned to each field follows the relevant protocol documentation.
Bitcoin exposes a change output alongside payment outputs in most transactions. An ETH transfer shows from, to, value, nonce and input data. ERC-20 token transfers add a Transfer log, while plain ETH transfers emit no log. Uniswap v3 swaps also record the resulting price. A blockchain address can become identifiable through common inputs, change heuristics or exchange identity checks. Nodes and RPC providers can log IP addresses. The EDPB's guidelines adopted on 7 July 2026 treat public keys as personal data when identification uses reasonably likely means.
Zcash shielded transfers hide amounts, addresses and memos but expose fees. Sapling reveals counts of spends and outputs, while Orchard also hides that split. Canton describes itself as a public layer 1 blockchain that splits a transaction into encrypted views for its informees. Its participant nodes store only contracts involving their hosted parties. The synchronizer never accesses transaction data, so public participation does not mean every node receives the same readable payment record.
Admission to a public blockchain does not reserve capacity. Ethereum measures transaction work in units of gas, while Bitcoin miners select payments by their offered rate. This is an open market, not an account approval process. Adjust demand in the model to see pricing change, then compare it with a dated replay.
Above-target blocks raise the base fee by up to 12.5% each. Six full blocks roughly double it in the model.
Blocks that use exactly the target gas leave the base fee where it is, block after block.
Blocks below the target lower the base fee by up to 12.5% each, and five empty blocks roughly halve it.
The 8 November 2026 replay reproduces all 24 base fee changes exactly, to the wei, across 0.1078 to 0.1511 gwei.
This page team EIP-1559 model includes a replay of 25 Ethereum blocks read on 8 November 2026.
Ethereum's transaction fee combines a burned base fee with any priority fee paid to the proposer. EIP-1559 limits each adjustment to 12.5%. Client releases for Fusaka made 60 million gas the default block limit, with a target of half that. The page team's 8 November 2026 replay matches all 24 changes across 25 blocks exactly. Bitcoin miners choose by fee rate. Estimates on 8 November 2026 span about 0.1 to 2.5 sat/vB. Bitcoin Core 31.0 introduced cluster mempool ordering in April 2026.
Network categories describe access, authority and visibility, not a security ranking. A public blockchain can be transparent and permissionless, or readable by everyone with approved validators. A consortium shares control among selected participants. A private blockchain reserves access. Pseudonymous accounts and identified parties also create different expectations about who sees records.
| Topic | Public | Public permissioned | Consortium | Private |
|---|---|---|---|---|
| Who can read | PublicAnyone | Public permissionedUsually anyone. Hedera's mirror nodes are open to all | ConsortiumMembers, or the public if members choose | PrivateWhoever the operator allows |
| Who can write and validate | PublicAnyone can send. Anyone with stake or hash power can produce blocks | Public permissionedAnyone can send on Hedera. Approved operators validate | ConsortiumA pre-defined set of trusted nodes | PrivateThe operator |
| Who you trust | PublicThe protocol rules, checked by your own node or a provider's | Public permissionedA council or a set of named operators | ConsortiumThe member firms and their agreement | PrivateOne organization |
| Who sees the data | PublicEveryone, under pseudonymous addresses | Public permissionedEveryone, in the examples read | ConsortiumMembers | PrivateThe operator and the users it allows |
| How rules change | PublicOff-chain debate, client upgrades and forks | Public permissionedCouncil or member decisions | ConsortiumMember agreements | PrivateThe operator decides |
| Examples | PublicBitcoin (2009), Ethereum (2015) | Public permissionedHedera, LACChain, Alastria Red B | ConsortiumPartior (founded 2021) | PrivateKinexys by J.P. Morgan, HSBC Tokenised Deposit Service |
A public blockchain trades operator control and privacy for open participation and shared rules. A private blockchain reverses those priorities, but isolation does not establish security. A consortium relies on a predefined trusted node set. Canton does not fit one column. It calls itself a public layer 1 blockchain. Its Global Synchronizer is operated by Super Validators. A new validator needs sponsorship from a Super Validator, and each party sees only its own data.
Open participation does not exempt people or businesses from regulation. The table covers the GDPR, MiCA, the EU travel rule, FATF standards, US sanctions and the GENIUS Act. For public blockchains, legal duties depend on roles and jurisdiction, not simply whether the network describes itself as decentralized.
| Rule | Who it applies to | What it means for a public chain |
|---|---|---|
| GDPR, with EDPB Guidelines 02/2025 (final 7 July 2026) | Who it applies toControllers of personal data, which can include nodes that decide purposes and means | What it means for a public chainPublic keys can be personal data. Use a public chain only if public access is needed, and design erasure in from the start |
| MiCA, Regulation (EU) 2023/1114 | Who it applies toCrypto-asset service providers in the EU, licensed by 1 July 2026 at the latest | What it means for a public chainFully decentralized services are out of scope. Providers disclose each asset's consensus energy use (Delegated Regulation 2025/422) |
| Transfer of Funds Regulation (EU) 2023/1113, from 30 December 2024 | Who it applies toCrypto-asset service providers in the EU | What it means for a public chainNames and addresses travel with each crypto transfer, with no EUR 1,000 threshold |
| FATF Recommendation 16, updated 18 June 2025 | Who it applies toCountries and the providers they regulate | What it means for a public chainThe travel rule for virtual assets, with the 2025 changes in effect by the end of 2030 |
| US sanctions: IEEPA and OFAC guidance of 15 October 2021 | Who it applies toUS persons, including firms that run front ends, nodes or validators | What it means for a public chainObligations apply equally to virtual currency. Courts review designations, as in Van Loon (26 November 2024) |
| GENIUS Act, enacted 18 July 2025, effective 18 January 2027 | Who it applies toIssuers of payment stablecoins in the US | What it means for a public chainIssuers must be able to seize, freeze or burn their tokens on a lawful order |
These rules bind providers, issuers and personal data controllers, not the protocol itself. The EDPB's final guidelines of 7 July 2026 ask whether public access is necessary. They reject technical impossibility as an excuse for GDPR noncompliance and require erasure rights to be addressed by design. The GENIUS Act takes effect on 18 January 2027. Payment stablecoin issuers must be technically able to comply with lawful orders, including freezes, and must follow them. This page is not legal advice.
From Bitcoin's first block in 2009, public blockchains developed through software choices, forks, sanctions and data protection law. Ethereum's launch in July 2015 brought another permissionless network. Later disputes split shared histories, while regulators addressed personal data and obligations on providers.
The Bitcoin genesis block was created on 3 January 2009 at 18:15:05 UTC. It followed the white paper announced on 31 October 2008, which described payments without a financial institution.
Ethereum's Frontier release went live on 30 July 2015 at block 0 as another public permissionless network. Transactions became possible once the Frontier thawing fork lifted the 5,000 gas block limit on 7 September 2015.
The DAO fork occurred on 20 July 2016 at block 1,920,000. Some miners refused to fork, and the unforked chain continued as Ethereum Classic. Shared history did not prevent different communities adopting different rules.
Bitcoin Cash split from Bitcoin on 1 August 2017 after block 478,558. The public blockchain divided when participants adopted different software rather than settling on one rule set.
The CNIL published blockchain and GDPR guidance on 20 September 2018, followed by an English version on 29 October 2018. It stressed the importance of keeping personal data off a blockchain in cleartext.
OFAC designated Tornado Cash on 8 August 2022. Circle blocked designated USDC addresses that day, and API providers blocked access the next day. These actions occurred at service and token layers rather than rewriting Ethereum's rules.
The Fifth Circuit ruled in Van Loon on 26 November 2024 that Tornado Cash's immutable contracts were not property of a foreign national or entity. Treasury removed the sanctions on 21 March 2025.
The EDPB adopted version 2.0 of Guidelines 02/2025 on 7 July 2026. Its framework separated public access from permission to participate and required data protection obligations to be considered in the design.
Openness does not settle questions about retention, capacity, recovery or resource use. A public blockchain can preserve records while leaving users exposed to mistakes and intermediaries. Records written openly to a public chain stay there and remain visible to everyone.
The EDPB's July 2026 guidelines describe no practical deletion option for most on-chain data. Bitcoin documentation warns that records difficult to trace today may become easy to trace later.
Bitcoin's 20 April 2024 halving block had a median fee of 200 sat/vB. Estimates on 8 November 2026 range from about 0.1 to 2.5 sat/vB, illustrating changing demand.
Lost Bitcoin keys can leave coins dormant forever. Chainalysis counted about 3.7 million BTC unmoved for at least five years in June 2020, but inactivity does not prove loss.
Ethereum's DAO fork produced Ethereum Classic in July 2016. Bitcoin Cash split in August 2017. Public blockchain governance depends on software adoption, not a universal administrator.
Providers restricted Tornado Cash API access in August 2022. On 7 November 2026, relays classified as censoring handled 16.7% of MEV-Boost deliveries, a delivery-share measure rather than an exact block count.
Cambridge estimated Bitcoin's annual electricity use at 138 TWh on 28 April 2025. Its 10 July 2026 estimate for Ethereum after the Merge was about 7.87 GWh annually.
We build products for public networks, from smart contracts and tokens to protocol design. Our public blockchain development work covers open, transparent and permissionless networks. We also address the choice between public, consortium and private blockchain architectures. PixelPlex is a software engineering company founded in 2007, with blockchain work dating to 2013.
The KickICO crowdfunding case documents an Ethereum platform for reward and donation-based crowdfunding, launched in 2017 with its own KickCoin token. We built the ICO and KICK token contracts and an ICO contract generator. PixelPlex has built blockchain software since 2013.
Discuss a product for a public blockchain
We can discuss your product's access, data and contract requirements, including where a public network fits and where it does not.
Discuss your projectGet updates about blockchain, technologies and our company
We will process the personal data you provide in accordance with our Privacy policy. You can unsubscribe or change your preferences at any time by clicking the link in any email.Services
Blockchain
Blockchain consultingStrategy, architecture, feasibility
Crypto wallet developmentSelf-custody, MPC, cards on top
Cryptocurrency exchange developmentTrading venues, liquidity and protocols
Tokenization servicesRWA, funds, collateral
Crypto payments developmentAccept, settle and pay out in crypto
Smart contracts developmentDesign, build, audit
Blockchain integration dApp development DeFi development NFTs Tokens Web3 development All blockchain services All servicesNetworks
Canton developmentDaml apps, wallets, settlement, validators
Official Partner
Ethereum developmentSmart contracts, L2s and dApps
Solana developmentHigh-throughput programs and dApps
TON developmentMini apps, wallets, Telegram ecosystem
Official Partner
Hedera developmentHashgraph apps and token services
Exclusive Partner
Hyperledger developmentPermissioned networks for enterprises
Certified Partner
Cardano Algorand Stellar Avalanche Bitcoin Polygon All networks All servicesAI & ML
AI agents developmentConnect tools and automate multi-step workflows
RAG developmentFind answers across your company’s documents and systems
AI copilot developmentAdd useful assistance to your product or internal tools
LLM developmentCustom and fine-tuned models for your domain
Private AI deploymentRun models in your own environment
AI consultingUse cases, feasibility and a roadmap
Generative AI development Machine learning development Computer vision Chatbot development ChatGPT integration Deep learning development All AI services All servicesData & analytics
Data engineeringPipelines that keep your data reliable
Data platform developmentOne source of truth for analytics
Analytics & dashboards developmentBI your teams actually use
Predictive analyticsForecasts built on your own history
Data strategyWhere data can pay off first
Data visualizationDashboards and visual stories from your data
Data science development Development of data marts All data services All servicesSoftware
Product discoveryValidate scope and cost before you build
MVP developmentA launch-ready first release
Web application developmentPlatforms, portals and internal tools
Mobile app developmentiOS, Android and cross-platform
SaaS developmentMulti-tenant products that scale
Software integrationConnect the systems you already run
Infrastructure & cloud cost UI/UX design IT consulting QA & software testing R&D Serverless development All software services All servicesSecurity & compliance
Smart contract auditsFind vulnerabilities before launch
Transaction monitoring developmentIntercepta inside your systems and processes
Security assessmentsTest apps, infrastructure and processes
Data security servicesProtect sensitive data across its lifecycle
Cloud security servicesSecure cloud workloads and configurations
DAML smart contract auditReview DAML contracts before they go live
All security services All servicesSolutions
Products, APIs and platforms
New
Products and engineering to build and operate on Canton.
In production 55M API requests served in 8 months
Crypto APIBlockchain data for your applications.
Power in numbers 6 TB Data storage. 500K Tokens indexed
RWA platformA foundation for your asset tokenization platform.
Time to launch 2–4 weeks Branding & setup. 90% more cost-efficient
DocFlowBlockchain-based document management.
Use case & value 100% Secure workflows. Zero third-party risks.
OTC Hawk Arbitrage Bot Book a solution consultWork
450+ projects. 250+ clients. 3 unicorns in portfolio
The first non-custodial wallet built natively for Canton
TON ecosystemA series of improvements for The Open Network
Mining platformEnvironmentally friendly web platform for Bitcoin pool mining
Mantra DAOCommunity-governed DeFi: 60+ staking pools, $23M TVL
Canton TON Web3 & DeFi Digital Assets & Tokenization AI & Data Intelligence IoT & Edge Computing Consulting See all projectsIndustries
Trusted by startups, small businesses, and enterprises
Banking, payments, lending, insurance, capital markets
Real estate software developmentInvestment, property operations, tokenization
Retail & commerce software developmentCommerce, loyalty and fulfillment
Supply chain software developmentTraceability and connected operations
Healthcare software developmentPatient services, data and connected systems
Banking software developmentCore banking, digital channels, payments
Fitness Education Oil & Gas Insurance Construction TravelCompany
From R&D to launch, we bring any of your ideas to life
Engineering partner. Product builder. Since 2007.
Technical experience 19+ years All competencies on board. Scalable team.
AchievementsIndustry recognition & awards.
Delivering real value 4.9 Clutch ratings. 150+ awards
Contact usDiscuss your project.
Quick response 30 min Average reply time. Offices in 6 countries
BlogDive into the latest software trends.
Fresh insights 500+ Articles in blockchain, AI, big data, AR/VR
Team Careers Social responsibility Glossary