UBID

UBID offers unique identifiers that are cryptographically verifiable and self-owned, empowering users with control over their digital identities without relying on centralized authorities. It enables seamless integration across UBIT's ecosystem, allowing users to manage attributes, authenticate transactions, and interact securely with decentralized applications (DApps). UBID enhances privacy, security, and interoperability within UBIT, ensuring trustworthy and efficient digital identity management for all participants

Understanding UBID

A DID is an Identifier that allows you to lookup a DID document that can be used to authenticate you and messages created by you. Any Ethereum account regardless of whether it's a key pair or smart contract based is considered to be an account identifier. An identity needs no registration.

Each identity has multiple address which maintains ultimate control over it, which are called the controllers of the DID. By default, each identity is controlled by itself. As ongoing technological and security improvements occur. Now coming to the DID document A DID (Decentralized Identifier) document is a JSON-LD (JSON Linked Data) format document that encapsulates essential information about a decentralized identifier. It serves as a structured representation of an entity's digital identity within decentralized identity systems

{
    "@context": "https://www.w3.org/ns/did/v1",
    "id": "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4",
    "controller": [
        "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4"
    ],
    "verificationMethod": [
        {
            "id": "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#vm-0",
            "type": "Secp256k1VerificationKey2018",
            "controller": "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4",
            "publicKeyHex": "0x8f26d683822e60d522b58f7db63d352cb7fae6e4"
        }
    ],
    "authentication": [
        "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#vm-0"
    ],
    "capabilityInvocation": [
        "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#vm-0"
    ],
    "capabilityDelegation": [
        "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#vm-0"
    ],
    "assertionMethod": [
        "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#vm-0"
    ],
    "keyAgreement": [
        "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#vm-0"
    ],
    "service": [
        {
            "id": "did:ubit:0x8f26d683822e60d522b58f7db63d352cb7fae6e4#mailbox",
            "type": "DIDComm",
            "serviceEndpoint": "http://localhost:5173/network"
        }
    ],
    "attributes": {
        "0x120d9a3c10568303ea1744ea1c17ec39fbca86bc": {
            "value": "",
            "validity": 0
        }
    }
}

Now as you understand the basics of what a DID is moving on to the implementation of UBID and how it works, also a point to note it follows the ERC-105 standard and also is compliant with the W3C standards

The main contract DIDregistrybase.sol is deployed on the UBIT testnet at this address contract address: 0xf45DC743cb3122bfF9135c5C8FDc9EA88e74116D

Architecture

This is the overall architecture of the UBID dapp