Liccium
Liccium.comTDM·AI Opt-OutCreator CredentialsFAIA – FAIR AI AttributionContact us
  • About Liccium
    • Introduction
      • What is Liccium?
      • Who is Liccium for?
      • Why Does Liccium Matter?
  • Technology
    • ISCC Content Fingerprinting
    • Verifiable Creator Credentials
    • Soft Binding of Metadata
    • Federated Content Registries
  • Products
    • Liccium Cloud app
      • Generating ISCC Codes
      • Basic metadata
      • Liccium plugins
      • Creator credentials
      • Liccium browser plugin
  • Liccium B2B Declaration Engine
  • Metadata API
  • Registry Set-up
  • Solutions
    • FAIA – Fair AI Attribution
    • Opt-Out Registry
    • TDM·AI 𐂂 – Asset-Based Opt-Out
  • Use Cases
    • Creators & Rightsholders
    • AI Model Providers & Digital Platforms
  • Journalists, Fact-Checkers & News Organizations
  • Institutions & Regulatory Bodies
  • References
    • Liccium
    • ISCC
    • Standards
    • Regulation
  • Legal information
    • Imprint
Powered by GitBook
On this page

Was this helpful?

  1. Context
  2. Complementary solutions

Making a difference

For the last 15 years, Liccium B.V. (former Posth Werk B.V.) has been a main contributor in developing new standards, protocols and products that significantly impact and revolutionise the digital media markets of the future.

The Liccium app is implementing and improving novel and highly innovative technology, creating an application of a new kind that helps content creators and rightsholders to tackle the current challenges of digital media and trust.

  • Instead of timestamping and signing cryptographic hashes, users can declare ISCC codes. With a combination of cryptographic and similarity-preserving hashes, ISCC supports decentralised content identification and matching of same and similar, near-duplicate content, even if the content has been altered or manipulated or embedded metadata have been stripped from the file;

  • Instead of embedding digital signatures and claims into the digital media files, users can digitally sign a declaration transaction by means of a wallet software under their own control;

  • Instead of embedding metadata into the file itself or including watermarks and other information to the perceptual content, we suggest inseparably connecting external metadata to the content together with the declaration of ISCC codes;

  • Instead of relying on centralised services to verify content integrity or claims to content and metadata, users can rely on decentralised trust, generate the ISCC and reverse-lookup all data associated with the ISCC declaration.

Last updated 1 year ago

Was this helpful?