Next, let's talk about the technical overview. Now, this may be a separate section or this may be something that's kind of spread throughout paper. But I kind of like the idea of going over this way. Until you talk about the structure of your token, whether it's ERC 2023, to 23, or any other type or some kind of hybrid, or even maybe a security token. So you want to discuss, is there a new blockchain being created? Is there a hybrid solution?
What's the method of consensus? Is it proof of work as in the old Bitcoin? Or is it a proof of stake, proof of authority, proof of elapsed time or even something else that you created out of thin air? You want to talk about that? So you want to talk about the technology that exists today, the technology that existed on the roadmap, and you want to relate it to the blockchain? So you really want to pull out the real reasons why you're using blockchain.
And while you understand its use, is there an API is there any way Others can leverage the technology and integrate and potentially bring more people in your platform, create customers or create their own solutions. So essentially, how does the technology in concert, all the technical pieces, how do they solve the problem? So let's take a look at some ways people have done this. So we'll look at medical chain, a medical chain has a section called technical explanation. And in here, we get information about the data structure. So they talk about a CTO file.
And you may not know what that is, that's a model file for hyper ledger. And hyper ledger is what you use for permission blockchain. They talk about the units that go way too deep in here about the entities and data description. This is more for programmers, but it lets you know that they've done the homework and they actually implement this thing and they build out the data model. And they talk about each asset variable types. So you may not want to do this in yours, but it's entirely up to you.
They just really want to show that they've really concept this thing out. This is a real thing. They have the code, then they go into the permissions files. So it really, because it's a healthcare related project, they want to show that they've thought all of this out. So it's showing you the code, talk about the API platform and user data security and all this good stuff. Let's take a look at another one that may help you a little bit better.
So Nexo has a technology section. And in this technology section, you get an overview of the technology where it's gone in 10 years, what they're doing now, all this stuff, then you got the next Oracle, which is the Canada, the model, the tech model, the back end automated piece, and they kind of diagram it out here, which I think is very helpful. Because a lot of people if you're not a programmer, you want to see this visually, and even some programmers will as well. And then they talk about the development of the long contracts, the real time data aggregation, so they're really getting into the technical bits here, giving you a high level explanation. So that you can kind of look this stuff up if you don't know You're interested, he talks about how the loan contracts works, the flow step by step, then they go into the actual smart contracts and the future protocol and we still create on their own platform.
Good stuff. So it's like it probably co probably co has a consensus system. And then they have technical overview, bam, so hit you right in the face with it. And they give you an overview. They talk about their blockchain, the peer to peer system integrated with the app that already exists. You have the back end smart contract deployment, the ERC 223 token standard.
You have the blockchain selection, why they use the blockchain to use and why they use an aetherium why they write down smart contracts. You have a dap decentralized app aggregator which interfaces with the theorem virtual machine, the hybrid approach and what they're going to do in the future. They even talk about the tech specs here of the token and so they Put all the regular information here fixed amount 18 decimals, the symbol the blockchain and what compatible wallets so here to go back into the ERC 223 standard. And then they talk about the API and integration, artificial intelligence thinks in future. And that's about it. So that's an idea of how you could make it into a section.
I say you should include it. And depending on what type of project you have, you may want to have it as a separate section. And so feel free to reach out to me for my opinion, you can send me your drafts or final projects and I'll give you my ideas on that.