Long before Lisk became a recognized name in the blockchain development world, there was Crypti, a bold, early attempt to build a JavaScript-powered decentralized application platform in an era when Ethereum was barely a whitepaper. Founded in 2014, Crypti laid the architectural groundwork for sidechain-based dApp deployment, Delegated Proof of Stake consensus, and developer-first blockchain tooling. This article covers what Crypti was, how it worked, why it was significant, and why it ultimately gave way to the Lisk network.
What Was Crypti?
Crypti was a decentralized application (dApp) platform and cryptocurrency that provided a full-stack solution for deploying truly decentralized applications onto the blockchain. Its native token was XCR, and it positioned itself as a developer platform where JavaScript programmers, already the world’s largest developer community, could build, deploy, and monetize dApps without learning a new language.
Crypti offered APIs and other resources for developers to build and publish decentralized applications, with dApps created and deployed on the Crypti network in three simple steps: development using JavaScript and the provided APIs, deployment via integrated services like GitHub and Sia, and execution across the Crypti master node network.
The Crypti Foundation, the organization behind the project, was headquartered across Germany, Italy, France, and China through an international ambassador network, giving it an early cross-border footprint unusual for projects of its era.
How Crypti Worked: The Technical Architecture
Sidechains and the Main Blockchain
Crypti’s most forward-thinking design decision was its sidechain model. Rather than running every application directly on the main chain (as early Ethereum did), each dApp on Crypti operated on its own independent sidechain.
Crypti dApps were blockchain-based applications that operated on their own custom sidechain, allowing developers to create decentralized applications that used XCR or BTC as an internal currency or token. Each dApp had its own unique private sidechain operating in synchronization with the Crypti block time and current block height.
This design kept the main blockchain small and efficient while giving individual applications the flexibility to set their own rules. Crypti’s decentralized applications operated on their own unique sidechains, with block times of up to 10 seconds.
Delegated Proof of Stake (DPoS)
Crypti was one of the early adopters of Delegated Proof of Stake, a consensus mechanism that remains influential across modern blockchains, including Tron and EOS.
Sidechain consensus was maintained among up to 101 master nodes using the same Delegated Proof of Stake (DPoS) method used to secure the Crypti blockchain. In this model, token holders vote for delegates who are then responsible for validating transactions and forging new blocks. The top 101 delegates by vote weight earned block rewards, creating a democratic but performance-efficient governance structure.
DPoS offered meaningful advantages over Proof of Work: no energy-intensive mining, faster finality, and a more democratic validator selection process.
JavaScript as the Developer Language
The choice of JavaScript was a deliberate, developer-first decision. Max Kordek and Oliver Beddows envisioned a way to make blockchain development more accessible, reasoning that since the internet primarily runs on JavaScript, it made sense to use it for creating a blockchain and dApp platform. This put Crypti in direct philosophical contrast to Ethereum, which required developers to learn Solidity, a new, purpose-built smart contract language.
Storage and Deployment Integration
Crypti is integrated with Sia (a decentralized cloud storage platform) and GitHub for code deployment, giving developers familiar tooling. Developers could store their code on GitHub or through the Sia integration and utilize the Crypti master nodes to execute the code.
Crypti’s First dApp: Crypti Tokens
The Crypti Foundation released its first dApp, Crypti Tokens, in December 2015, allowing users to issue their own custom tokens and send and receive them on the Crypti Tokens sidechain. This was a significant milestone, demonstrating that the platform’s sidechain architecture was functional and that custom token issuance was achievable outside the Ethereum ecosystem.
However, the dApp also highlighted some of the platform’s early-stage limitations, and critics at the time noted that Crypti was competing in an increasingly crowded dApp platform space alongside Ethereum, NXT, and others.
The Fork: Why Crypti Became Lisk
Crypti’s story doesn’t end with obsolescence; it ends with evolution. Lisk was created by Max Kordek and Oliver Beddows in 2016 as a fork of Crypti. Max and Oliver were part of the Crypti development team but decided to fork the Crypti code and start Lisk due to disagreements within the Crypti network.
Despite being successful on a community level, Crypti was forked by its founders due to the need to develop further. The disagreements reportedly centered on management direction and the pace of development within the Crypti Foundation.
What Changed in the Fork
Lisk started as a fork of Crypti, beginning with an ICO to decide the initial distribution and raise development funds. The ICO raised 14,000 BTC, at the time, the second most successful cryptocurrency crowdfund. Among the key technical improvements Lisk made over Crypti were a database upgrade from SQLite to PostgreSQL and a fully open-source, publicly visible development process on GitHub.
Lisk funded its vision by holding a four-week crowdsale, with Kordek becoming very involved in cryptocurrency as a college student in 2013 before becoming an active member of the Crypti cryptocurrency team.
The massive community support Crypti had built transferred to Lisk almost entirely; in fact, 80 percent of all existing Crypti tokens were sold to support the Lisk crowdsale, a remarkable signal of confidence in the new direction.
Crypti’s Legacy in the Blockchain Ecosystem
Even though Crypti is no longer actively developed, its architectural contributions remain relevant.
Sidechain Architecture
The idea that each dApp should run on its own sidechain, rather than competing for resources on a shared main chain, was ahead of its time. Today, Layer 2 solutions, rollups, and application-specific chains are among the most discussed scalability strategies in blockchain, validating the core intuition behind Crypti’s design.
JavaScript-First Development
Crypti’s emphasis on developer accessibility through mainstream programming languages directly influenced Lisk’s positioning and, more broadly, the growing movement toward developer-friendly blockchain tooling. Modern platforms like Hardhat (Ethereum’s JavaScript testing framework) and the wider Web3.js ecosystem reflect this same philosophy.
DPoS Consensus Adoption
The DPoS concept, first outlined by Daniel Larimer in 2014, saw further adoption in major blockchain projects including Steem and EOS. Crypti was among the early platforms to implement DPoS in a production context, contributing to its validation as a viable consensus model.
Crypti vs. Ethereum: A Side-by-Side View
| Feature | Crypti | Ethereum (2014–2016) |
|---|---|---|
| Developer Language | JavaScript | Solidity (new language) |
| Consensus | DPoS | Proof of Work |
| App Architecture | Sidechains | Main chain (EVM) |
| Token Standard | XCR | ETH / ERC-20 |
| Status | Inactive (forked → Lisk) | Active, dominant |
| Key Legacy | Inspired Lisk | Industry standard |
Is Crypti (XCR) Still Active?
As of 2026, Crypti is effectively a legacy project. The original team departed to build Lisk, and the platform has not seen meaningful development since 2016. XCR tokens exist on record but are not actively traded on major exchanges, and the Crypti Foundation does not appear to be operational.
Anyone encountering XCR offerings on obscure platforms should exercise extreme caution; the coin holds no current utility or active development backing, and any trading market for it would be highly illiquid and speculative. This is not an investment recommendation in either direction; it is simply an accurate description of the project’s current state.
FAQs:
What is Crypti in cryptocurrency?
Crypti (XCR) was a JavaScript-based decentralized application platform and cryptocurrency launched in 2014. It was designed to let developers build and deploy dApps on individual sidechains using DPoS consensus. Crypti is best known today as the predecessor project from which Lisk was forked in 2016.
What is the difference between Crypti and Lisk?
Lisk is a fork of Crypti, created in 2016 by the same founding team, Max Kordek and Oliver Beddows, after disagreements within the Crypti Foundation. Lisk upgraded several technical components (including the database layer), ran a successful ICO raising 14,000 BTC, and has been actively developed ever since, while Crypti ceased active development after the fork.
What does XCR stand for in crypto?
XCR is the ticker symbol for the Crypti cryptocurrency. It was the native token used to power transactions, pay network fees, and fund dApp deployments on the Crypti platform. XCR is no longer actively traded on major exchanges, and the project is considered inactive.
What programming language did Crypti use?
Crypti used JavaScript for dApp development, a deliberate choice to lower the barrier to entry for blockchain development by letting the world’s largest developer community build on the platform without learning a new language. This same philosophy was carried forward into Lisk.
Why did Crypti fail?
Crypti did not fail so much as it was superseded by its own founders. Internal management disagreements led Max Kordek and Oliver Beddows to fork the codebase in early 2016 and launch Lisk, taking the majority of the Crypti community with them. Without its core development team, Crypti had no realistic path forward.
What is Crypti’s relationship to the Lisk Foundation?
Crypti’s website acknowledged the transition directly, noting that the Lisk Foundation was continuing the Crypti vision. Lisk inherited the sidechain architecture, JavaScript-first philosophy, and DPoS consensus model from Crypti, making Crypti the conceptual and technical foundation of everything Lisk built.
Final Words
Crypti occupies a unique place in blockchain history: a project that succeeded not by surviving, but by seeding something larger. Founded in 2014 as one of the earliest JavaScript-based dApp platforms, it introduced sidechain architecture, DPoS consensus, and developer accessibility to the blockchain world at a time when Ethereum was still under construction. When its founders forked it into Lisk, which went on to raise $6.5 million in one of crypto’s most successful early ICOs, Crypti’s core ideas were vindicated rather than abandoned.
For developers, historians, and blockchain enthusiasts, understanding Crypti means understanding the intellectual lineage of modern developer-first blockchain platforms. The next time you read about Layer 2 sidechains or JavaScript dApp frameworks, you’re reading the echo of what a small international team tried to build a decade ago in Aachen and Birmingham.
For any suggestions or changes, please contact us.