Glossary · Blockchain basics

Blockchain

Published 27 Apr 2025 · Updated 1 Nov 2026 · 15 min read

A blockchain is a shared ledger that groups records into blocks, with each block storing the previous block's hash. Many computers, called nodes, keep the records and agree on additions through a consensus protocol. Permissionless blockchains let anyone join, while permissioned blockchains admit only approved operators. Hash links make changes visible rather than impossible.

  • Changing a 2009 Bitcoin block means redoing all later blocks, about 3.1 years at 1 November 2026 mining rates.
  • Permissioned ledgers limit who validates, and private ledgers limit who can read the records.
  • A blockchain makes records tamper-evident, but cannot make their contents true or keep keys safe.

How blockchains link records and agree

A blockchain stores transactions in blocks. Each block in the chain has a header and a list of transactions. The header stores the previous block's hash value, a fingerprint that changes when any input changes. Its Merkle root commits to every transaction. Digital signatures show that the owner's private key authorized a payment. Bitcoin block 170 records the first payment between two people, 10 BTC from Satoshi Nakamoto to Hal Finney, on 12 January 2009.

Figure 1 · Bitcoin blocks 169 to 172, January 2009Try to rewrite Bitcoin block 170Choose an edit to block 170 to compare signatures, hash links, mining work and the blockchain history that still needs rebuilding.
Change
The payment in block 170, 12 January 2009
To Hal Finney10 BTCBack to Satoshi Nakamoto40 BTCTransaction IDf4184fc5…1e9e16
To Hal Finney11 BTCBack to Satoshi Nakamoto39 BTCTransaction ID66dfcc4a…4d127d
Payment to Hal FinneyRemovedLeft in block 17050 BTC reward onlyMerkle rootb1fea524…1c5082
Payment to Hal FinneyRemovedLeft in block 17050 BTC reward onlyMerkle rootb1fea524…1c5082
Payment to Hal FinneyRemovedLeft in block 17050 BTC reward onlyMerkle rootb1fea524…1c5082
What the change does
Satoshi Nakamoto's private key signed this payment. Block 170 commits to it through the Merkle root, and block 171 stores block 170's hash.Valid signatureChecked against Satoshi Nakamoto's public key
Changing the amounts changes the signed data and the transaction ID, so the old signature fails. Only Satoshi Nakamoto's private key could sign the new amounts.Invalid signatureThe key signed 10 BTC and 40 BTC, not the new amounts
A miner could leave the payment out and keep only the 50 BTC reward. The Merkle root changes, so the block hash changes and misses the target.No payment to signThe block keeps only its reward transaction
With the payment gone, the page team searched for a new nonce until the hash met the 2009 target again. Block 171 still points to the old hash.No payment to signThe block keeps only its reward transaction
Block 171 was re-mined on top of the new block 170. Block 172 still points to the old hash. Re-mining it would break 173, and so on up to today.No payment to signThe block keeps only its reward transaction
#169ValidBlock hash000000002a22cfee…84bd55Stored hash of the previous block00000000567e9579…a66a69Matches #168#169ValidBlock hash000000002a22cfee…84bd55Stored hash of the previous block00000000567e9579…a66a69Matches #168#169ValidBlock hash000000002a22cfee…84bd55Stored hash of the previous block00000000567e9579…a66a69Matches #168#169ValidBlock hash000000002a22cfee…84bd55Stored hash of the previous block00000000567e9579…a66a69Matches #168#169ValidBlock hash000000002a22cfee…84bd55Stored hash of the previous block00000000567e9579…a66a69Matches #168
#170ValidBlock hash00000000d1145790…d4a2eeStored hash of the previous block000000002a22cfee…84bd55Matches #169#170Hash too highBlock hash89582d57…8b0539Stored hash of the previous block000000002a22cfee…84bd55Matches #169#170Hash too highBlock hash9386738e…b35b5aStored hash of the previous block000000002a22cfee…84bd55Matches #169#170Re-minedBlock hash000000005599ac85…208f56Stored hash of the previous block000000002a22cfee…84bd55Matches #169#170Re-minedBlock hash000000005599ac85…208f56Stored hash of the previous block000000002a22cfee…84bd55Matches #169
#171ValidBlock hash00000000c9ec538c…bfb4e0Stored hash of the previous block00000000d1145790…d4a2eeMatches #170#171Link brokenBlock hash00000000c9ec538c…bfb4e0Stored hash of the previous block00000000d1145790…d4a2ee#170 no longer has this hash#171Link brokenBlock hash00000000c9ec538c…bfb4e0Stored hash of the previous block00000000d1145790…d4a2ee#170 no longer has this hash#171Link brokenBlock hash00000000c9ec538c…bfb4e0Stored hash of the previous block00000000d1145790…d4a2ee#170 no longer has this hash#171Re-minedBlock hash00000000ee98c5de…b58096Stored hash of the previous block000000005599ac85…208f56Matches #170
#172ValidBlock hash00000000e3efabf6…686854Stored hash of the previous block00000000c9ec538c…bfb4e0Matches #171#172ValidBlock hash00000000e3efabf6…686854Stored hash of the previous block00000000c9ec538c…bfb4e0Matches #171#172ValidBlock hash00000000e3efabf6…686854Stored hash of the previous block00000000c9ec538c…bfb4e0Matches #171#172ValidBlock hash00000000e3efabf6…686854Stored hash of the previous block00000000c9ec538c…bfb4e0Matches #171#172Link brokenBlock hash00000000e3efabf6…686854Stored hash of the previous block00000000c9ec538c…bfb4e0#171 no longer has this hash
#974,1801 November 2026, 21:30 UTCBlocks after #170974,010 blocksToday a hash needs 19 leading zeros
Block 170 meets its targetYesIts hash is below 00000000ffff…
Blocks to redo0Nothing has changed
Blocks built on top since974,010Up to #974,180 on 1 November 2026
Block 170 meets its targetNoThe new hash starts 89582d57
Blocks to redoNot fixableNo amount of mining repairs the signature
Blocks built on top since974,010All of them point back to the original
Block 170 meets its targetNoThe new hash starts 9386738e
Blocks to redo974,011#170 to #974,180
Work to redo1.06 × 10²⁹Hashes, about 3.1 years for today's whole network
Block 170 meets its targetYesNonce 368,771,172, found after 741 million tries in 7 min
Blocks to redo974,010#171 to #974,180
Today's difficulty148.4 trillionTimes the work per block of January 2009
Blocks re-mined25.6 billion tries in 60 min on one cloud server
Blocks to redo974,009#172 to #974,180
Work to redo1.06 × 10²⁹Hashes, about 3.1 years for today's whole network

The original signature verifies, the block hash meets the 2009 target, and all later blocks trace back through this unchanged history.

Paying 11 BTC changes the transaction ID and breaks the signature. Only Satoshi Nakamoto's private key can sign new amounts. Mining cannot fix this.

Removing the payment changes the Merkle root and block hash. The hash misses its target, and block 171 loses its link.

The page team re-mined block 170 without the payment in about 7 minutes. It meets the 2009 target, but block 171 still stores the original hash.

Even with block 171 re-mined, 974,009 later blocks point to the original. Redoing them would take about 3.1 years at the network's 1 November 2026 rate.

The page team read real block data from mempool.space on 1 November 2026 and re-mined edited blocks on one cloud server.

Bitcoin's Proof of Work hashes its 80-byte header twice with SHA-256. Miners change the nonce field until the hash falls below the target set by the difficulty. Bitcoin targets ten-minute blocks. Difficulty rose from 1 in January 2009 to about 148.4 trillion on 1 November 2026, with mining at about 1,070 exahashes per second. The page team summed every Bitcoin block's expected work from difficulty history: about 1.06 × 10²⁹ hashes. Today's whole network would need about 3.1 years to redo it.

Transactions spread over a peer-to-peer network and wait in a mempool. Full nodes verify every transaction and block against consensus rules. Ethereum's Proof of Stake requires validators to deposit 32 ETH. Reverting a finalized block would cost an attacker at least one-third of all staked ETH. Finalization takes about 15 minutes, according to ethereum.org. Approved operators in permissioned systems can use BFT-style voting, with immediate finality once agreed. Bitcoin's finality is probabilistic, with reversal less likely after each block.

The parts of a blockchain

Eight parts appear in almost every blockchain. This table explains what each does, with one example from Bitcoin, Ethereum or Canton. Read in order, the rows follow one payment from signing to acceptance by the network.

PartWhat it isExample
LedgerWhat it isA ledger is a record of transactions that many computers keep in syncExampleBitcoin records the payment from Satoshi Nakamoto to Hal Finney
TransactionWhat it isA transaction is a signed instruction proposing a change to shared recordsExampleBitcoin block 170 records a payment of 10 BTC
Digital signatureWhat it isA digital signature proves that a private key authorized transaction dataExampleChanging block 170's payment to 11 BTC breaks its original signature
BlockWhat it isA block is a header and a list of transactions, linked to the block before itExampleBitcoin's block header contains a previous hash and a Merkle root
HashWhat it isA hash is a cryptographic fingerprint that changes when its input changesExampleBitcoin applies SHA-256 twice to its 80-byte header
Merkle rootWhat it isA Merkle root is one hash that commits to every transaction in a blockExampleRemoving Hal Finney's payment changes block 170's Merkle root
NodeWhat it isA node keeps a copy of the ledger and checks new dataExampleA Canton participant node stores only contracts involving its hosted parties
ConsensusWhat it isConsensus is the process participants use to agree which records to acceptExampleEthereum validators use Proof of Stake to agree on accepted history

Public, private and permissioned blockchains

Public or private describes who can read. Permissionless or permissioned describes who can write and validate. Every blockchain is a distributed ledger, but not every distributed ledger uses a blockchain. Distributed ledger technology (DLT) also includes systems without one shared chain of blocks. In R3 Corda and Canton, each node stores only the records that involve its own parties.

Figure 2 · Six ledgers, checked on 1 November 2026Compare six ledgersSelect a blockchain or another ledger to compare access, data sharing, consensus and finality, then check the distinctions across all six.
Ledger
BitcoinPublic, permissionlessSince 3 January 2009Who adds blocksAnyone with mining hardwareWho can readAnyoneHow data is sharedEvery block goes to every full nodeConsensusProof of Work, the chain with the most work winsFinalityProbabilistic, six blocks or about an hour is the usual ruleSmart contractsBitcoin Script, deliberately limitedBlock producers today3 pools found 63.5% of blocks in the month to 1 Nov 2026
EthereumPublic, permissionlessSince 30 July 2015Who adds blocksValidators who stake 32 ETHWho can readAnyoneHow data is sharedEvery full node keeps a copy of the stateConsensusProof of StakeFinalityAbout 15 minutes for a block to finalizeSmart contractsSolidity or VyperBlock producers today814,338 active validators on 1 Nov 2026
SolanaPublic, permissionlessMainnet Beta since March 2020Who adds blocksStaked validators, in turn on a leader scheduleWho can readAnyoneHow data is sharedEvery block goes to every validatorConsensusAlpenglow since 21 Oct 2026, before that TowerBFTFinalityTarget about 150 ms with Alpenglow, 12.8 s beforeSmart contractsPrograms written in RustBlock producers todayAbout 662 active validators on 1 Nov 2026
Hyperledger FabricPermissionedVersion 1.0 since 11 July 2017Who adds blocksOrdering nodes of member organizationsWho can readMembers of each channelHow data is sharedOne ledger per channel, private data only to approved membersConsensusRaft, or BFT ordering since version 3.0FinalityFinal once a peer validates the blockSmart contractsChaincode in Go, Java or Node.jsBlock producers todaySet by each network, no public count
R3 CordaPermissioned, no blocksOpen source since November 2016Who adds blocksNo blocks. The parties sign, a notary blocks double spendsWho can readOnly the parties involvedHow data is sharedPoint to point, on a need-to-know basisConsensusNotaries using crash or BFT fault toleranceFinalityAt notarizationSmart contractsJVM code, such as Kotlin or JavaBlock producers todayNotaries set by each network
Canton NetworkPermissioned, private by partyGlobal Synchronizer live since 1 July 2024Who adds blocksNo global chain. Super Validators order encrypted messagesWho can readOnly the stakeholders of each contractHow data is sharedEach party receives only its part of a transactionConsensusBFT ordering, then confirmation by the parties' validatorsFinalityWhen the mediator declares the transaction committedSmart contractsDamlBlock producers today13 Super Validator nodes in governance rules and 838 validators on 1 Nov 2026
All six at a glanceLedgerAnyone can validateAnyone can readOne chain of blocksBitcoinYesYesYesEthereumYesYesYesSolanaYesYesYesHyperledger FabricNoNoPer channelR3 CordaNoNoNoCanton NetworkNoNoNo

Anyone can verify Bitcoin's public blockchain history. Proof of Work provides probabilistic finality, not a fixed moment when reversal becomes impossible.

Ethereum has 814,338 active validators on 1 November 2026. Smart contracts run publicly, and a block finalizes in about 15 minutes.

Solana has about 662 active validators on 1 November 2026. Since Alpenglow went live on 21 October 2026, it targets finality in about 150 milliseconds.

Blocks are final once a peer validates them, so a Fabric ledger cannot fork. Each channel keeps its own ledger.

R3 Corda has no blocks or global transaction broadcast. Each node holds its own vault, and notarization establishes finality.

Only a contract's stakeholders see its content. The Global Synchronizer orders encrypted messages, and its governance rules list 13 Super Validator nodes on 1 November 2026.

Figures come from network documentation and public dashboards, checked on 1 November 2026.

Anyone can read a public blockchain, send transactions and run a node. Producing blocks also requires the relevant hardware or stake. Bitcoin, Ethereum and Solana fall into this category, but their timing and participation differ. These networks publish transaction records rather than limiting each record to its counterparties. A reader can check the shared history without receiving access from a company or consortium.

A private blockchain limits who can read, and a permissioned one limits who can write and validate. In a consortium, approved organizations share control. Hyperledger Fabric channels keep separate records. Private collections share data only with authorized organizations and record its hash with channel peers. R3 Corda shares transactions point to point, with notaries preventing double spends. Canton participant nodes store only their parties' Daml contracts. Canton's Global Synchronizer orders encrypted messages without seeing transaction content.

What a blockchain does not guarantee

A blockchain protocol checks signatures, links blocks and orders transactions. It cannot tell whether a business claim is true. It also does not protect the keys, apps, bridges and exchanges around it, and each of those needs its own controls.

Tamper-evident, not unchangeable

Blockchain immutability is conditional. Reorganizations can replace recent blocks. A 51% attack on Ethereum Classic replaced 3,615 blocks between 31 July and 1 August 2020.

People can change rules

Blockchain forks can change accepted history. The DAO fork moved about 12 million ETH in July 2016. In August 2010, a fixed Bitcoin chain replaced one where block 74,638 created 184 billion bitcoins.

Inputs can be false

The oracle problem remains: a blockchain cannot establish whether supplied data reflects real events. Recording an off-chain claim does not verify the goods, measurement or event behind it.

Most losses happen around chains

Chainalysis counts over $3.4 billion stolen in 2025, including $1.5 billion from Bybit. TRM Labs reports $972 million stolen in the first half of 2026, about 76% through compromised keys, custody and signing systems.

Public records are traceable

Bitcoin addresses are pseudonymous, not anonymous. Public transaction histories remain traceable. The EDPB's 7 July 2026 guidelines warn against putting personal data on a blockchain, given GDPR requirements including erasure.

Decentralization varies across networks

In the month to 1 November 2026, three Bitcoin mining pools found 63.53% of 4,686 blocks. Lido accounts for 21.11% of Ethereum's stake on 1 November 2026, according to Rated Network.

Where blockchains are used in 2026

Measured blockchain activity is more informative than a list of industries. The examples below distinguish payment balances, asset records, value locked in apps and settlement volume. These figures describe different things, so they should not be added together as a single measure of blockchain adoption.

Stablecoins and payments

Stablecoin supply is $315.94 billion on 1 November 2026, according to DefiLlama. The US GENIUS Act on payment stablecoins was signed into law on 18 July 2025.

Tokenized assets

The rwa.xyz dashboard reports $39.03 billion in transferable tokenized real-world assets on 1 November 2026. Another $397.97 billion is recorded on platforms where tokens cannot leave the issuer.

Institutional settlement

Broadridge's Distributed Ledger Repo platform processed $7.5 trillion in September 2026, averaging $359 billion daily. JPMorgan's Kinexys reports over $7 billion in average daily transaction volume in its 2025 data.

Decentralized finance

DefiLlama reports $95.55 billion in total value locked on 1 November 2026. These blockchain applications use smart contracts to execute transactions rather than relying only on a central operator.

Bitcoin payments

Bitcoin averaged 719,028 transactions a day from 29 September to 28 October 2026. The US SEC approved spot bitcoin exchange-traded products on 10 January 2024.

DefiLlama tracks 536 chains on 1 November 2026. L2BEAT lists 94 layer 2 projects securing $38.15 billion on the same date. Over the past day, those networks processed about 65 times as many user operations as Ethereum itself. Operations, transactions, asset balances and settlement totals are different measures, not interchangeable indicators of blockchain use.

When a blockchain fits better than a database

A blockchain replaces dependence on one trusted operator with shared verification, but costs speed, money and privacy. Wüst and Gervais's 2018 framework starts with several parties that need to update records without fully trusting one another. A blockchain is not the default answer for shared data. If one operator can be trusted to maintain it, a regular database usually avoids unnecessary coordination and duplicated work.

Figure 3 · Do you need a blockchain?Check your project question by questionAnswer up to six yes or no questions about writers, trust and visibility to see which system the 2018 framework suggests.
  1. 1Do you need to store state?Data that changes over time, such as balances or who owns what
  2. 2Are there multiple writers?More than one party adds or changes the data
  3. 3Can you use an always online trusted third party?One operator everyone accepts. If it is mostly offline, it can still act as a certificate authority for a permissioned chain
  4. 4Are all writers known?Writers are the parties that take part in consensus
  5. 5Are all writers trusted?You can rely on every writer to act honestly
  6. 6Is public verifiability required?Anyone, not only the participants, must be able to check the data
OutcomeDon't use a blockchainNo state means no database is needed. Otherwise a regular database, run by the one writer, a trusted operator or trusted writers, is simpler.
OutcomePermissionless blockchainAnyone can join as a reader and a writer. The paper names Bitcoin and Ethereum.
OutcomePublic permissioned blockchainKnown writers keep the ledger, and anyone can read and verify it.
OutcomePrivate permissioned blockchainKnown writers keep the ledger, and only a limited group can read it.
Question 1 of up to 6

Answer each question in sequence, starting with stored state, to identify the trust and access requirements of your project.

With no state to store, no database is needed at all. With one writer, an always-online trusted intermediary or fully trusted writers, choose a database.

Unknown writers lead to a permissionless blockchain when state and multiple writers are needed and no trusted online intermediary can serve.

Known but mutually untrusted writers point to a public permissioned blockchain when outsiders must verify the records.

Known but mutually untrusted writers point to a private permissioned blockchain when verification can remain within the approved group.

The questions and outcomes follow Wüst and Gervais, Do you need a blockchain? (2018).

Wüst and Gervais's 2018 comparison reports roughly seven Bitcoin transactions per second. Cambridge's 2025 estimate puts annual Bitcoin mining electricity use at 138 TWh. Ethereum's documentation cites a 2022 CCRI estimate of about 0.0026 TWh annually, after The Merge cut electricity use by over 99.988%. The Bitcoin chain was about 779 GB on 28 October 2026. Repeating checks across full nodes also makes large files costly. The EDPB's 7 July 2026 guidelines favor hashes or proofs on chain instead of personal data.

Blockchain projects also need workable governance and a sustainable business model. Maersk and IBM announced TradeLens's closure on 29 November 2022, citing insufficient industry collaboration and lack of commercial viability. The bank trade-finance network we.trade entered liquidation in June 2022. ASX paused its CHESS replacement on 17 November 2022 after a review found significant solution design challenges. The technical choice alone cannot establish commercial viability or secure participation from the organizations that must use the system.

How blockchains developed

Bitcoin did not invent hash-linked records. Earlier timestamping work supplied part of the design, while later networks changed how applications, access and agreement work. The blockchain timeline separates those technical milestones from the regulatory developments affecting blockchain projects in 2026.

  1. 1991

    Linked timestamps precede Bitcoin

    Stuart Haber and W. Scott Stornetta describe linked document timestamps. Bitcoin's white paper later cites this research and their 1993 Merkle-tree extension.

  2. October 2008

    Bitcoin's design becomes public

    Satoshi Nakamoto announces the Bitcoin white paper on 31 October 2008. It describes electronic cash exchanged over a peer-to-peer network without a trusted third party.

  3. January 2009

    Bitcoin's first blocks are mined

    Bitcoin's genesis block on 3 January 2009 quotes a Times headline about a second bank bailout. Block 170 holds the first payment between two people on 12 January 2009.

  4. July 2015

    Ethereum adds programmable applications

    Ethereum launches Frontier on 30 July 2015, adding general smart contracts. Nodes execute deployed code and must derive the same results.

  5. July 2017

    Hyperledger Fabric 1.0 ships

    Hyperledger Fabric 1.0 arrives on 11 July 2017 as a permissioned ledger for companies. Its model separates participation and data access through channels.

  6. September 2022

    Ethereum changes its consensus

    The Merge moves Ethereum from Proof of Work to Proof of Stake on 15 September 2022. Validators who stake ETH now propose its blocks instead of miners.

  7. July 2024

    Canton's Global Synchronizer goes live

    Canton's Global Synchronizer and Canton Coin go live on 1 July 2024. The network combines shared ordering with records held only by relevant parties.

  8. July 2026

    Regulation and data guidance change

    MiCA's transition for existing crypto-asset service providers ends on 1 July 2026. The EDPB adopts version 2.0 of its blockchain personal-data guidelines on 7 July 2026.

Planning a blockchain implementation

Start with the parties, their permissions and the records they need to share. We treat blockchain development as a set of architecture and operational decisions, not a default choice of technology. PixelPlex is a software engineering company founded in 2007, building in blockchain since 2013. These choices determine what the team must build, integrate and operate.

PixelPlex case icon

We built the Echo smart contract protocol, launched in 2017, with its explorer, wallets, bridge and SDK. For Qtum's blockchain implementation, we implemented Proof of Stake consensus on a Bitcoin fork and integrated it with Ethereum and WASM virtual machines. We built Kazakhtelecom's contract platform on Quorum with private smart contracts, and a Hyperledger Fabric document network for Rinne Technologies.

  1. Network and governance

    Choose a public or permissioned network and decide who governs it. For Canton, our Canton development services help teams pick a private synchronizer for a consortium or the Global Synchronizer.
  2. Data boundaries

    Decide which records need blockchain verification and which stay off chain. Keep document contents separate from the hashes used to check them.
  3. Keys and custody

    Assign responsibility for each private key and signing process. Plan custody and access recovery without assuming the network can restore lost keys.
  4. Node and app connections

    Plan node access, indexing and application integration. We deploy, configure and manage Canton participant nodes, with responsibilities agreed before implementation.
  5. Review and operations

    Set a review and monitoring plan before deployment. Include contract behavior, node health, software changes and responses to compromised signing infrastructure.

Discuss the architecture behind your shared records

We can discuss participants, data boundaries and operating responsibilities before you decide whether a blockchain belongs in the design.

Discuss your project

Blockchain FAQ

What is a blockchain in simple terms?

A blockchain is a shared record of transactions kept by many computers. New entries form blocks, and each block stores the previous block's hash, making changes detectable. The computers follow agreed rules, called consensus, to decide which blocks to accept.

How does a blockchain work step by step?

A user signs a transaction with a private key, and nodes check it against the network's rules. Valid transactions are grouped into a block that stores the previous block's hash. Nodes then agree through consensus which blocks to accept. Each later block, or a finality rule, makes an accepted block harder to reverse.

Is blockchain the same thing as Bitcoin?

No. Bitcoin is one application of blockchain technology, focused on recording payments. Ethereum supports general smart contracts, while business networks can restrict participation and data access. The technology describes how records are organized and agreed, not a particular currency.

Can a blockchain be hacked or changed?

Yes. A 51% attack can revise a Proof of Work blockchain's history, but cannot create valid signatures for someone else's keys. Most losses happen around the chain, through keys, exchanges or contract bugs. Chainalysis counts over $3.4 billion stolen in 2025, including $1.5 billion from Bybit.

How do public and private blockchains differ?

A public blockchain lets anyone read its records, while a private blockchain limits reading to approved participants. A separate question is who validates: anyone on a permissionless network, only approved operators on a permissioned one. A permissioned ledger can still be public, so outsiders can verify it.

How is a blockchain different from a database?

A conventional database can place authority with one trusted operator. A blockchain distributes verification among participants, adding coordination and repeated checking. That trade can help parties that distrust one another. It adds little when one writer or mutually trusted writers can maintain the records.

What are blockchains actually used for today?

Blockchains support stablecoin payments, tokenized assets, institutional repo and settlement, decentralized finance and Bitcoin payments. Stablecoins total $315.94 billion on 1 November 2026, according to DefiLlama. Broadridge's repo platform processed $7.5 trillion in September 2026. These uses have different participation and data-sharing requirements.
Sources (35)

Get 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.

Follow us on social networks and don't miss the latest tech news

  • facebook
  • X
  • linkedin
  • instagram
Stay tuned and add value to your feed