-
Notifications
You must be signed in to change notification settings - Fork 85
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
Update BullBitcoin's Wasabi-Coinjoin support guides #1286
Comments
Once this is done, maybe @thibistaken can help update the french version of those guides:
|
Specifics
I emailed their support to ask where the GitHub repo was for this page. I described that I wanted to update this section. The two main things I see is that the sentence
The main thing I see that needs updated here is the logo. If we want to be fussy we could request them to change the sentence
Again, the logo needs updated. The sentence |
I've opened a couple PRs to fix sentences about minimum amounts required for coinjoins
I'm working with @CAnorbo and the marketing team to update the logos. Also, I found another page on their website that needs completely rewritten: |
I have mentioned https://guides.bitcoinsupport.com/guides/v/coinjoin/ in the description and all the pages of that guide should be updated if needed. There is this example for labelling in https://guides.bitcoinsupport.com/guides/v/coinjoin/using-coinjoin/overview: IMO the label should simply be |
I created another PR: SatoshiPortal/coinjoin-guide#5 |
This one is merged. |
This is obsolete, I cannot find those guides anymore. |
Check all the following guides and update their content and their visuals (logo):
Either open pull requests to update the guides, or at least open issues in their repositories.
Whoever takes this issue, please tag me in the PRs to help review them.
Some already open issues:
SatoshiPortal/wasabiwallet-guide#7
SatoshiPortal/wasabiwallet-guide#8
SatoshiPortal/wasabiwallet-guide#9
SatoshiPortal/coinjoin-guide#1
cc @MarnixCroes @BTCparadigm @jesseaam
The text was updated successfully, but these errors were encountered: