> For the complete documentation index, see [llms.txt](https://docs.lostsoulsnft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lostsoulsnft.com/research/cute-archived/tech.md). # Tech ### Decentralized Identifier Because of the web2 nature of most of these products the points will begin on a web2 platform but will all data stored in a IPFS backend hosted by Lost Labs. Currently the backend is not pinned to the global IPFS network, but as the solution becomes more stable and defined we will work to release it to the wider IPFS network. The goal of this backend is to form a [Digital Identity](https://en.wikipedia.org/wiki/Decentralized_identifier) that can be used by other projects and serve as a home for all your points, badges and preferences (think dark mode) across the NFT sector. ### Soul Bound Tokens We've done a great amount of [Research](/research/start-here.md) about the possibilities of Soul Bound Tokens, Badges etc. and through that research we've got a good sense of what needs to be done to make these tokens a reality. Therefore, CUTE points are our first building block into this sector. Soul Bound Tokens require a few things to work: Consent among participants, knowledge of the agreement and transparency into the parties. With the current design of the CUTE points we decided to begin with creating an Issuer of the tokens - to understand how we can design a trusted system that marries the web2 and web3 world. We've done some prelimiary work with [EIP-4337](https://ethereum-magicians.org/t/eip-4973-account-bound-tokens/8825) with think has a good shot at achieving the desired goals of Soul Bound Tokens. ### Issuance CUTE points are issued by the Nftyswap team and are up to the discreation of the team. If there is misuse or abuse of the system, Nftyswap reserves the right to remove accounts and/or points. --- # 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://docs.lostsoulsnft.com/research/cute-archived/tech.md?ask=&goal= ``` `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.