📂
📂
📂
📂
ENVELOP (NIFTSY)
Search…
📂
📂
📂
📂
ENVELOP (NIFTSY)
Envelop (NIFTSY) documentation
Key documents
Key terms
FAQ
White paper
Disclaimers
Introduction
Key terms
Industry (market) analysis and NIFTSY's place in it
Protocol. Oracle. Index
The architecture of the Project and the role of the Token
DAO. Token. IDO
The token as a linking element in the project
IDO
Roadmap
Conclusion
List of references
Lite paper
White paper (Spanish)
Lite paper (Spanish)
White paper (BAHASA INDONESIA)
LITE PAPER (BAHASA INDONESIA)
Tokenomics
Technical documentation
Technical paper
Smart-contracts
Video tutorials
Metamask settings for different networks
Instruction for wrapping packs from the front
Bounty
Bounty FAQ
General conditions
Bounty rules
Approximate (maximum) activity estimates
Bug Bounty
Legal
Legal FAQ
Licence
DAO
Cases
Marketplaces
Gaming industry
Powered By
GitBook
The architecture of the Project and the role of the Token
basic functions and tasks of the NIFTSY token
So, the Architecture of the Project is as follows:
It is important to note the following principles of model formation:
1.
The links between Protocol - Oracle - Index are formed initially from the bottom up, but then the Project works from all three elements.
2.
Oracle and Index can be created outside the Project, Protocol cannot.
3.
All three entities are based on primitive transactional reputation models, i.e. they consider a) quantitative; b) temporal; c) subjective criteria.
4.
All elements operate on the basis of openness, decentralisation and consider all entities as possible actors in the Project: scripts, AIs, users, etc.
5.
All three entities interact with each other through the Token functionality, which is a necessary element of the Project ecosystem.
The features of the Token are discussed in more detail below.
Previous
Index
Next
DAO. Token. IDO
Last modified
10mo ago
Copy link