209 похожих чатов

Currently bch uses the mempool state to prevent double spend

for unconfirmed transactions. Are you suggesting it's not doing the job?

2 ответов

8 просмотров

The dex transactions are anyone can spend, so two different people could perform different transactions that broadcast to different servers at the same time, and then more transactions could occur on each of those competing unspent outputs leading to two different chains where one will ultimately be included in the next block and the other will cease to exist. This is a theoretical scenario for now, but his argument is that this is the way to prevent that from occurring.

Hossein- Автор вопроса
Dustin 🪐
The dex transactions are anyone can spend, so two ...

I see. I'm aware of this issue. Forks in the state of mempool. Having a central authority to include transactions is not the only solution.

Похожие вопросы

Обсуждают сегодня

Карта сайта