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

Their are -> There are #38

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2015-01-29-How-BitShares-Prevents-Front-Running.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ On the BitShares block chain orders are grouped into blocks every 10 seconds whi

# Solutions to Front Running

In our example the average user ended up getting less than they expected and the profits accrued to the advanced user who was able to run a bot or any one that could get their order in first. Their are many ways people have suggested for solving this, but it all boils down to timing. Some people suggest “randomizing” the order in which transactions are processed every block. Others have suggested a two-phase commit and reveal process. All of these strategies have significant shortcomings.
In our example the average user ended up getting less than they expected and the profits accrued to the advanced user who was able to run a bot or any one that could get their order in first. There are many ways people have suggested for solving this, but it all boils down to timing. Some people suggest “randomizing” the order in which transactions are processed every block. Others have suggested a two-phase commit and reveal process. All of these strategies have significant shortcomings.

## Randomizing Orders

Expand Down