> For the complete documentation index, see [llms.txt](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/lite-paper/additions.md).

# Additions

Here are the basics:

1. Project **Team**:
   1. **CEO - Aleksandr Shedogubov**:
      1. Linkedin: <https://www.linkedin.com/in/aleksandr-shedogubov-007438115>&#x20;
      2. Role: management and product
      3. Exp: entrepreneur in the field of  IoT, Blockchain and Logistic (Founder Pax Plus)
      4. Other: 33 y.o., 7 years of management experience, 4 years in Web3.0
   2. **BDO  - Aleksandr Kuzin**:&#x20;
      1. Linkedin: <https://www.linkedin.com/in/alexander-kuzin>
      2. Role: development of the product
      3. Exp: entrepreneur, business development of IT products and partner networks for 11 years (EVEN (founder), Agora, AcquiroPay)
      4. Other: 37 y.o., 13 years years in strategic development, 5 years in Web3.0
   3. **CTO - Maksim Sesykh**:
      1. Livejournal: [https://max-siz.livejournal.com](https://max-siz.livejournal.com/)&#x20;
      2. Role: technology management and development
      3. Exp: entrepreneur, blockchain and smart-contract development software engineer in Blockchain and FinTech (IberGroup (founder))
      4. Other: 43 y.o., 6 years of experience in Web3.0 software development 20+ years
   4. **CA - Menaskop**:
      1. Linkedin: <https://www.linkedin.com/in/menaskop>
      2. Role: system architecture, legal and tokenomic consulting, information support.
      3. Exp: entrepreneur, Web3.0 explorer and analytic, investor in Ethereum ICO, crypto evangelist, writer, FinTech (Synergis (founder))
      4. Other: 36 y.o., 15 years of experience in IT-legal, 9 years in Web3.0
   5. **Investors and Partner**s:&#x20;
      1. Waterdrip Capital: [http://waterdrip.io](http://waterdrip.io/)
      2. YBB Foundation: [http://www.ybb.io](http://www.ybb.io/)
      3. CarbonBlue Innovations: [https://www.carbon.blue](https://www.carbon.blue/)
      4. Autonomy Capital: [https://autonomycapital.com](https://autonomycapital.com/)
      5. Damo Labs: [www.aex.com](http://www.aex.com/)
      6. LD Capital: [https://ldcap.com](https://ldcap.com/)&#x20;
      7. Lancer Capital: <https://twitter.com/capitallancer>&#x20;
      8. Cypher Ventures: Coming soon
      9. InnMind: [https://innmind.com](https://innmind.com/)&#x20;
      10. Nova Club: Coming soon
      11. MoonCarl: <https://www.youtube.com/channel/UCc4Rz_T9Sb1w5rqqo9pL1Og>
2. GitHub - <https://github.com/niftsy/niftsysmarts>&#x20;
3. Public presentation - [https://drive.google.com/file/d/1UX8VWdn7TaRbAW3QlPMh02UfD--CViic](https://drive.google.com/file/d/1UX8VWdn7TaRbAW3QlPMh02UfD--CViic/view?usp=sharing)
4. Blog - [https://envelop.medium.com/](<https://envelop.medium.com/ >)
5. LinkedIn - <https://www.linkedin.com/company/niftsy>&#x20;
6. WWW - <https://envelop.is>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://niftsy-protocol-niftsy-1.gitbook.io/niftsy/key-documents/lite-paper/additions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.