TON Social network

What is this project about?

There are many social networks in the world, but none of them are fully decentralized.

What is it, a fully decentralized social network? It is a social network that is not controlled by any single entity, but by the blockchain.

This projects contains implementation of a social network on the TON blockchain, where all data about users/posts/comments/likes stored and managed directly by smart contract, written in tact language.

Conception

Let's take a look, how it works. First of all, there is Account - the main object contract, through which real users (wallets V5, V4 and etc.) communicates with other objects smart contracts (by sending messages to them through wallets, for example TonKeeper).

You can think of it as a typical "account", which exists in any social media. It implements NFT interface, thus the ownership can be sold/transferred to other wallet (official way to sold accounts).

Owner can set account's avatar (it can be stored either directly in blockchain or in any IPFS-like/TON-Storage-like service, contract support any of them), nickname (he can purchase NFT with unique nickname), and some other data.

Now, what account can do?

1. Each account can create posts (share some text data), which would be linked to it.
2. Other users can leave comments to the post or to other comments (answering them).
3. Users can like any post or comments (in future, like can contain some value, to support user).
4. Users can receive achievements (SBT) for doing actions.
5. You can buy NFT with unique nickname (on auction) and "link" it to your account, s.t. it would be accessible by DNS domain nickname.neto.ton (for example, pavel-durov.neto.ton).

Features

• Users can create accounts (many accounts) from one wallet, and use this account to communicate with other users and objects.
• Users can create posts, edit them, like them and comment them.
• Users can answer other comments, like them and edit.
• Users receive SBT-achievements, when they're done some actions (add 1,10,100,... likes, posts, subscriptions, comments)
• Users can subscribe to other users, and receive special SBT-achievements for this (the "master" of this SBT is user contract). Users can set its own "subscriptions levels". One can easily check if user is subscribed to another user, until which time, for which amount etc.
• Users can have unique nickname in the system and can be found by this nickname.
• Users can navigate through ton DNS:
  • neto.ton -> Master smart contract
  • master.neto.ton -> Nicknames collection contract
    • owner.master.neto.ton -> Owner of master contract
  • id123.neto.ton -> id123 account
    • owner.id123.neto.ton -> id123 account's owner
  • pavel-durov.neto.ton -> Account in netoton network
    • owner.pavel-durov.neto.ton -> pavel-durov account's owner
    • domain.pavel-durov.neto.ton - > pavel-durov NFT domain contract

Is it fully decentralized?

Right now, there are 2 "centralized" parts in the system:

1. Moderation. We're going to get rid of it in the future, introducing "reputation", s.t. users with good reputation can moderate the content, getting a little profit from it.
2. Frontend. It's opensource, but doesn't stored directly on blockchain (yet). Anyway, it can be accessed by .ton domain name.

Developing

You can use either npm,yarn, pnpm or any other package manager you like.

To start developing, you need to install the dependencies:

npm install

After installation, it is required to polyfill the TACT language, which is used in the project (see tact-plus-plus). To do this, you need to run the following command:

npm polyfill

Building

To build the project, run the following command:

npm run build

To run the tests, use the following command:

npm run test

Project structure

• contracts - source code of all the smart contracts of the project and their dependencies.
• wrappers - wrapper classes (implementing Contract from ton-core) for the contracts, including any [de]serialization primitives and compilation functions.
• tests - tests for the contracts.
• scripts - scripts used by the project, mainly the deployment scripts.

Visits