LDSC

Open source · Apache-2.0 · Rust · latest release v0.1.0

A small, fast connector for the Luxembourg data space.

LDSC lets an organisation offer and use data under agreed rules, using the open standards of European data spaces: the Eclipse Dataspace Protocol for catalogs, contracts and transfers, and the Decentralized Claims Protocol for identity and verifiable credentials. It is built to work with Eclipse EDC and Simpl-Open, and to follow the Gaia-X Trust Framework.

Prototype. LDSC is in its 0.x releases and not ready for production. What works today is listed in the roadmap.

Source code Architecture

Objectives

  • Standards first

    Behaviour comes from the specifications (DSP 2025-1, DCP 1.0, Gaia-X Danube), checked against their official conformance kits.

  • Interoperable

    Talks to Eclipse EDC and Simpl-Open connectors; interoperability is tested, not assumed.

  • Small and predictable

    Static binaries in empty images of a few megabytes, starting in milliseconds and using a few megabytes of memory.

  • Secure by default

    Strict message parsing, a short list of signature algorithms, keys kept out of the internet-facing service, signed releases.

  • Simple to run

    Few components, one version for all of them, configuration through environment variables.

  • Open

    Apache-2.0, decisions recorded in the open, and a public security assurance case.

Minimum functionality

What a participant can do with LDSC 1.0:

  1. Publish a catalog of datasets with usage policies (ODRL offers), and browse other participants' catalogs.
  2. Negotiate a contract for a dataset, with the policy checked on both sides.
  3. Transfer the data over HTTP, push or pull, through the built-in data plane.
  4. Prove who you are with a did:web identity and verifiable credentials (DCP), and check the credentials of others.
  5. Issue credentials, such as dataspace membership, when you run the dataspace.
  6. Meet Gaia-X rules: hold and present Gaia-X compliance credentials.

Components

One code base and one version. Each component ships as its own small image, split by who runs it and which keys it holds (ADR 0003).

ImageDoesWho runs it
ldsc-connectorCatalog, contract negotiation, transfer and data plane; checks partners' credentialsEvery participant
ldsc-identityHolds the participant's identity, keys and credentials; answers credential requestsEvery participant using DCP (optional with an external wallet)
ldsc-issuerIssues and revokes credentialsThe dataspace authority only

Deployment order

  1. PostgreSQL.
  2. ldsc-identity: publish the did:web document over HTTPS.
  3. The dataspace authority issues a membership credential (and, for Gaia-X, the participant obtains a compliance credential).
  4. ldsc-connector, pointed at the identity and the database.

Roadmap

Short releases; each one is usable on its own. Details in the roadmap.

  1. 0.0 Technology spike: Rust chosen; catalog slice passes the DSP conformance tests (metadata, catalog)
  2. 0.1 Repository foundations: licensing, supply-chain checks, signed releases, this website
  3. 0.2 DSP version and catalog; higher OpenSSF scores (Best Practices passing, Scorecard)
  4. 0.3 Contract negotiation
  5. 0.4 Transfer process and HTTP data plane; EDC interoperability test
  6. 0.5 DCP identity and presentation; Simpl-Open spike
  7. 0.6 Credential issuance and credential-based policies
  8. 0.7 Gaia-X Trust Framework (Danube)
  9. 0.8 Operations: health checks, logs, metrics (OpenTelemetry), a two-participant demo dataspace
  10. 0.9 Hardening and release candidate for 1.0

Trust and quality

Checked on every change; values read when this page was built (2026-11-11).

Report a vulnerability privately: GitHub security advisories. Read the security policy and the security assurance case.