Resources

The documents behind the claims

The whitepaper, the marks, the palette and the references. Everything a partner, an integrator or a journalist needs to describe the project accurately — without having to ask us first.

Whitepaper

LKSCOIN 2.0

Seventeen pages on what the network does, why the proof holds, what it is worth in law, and in what order the work is being done.

Cover of the LKSCOIN 2.0 whitepaper

Decentralised proof infrastructure for documents, data and supply chains

Written for three readers at once: a technical evaluator asking what the proof is actually worth, a legal department asking what it proves in court, and an operator of the existing network asking what changes for them.

What is inside: the three-layer security model and why finality is the whole argument; LKS Notary, Trace and Identity; the eIDAS and Italian legal perimeter stated plainly; the open standards used at every external interface; the service revenue model; and the roadmap as an ordered sequence.

Version 2.0 — August 2026. English. Approximately 110 KB.

Earlier versions are obsolete. Whitepapers published before this one described a different project — a token for remunerating creative content, together with material relating to a token sale. They do not describe what LKSCOIN is or what the Foundation is building, they are no longer distributed, and they should be treated as historical documents. Version 2.0 supersedes all of them.

Brand assets

The marks

Two marks, used for two different things. The coin mark identifies the network and its asset; the Foundation wordmark identifies the entity that governs the project. They are not interchangeable.

LKSCOIN coin mark

LKSCOIN mark

The network and the asset. Use on light backgrounds; the mark carries its own dark ring and needs no container.

LKS Foundation wordmark

Foundation wordmark

The entity that governs the project, holds the intellectual property and enters into agreements. Use on light backgrounds.

LKS Foundation wordmark, white version

Foundation wordmark, reversed

The white knockout, for dark backgrounds and photography. Never place the dark wordmark on a dark field instead.

Vector files. Scalable source files (SVG and EPS) are held by the Foundation and issued on request, so that what is published always matches the master artwork. For print, packaging, or any reproduction above 1024 px, write to us rather than upscaling a PNG — request the vector pack.

Palette

Colours

Deep blue for authority, cyan for the accent. The two greys carry every body text and rule on the site.

Signal blue#175DAB
Deep navy#08284C
Cyan accent#12B5D8
Ink#0C1C2E
Body#33475B
Tint#F4F8FC

Using the marks

  • Keep clear space around the mark equal to at least the height of the letters in the wordmark.
  • Scale proportionally. The coin mark is square and must stay square.
  • Use the reversed wordmark on dark or photographic backgrounds.
  • Refer to the network as LKSCOIN and to the entity as the LKS Foundation.
  • Do not recolour, outline, add gradients or apply effects to either mark.
  • Do not rotate, stretch, condense or crop.
  • Do not place the mark on a background that leaves it without contrast.
  • Do not use the marks in a way that implies partnership, endorsement or affiliation that does not exist.

The marks are the property of the LKS Foundation. Editorial and journalistic use of the marks to identify the project is welcome and needs no permission. Any other use — product, packaging, marketing material, merchandise — requires written agreement.

References

Verify rather than believe

The chain is live and public. Where the whitepaper makes a claim about the state of the network, it can be checked directly.

Block explorer

Blocks, transactions and addresses on the live chain, updated as they are produced.

Open the explorer →

Node and wallet

Software releases, masternode requirements and the setup documentation for operators.

Downloads & requirements →

Service API

Endpoint specification for the notarisation service, published early so integrators can challenge it.

API reference →

Standards referenced in the whitepaper

StandardBodyUsed for
GS1 Digital LinkGS1Resolvable product and batch identifiers
EPCIS event modelGS1Supply chain event semantics
Decentralised Identifiers (DID)W3CParticipant identity
Verifiable CredentialsW3CRoles, mandates and attestations
C2PA content credentialsC2PA / CAIContent provenance and edit history
JSON Canonicalization Scheme (RFC 8785)IETFDeterministic hashing of structured data
OpenTimestampsOpen protocolAnchoring to the Bitcoin blockchain
SHA-256NIST FIPS 180-4Document and event hashing

Regulation cited

InstrumentRelevance
Regulation (EU) 910/2014 (eIDAS), Art. 41Legal effect and admissibility of a simple electronic timestamp
Regulation (EU) 2024/1781 (ESPR)Ecodesign framework and the Digital Product Passport
Decree-Law 135/2018 Art. 8-ter (Italy), conv. L. 12/2019Distributed ledgers and electronic timestamping under Italian law

Regulatory references are informational. They describe the position as at the date of the whitepaper and do not replace a legal opinion on a specific matter.

Something missing?

If you need the vector artwork, a technical detail the whitepaper does not cover, or material for an article, ask us directly.