Blockchain
Distributed ledger technology where it actually fits, which is a narrower set of problems than the market usually admits.
What this covers
Blockchain is an area TecFlax is exploring rather than a service we are currently selling, and this page is written accordingly.
The honest position is that most problems presented as blockchain problems are database problems. A distributed ledger earns its considerable complexity in one specific situation: when several organisations that do not fully trust one another need to agree on a shared record, and no single one of them can be allowed to control it. If one organisation owns the data, a well run database with a proper audit trail is simpler, faster, cheaper and easier to support.
Where the conditions genuinely hold, the applications that interest us are multi party record keeping, supply chain provenance where goods change hands between independent parties, and verifiable credentials such as tamper evident certificates. There are real candidates in each of those categories across the markets we serve.
We would rather talk you out of a blockchain project that does not need one than take the work. That is a strange thing to put on a website, but it is the same principle we apply everywhere else: we implement what we can support, and complexity you do not need is complexity somebody has to maintain.
Where we are today
- A candid assessment of whether your problem needs a ledger at all
- Multi party record keeping where no single party can own the data
- Supply chain provenance across independent organisations
- Verifiable, tamper evident credentials and certificates
- Integration with the systems you already run
- A clear view of what it will cost to operate, not just to build
At a glance
- StatusExploratory
- Best fitMulti party records
- Poor fitSingle owner data
- First stepFit assessment