What can I do with Licium?
Users can create, manage and register content-derived, decentralised identifiers on blockchain networks.
Rightsholders can declare metadata and rights management information and associate them with the identifiers.
Verifiers 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 sign certificates for digital content that acknowledge registrations, declarations, public keys and identities.
Online platforms (OCSSP)
Online platforms (OCSSP) can use the Licium API to generate ISCC – decentrally, on their premise!
This way they can unambiguously identify digital content without access to any metadata and verify the authenticity of the original content.
To comply with EU regulation they can receive content ownership information get access to trustworthy metadata and rights management information, clear the rights for digital assets and user generated content, and license content in an automated way.
This is rather abstract ...
Ok, the process starts with the digital content on your local device or cloud storage. You can select a file, and in seconds Licium will extract a unique ID from it: the ISCC.
The ISCC is derived from the file, no need to manually attach an identifier. From now on it will represent your content in any transaction as a persistent reference to your digital asset.
As a second step you can register the ISCC on a public ledger. This transaction transparently connects you to the ID that represents your content. Nothing more and nothing less.
As a consequence of this registration transaction, you will receive a unique registration ID. This 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.
This registration 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 identity.
I'm a nerd ... Some details cannot harm
When you select content from your computer or cloud storage, the Licium app will generate a multi-composite hash from the digital media asset according the the ISCC specification.
Currently, the ISCC can be registered on the bloxberg blockchain, which is based on a public Ethereum blockchain network. For this transaction you can use MetaMask and create wallet account for the registration of ISCC on the bloxberg blockchain. As simple as that.
Each individual registration of an ISCC on a public blockchain network will generate a short and unique registration ID. This registration ID takes into account all ISCC registrations across multiple blockchain networks and integrates them into one self-emerging index of ISCC registrations.
This registration ID unambiguously connects your individual public (MetaMask) blockchain address with the ISCC. In the future, metadata, licensing terms, rights management information or other assertions and claims may be connected to the registration ID. By using the same public (MetaMask) blockchain address you can technically prove that any follow-up messages or data entries associated with the registration ID are generated from the same credentials. For each subsequent transaction any third party can verify whether new information has been published by the same credentials as the ones that are associated with the registration ID.
What is required to register content with Licium?
Currently, users can only interact with the bloxberg blockchain, which is based on Ethereum. In order to perform transactions on the bloxberg network you need to have a MetaMask wallet and create a wallet for the network.
Creating a MetaMask wallet 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
As a user of Licium, you can claim the necessary ‘bergs’ tokens to perform registration transactions, free of charge – although there might be a limit depending on the number of transactions.
Did someone mention the word 'blockchain'?
Currently, users can interact with the bloxberg blockchain. The bloxberg blockchain is live, up & running and based on a public Ethereum blockchain network. bloxberg was initiated by the bloxberg consortium at the beginning of 2019 under the leadership of the Max Planck Digital Library to provide scientists with decentralized services worldwide. The consortium consists of leading research organisations, worldwide.
The bloxberg blockchain is a low energy-consuming network, that is based on a proof-of-authority (PoA) consensus algorithm. This means that – in comparison to a proof-of-work consensus algorithm – no energy needs to be uselessly burned to reach the consensus.
However, in the future, Licium will allow to register transactions on alternative blockchain networks, such as Bitcoin, Ethereum, Content Blockchain, etc.
And there are no costs involved in using Licium?
For rightsholder, individual verifiers and certification authorities, the services of the Licium app are designed to be free of charge.
You mentioned tokens, though?
Transactions on public blockchain networks usually cost transaction fees. Please keep it in mind that this depends on the blockchain you want to use for your registration transactions.
In order to interact with the bloxberg blockchain, you need ‘bergs’ tokens. But as a user of the Licium app you can claim the necessary ‘bergs’ tokens to perform registration transactions free of charge – although there might be a limit depending on the number of transactions.
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 registration of ISCCs (write operations) require a wallet, that contains 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, 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.
With the Licium Box, you 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 new identifier for digital content. It helps creative individuals and media organisations to better manage their assets by using machine learning, fingerprinting and cryptographic technologies. The ISCC can be used to identify digital assets of all media-types like text, image, audio and video in all granularities across all industry sectors alongside existing standard identifiers.
The ISCC supports versioning, deduplication, content clustering, timestamping, similarity detection and granular identifier assignment. It enables content transactions to operate faster and more efficiently in networked and increasingly decentralised media environments.
The ISCC is an identifier that is created from the content file itself. This means that an ISCC can be generated by anyone with access to the content, free of charge by using open-source software. By using ISCC, anyone with access to digital content can decentrally generate the same identifier from the same digital asset. This allows anyone to unambiguously identify same or similar content independently of centralised organisations, registries or proprietary third-party services and software.
Why do we need Content Certification?
Anyone can generate ISCCs 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 register 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.