JLINC is a new ‘permissioned data’ layer on the internet – a simple way to create digitally signed agreements that govern the automated exchange of data between databases at separate domains.
This provides ‘data-provenance’, a signed chain of custody for data with audit proof written to any database, ledger or blockchain.
JLINC provides human and machine readable ‘self-validating’ secure contracts, which are different than ‘self-executing’ smart contracts.
JSON-LD provides a graph data language to serialize data in contexts
JLINC is signed with standard PKI (public-private key cryptography)
Public key look-up is performed on any combination of databases, distributed ledgers, or blockchains, specified by any party
Digital identity is represented using one of the first actual working implementations of the new W3C DID-spec for digital identifiers
Standard contracts can be hosted by 3rd parties at published URLs, where a hash of the contract is contained in the URL
A signed hash of each data exchange is recorded to an audit trail on all databases, logs, ledgers, or blockchains specified by any party
A cryptographically signed chain of custody and contractual agreement provides 'data provenance' that can be used to support a wide range of data exchange on the Internet, from shared PII, to B2B contracts, to IoT, FinTech, supply chain, medical, news, content and distributed social
The standard, universal, developer-friendly, inter-operable 'off-chain solution'
JLINC provides 3rd party permissioning of data across multi-party chains
JLINC can automate existing contracts under existing law
Vastly reduced risk in case of a hack, exploit, or simple error
In case of a dispute, a judge can read the contract, and decide the case
Safe, secure method for cryptographically signing online agreements
If there is an error in the code, the code can be corrected
The missing 'middleware' in many blockchain stacks
Each party has a cloud service that holds and manages all of its contracts. Human-readable (and therefore legally admissible) contracts, expressed in JSON, are signed using standard public key cryptography with audit proof recorded on any combination of immutable ledgers or blockchains.
JLINC allows simple, verifiable, permission-based exchange. It creates a new 'consent management layer' on the internet where human and machine-readable information sharing agreements set terms for data use after transfer.
The core system consists of several API servers and their backend datastores, and an array of use case specific front-end applications, mainly javascript SPAs and mobile and desktop apps.
If you are a developer with javascript or go and/or dev-ops experience, and are interested in working with a very agile company that is out to change the paradigm, introduce yourself to us via dev@jlinc.com. Especially include pointers to any public repo code that you have contributed to and would like us to see.
A general introduction to JLINC: https://www.jlinc.com/post/jlinc-and-the-internet
JLINC Technical Philosophy whitepaper: https://jlinc.com/JLINC-whitepaper-2020-06-15.pdf
The API documentation is available here: https://jlinclabs.github.io/apidocs/
The JLINC protocol - somewhat out of date: https://protocol.jlinc.org/
The JLINC open-source implementation of JWT is here: https://github.com/jlinclabs/jlinc-jwt
The JLINC DID spec: https://did-spec.jlinc.org/
The JLINC DID client is open-sourced here: https://github.com/jlinclabs/jlinc-did-client
The W3C Authorization Capabilities working group: https://w3c-ccg.github.io/zcap-ld/
The JLINC Authorization Capabilities proposal: https://github.com/jlinclabs/jlinc-zcap
JLINC proposes the we use DIDs themselves as a new secure login method: https://www.jlinc.com/post/a-modest-proposal
The dev doc site is up and public now: https://docs.jlinc.io
