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
{{ message }}
This repository has been archived by the owner on May 13, 2022. It is now read-only.
More graphs would be useful. Perhaps graphs like those on http://bitcoinity.org/markets which show the depth of the orderbook at a given coinjoin amount.
This would need talking to some trader / algo types, and investors and heavy users to see exactly what kind of information they'd find useful
The text was updated successfully, but these errors were encountered:
An interesting graph could be of implied relative fee vs coinjoin amounts. Implied relative fee meaning you take absolute fee orders divided by coinjoin amount.
With reference to this quote
think how many individual people own 0.01btc and how many own 100btc. It should be obvious which is more scarce and can command the higher fee.
Such a graph would tell us exactly how much proportionally cheaper it is to join 0.01btc than 100btc
Another one could be a 3D graph of a histogram of coinjoin amount and implied relative fee. It would probably be much easier to read than all the graphs currently on the /depth page of ob-watcher.py
Log scales are good and useful because power law distributions of wealth and income.
Some kind of interface which describes to people how the weighted random order choosing works. They type in a coinjoin amount and it shows all the suitable orders along with a probability, plotted on a nice graph so the exponential decay is obvious.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
More graphs would be useful. Perhaps graphs like those on http://bitcoinity.org/markets which show the depth of the orderbook at a given coinjoin amount.
This would need talking to some trader / algo types, and investors and heavy users to see exactly what kind of information they'd find useful
The text was updated successfully, but these errors were encountered: