Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

confusion about the daodao order book mechanism #405

Open
deso2021 opened this issue Oct 13, 2022 · 0 comments
Open

confusion about the daodao order book mechanism #405

deso2021 opened this issue Oct 13, 2022 · 0 comments

Comments

@deso2021
Copy link

deso2021 commented Oct 13, 2022

I have a question about the order matching. I hope you can answer it.

The core problem is that the transaction results may be different on different nodes in the concurrent state, and the results can be determined only after the block is generated (it takes several minutes). How to solve this problem now?

eg. sell order book

num price
1 2
1 1

In this example, A and B initiate a buy request at the same time. They both bid price is 2 and the buy quantity is 1. In the daodao node, A's request is processed first and B's request is processed later. Then A's cost is 1 and B's cost is 2. Users perceive the processing results of the daodao node. But at other nodes (such as diamondapp), B's request arrives first for processing. B's cost is 1, and A's cost is 2. If this block is mined by the diamondapp node, does the transaction result displayed on the daodao platform need to be updated? Or order matching can only occur in the daodao node (this is centralization)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant