I can do some testing for your service when I find some free time, but for now I can do it only for testnet version if that is still available.
Is there any instructions I can read before I use it, and what should be written instead of mainnet custodian url address?
Taproot is already supported on your wallet if I understand correctly or not?

We support sending to Taproot addresses starting with witness version (1). I'm not sure what current developments are (if there have been more witness versions introduced) We don't support generating taproot deposit addresses, not until bitcoin core supports it.

double click the input field and the url for the testnet custodian should show up (https://testnet.blindmixer.com/#pubmp1qf98kxatpw43mqjft6j72dps5wn66yzp47k3zm0yn4skhedv32x5sphklj2)

After that, simply deposit using a lightning testnet wallet or a testnet faucet.

Correct. Since the wallet is fully custodial it can only be restored with your current custodian.

This was done to reemphasize the importance of remembering the right custodian in case there would have been multiple operators running the blindmixer software, which has not been the case thus far. Still, you might get confused between testnet and mainnet wallets.

Thank you for doing so, first of all.

Both of these issues are actually intended behaviour, though it can probably be repackaged to look a bit more professional.

I see. This is because you're asking the host (github) for a certain URL that only existed client-side (SPA). We should just automatically redirect you back to the "login page" to avoid any confusion.


This is also intended behaviour; the wallet is not really supposed to be "refreshed". If you have just made a transaction it should automatically redirect you to the transaction status. Refreshing the transaction page will not actually fetch any new data. Perhaps it does display previously unseen states that were already stored locally but not visible yet, however switching between the send/receive/transaction tab should make these new entries visible -- there would be no need to refresh. I guess this should perhaps be made more clear?

The "check" button sends a request to a blockchain explorer to discover if there have been any new transactions made to said address - if so - the wallet will ask the custodian to accredit the deposit.
I agree with you that there are two potential issues / improvements. We could remove the button on the /receive/ tab and automatically check the latest address to see if it received any new deposits, (but keep it on /addresses/ as that would become resource-intensive)

And secondly we should probably redirect users to the deposit once it is found. Currently after clicking "Check" you should switch back to the transactions tab to see the new transaction item and the corresponding information, which is admittedly a bit confusing. (No page refresh is needed though)

The sync button checks for any missing deposits, withdrawals, or unfinished states (unclaimed) by querying the custodian with your deposit addresses + unspent coins. You can try and see for yourself by taking your current seed, restore, and click sync. The transactions tab should automatically be populated with all of your previous transactions, and attempt to finalize them.

I like the "Generate Lightning Invoice" option for the Lightning Network feature....

I just want to ask a question... Seeing that a major "Mixer" owner gave up the data of it's users when things got heated a while ago, would it be possible to create a Mixer service that are OpenSource and decentralized and not owned and operated by a centralized individual or group?

It will give proof that logs are not stored and it will not be controlled by a owner that can give up any personal information or transaction history? (The code can then be scrutinized and Peer reviewed by experts to confirm that)

It can still push the "fees" to an address that are predefined in the code and the receiver of those funds can then use other mixer services to hide it's destination.  

Bump! Looking for people to test and review our software!

Thank you! We've added this to the list of bugs to fix.