About Drep (new)
Drep (new) (/ˈdrip/, /drep/) is committed to building “connectors” and “toolkits” based on blockchain technology, providing solutions that combine ease of use, flexibility and frictionless integration. Based on DREP Chain, DREP ID, DREP Reputation Protocol and DREP SDK, DREP aims to build an open data ecosystem on chain, opening up segregated user groups and data silos across multiple chains. Teams building DApps will be able to easily integrate multiple public-chain versions of DApps, built-in wallets and asset trading platforms with one-click using the DREP Chain, DREP Decentralized ID, DREP software development kit (SDK) and DREP Client.
Drep (new) Inadequate public chain performance and poor developer experience Segregated public chain ecosystems and small user bases A mismatch between blockchain technology and enterprise needs DREP is a blockchain-based cryptocurrency, A unit of the currency is called a drep The utility scenarios of DREP tokens in the DREP ecosystem mainly include.
Drep (new) Storage Key Points
|Circulating Supply||39,900,000.00 DREP|
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Chat||Click Here To Visit|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
How Does It Work
DREP provides the following technical solutions: • The DREP Chain is a high-performance public chain fully developed by the DREP team. It is compatible with Smart Contracts in EVM and WASM formats with a dual-layer structure consisting of a root chain and sub-chains. • The Smart Pipeline proposed by the DREP team is a “pipeline” for data transmission and for transferring data between the blockchain virtual machine and external applications. It is able to achieve high efficiency, zero gas consumption and strong scalability without affecting security. These needs are not met with Smart Contracts. • DREP adopts a Schnorr multi-signature algorithm based on Secp256k1 to improve network efficiency and reduce transmission overheads.
DREP has designed a decentralized ID system based on HMAC (Hash Message Authentication Code) algorithm, forming a dual-layer system of master ID and multiple sub-IDs to achieve data connectivity and privacy protection. The DREP Client allows users to manage data and assets on centralized and decentralized platforms all in one place. • To enhance data privacy protection, DREP uses homomorphic encryption to process users’ private information. • To provide long-term value of DREP DID, DREP features a reputation system consisting of a general reputation protocol, a reputation pipeline interface, a reputation data on-chain and algorithm library, a reputation incentive mechanism, a reputation account management, a fake account identification mechanism and more.
A tool for inspecting the contents of blocks in a more user-friendly format. Block header Metadata at the beginning of a block that defines information about the block. The hash of a block header is the main way of identifying a block.
Outputs from coin base and stake base transactions cannot be spent until the coin base maturity period has passed. The coin base maturity period is 256 blocks.
To reward DREP community member’s long-term support, DREP team launched DREP Summoner Plan, gathering qualified DERP summoners to build a stronger DREP ecosystem.
Summoner Skill Card
- Join Summoner WeChat group and have intimate interaction with DREP co-founder
- Get to know DREP’s re-announcement at first
- Get seed user identity in DREP node plan
- Get genesis user identity in alpha test of DREP game
- Exclusive treatment and birthday gift
A transaction is confirmed when it has been included in a block that has been verified by the network (added to the blockchain). Each additional block added to the blockchain reconfirms all transactions in all previous blocks. The number of times a transaction has been confirmed is used as a measure of confidence that the transaction will remain in the blockchain. A wallet or other service may require a certain number of confirmations before it considers a transaction to be valid. For example, if a wallet requires three confirmations to consider a transaction valid, it would require the next two blocks after the block including the transaction to confirm the transaction.