Overview

PepperDB is a decentralized database based on blockchain technology.

Project stage

Only a whitepaper

Detailed description

PepperDB is a decentralized database that makes DApp developers build DApps much easier and lower down blockchain storage cost tremendously, and with our Pepper Rank (Inspired by Google PageRank) system, PepperDB is able to self-evolving continuously.

PepperDB provides a SDK that supports SQL/NoSQL operations directly on blockchain, which release developers from coding and testing complex smart contracts.

PepperDB also achieved best data compression ratio than anyone else in the market, which has already been proven inside Alibaba Cloud (Alibaba bought the license of TerarkDB storage engine, which is an implementation of our technology). Our Searchable Compression technology can access data directly on highly compressed data file, which means it is much faster than ever (No decompression cost).

Problem

DApp Development is Painful
One of the most famous blockchain that supports smart contract development is Ethereum. If a Ethereum developer wants to do something special rather than to make a simple token or a simple crowdsale, he is likely to create his own smart contract. But a serious Ethereum smart contract development requires a programming language like Solidity or Javascript, a Ethereum client like Ganache, a test / debug / deploy environment like Truffle, and some new developers may need a secure smart contract library like OpenZeppelin.

Block Data Grow Too Fast
We all know that blockchain data is growing very fast and there seems no efficient way to reduce the growth speed. Some people turn to new path like sharding (Ethereum), off-chain storage (IPFS) or centralized server groups (EOS). Each of these methods has their advantages and disadvantages, we choose to use off-chain storage in the future (after it has been proven to be secure). But for the data itself, we are going to make them grow slower than ever.

Most DApps are Still Using Centralized Server
Most of the world’s DApps are using deployed in a centralized server now. These centralized servers are used for handling user requests and interact with blockchain. This is not pure DApp because users still need to trust these centralized servers and these server could been hacked or service down. And this also requires developer to handle server security, user privacy properly, which is not a simple task for most people.

Blockchain is Relatively Hard to Upgrade
All softwares need updates, including blockchain. Small or simple updates in blockchain are easy, but for those critical updates like migrate from PoW to PoS, could hurt some participants, which sometimes could leads to a hard fork. But for a blockchain database, we understand that a lot of work hasn’t be done properly (e.g. the off-chain storage mechanism is still not proven to be secure), so a strategy that allows us to upgrade important components is very useful

Solution

DApp Development is Painful
PepperDB wants to make it easier and provides a set of SDKs that allows developers to store or query data from blockchain directly using SQL / NoSQL schema. And for most of cases, smart contract programming is no longer needed (But is still supported).

Block Data Grow Too Fast
PepperDBs' cutting edge Searchable Compression technology could compress the whole blockchain dataset into one single block, which can significantly reduce the total disk size of the data. From tests in different scenarios, we achieved 3 to 10 time better compression than other compression algorithms. And with this great compression, we can extract data directly on compressed data file, which has never been done before.

Most DApps are Still Using Centralized Server
PepperDB is trying to build a completely distributed application platform via a DApp store and native client side support. Users can download DApp and run it directly on their own machine. Since we have best compression and these DApps don’t need to cached in every node, so the cost of storage is acceptable under our technology.

Blockchain is Relatively Hard to Upgrade
To avoid hard forks as much as possible, PepperDB is designing a new voting system based on user contribution. This means when a user is more valuable (instead of hold more tokens) to the network, he will has more power to influence the result. User contribution is calculated based on their connection with each other (We call it Pepper Rank, inspired by Google PageRank).

Features

SQL/NoSQL Protocol and SDKs
Developers can build DApps using their existing tech stack, smart contract is no longer needed.

Best Compression and Access Ability Ever
Benefits from our Searchable Compression algorithm, we are able to compress all blocks and all DApps into one single file (for each node), which tremendously reduce storage cost.

Self-Evolving Consensus (Pepper Rank)
Innovative blockchain consensus algorithms are merging, the best strategy to follow is to build a self-evolving strategy which allows our system can fully upgrade when necessary.

Pure Decentralized Application Support
Most of current DApps need a centralized server to response users’ requests and help their users to store/retrieve data from blockchain, this is NOT safe. PepperDB build a decentralized DApp Store and a client side runtime environment that allows users automatically download a DApp and run it locally without centralized server.

Show details

Additional links

  • Token details

    • Token symbol ? Token symbol — a shorten token name. It is used during an ICO and after the coin listing at the cryptocurrency exchanges. : PDT
    • Fundrasing target ? Fundraising target — the maximum amount of funds to be raised during an ICO. When it is reached, the developers stop selling the tokens because they do not need to raise more money for the project development. : 30,000,000 USD
    • Token type ? Token type — a platform for a startup launch that influences the stability of blockchain operation, the speed of transactions and the fees. :Ethereum (ERC20)
    • Soft cap ? Soft cap — the minimum amount of funds to be raised for the project development. Sometimes when the soft cap has not been reached, the money is returned to the participants. : NA
    • Role of token ? Role of Token — type of token depending on the opportunities it offers to its owner. Utility tokens give their owners a right to use the project services, security tokens are aimed at bringing profit, and currency tokens are a money substitute. :Utility token
    • Total supply ? Total supply — a total amount of tokens that will be released by the developers. :1,000,000,000 PDT
    • Escrow agent ? Escrow agent — a qualified agent who has the right of signature in a multisig wallet. An escrow agent participates in an ICO, monitors the financial operations of the developers and confirms their fairness. :No
    • Tokens for sale ? Tokens for sale — the number of tokens offered to the participants of an ICO. :400,000,000 PDT
    • Whitelist ? Whitelist — a list of participants, who get an opportunity to buy tokens. To be whitelisted, you need to register on time because the number of participants and the registration period are usually limited. :Whitelist Soon(Start TBA)
    • Additional emission ? Additional emission — an additional release of tokens. It can be done once after the crowd sale or on an ongoing basis. In the projects with a limited emission there is no additional emission. :No
    • Exchange listing ? Exchange listing — an assumed date when the token will be listed at a cryptocurrency exchange. The developers usually indicate it in a roadmap and a white paper. :NA
    • Accepting currencies ? Accepting currencies — cryptocurrencies and fiat currencies that can be used for buying the project tokens. :ETH,
    • Can't participate ? Can't participate — the countries where it is prohibited to buy tokens. These can be countries where ICOs are prohibited altogether, or countries that have the requirements that a particular project does not meet. :China, USA,
    • Know Your Customer (KYC) ? Know Your Customer — a verification procedure for ICO participants, during which the developers can ask for personal data, a photo and a scanned copy of a passport of a potential investor. :Yes
    Get details
  • Token and Funds Distribution

    Token distribution date

    NA

    Unsold tokens

    NA

Sale schedule

Round Token Price Bonus Min / Max Purchase Soft Cap Hard Cap
ICO — Soon
Start Soon
NA No - Uncapped Uncapped
Pre-ICO — Soon
Start Soon
0.0013 ETH No - Uncapped Uncapped
Private sale — Ended
Start Soon
End 24 Jul 00:00 UTC
0.001 ETH No Min 10 ETH Uncapped 45,000 ETH
  • Team

    • Roy Guo photo
      Roy Guo
      Founder
    • Sean Fu photo
      Sean Fu
      Co-Founder
    • Remy Trichard photo
      Remy Trichard
      Co-Founder
    • Peng Lei photo
      Peng Lei
      Co-Founder & Tech Leader
    • Guangxuan Luo photo
      Guangxuan Luo
      Cryptography
    • Leon Han photo
      Leon Han
      Engineering
  • Advisors

    • Guojun Ma
      Advisor
    • Qingqi Pei
      Academic Director

Roadmap

  • Milestone 1

    Finish PepperDB's core engine PepperKV(A blockchain based storage engine)

  • Milestone 2

    Integrate a basic SQL/NoSQL layer on our PepperKV and finish the first PoC version PepperDB

  • Milestone 3

    Launch PepperDB test network, start building our developer community around the world.

  • Milestone 4

    Launch main network, build several third-party data center around the world.

  • Milestone 5

    Launch the first group of decentralized applications

Activity

Social