Traceability and records on DLT, without a financial token
Not every DLT project issues a financial token. We build shared, verifiable records for companies that need to show where a product comes from, what a document certifies or who was entitled to vote in a ballot, without every party having to trust the same database.
We do not provide legal or regulatory advice. Your advisors confirm which rules apply to each project.
Manufacturers and distributors that have to show where their products come from and the route they took
Companies preparing the EU digital product passport
Organisations that issue degrees, warranties or certificates and want them to be verifiable without anyone having to ask
Cooperatives, associations, clubs and companies that run votes among their members or employees
What we build
Supply chain traceability
Every step of the product, from origin to delivery, is recorded in a register shared by the companies involved. IoT sensor data, such as temperature, location or humidity, is sealed when it is taken, so it can later be checked that it has not changed.
Digital product passport
EU rules require a digital passport for a growing number of products. The EU registry has been live since 20 July 2026, and the first products that must have one are certain types of batteries, such as electric vehicle batteries, from 18 February 2027. Textiles, steel and other products will follow through later delegated acts. The rules do not require blockchain. DLT is one way to protect the integrity of passport data, not a requirement.
Certificates and verifiable credentials
Degrees, warranties and quality certificates that anyone can verify without asking the issuer. We design them to be compatible with the European Digital Identity Wallet.
Document timestamping and shared records
Contracts, minutes, reports or delivery notes sealed with their digital fingerprint and date, to show later that they existed and have not changed. And records shared by several companies without any of them depending on another's database.
WHY IT MATTERS
No financial token
Without a financial token, the project generally falls outside the securities and crypto-asset regimes (MiCA), because nothing is issued that is bought, sold or carries a right to returns. Your advisors confirm each case. What does apply is the GDPR, so the chain holds cryptographic fingerprints and references, and personal data stays in your company's systems.
Votes with verifiable credentials
Who it is for
Cooperatives, associations, clubs with members, internal employee consultations and technical support for remote voting at general meetings, where the articles of association allow it.
One credential per person, not per token
Each voter receives a non-transferable credential tied to their identity. The DLT keeps a verifiable record of the voter roll, of who was entitled to vote and of the result. The vote is tied to being a member or an employee, never to holding participations or tokens with economic value.
Ballot secrecy and GDPR
No personal data and no individual vote is stored on the chain in the clear. Cryptographic commitments or equivalent techniques let the count be checked without revealing how each person voted. The design limits what can be learned about each person's vote, but it does not promise absolute anonymity, which also depends on how the vote is organised.
Validity
The tool records the vote, but it does not replace the legal formalities, such as the notice of meeting or the minutes. Whether each vote is legally valid depends on the articles of association and the rules that apply to the organisation, and its advisors review it.
What gets sealed, who writes, who verifies
01ScopeA call and a written scope covering what has to be recorded, who takes part and which data stays off the chain.
02SpecificationWhat is sealed, who can write and who can verify, agreed before any code.
03Phased buildEach milestone is delivered with its own unit, fuzz and stateful invariant tests.
04Hardening and handoverStatic analysis, coverage review, documentation and NatSpec, plus support for your team during the audit.
What you get
DELIVERABLE
FORM
Smart contracts for the register, with NatSpec documentation
Repository
Foundry tests for the write and verification rules
Repository
The integrations with your sensors, your systems or your identity providers
Repository · Document
A verification page or API for third parties, when the project needs one
Repository
A design document that explains what is stored on the chain and what is not, for your advisors to review
Do I need blockchain for the digital product passport?+
No. The rules do not require blockchain. DLT is one option to protect the integrity of the data and share it between companies, and we help you weigh whether it adds anything in your case.
Is personal data stored on the chain?+
No. The chain holds cryptographic fingerprints and references. Personal data stays in your company's systems, where it can be corrected or deleted as the GDPR requires.
Are the votes legally valid?+
The tool records the voter roll, who was entitled to vote and the result, but it does not replace the notice of meeting, the minutes or the other formalities. Whether each vote is valid depends on the articles of association and the rules that apply to the organisation, and its advisors review it.
Do more tokens mean more votes?+
No. The vote is tied to being a member or an employee, through a non-transferable credential. Participations or tokens with economic value are not used to vote.
Public blockchain or private DLT?+
We work with EVM-compatible networks, public or permissioned. Which one fits depends on your requirements, and we can help you weigh the technical trade-offs.
Do you provide legal or regulatory advice?+
No. We work on the technical side, alongside your legal advisors, who decide which rules apply to each project.