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

Re-Design of DFI anchor system in a fair way #306

Closed
AltCoiFish opened this issue Apr 6, 2021 · 2 comments · Fixed by #314
Closed

Re-Design of DFI anchor system in a fair way #306

AltCoiFish opened this issue Apr 6, 2021 · 2 comments · Fixed by #314

Comments

@AltCoiFish
Copy link

What would you like to be added:

I am proposing a new re-design of the DFI anchor system to make it fair and transparent as it should be.
At the moment a lot of users a not anchoring anymore due to some technical disadvantages on the user side.

DFI anchoring was designed to set anchor on the Bitcoin chain in a regular time intervals and at the convenient of an anchor-user.
At the moment a lot of technical requirement is needed to protect your anchor against stealing anchor attempt. Stealing anchors is successfully performed at the moment on DFI chain.

Anchoring was described in the Whitepaper https://defichain.com/white-paper/ and it got funded/activated at DFIP#1 & DFIP#2 and also documented here https://github.com/DeFiCh/ain/wiki/What-is-an-anchor%3F

Latest changed to the anchoring where done in #277.

Currently we see the following anchoring happening on DFI & BTC blockchain:

  1. User#1 sends an valid anchor
  2. Another User#2 sends a bit later (between 2-10min) also an anchor which has a lower transaction hash value
  3. User#2 gets the anchor although he did send the anchor later then User#1.

Based on public documentation about DFI anchoring, the first user should get the anchor independently of anyone sending another anchor later if User#1 gets confirmed first or at the same time as User#2.

But., as we can see here

else if (a1->txHash < a2->txHash)
its not following these first-come-first serverules.

Why is this needed:

To restore the balance in anchoring and have some more competing users and let them anchor whenever they think its appropriate.

@defichain-bot
Copy link
Member

@AltCoiFish: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.

@monstrobishi
Copy link
Contributor

/triage accepted

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

Successfully merging a pull request may close this issue.

4 participants