You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Latest changed to the anchoring where done in #277.
Currently we see the following anchoring happening on DFI & BTC blockchain:
User#1 sends an valid anchor
Another User#2 sends a bit later (between 2-10min) also an anchor which has a lower transaction hash value
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.
@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.
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:
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
ain/src/masternodes/anchors.cpp
Line 659 in b4175b8
first-come-first serve
rules.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.
The text was updated successfully, but these errors were encountered: