Extrimian SSI Framework groups standards and specifications related to self-sovereign identity, DID, and verifiable credentials.
The NPM package provides the necessary functionalities for modular implementations of decentralized identity applications and provides interoperability with other components in an easy and flexible way.
Some of the solutions it provides are: DWN client, interpreting WACI-DIDComm messages, verification of verifiable credentials.
Extrimian SDK groups standards and specifications related to self-sovereign identity, DID, and verifiable credentials.
The NPM package provides the necessary functionalities for modular implementations of decentralized identity applications and provides interoperability with other components in an easy and flexible way.
Some of the solutions it provides are: DWN client, interpreting WACI-DIDComm messages, verification of verifiable credentials.
The Extrimian SDK groups standards and specifications related to self-sovereign identity, DID, and verifiable credentials.
We know that integration with the legacy systems of any government and/or company is key to the success in the implementation of sovereign identity solutions, this component is capable of solving the mapping of the legacy data with its corresponding one in the Context.
Most digital activities between people, organizations, devices, and other entities require the exchange of messages and data.
For entities to make this exchange with credential flows, applications, or services, they need an interface through which to store, discover, and retrieve data related to the flows and experiences in which they participate.
A decentralized web node (DWN) is a message transmission and data storage mechanism that can be used to locate authorized public or private data related to a given decentralized identifier (DID).
DWN are a mesh-like data warehouse construct that allows an entity to operate multiple nodes that are state-synchronized with each other, allowing the owning entity to protect, manage, and transact their data with others regardless of location or vendor, specific infrastructure, interfaces, or routing mechanisms.
Extrimian’s implementation of the DWN specification is a network node for messaging ,using rest api services as an interface to interact with decentralized applications, using JWS to authorize the entry of messages, and JWE to keep only readable by the recipient or user. Message creator, using decentralized identification networks to verify both public keys, and replicate the messages to other network nodes for messaging.
A decentralized web node (DWN) is a message transmission and data storage mechanism that can be used to locate authorized public or private data related to a given decentralized identifier (DID).
Modena-sidetree provides a Rest API that interacts with different technologies to allow creating, storing and verifying a DID Document.
The access point consists of a Rest API that exposes two endpoints, one to write a DID Document (either create, update, retrieve, or delete) and other one to resolve it.
The request that reaches the API must be signed with the private key that the DID Document exposes as the public update key. This information is validated by the API, which then generates a json file that allows the updates of a DID Document to be reconstructed. This file is published on IPFS.
On the other hand, every certain time, a process of all operations that were queued in the API is executed and taken to the anchor smart contract, pointing to the IPFS cid that contains the json that allows rebuilding the DID Documents for that batch.
When a new node joins the network, it must consult the anchor Smart Contract, from there it will index the cids in IPFS and will be able to reconstruct all the DID Documents created in the network previously. All the information already downloaded from the blockchain and IPFS is taken to a local database, currently implemented with MongoDB.
This rebuilding process occurs on all nodes, even those already on the network, to achieve continuous synchronization with each other.
In this way, the Modena node interacts with the Blockchain and IPFS continuously and saves the information obtained in a MongoDB to guarantee a continuous consultation of the DID Documents in a more performant way.
This rebuilding process occurs on all nodes, even those already on the network, to achieve continuous synchronization with each other.
Modena-sidetree is multichain, it currently supports: Starknet, RSK and Polygon networks
Isn’t your favorite network? contact us to evaluate the feasibility of adding it to the ecosystem.
Modena-sidetree is multi-didmethod currently supports:
did:modena:starknet:123
did:modena:rsk:123
did:modena:matic:123
Modena-sidetree provides a Rest API that interacts with different technologies to allow creating, storing and verifying a DID Document.
Resolves all Modena dids methods plus those registered in the W3C https://w3c.github.io/did-spec-registries/#did-methods
Modena-resolver is able to resolves decentralized identifiers (DIDs) through many different DID methods, according to the W3C DID Core 1.0 and DID Resolution specifications.
Extrimian SDK groups standards and specifications related to self-sovereign identity, DID, and verifiable credentials.
The NPM package provides the necessary functionalities for modular implementations of decentralized identity applications and provides interoperability with other components in an easy and flexible way.
Some of the solutions it provides are: DWN client, interpreting WACI-DIDComm messages, verification of verifiable credentials.
The Extrimian SDK groups standards and specifications related to self-sovereign identity, DID, and verifiable credentials.
We know that integration with the legacy systems of any government and/or company is key to the success in the implementation of sovereign identity solutions, this component is capable of solving the mapping of the legacy data with its corresponding one in the Context.
Most digital activities between people, organizations, devices, and other entities require the exchange of messages and data.
For entities to make this exchange with credential flows, applications, or services, they need an interface through which to store, discover, and retrieve data related to the flows and experiences in which they participate.
A decentralized web node (DWN) is a message transmission and data storage mechanism that can be used to locate authorized public or private data related to a given decentralized identifier (DID).
DWN are a mesh-like data warehouse construct that allows an entity to operate multiple nodes that are state-synchronized with each other, allowing the owning entity to protect, manage, and transact their data with others regardless of location or vendor, specific infrastructure, interfaces, or routing mechanisms.
Extrimian’s implementation of the DWN specification is a network node for messaging ,using rest api services as an interface to interact with decentralized applications, using JWS to authorize the entry of messages, and JWE to keep only readable by the recipient or user. Message creator, using decentralized identification networks to verify both public keys, and replicate the messages to other network nodes for messaging.
A decentralized web node (DWN) is a message transmission and data storage mechanism that can be used to locate authorized public or private data related to a given decentralized identifier (DID).
Modena-sidetree provides a Rest API that interacts with different technologies to allow creating, storing and verifying a DID Document.
The access point consists of a Rest API that exposes two endpoints, one to write a DID Document (either create, update, retrieve, or delete) and other one to resolve it.
The request that reaches the API must be signed with the private key that the DID Document exposes as the public update key. This information is validated by the API, which then generates a json file that allows the updates of a DID Document to be reconstructed. This file is published on IPFS.
On the other hand, every certain time, a process of all operations that were queued in the API is executed and taken to the anchor smart contract, pointing to the IPFS cid that contains the json that allows rebuilding the DID Documents for that batch.
When a new node joins the network, it must consult the anchor Smart Contract, from there it will index the cids in IPFS and will be able to reconstruct all the DID Documents created in the network previously. All the information already downloaded from the blockchain and IPFS is taken to a local database, currently implemented with MongoDB.
This rebuilding process occurs on all nodes, even those already on the network, to achieve continuous synchronization with each other.
In this way, the Modena node interacts with the Blockchain and IPFS continuously and saves the information obtained in a MongoDB to guarantee a continuous consultation of the DID Documents in a more performant way.
This rebuilding process occurs on all nodes, even those already on the network, to achieve continuous synchronization with each other.
Modena-sidetree is multichain, it currently supports: Starknet, RSK and Polygon networks
Isn’t your favorite network? contact us to evaluate the feasibility of adding it to the ecosystem.
Modena-sidetree is multi-didmethod currently supports:
did:modena:starknet:123
did:modena:rsk:123
did:modena:matic:123
Modena-sidetree provides a Rest API that interacts with different technologies to allow creating, storing and verifying a DID Document.
Resolves all Modena dids methods plus those registered in the W3C https://w3c.github.io/did-spec-registries/#did-methods
Modena-resolver is able to resolves decentralized identifiers (DIDs) through many different DID methods, according to the W3C DID Core 1.0 and DID Resolution specifications.
