Hi, this is
@sepezho. I'm here with some news.
I've had an idea for a long time to build toncells the right way. What does "right" mean? It means completely without backend layers, make it completely onchein.
* toncells1 was built as a web2 application, with nft as cell ownership. I.e. I built a backend that kept all pictures of all fields in its memory. The overall picture of the whole field was also built by the backend. Even min nft did the backend (when it saw that tones with a special message came to the wallet)! In general, the application essentially ran itself outside of the toon, and the NFTs on the toon were accesses to the cells on the map. This architecture was deliberately ideologically wrong, where the server was a bottleneck. Server goes down, application is gone. And neither are your pictures. But it's worth saying that this approach allowed us to lance this nft collection literally in the first wave. Toncel's is one of the oldest nft collections on tone as a whole. We started building nft collections on tonceles before the nft smart contract standard even existed. I.e. editable nft smartcontracts were out of the question. /// And in general, in those times I didn't have a deep understanding of what and how it works in tone. In general, we did what we could. As it turned out.
* The idea of building an onchein version of the project has been in the air for more than a year now. It consists in transferring all the logic of toncels1 (editing and storing pictures) to smart contracts themselves. This way the users have full ownership of their cell. It is on the NFT (on the blockchain) that information about the picture and other data (name / description) is written. It is important to note that the format has also changed. There is no longer a 16x16px image limit! The only limitation that is on the picture is the weight - 100kb (and this limitation comes from the blockchain TON / the picture more simply can not be placed in the store smart contract nft). Also in toncels2 there is no area. And the number of cells itself has changed from 10k to 1.6k.
The technical advantages of toncells2 over toncells1 in general are obvious, just go to getgems and look at the collection - each nft displays the picture it stores (+ name and description of the nft)! If you look at this metadata you will see the onchain signature - this means that this data is written directly to the smartcontract. The toncels2 map will live as long as the TON itself!!! A small remark, yes the frontend application itself is hosted on a server for now. But, first of all, this application is open-source / everyone can download a copy of the site for themselves and deploy it on their PC / secondly, this application is very simple and does not require middleware backend at all, so soon I will host it on ton sites / on ipfs. It turns out that the frontend site itself will live forever :D !
Moving on.
It's worth saying that toncels2 was written by me in hackathon mode in one weekend so it may seem a bit raw. In fact, between you and me, I personally like this design more than overloaded designs (for example I'm a fan of the old curve fi protocol design). I think genius lies in the simple, not in the complex. By the way, I have recorded ALL of the design process on video FROM AND BEFORE (links will be below)!
It's also worth noting that ALL of the TONCELLS codebase is now open source. This weekend I made the decision to give back to the community what you once paid for (development). Anyway, absolutely everything is now open! From the backend and frontend of the old toncells, to the telegram bots and smart contracts of the new toncells2!
Ok, now for the links
Here's the toncells2 collection on getgems
https://getgems.io/collection/EQAY-HSJsRfXpFASJfc2QgDYAOoUgc7NjIQSE-a603qe4efOHere's the toncells2 app -
https://2.toncells.orgHere's the github organization toncells with the opensource code of the WHOLE PROJECT
https://github.com/orgs/Toncells/repositoriesHere's a youtube
playlist with a video on how toncells2 was developed
