Skip to content

Concepts

Technical

Tree3 technology stack consists of Stellar, Stellar Assets(T3 token), Stellar smart contracts, IPFS and features of IPFS such as libp2p, bitswap, Unixfx, bootstrap nodes and IPLD. The backend API currently serves as a gateway for IPFS content and this will become more distributed when more nodes join Tree3.

Fees, Content and contracts

Content Fees

Content fees is divided in two parts.

1. Storing IPFS hash on blockchain

Tree3 stores IPFS hash in stellar blockchain in memo field and manage data fields. Each operation cost minimum fees on stellar operation.

The base fee (currently 100 stroops) is used in transaction fees. The base reserve (currently 0.5 XLM) is used in minimum account balances.

(# of operations × base fee)

Reference Stellar Fees

2. Storing data using IPFS

Tree3 stores data on nodes using IPFS, each node is paid minimum T3 fees and the fees is distributed to every node that stores this data. Currently minimum fees is 10 T3 for any content which can be changed in future since data size may vary for video, images and text based content.

Refer nodes.md for more information

Speed

Speed is an important factor in Distributed Ledger Technology(DLT), every content on Tree3 is a transaction and hence transaction time determines when an article is available on Stellar. Stellar transaction time is approximately around ~5 seconds.

Reference Stellar Transactions

Smart Contracts

Tree3 has various types of rewards on the platform but subscriptions are processed based on smart contract. Once a reader/user subscribes to the author, the transactions are processed based on smart contract. By Alpha 0.5, even the goals will be based on smart contract so that an author can raise funds for a particular goal and if authors fails to achieve those goals, the funds will be released back to all contributers.

Refer rewards.md for more information

Key Storage

In Alpha 0.1.x i.e. testnet, private keys were stored in browser storage. While this improves usability, it is preferred to never store private keys. Your private keys will never be stored at any node as well. For Alpha 0.2, you will have to use your private key for every operation. Since anyone can be a node on Tree3 and key security is most important, we are working on making this a much better experience in future Tree3 release.

Stellar

Tree3 uses Stellar network through Horizon (RESTFUL HTTP API Server), which is basically built on stellar core that is maintained by various individuals and organizations. The main backbone of Tree3 is Stellar Network and we interact with Horizon for all operations.

Stellar

Read more about Stellar

NOTE: Tree3 is also planning to be a stellar node for better operations in future.

IPFS

Storing content related data on blockchain is possible but not preferred. Instead we use IPFS to store that data, IPFS is a distributed system for storing and accessing files, websites, applications, and data. Read more on IPFS

Since there is no reward for storing IPFS data for users, we reward each node to store Tree3 content in a unique manner using T3. Read nodes.md for information on storage of content.

IPFS is still in active development and so is Tree3, make sure to read CHANGELOG on github to stay updated about every release.

T3 Nodes

There are two type of nodes on Tree3, Active and Dormant nodes. Key difference in both node is that Active node are server specific and Dormant Node re user specific.

Active Node

  • Need server space
  • Stores all content on T3 ecosystem
  • Can have their own website/niche
  • Can create their own community of users
  • Gain T3 rewards for storing content

Dormant Node

  • User specific nodes
  • Stores own content
  • Do not gain T3 rewards

General

These are general concepts on Tree3 where your XLM/T3 address of Stellar Network becomes your identity.

Content

Your content on tree3.network (or any other node) will be like tree3.network/article/73.......dc4062defb01

As you might have guessed, the 73....dc4062defb01 is the transaction id. Every transaction id can be viewed as a content if they are using valid IPFS data.

An example of article :- On Tree3 Alpha 0.1.x testnet :-

Tree3 Article

Profile

Your profile on tree3.network (or any other node) will be like tree3.network/profile/G....ADDRESS

All the data of this profile is stored in IPFS which is distributed to different peers using T3.

Public key or Sharable Address on Stellar starts with alphabet G..

For example :- On Tree3 Alpha 0.1.x testnet :-

A profile for address GBD3ECXAO4427NFYIZH6TYSZVX2I76KVUHYYKJIQZUYC3GHA73KHGNNV

Tree3 Profile

Blog

Your blog on tree3.network (or any other node) will be like tree3.network/blog/G....ADDRESS

All the data of this blog is stored as transactions on stellar network and content is stored on IPFS which is distributed to different peers using T3.

Public key or Sharable Address on Stellar starts with alphabet G..

For example :- On Tree3 Alpha 0.1.x testnet :-

A blog for address GBD3ECXAO4427NFYIZH6TYSZVX2I76KVUHYYKJIQZUYC3GHA73KHGNNV

Tree3 Blog

Goals

On tree3.network, content creator can create their own goal and goal URL will be like tree3.network/goal/G....ADDRESS

All the data of this goal is stored in IPFS which is distributed to different peers using T3.

Public key or Sharable Address on Stellar starts with alphabet G..

For example :- On Tree3 Alpha 0.1.x testnet :-

A creators goal for address GDVYWH7RHCVOGNTMP2UOSVQ2Y74CXK25I7V7NKOTXEDPNWV2OFEJ4Y6R

Tree3 Goal

Promote

Promoting content on Tree3 requires a fee of 10 T3 and allows content to be promoted on Front page of Tree3. The contnet is bumped as a transaction and is pushed on top of explorer, that transaction can be viewed on any stellar explorer.

Community

Read the community section of the docs.

Tree3 will be completely open source by Alpha 1.0