Hi! We are working on a sidetree implementation using ethereum-ledger and we are making changes to support some use cases that can't be resolved in the current sidetree implementation.
We need to have two (or more) different nodes writing in the same blockchain block.
In the current implementation, only the first transactions is the one that applies and the others are discarded.
We would like to know why this limitation exists, and if you had thought about any possible solution.
We are considering changing the Ledger implementation and waiting for a specific number of blockchain confirmations before impact the changes on the local node database. In this way we can confirm that the timeline will not change after that, but we are not sure if this is the problem.
We will have to set the "writer" field of the Sidetree transaction to something different for each node. But we are not fully aware of the possible problems that this could bring.
Hi! We are working on a sidetree implementation using ethereum-ledger and we are making changes to support some use cases that can't be resolved in the current sidetree implementation.
We need to have two (or more) different nodes writing in the same blockchain block.
In the current implementation, only the first transactions is the one that applies and the others are discarded.
We would like to know why this limitation exists, and if you had thought about any possible solution.
We are considering changing the Ledger implementation and waiting for a specific number of blockchain confirmations before impact the changes on the local node database. In this way we can confirm that the timeline will not change after that, but we are not sure if this is the problem.
We will have to set the "writer" field of the Sidetree transaction to something different for each node. But we are not fully aware of the possible problems that this could bring.