Scalable DAG-based distributed ledger protocol using Avalanche consensus
Visit Perlin ICO site
PRE ICO Dates : 10/09/18 – 28/09/18
Assessing from how distributed ledgers have scaled throughout the years, Perlin introduces a different mindset as to how distributed ledgers may be utilized for the development of decentralized applications and technical infrastructure.
For example, Perlin was intentionally designed to not support Turing-complete smart contracts. Rather, should a developer wish to develop a decentralized application on Perlin, developers would instead utilize Perlin as a ledger that bypasses middlemen and brings finality and consensus into off-chain high-throughput computing systems.
Hence, rather than having Turing-complete smart contracts, Perlin provides a platform in which developers can both write and run smart contracts compiled as WebAssembly bytecode that only exist for the sake of bringing finality and consensus into an off-chain system.
More specifically, smart contracts work as either time, resource, or signature lock verification mechanisms redundantly computed across all nodes in Perlin’s network which reward, deplete, or release funds that are in the form of mintable tokens called perls.
The first mechanism that Perlin bootstraps on top of Avalanche consensus is the ability to create, test, destroy, and deploy smart contracts representing time, resource, or signature locks that run as WebAssembly byte code.
All forms of locks are intended to be verifiable in a timely manner by being limited to being represented under Q instructions, as locks are redundantly computed on every node in Perlin’s network. An inability to meet this aforementioned criterion results in the lock from being rejected within the system.
PERL token will initially be distributed as ERC20 tokens. However PERLs will be swapped with our native token upon the release of our mainnet.