• Start Date: 2019-06-03
• RFC PR #: 1
• Rust Issue #: 1

Summary

Design a trusted distributed network that allows everyone to manage their data freely and securely. Developers can implement interactive, computable, serverless applications based on this network, while helping to communicate and data between applications.

Motivation

Not yet

Detailed Design

Architecture Design

• Support different data structures
• Support different consensus algorithms
• Support different permission mechanisms
• Support different account systems
• Applications can communicate with others
• Trust can be passed on and accumulated

P2P & RPC Network

Teatree - Code - Design

Distributed Strorage

Black Tea - Code - Design

Virtual Computing Machine

Not yet

Distributed Computing

Not yet

Privacy Data & Privacy Computing

Not yet

Auxiliary library

• Oolong Tea - permissioned library for Distribution & Blockchain.
• PBFT - PBFT Consensus.
• KeyStore - Private Key & Account security store.
• Git On TDN - Github On Trusted Distributed Network/Github on Blockchain.

Drawbacks

Not yet

Alternatives

Not yet

Unresolved questions

Not yet

Now JSONRPC work on HTTP1.1.
If support HTTPS, it can be safely transmitted information in a network environment.

4-type has different message type.

TDN can build 4-type for applications.
Use feature to control. (one group, is one chain, is one application.)

1. single. Support only one group, and no layers. Like Bitcoin.
2. std (default). Support only one group, and multiple layers (cross-chain, Interactive with other groups).
3. multiple. Support many groups (in one runtime, support many applications), and no layers. Like Ethereum
4. full. Support many groups, and multiple layers.

Add some mechanism to ensure the security verification when jsonrpc is connected if need.

The following line contains an invalid link.

tdn-permission Group permission library, include permissioned & permissionless group algorithm.

Also, the example code snippet given in readme.md has no language-specific formatting available.

We are also working on the framework of Web3 recently, and are collecting a lot of knowledge in this field. We are lucky to see this project. Thank you very much, and hope to refuel

Yes.

Now Layers interaction only use default TCP stream.
We want to refactor it to use chamomile's p2p network.
Layers connection use chamomile's peer_id as it's network address.
Layers' id is group_id, and this id should signed peer_id, so application can verify it. (we will define how to generate layer's id, and how to sign, how to verify. maybe will use tdn_did.)

v2