Start amount organization specification #88
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think it'd also make sense to constrain this initial discussion between @nothingmuch @seresistvanandras @MaxHillebrand @lontivero and @molnard based on the "too many cooks spoil the soup" principle. In fact, this is already too many people to hope to get agreement on so keep that in mind and be more cooperative than usual. |
Co-authored-by: Max Hillebrand <[email protected]>
Co-authored-by: Max Hillebrand <[email protected]>
Co-authored-by: Max Hillebrand <[email protected]>
Pow2Pow3Pow10Pow10 + Pow10 * 2 + Pow10 * 5Pow3 + Pow3 * 2 |
yahiheb
suggested changes
Dec 11, 2020
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
Co-authored-by: yahiheb <[email protected]>
|
I've added some more information to look at. Summary
Pow 2Pow 3Pow 10 1-2-5 (Pow 10 + Pow 10 * 2 + Pow 10 * 5)Pow 3 + Pow 3 * 2 |
|
Blockspace efficiency: |
|
A couple of stats to look at with our blockspace efficiency metric. 1000 runs per configuration, powers of 2, average, median, standard deviation. My last 3 findings are really strange. Note that I either made a bug or something really strange is happening we must explain. Defaults:
Minimum Probable Denomination (RESULTS EXPECTED)There's a constant we can tweak based on the probable denominations. I set this based on the number of inputs/div. Div is the divisor:
So it looks like for pow2, if we choose div for around 4, then that's how the most blockspace efficient mixes are got. Remix Ratio (RESULTS EXPECTED)So I've chosen div to 4 and started tweaking the remix ratio. (This isn't something we can tweak, but it's interesting to see the results.)
User Ratio (RESULTS NEED EXPLANATION)For example if user ratio is
Input Count (RESULTS NEED EXPLANATION)Next I'll set the user count to be 4/5 of the input count (to keep it constant) and see the changes like that.
Input Count where Input Count = User Count (RESULTS NEED EXPLANATION)Next I wanted to see what happens if input count is exactly the user count as the previous results surprised me.
Input Count where Minimum Probable Denomination = 2 (RESULTS NEED EXPLANATION)Next I wanted to see what happens if I set the minimum probable denomination to constant 2 - and I set back the user count to be dynamic- as the previous result surprised me.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added a document to kick off our amount organization specification. I'm proposing to first define the most typical target user, then collect their problems/objectives and specify alternative approaches on how we could start out building the scheme.