LogoLogo
eckoDAOeckoDEXeckoWalleteckoGOV
  • 👾Welcome
    • eckoDAO - Introduction
    • Product Suite
    • $KDX Tokenomics
      • $KDX Token Distribution
      • $KDX Liquidity Mining
    • Governance
  • 🔄eckoDEX
    • Introduction
    • eckoDEX Litepaper
      • Why eckoDEX?
        • Problems in DeFi
        • Solution: Long Term Scalability
        • Solution: Gas-free
        • Solution: Slippage Control
        • Solution: Decentralised Infrastructure
        • Solution: Secure Smart Contracts
      • Industry Outlook
        • DEX Market Potential
        • eckoDEX: The Next Generation of DEXes
      • Vision
    • Platform
    • How to Swap
      • X-Swap
      • The eckoDEX Wrapper
    • Migrate liquidity from eckoDEX Beta to Mainnet V1
    • How to Add Liquidity
      • Single-Sided Liquidity
      • Understanding Liquidity Provision and Impermanent Loss
    • Governance Mining
      • Understanding Governance Mining
  • 💰eckoWALLET
    • Introduction
    • eckoWALLET API
    • Quicksign: KIP-0015
    • WalletConnect
    • FAQ
  • 🏛️eckoGOV
    • 👋Welcome to eckoGOV
      • 📚Litepaper Overview
    • 🚀Getting Started
      • 📋Minimum Requirements
      • 📥Login
      • 🌍Spaces
        • 💰Spaces Treasury
      • 👥Members
        • 🔠Edit Profile
    • 🧑‍🏫Role System
      • 1️L1 - eckoMEMBER
      • 2️L2 - eckoLEAD
      • 3️L3 - eckoCORE
      • 🧮Voting Power
      • 🙋Applying for a eckoDAO Role
      • 🔎KYC
    • 🌀Proposal Epoch
      • 🗃️Proposal Categories
      • 📑Creating Proposals
        • 🧾Proposal Template
        • 👍Proposal Example
      • 📊Voting on Proposals
      • 🗣️Discourse - Proposal Discussion
    • 💰Using the KDX Treasury
    • 📄Smart Contracts
  • 🔒Security & Contracts
    • Bug Bounty
    • Audits
  • 🤝Marketing
    • Social & Communities
    • eckoDAO Brand Assets
    • eckoWALLET Brand Assets
  • ⚡SDK
    • Overview
    • Quickstart
    • Reference
      • eckoDEX SDK
        • createPair
        • addLiquidity
        • removeLiquidity
        • swap
        • swapExactIn
        • swapExactOut
      • retrieveVerifiedAccount
      • TOKENS
Powered by GitBook
On this page
  1. eckoDEX
  2. eckoDEX Litepaper
  3. Why eckoDEX?

Solution: Secure Smart Contracts

PreviousSolution: Decentralised InfrastructureNextIndustry Outlook

Last updated 1 year ago

Half of the time DeFi is in the news is because of hack that has caused a massive leak of funds from a DeFi protocol. No matter the size of the attack and whether or not it was fixed, the project and protocol never recover. Many of these vulnerabilities are direct consequence of the language they were developed in, Solidity, being Turing complete.

Turing completeness describes the ability of the language to express all tasks accomplishable by computers. This sounds powerful in theory, creating no bounds to what could be done on the blockchain (if we ignore gas). But what started as a powerful idea has actually turned into a problem. With this open-ended ability came hard to anticipate attack vectors. To date, there are 16 known attack vectors in Solidity, which much of the DeFi ecosystem is built upon, most of which would not be possible if Solidity was Turing incomplete.

With Turing completeness comes unnecessary risk.

Kadena’s smart contract language, Pact, seeks to improve on this problem by designing a language with the known limitations of blockchain in mind, resulting in a Turing incomplete language that is purpose driven to produce easy to read, secure and efficient smart contracts. This is amplified by the built-in support of formal verification, giving developers immediate feedback on possible bugs that would otherwise go unnoticed. This overlooked detail ensures eckoDEX will be not only secure transactionally via PoW but also secure from attack.

🔄
Figure 2 – Unnecessary risk associated with turing completeness