About ownership

Libra.Codes has been made from the ground up to simplify token creations.

When you upload an image, video, song or something, you're the one that is supposed to be the creator/owner of the item, or you have the rights to distribute it.

When the file is tokenized, it is uploaded to the IPFS network, when it becomes publicly available and, most important, it can't be altered.

The token built out from the file can't be changed either. Metadata of the file is used as base for the token, and that's where the proof of ownership lives.

Now, when the token is deployed, we (Libra.Codes) become the guardians of your token. It will be tied to your user account.

When you sell the token on the marketplace or on an auction, the token changes hands and it is moved to the buyer user account. New private keys are issued in our HTMLcoin wallet to reflect the change.

Now, since we're the guardians of your NFTs, we keep the private keys secured, and we are responsible for their safety.

When you want to take a token out, then we transfer it to the HTMLcoin wallet address you tell us to. Then you get the token in your wallet with your own private keys.

About duplication

Duplicating a tokenized file is easy. Not only on our platform, but on any other NFTs platform.

But it all ends on the proof of ownership, because anybody can claim they're the sole owners, but only those with the token in their wallet can say they're the true owners of it.

In fact, a file can be deployed on the HTMLcoin network and also on the Ethereum network or others, and that means the same "unique" item will end up having different "originals", and that's something the entire NFTs ecosystem can't dodge.

There have been endless discussions about this topic all over the internet. There's still no consensus about it.

Time will lead us to the right way, and you'll know when we have a feasible solution for it.