So it can work, right? Cause it says that epochs last a minute, but transactions happen way faster, I don't get it.
The article states that there are no blocks,
but at the same time Epochs are like lists of transactions themselves.
So shouldn't they be considered as blocks?
Topic: Is Epoch-CRDT a working model? (Read 82 times)
To be honest, CRDT sounds like a fancy word for blockchain, and you don't have to be an OG to figure that out.
I looked it up and found this article:
So from a birds eye it's just putting transactions on the chain after every epoch, and not every time a block is generated. An epoch is 2 weeks in bitcoin so that would make transactions prohibitively slow to confirm. Of course I could be wrong about all this because I just glanced through the article.
(DLT just stands for distributed ledger technology.)
I looked it up and found this article:
Quote from: https://blog.humanode.io/epoch-crdt/
For the application level, which represents transaction processing and validation logic, we defined the following set of buckets to hold the state:
Epochs — a KV subspace (bucket) that holds epoch snapshots. An epoch snapshot is similar to a block in the classic blockchain, but within our network transactions are grouped in epochs. More on that below. Each epoch has a number as a key that points to a list of transactions.
Transactions — a bucket holding set of confirmed transactions. Consensus participants decide whether or not to include a transaction into that set. If the transaction is confirmed, its CID and validator signatures are added to the set, and the body (data, metadata, result, etc) will be replicated through IPFS using DAGSyncer.
Epochs — a KV subspace (bucket) that holds epoch snapshots. An epoch snapshot is similar to a block in the classic blockchain, but within our network transactions are grouped in epochs. More on that below. Each epoch has a number as a key that points to a list of transactions.
Transactions — a bucket holding set of confirmed transactions. Consensus participants decide whether or not to include a transaction into that set. If the transaction is confirmed, its CID and validator signatures are added to the set, and the body (data, metadata, result, etc) will be replicated through IPFS using DAGSyncer.
So from a birds eye it's just putting transactions on the chain after every epoch, and not every time a block is generated. An epoch is 2 weeks in bitcoin so that would make transactions prohibitively slow to confirm. Of course I could be wrong about all this because I just glanced through the article.
(DLT just stands for distributed ledger technology.)
Guys, I've stumbled a DLT called Epoch-CRDT.
Really interested if that is a scam or not because it claims to solve many problems that blockchain can't. Any OG's here to help me out?
Really interested if that is a scam or not because it claims to solve many problems that blockchain can't. Any OG's here to help me out?
Jump to: