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.
I want to compare JM activity in old, non-SW pool vs. the new SW pool.
At a certain point I expect the majority of JoinMarket activity to migrate over to the SegWit pool, but until that happens I would prefer to leave my coins in the pool which is throwing off more coinjoin transactions (and thus fees).
@adlai I suppose that counting the total number of messages in either pit should be correlated with total number of join transactions taking place... fair?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I want to compare JM activity in old, non-SW pool vs. the new SW pool.
At a certain point I expect the majority of JoinMarket activity to migrate over to the SegWit pool, but until that happens I would prefer to leave my coins in the pool which is throwing off more coinjoin transactions (and thus fees).
Could
ob-watcher.py
be used for this, @chris-belcher @AdamISZ @adlai? Thanks.The text was updated successfully, but these errors were encountered: