Glossary · Consensus
Published 28 Apr 2025 · Updated 3 Nov 2026 · 16 min read
Consensus is the set of rules and messages by which the nodes of a blockchain or distributed ledger agree which transactions are valid and in what order. It keeps one shared history even when some nodes fail or lie, within the protocol's fault assumptions. Agreement requires enough participants under those rules, not unanimous approval.
Copies of a ledger sit on computers that receive transactions in different orders. Some computers may be offline or dishonest. A distributed ledger needs rules for selecting records and their sequence despite those differences. Consensus supplies those rules. The definitions below show how ISO 22739:2024, MiCA and NIST IR 8202 describe agreement, transaction validation and a shared state.
| Source | Date | Definition, in its own words | What it adds |
|---|---|---|---|
| ISO 22739:2024 | DateJanuary 2024 | Definition, in its own words"agreement among distributed ledger technology (DLT) nodes that: a transaction is validated; the distributed ledger contains a consistent set and ordering of records of validated transactions" | What it addsValidation and order. "Consensus does not necessarily mean that all DLT nodes agree." |
| MiCA, Article 3(1)(3) | Date31 May 2023 | Definition, in its own words"the rules and procedures by which an agreement is reached, among DLT network nodes, that a transaction is validated" | What it addsThe EU's legal term, also used in the DLT Pilot Regime |
| NIST IR 8202 | DateOctober 2018 | Definition, in its own words"A process to achieve agreement within a distributed system on the valid state." | What it addsWhen versions conflict, most networks treat the longer chain as correct |
| ethereum.org | DateUpdated 22 April 2026 | Definition, in its own words"the complete stack of ideas, protocols and incentives that enable a distributed set of nodes to agree on the state of a blockchain" | What it addsProof of work and proof of stake are Sybil resistance, not the whole protocol |
| Bitcoin white paper | Date31 October 2008 | Definition, in its own words"The majority decision is represented by the longest chain, which has the greatest proof-of-work effort invested in it." | What it adds"Proof-of-work is essentially one-CPU-one-vote." |
| Lamport, Shostak and Pease | DateJuly 1982 | Definition, in its own words"All loyal generals decide upon the same plan of action." | What it addsAgreement despite traitors: 3m + 1 generals cope with m traitors when messages are unsigned |
Each full node checks signatures and balances itself. A consensus mechanism chooses one order and history among valid but conflicting alternatives. Two transactions can each pass those checks separately while spending the same funds. Ordering them prevents a double spend because both cannot stand in the accepted history. ISO 22739:2024 explicitly says consensus need not include every DLT node. Nodes can see different newest blocks for a while and still agree on the history the rules accept.
In the 1982 Byzantine Generals problem, commanders must agree on one plan despite traitors sending misleading messages. Lamport, Shostak and Pease showed that unsigned messages need at least 3m + 1 generals to tolerate m traitors. With signed messages, their problem is solvable with any number of generals and traitors. Ledger nodes take the commanders' place. A validator sends proposals or votes, while the consensus protocol defines which combinations establish an agreed history.
A fault threshold belongs to a specific model, not to blockchains in general. Consensus rules distinguish stopped participants from dishonest ones. The table uses f, the number of faulty nodes tolerated. Safety and liveness depend on timing assumptions as well as participant numbers.
| Fault model | Nodes needed for f faults | Example | Source |
|---|---|---|---|
| Crash or omission, partially synchronous network | Nodes needed for f faults2f + 1 | ExampleRaft: five servers keep working with two down | SourceDwork, Lynch and Stockmeyer, April 1988. Raft, May 2014 |
| Byzantine, unsigned messages | Nodes needed for f faults3f + 1 | ExampleFour generals cope with one traitor | SourceLamport, Shostak and Pease, July 1982 |
| Byzantine, signed messages, synchronous network | Nodes needed for f faultsAny number | ExampleSolvable for any number of traitors | SourceLamport, Shostak and Pease, July 1982 |
| Byzantine, partially synchronous, signed or not | Nodes needed for f faults3f + 1 | ExamplePBFT, Tendermint and HotStuff: four validators tolerate one | SourceDwork, Lynch and Stockmeyer, April 1988. PBFT, February 1999 |
| Any fault, fully asynchronous, deterministic protocol | Nodes needed for f faultsNo protocol always decides | ExampleOne crashed process can block a decision forever | SourceFischer, Lynch and Paterson, April 1985 |
Safety means correct nodes never decide differently. Liveness means they eventually decide. Crash faults stop nodes, while Byzantine fault tolerance covers arbitrary behavior, including contradictory messages. Crash consensus needs 2f + 1 nodes under partial synchrony. Byzantine consensus needs 3f + 1, with 2f + 1 votes per quorum. Two such quorums overlap in at least f + 1 nodes, including an honest one. Crash majorities also overlap. Raft tolerates two crashes among five servers. GoQuorum's documentation stresses that Raft handles crashes only, assuming an honest leader.
The 1985 FLP result rules out guaranteed deterministic consensus under unbounded message delays with even one possible crash. Partial synchrony, formalized in 1988, allows timing bounds that are initially unknown or only eventually hold. PBFT preserves safety without synchrony but needs it for liveness. Timeouts enable retries. In November 2026, CometBFT's default proposal timeout starts at three seconds and grows by half a second each round. When agreement fails, Stellar and the XRP Ledger stop rather than diverge. Ethereum can keep producing blocks without finalizing.
An open network cannot treat every identity as an equal vote. A consensus mechanism therefore needs both participation rules and an agreement rule. Work, stake or admission determines influence. Fork choice and voting then determine which proposed history the participants accept.
Ethereum's documentation, updated 22 April 2026, describes proof of work and proof of stake as Sybil resistance mechanisms and block author selectors. Neither alone is a complete consensus protocol. Spending energy or providing collateral creates an economic deterrent to Sybil attacks. Permissioned systems instead restrict admission. This separates the cost or permission needed to participate from the rules that turn eligible participants' messages into one decision.
In November 2026, Bitcoin pairs work with most cumulative work, while Ethereum pairs stake with Gasper's LMD-GHOST fork choice and validator votes. Solana pairs stake with Alpenglow's Votor voting. Hedera combines admitted, stake-weighted council nodes with hashgraph virtual voting. Avalanche's Snowman uses repeated, stake-weighted subsampled voting. Stellar uses federated quorums, while XRP Ledger participants use UNL lists. Cardano's developer portal contrasts Raft's honest-node assumption with Ouroboros's Byzantine model. Praos selects the longest chain. Eligibility alone therefore does not identify the consensus algorithm.
A consensus protocol turns proposals into decisions through messages and waiting rules. Choose Nakamoto, Raft, PBFT, Tendermint or HotStuff, then select 4, 7, 10, 31, 100 or 180 validators. Step through each exchange to see senders, recipients, the waiting quorum, tolerated faults and the running message count.
Nakamoto uses blocks and confirmations, not voting rounds. There is no leader to replace when block production pauses.
One leader collects majority acknowledgements before committing. This consensus model tolerates crash faults, not dishonest behavior.
Three phases include all-to-all prepare and commit messages. A timeout triggers a view change to replace the primary.
Propose, prevote and precommit form a round. After a timeout, participants advance to another round with the next proposer.
Votes go to the leader, so message counts grow linearly. Basic HotStuff uses additional phases before committing.
Message counts are the page team's model from protocol papers and ignore gossip, batching and signature aggregation.
PBFT's 1999 protocol uses pre-prepare, prepare and commit. Preparing requires 2f backup prepares matching the pre-prepare, and committing requires 2f + 1 commits. Tendermint and its fork CometBFT use propose, prevote and precommit, with more than two thirds of voting power needed to commit. Raft instead commits an entry once its originating leader replicates it to a majority. The 1999 paper's PBFT file system was only 3% slower than an unreplicated one.
All-to-all voting drives the page team's 100-participant model to 19,800 messages for PBFT and 19,899 for Tendermint. Basic HotStuff needs 792, with votes collected by a leader. Chained HotStuff overlaps consecutive blocks' phases, committing through a three-chain pattern. In November 2026, Flow documents Jolteon, and Aptos uses AptosBFT from the same lineage. Monad compares MonadBFT with pipelined HotStuff-family consensus protocols. Sui's Mysticeti instead uses a directed acyclic graph. These model counts are not measured traffic.
Acceptance does not always rule out chain forks. Probabilistic finality reduces reversal risk, economic finality attaches penalties, and deterministic or absolute finality excludes reversal within stated assumptions. At 05:01 UTC on 3 November 2026, Ethereum's newest block was 79 slots, or 15.8 minutes, ahead of its finalized checkpoint.
At 50%, no confirmation count prevents eventual catch-up, consistent with Ethereum Classic's and Bitcoin Gold's 2020 majority attacks.
At 25% to 45% attacker hash power, reaching below 0.1% probability takes 15 to 340 blocks.
Below 25% attacker hash power, catch-up probability falls quickly as confirmations accumulate in the white paper's model.
Probabilities use the Bitcoin white paper's formula, computed in this page with 10-minute blocks.
The Bitcoin white paper gives a 10% hash-power attacker about a one-in-1,094 catch-up chance after six confirmations. At 30%, falling below 0.1% takes 24 blocks. In November 2026, Ethereum finality takes two epochs, calculated as 12.8 minutes, or about 15 minutes in Ethereum's documentation. Reverting finalized history requires losing at least one third of staked ETH. Casper FFG's accountable safety means conflicting finalized checkpoints require at least one third of validators to violate slashing conditions.
CometBFT finalizes a block once over two thirds of voting power precommits it. Fabric guarantees that validated blocks are final, and Canton documents no forks, reorganizations or rollbacks. Solana's Alpenglow, live since 21 October 2026, finalizes in one round with 80% of stake or in two with 60% certificates, targeting about 150 ms. Confirmed and finalized now describe the same state. Polkadot's GRANDPA finalizes all blocks up to one that more than two thirds of validators attest to. Ethereum research targets a few tens of seconds, with no fork date.
The table separates agreement rules, participation rules and finality for twelve networks on 3 November 2026. A block time or slot target is not a promise of settlement. Hedera orders events rather than blocks, and Canton has no single chain that all nodes replicate, so their timing needs different labels.
| Network | Agreement rule | Sybil resistance | Block or slot time | Finality as documented | Validators or producers |
|---|---|---|---|---|---|
| Bitcoin | Agreement ruleMost cumulative work (Nakamoto) | Sybil resistanceProof of work | Block or slot time600 s target, 598.4 s over 14 blocks to 974,344 | Finality as documentedProbabilistic, 6 confirmations in about an hour | Validators or producersAny miner |
| Ethereum | Agreement ruleGasper: LMD-GHOST and Casper FFG | Sybil resistanceProof of stake, 32 ETH minimum | Block or slot time12 s slots | Finality as documentedTwo epochs, 12.8 min (about 15 min per ethereum.org) | Validators or producers814,678 active validators, 44.3M ETH staked (3 Nov 2026) |
| Solana | Agreement ruleAlpenglow's Votor since 21 Oct 2026 | Sybil resistanceProof of stake | Block or slot time200 ms target | Finality as documented80% in one round or 60% in two, ~150 ms target | Validators or producers659 staked validators (Solana Compass, 3 Nov 2026) |
| Cosmos Hub | Agreement ruleCometBFT (Tendermint) | Sybil resistanceProof of stake | Block or slot time5.72 s measured | Finality as documentedOne block, more than 2/3 precommits | Validators or producers180 bonded (2 Nov 2026) |
| Polkadot | Agreement ruleBABE production, GRANDPA finality | Sybil resistanceNominated proof of stake | Block or slot time6 s slots | Finality as documentedMore than 2/3 attest to a chain | Validators or producers600 in the active set |
| Avalanche C-Chain | Agreement ruleSnowman (k 20, α 15, β 20) | Sybil resistanceProof of stake, 2,000 AVAX | Block or slot timeDynamic since 19 Nov 2025 | Finality as documentedAbout 1 s per its docs | Validators or producers556 (2 Nov 2026) |
| Cardano | Agreement ruleOuroboros Praos, longest chain | Sybil resistanceProof of stake pools | Block or slot time1 s slots, about 20 s per block | Finality as documentedPractical in minutes, settled after about 12 h | Validators or producers2,856 pools with stake (2 Nov 2026) |
| BNB Smart Chain | Agreement ruleParlia with fast finality votes | Sybil resistanceStake-elected validator set | Block or slot time0.45 s since 14 Jan 2026 | Finality as documentedWithin two blocks, about 1.125 s | Validators or producers45 active (21 Cabinet, 24 Candidates) |
| XRP Ledger | Agreement ruleXRPL consensus, 80% of a UNL | Sybil resistanceEach server's UNL | Block or slot timeA ledger every several seconds | Finality as documentedValidated ledger, 3 to 6 s settlement | Validators or producersSet per server |
| Hedera | Agreement ruleHashgraph, virtual voting | Sybil resistanceCouncil nodes weighted by stake | Block or slot timeNo blocks at the consensus layer | Finality as documented3 to 5 s absolute finality | Validators or producers30 consensus nodes (3 Nov 2026) |
| Aptos | Agreement ruleAptosBFT (Jolteon family) | Sybil resistanceProof of stake | Block or slot timeNot stated in the docs read | Finality as documentedOrdering after 3 network hops | Validators or producers83 active (3 Nov 2026) |
| Canton Network | Agreement ruleBFT ordering by Super Validators, then a mediator verdict | Sybil resistanceAdmission by Super Validator sponsors | Block or slot timeNo chain all nodes replicate | Finality as documentedMediator verdict, no rollbacks | Validators or producers847 validators, 61 Super Validator nodes (3 Nov 2026) |
Counts reflect different trackers and read times, not identical categories of participation. Public trackers also differ on Solana's count. Alpenglow went live there on 21 October 2026. Canton's Global Synchronizer uses BFT ordering run by Super Validators in November 2026. Its documentation and release notes describe the ordering protocol differently, and no MainNet change date is published. Finality times in the table are each network's documented figures, not measurements.
Consensus can fail by accepting conflicting records or by making no progress. A partition exposes that distinction without requiring a dishonest participant. The model separates block production from finality and matches each rule to a dated incident from 2010 to 2025.
Both sides keep mining. When connectivity returns, the chain with less cumulative work loses its blocks through reorganization.
During a long equal split, blocks continue and finality pauses. The inactivity leak restores it on both sides after weeks, requiring social recovery.
A side above two thirds of voting power keeps committing. Otherwise, the chain halts without a fork.
The majority side can elect a leader and commit entries. A minority cannot commit, and an equal split stops both sides.
This page-team model applies protocol rules. Ethereum leak times come from a simulation of the consensus specifications.
| Date | Network | Family | What was lost | Length or amount |
|---|---|---|---|---|
| 15 Aug 2010 | NetworkBitcoin | FamilyNakamoto | What was lostSafety: nodes accepted an invalid block | Length or amountThe good chain overtook it at block 74,691, 53 blocks later |
| 11 to 12 Mar 2013 | NetworkBitcoin | FamilyNakamoto | What was lostSafety: a split between client versions | Length or amount0.8 side held about 60% of hash power, one large double spend |
| May 2018, Jan to Feb 2020 | NetworkBitcoin Gold | FamilyNakamoto | What was lostSafety: 51% attacks | Length or amount388,000 BTG stolen, then 12,858 BTG double spent |
| 5 to 7 Jan 2019 | NetworkEthereum Classic | FamilyNakamoto | What was lostSafety: 51% attack | Length or amount15 reorganizations, 219,500 ETC double spent |
| 31 Jul to Aug 2020 | NetworkEthereum Classic | FamilyNakamoto | What was lostSafety: 51% attacks | Length or amount807,260 ETC double spent, more than 3,600 blocks replaced |
| 2 Nov 2020 | NetworkCloudflare etcd (not a blockchain) | FamilyRaft | What was lostLiveness of writes | Length or amountAPI and dashboard affected for 6 h 33 min |
| 11 Nov 2020 | NetworkEthereum (proof of work) | FamilyNakamoto, client bug | What was lostSafety for nodes on old Geth versions | Length or amountAbout 30 blocks on a shorter chain |
| Sep 2021 to Feb 2024 | NetworkSolana | FamilyTowerBFT with Proof of History | What was lostLiveness | Length or amountSix outages, 4.5 to about 19.7 hours |
| 11 to 12 May 2023 | NetworkEthereum | FamilyGasper | What was lostLiveness of finality | Length or amount4 epochs, then 9 to 10 epochs, 28 ETH in penalties |
| 5 to 6 Jun 2024 | NetworkCosmos Hub | FamilyCometBFT | What was lostLiveness | Length or amountHalted 4 h 40 min, no fork |
| Nov 2024, Feb 2025 | NetworkXRP Ledger | FamilyUNL consensus | What was lostLiveness | Length or amountAbout 10 minutes, then about 64 minutes |
The 2013 Bitcoin split and Ethereum Classic's January 2019 majority attack show different routes to lost safety. BFT outages instead illustrate lost liveness, including Cosmos Hub's June 2024 halt. Ethereum's May 2023 incidents interrupted finality while blocks continued. The second interruption lasted about 64 minutes and activated the inactivity leak. Recovery also involved people, including Bitcoin pools downgrading in March 2013 and validators coordinating Solana restarts during its 2021 to 2024 outages.
Admission changes who participates, not the need for agreement. A permissioned ledger can use crash-tolerant or Byzantine consensus, depending on its trust assumptions. Operators, membership authorities, notaries or sequencers still carry responsibilities. Knowing the participants does not make their services incapable of failure.
Fabric v3.0.0 introduced SmartBFT alongside Raft ordering in its 17 September 2024 release. Corda's notary provides uniqueness consensus. Corda Enterprise's highly available notary is a cluster run by one party that tolerates crash faults, and its BFT notary is still experimental. Besu QBFT requires signatures from at least two thirds of admitted proof of authority validators, giving immediate finality. More than one third stopping prevents new blocks. GoQuorum's repository was archived on 5 June 2026. These implementations retain different fault assumptions despite restricted membership.
Canton documentation says the sequencer gives all validators messages in the same order and sees only encrypted data. Each validator confirms or rejects solely from its own view. The mediator collects confirmations from participant nodes hosting signatories, while observers need not confirm. Global Synchronizer Super Validators operate sequencer and mediator nodes with two-thirds BFT consensus for ordering and confirmation. Public counts read on 3 November 2026 showed 847 validators and 61 Super Validator nodes.
Agreement is one part of a ledger's behavior. It does not certify outside information or remove software and operational dependencies. These limits apply differently across consensus designs, so a protocol's guarantees should be read together with its assumptions and recovery rules.
Consensus orders transactions accepted under ledger rules. It cannot establish whether submitted data accurately describes a real event outside the network.
Nakamoto consensus cannot preserve history against an attacker controlling more than half the hash power. Ethereum Classic's 2020 and Bitcoin Gold's 2018 attacks demonstrate that limit.
Missing voting power can stop BFT progress. Cosmos Hub halted in June 2024, while Solana's 6 February 2024 outage stopped block finalization for about five hours.
Consensus cannot repair a shared validation mistake. Bitcoin's August 2010 bug accepted an invalid block, while client differences split Bitcoin in March 2013 and Ethereum in November 2020.
Protocol rules do not automate every recovery decision. Ethereum documents social recovery after conflicting finalized forks, while Solana's September 2021 restart required validator coordination.
Public consensus exposes transactions to validators rather than supplying confidentiality itself. Canton documentation states that the sequencer and other synchronizer infrastructure see only encrypted data.
Consensus research is older than blockchains. Pease, Shostak and Lamport's paper of April 1980 came first, and Lamport's Paxos was submitted in January 1990 and published in May 1998. The eight events below trace the line to Solana's change in October 2026.
Lamport, Shostak and Pease formalize agreement despite traitors. Their distinction between unsigned and signed messages shows why communication assumptions change the faults a protocol can tolerate.
Fischer, Lynch and Paterson show that fully asynchronous deterministic agreement cannot guarantee termination with one possible crash. The result does not rule out practical consensus systems.
Castro and Liskov present Practical Byzantine Fault Tolerance. Its replicated service uses pre-prepare, prepare and commit, with timeout-triggered view changes when the primary fails to make progress.
Bitcoin's 3 January 2009 genesis block follows the 31 October 2008 white paper. Nakamoto consensus connects block publication to accumulated computational work.
The 20 May 2014 Raft paper explains replicated logs through an elected leader and majority replication. Tendermint also begins in 2014, addressing agreement under a Byzantine fault model.
Buterin and Griffith publish Casper FFG, connecting checkpoint finalization with accountable safety. Conflicting finalized checkpoints imply that at least one third of validators violated a slashing condition.
The 15 September 2022 Merge moves Ethereum from proof of work to proof of stake. Its beacon chain had started on 1 December 2020.
Solana activates Alpenglow at epoch 1064, starting 21 October 2026. Votor replaces TowerBFT voting, and Proof of History no longer paces block production.
A protocol name leaves important engineering choices unresolved. Our blockchain development services include custom layer-1 protocol development and novel consensus mechanisms. We distinguish the agreement rules from the operating decisions around them. The five areas below help define the system a team intends to build or run, without treating any protocol as universally suitable.
PixelPlex has built blockchain software since 2013. Echo, our own protocol, went live in 2017. The Echo case describes its proof-of-weighted-randomness consensus as a Byzantine agreement protocol with a small committee of block producers and fast finality. On Canton, we are a validator operator and run our own production infrastructure that the ecosystem depends on daily.
Discuss the assumptions behind your consensus layer
We can discuss your fault model, participation rules and finality requirements before considering an implementation.
Discuss your requirementsGet 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