Is the DID Document instantly resolvable after successful DID operation creation?

One of the challenges when dealing with the Bitcoin network is it takes a while to confirm a transaction to the blockchain. Bitcoin writes a block of transactions at an average of every 10 minutes. And what goes to that block depends on the transaction fee that a user paid. The larger the fee the faster the transaction is included in a block. At the time of this writing, 16 US cents is the fee paid to get a transaction to go into the next block, 15 cents to make sure it goes in the next 3 blocks, and 5 cents into the next 6 blocks.

 Sidetree processes DID operations every 10 minutes as the default configuration. Syncing the DID Cache from blockchain happens every 5 mins This in turn would make the process to persist a DID into the blockchain take about 10 mins best case to around 25 minutes worst case. Why 25 minutes? Because if you are unlucky, it can take 10 minutes to run operation processor, plus 10 minutes for Bitcoin to persist the block, and an additional 5 minutes for the transaction processor to run. 

Is there anything we can do to use the DID immediately after writing the DID operation into sidetree? I think It would be a good idea to immediately store a valid DID operation into the DID cache even before persisting it into bitcoin. An advantage of this is the DID Document will be instantly resolvable to this specific sidetree node.

Comments

Post a Comment

Popular posts from this blog

The Sidetree Protocol

Blockchain scalability is a non-trivial problem, but there is now a promising strategy for scaling blockchain-based systems known as ‘Layer 2’ protocols, or L2s, for short (example: Bitcoin’s Lightning Network). L2s achieve scalability through deterministic processing and transaction schemes that take place ‘above’ the blockchain, with zero or minimal consensus requirements beyond small points of interaction with the underlying chain. For decentralized identity to become a reality, it requires a system that operates at massive scale, while still delivering on important features, such as deterministic state resolution and differential persistence. Using blockchains for anchoring and tracking unique, non-transferable, digital entities is a useful primitive, but the current strategies for doing so suffer from severely limited transactional performance constraints. Sidetree Entities is a Layer 2 protocol for anchoring and tracking entities across blockchains. Sidetree Enities, and nod...
Read more

On the IoT Exchange - DID integration

One of the challenges of introducing Decentralized Identifiers (DID) into Internet of Things (IoT) is the proprietary nature of the IoT ecosystem. Most IoT devices use proprietary technology. The ideal way of integrating DIDs is to put the keys and some cryptographic operations directly into the device. The assumption here is (1.) the manufacturer themselves can either generate and embed the keys from a secure or "offline" environment or (2.) manufacturer can embed cryptographic logic into the device and the device would generate the keys themselves, given that the device has enough power to execute the operations. If we are going create a service from DIDs and we do not have any access to the device manufacturing process, we may need to generate and maintain the keys elsewhere, but we need to make sure the pathway from that "elsewhere" to the device is _secure_, and how that secured pathway is implemented is *out* of the scope of this post. That "elsewher...
Read more

Smartkey Overview

Whenever we write applications, we need to keep our _secrets_ in a single central secure place. These secrets can be your password to your database, your api key, or your cryptographic keys used for signing messages. There are two major reasons why we want to do this. The first one is we want these secrets to be fetched by multiple instances of the application from a single place, instead of duplicating or hardcoding them in the application. This secure place may be a keystore stored in a directory in a file server, but making it reachable across different environments, specially when dealing with software development in the cloud, ultimately becomes a challenge. Nowadays, this is implemented as a service, where it expose endpoints easily accessible to applications for fetching the secrets themselves. Aside from key access, these type of services often offer key management solutions such as key rotation and key revocation. These solutions are sometimes referred as key management servi...
Read more