What can I do with Licium?
Everyone can create, manage and register content-derived, decentralised identifiers on blockchain networks. Rightsholders can declare and digitally sign metadata and rights management information and inseparably connect them to digital content.
Everyone can identify digital media content and get access to trustworthy metadata and rights management information. Content certificates allow to verify registrations, declarations, public keys and identities.
Certification authorities can digitally sign certificates for digital content that acknowledge registrations, declarations, public keys and identities.
Online platforms (OCSSP)
Online platforms (OCSSP) can use Licium to generate ISCC CODES– decentrally, on their premise! This way they can unambiguously identify digital content (UGC) without access to any metadata and verify the authenticity of the original content.
This is rather abstract ...
Ok, the process starts with your content on your local device or cloud storage. You can select a digital media file, and in seconds Licium will extract a unique ID from it: the ISCC.
The ISCC is derived from the digital media asset itself, there is no need to manually select and apply an identifier to the content. From now on it will represent your content in any transaction as a persistent reference of your digital asset.
As a second step you can declare the ISCC on a public ledger. Your digital signature transparently connects your pseudonymous identity to the ISCC that represents your content. Nothing more and nothing less.
As a consequence of this declaration, you will receive a unique declaration ID. The ISCC-ID is owned by you, globally unique and resolvable. This registration ID retains a record of the registration transaction, connecting you (respectively your pseudonymous identity) to the content.
The ISCC-ID is important. Because from now on you can use it to attach information to the content: metadata, ownership information, licensing or rights management information, reviews etc., whatever seems relevant for you to associate with the content – and this data will always and unambiguously be associated with your content and your pseudonymous identity.
What is required to register content with Licium?
To register content on a public blockchain you need a wallet. Licium will allow to declare ISCC codes on various blockchains. In order to perform transactions on Ethereum, Polygon and other EVM-based blockchains, you need to have a MetaMask wallet and create an address for each network.
In general, creating a MetaMask address is super useful, relatively easy and well documented. You can find further information on https://metamask.io/ and a lot of answered questions on their FAQ list: https://metamask.io/faqs.html
For the transactions you need the tokens of the selected blockchain network in order to pay for gas or transaction fees.
Did someone mention the word 'blockchain'?
For testing purposes, we implemented Licium the bloxberg blockchain.
However, in the future, Licium will allow to declare ISCC codes on blockchain networks, such as Ethereum, Polygon, Tezos, NEAR, Solana etc.
And there are no costs involved in using Licium?
For rightsholder declating content and individual verifiers, the services of the Licium app are designed to be free of charge.
You mentioned tokens, though?
Transactions on public blockchain networks usually cost gas or transaction fees. Please keep it in mind that this depends on the selected network you want to use for your declarations.
No registration, no login ... Seriously?
Licium is a decentralised application. The services of the Licium app require no registration or login. This means that no user credentials, no personal user data, no email addresses or passwords are stored on Licium servers. Awesome, isn’t it?
Some services, like the declaration of ISCC codes (write operations) require a wallet, that contain the user’s key material and the derived blockchain address. Only you will have access to your private key. No user data is stored on our servers.
What happens with my digital assets?
At only one initial point of the process your digital assets are needed. In order to generate ISCCs from the content with the Licium app, digital assets have to be temporarily uploaded to the service.
The upload is encrypted in transport via https. After generation of an ISCC, the digital asset will be permanently deleted from the servers. In general, no content will be permanently stored on Licium servers!
If you have terrabytes of assets and/or do not want to generate content codes via the service, you might be interested in using the Licium VM. With the Licium VM, the Licium app will run on a virtual machine on a server that is controlled by yourself. The virtual machine can be installed in your local network or on the servers of your data centers. This allows you to manage your digital media assets on premise and to generate ISCC without the need to upload content to the service.
Feel free to reach out to install the Licium VM.
In the future, with the Licium Box users can choose to purchase a dedicated hardware device that you can plug into your router and run in your local network. The Licium box will allow you to use the Licium app and manage your digital media assets offline on your local device in your local network and to generate ISCC without the need to upload content to the server.
What is the ISCC?
The International Standard Content Code (ISCC) is a proposal for a new open and decentralized identifier for digital media assets from all media sectors and of all media types, like text, image, audio and video.
The open specification and open source development are maintained by the not-for-profit ISCC Foundation. This will ensure interoperability and transparency of decentralised digital content identification.
The main distinguishing feature of the ISCC – in comparison to existing content identifiers – is the fact that the ISCC is derived from the digital media assets itself. This means that an ISCC can be generated by anyone with access to the content, free of charge by using open-source software.
The ISCC has been accepted as ISO/AWI 24138 International Standard Content Code (ISCC), as part of ISO/TC 46/SC 9: https://www.iso.org/standard/77899.html
Why do we need Content Certification?
Anyone can generate ISCC codes from digital assets. This is a feature, not a bug.
Anyone can register content codes on the internet or on blockchains for various reasons. Creative individuals, media organisations or other rightsholders may declare ISCCs in order to publish assertions, connect metadata, rights management information or other claims to the identifier. Other registrants may want to express ownership of a license or simply prove that they had access to a specific document or file by generating and publishing an ISCC.
It is the goal of the content certification process to create trust in assertions, claims and the authenticity of the original content, and to ensure accountability of entities, even if they must or prefer to remain pseudonymous.
Content Certificates are open, discoverable and verifiable by anyone online and accessible for individuals or systems, using software applications or APIs.
To learn more, read the whitepaper of the ‘Open Content Certification Process’: https://github.com/licium/occp
Licium can be used by certification authorities to certify content, verify the identity of creative individuals and acknowledge that a specific assertion or claim to a digital asset can verifiably be associated with this entity.