Skip to main content

Q3-Q4 2025 & January 2026 - Main Development Progress

TL;DR Second half of 2025 and beginning of 2026 has been an intense period for the TWIN Development team, with considerable progress that has resulted in further development of the technology, vision and ecosystem projects, while the team has been strengthened with new members and expertise.

Fundamental Achievements​

Architecture and specification​

  • New version of the TWIN White paper with the following highlights:

    • Alignment with Eclipse Dataspace Protocol and W3C DCATv3 for catalogue resource descriptions.
    • Simplification of the Gaia-X Loire Service Offering and Data Resource in favour of W3C DCATv3 Dataset and DataService.
    • Addition of Dataspace Contract Negotiation aspects.
    • DS Connector Data Plane based on the W3C Linked Data Notifications and W3C ActivityPub avoiding the need of custom subscription payloads for publish/subscribe.
    • TWIN Adaptors section refined with latest practices.

  • 8 RFCs have been drafted that outline the major detailed design decisions and our implementation roadmap. The development of these 8 RFCs is ongoing. See RFCs Repository

TWIN Core​

  • Multi-tenant Node feature: Allow a TWIN Node to act as an Agent for several organisations while keeping their data isolated.
  • Node bootstrapping improved including command line interfaces.
  • Hardening of all components including end-2-end tests with IOTA mainnet and gas station.
  • Aligning all of the Standards packages and introduction of new package for UN/CEFACT.
  • Added Trust Service with a modular, pluggable architecture that supports dynamic registration of trust processors. An initial plugin provides support for self-signed Verifiable Credentials (VC), enabling validation workflows without reliance on external issuers.
  • Federated Catalogue implementation aligned with Eclipse Dataspace Protocol Catalog standard.
  • Added validation utility for embedded i18n string references. The tool performs static analysis of source code to detect internationalisation (i18n) keys and verify their existence in the corresponding language resource files.

TWIN ID​

  • Successfully implemented IOTA DID Method, enabling identity for organisations with issuing flows for business licences, certifications, and accreditations.
  • TWIN ID has also adopted a number of globally recognised identifier APIs like GLEIF LEIs and EORI numbers in parallel to the development of a vLEI prototype enabling a comprehensive trust anchor for trade ecosystems.
  • A modular onboarding toolkit is now being tested to enable easy integration of authentication and IOTA identity functions to TWIN ecosystems, producing a consistent and frictionless user experience for ecosystem users.

Ecosystem Project implementation​

  • The Border Trade Demonstrators project (UK) is now using all the TWIN Core stack through the TWIN Supply Chain App. The pilot, currently in production, is using the IOTA Rebased mainnet as DLT.

Next Steps​

Webinar by end of March 2026. Updated end to end use case showing Data Exchange services in action, demonstrating how different Participants can pull or push supply chain data.

🚀 More quarterly updates and roadmap details coming soon...