Thank you - certificate has been renewed.

Yes, it is manual.

Please contact us again by e-mail and provide "invalid" key.

We did not run out of chips lately.

If it was never funded then signed receipt would be easy proof.

4 @ 0.10

Thank you very much.

4 @ 0.10

4 @ 0.10

You deposit 256 mBTC - You receive 256 CHIP no. 111.
You click "split" - Chip no. 111 is exchanged for two 128 CHIPs: no. 52 and no. 95
You click "merge" - Chips no. 52 and no. 95 are exchanged for one 256 CHIP no. 69

Split-then-merge does not affect privacy.

You split to hide chip sizes you receive from ChipMixer. By default you receive the most effecient chip sizes.
You merge (ie. new deposit and old voucher) to withdraw chip larger than each separate deposit.

Cloudflare introduced onion integration - https://blog.cloudflare.com/cloudflare-onion-service/



Bitcointalk uses Cloudflare already. Can we get .onion service and get rid of this recaptcha madness?

ChipMixer service updated

• session tokens and vouchers no longer contains confusing letters (ie. 0 and O, I and l) and both are displayed with different font style - it is easier to write them down by hand (if you really need it)
• our contact section contains pgp key - it is not required to use it and it was generated by protonmail.com
• our support staff can now publish notice / warning on mixers page - it will be easier to notify users about mixer problems
• step 2 has been redesigned to display value of vouchers and private keys - you no longer need to know about vouchers at step 3
• donate chip button has been redesigned to avoid accidental clicks

When you deposit 2.23 mBTC you receive 2 mBTC chips. One 2 mBTC or two 1 mBTC. Splitting and merging chips does not change amount you have.

We do experiments and measure their usage. Installing Electrum plugin is harder than using ChipMixer with browser. Low amount of our users use plugin. Updating the plugin will not change it.
We are working on bundling ChipMixer plugin with a special version of Electrum - it may change it.

You can prove BTC belong to you signing a message with your BTC address.
Exchange can prove owning their address signing a message with that BTC address.
You can prove depositing BTC to exchange address pointing transaction id on blockchain.

KYC does not prove anything. It is an image uploaded to one exchange then stolen and uploaded by somebody else to another exchange then stolen and uploaded by somebody else to another exchange.
Bitcoin is proof of ownership and change of ownership.

4 @ 0.10

As with every service - you need some trust. We are open about how our way of mixing work. There is no secret sauce. We break deposits into chips and redistribute them to other customers at random. We are breaking link on-chain and it is our offer. You are free to find a way to break a link with us ie. use another mixer.

That is why chips are not to be long term storage. Spend them at random time, send them to hardware wallet.

Please use chipmixer@protonmail.com email support instead of forum PM. It is easier to keep track of support requests and email is checked more frequently due to forum captcha.

Issue has been resolved and chips have been refilled - https://bitcointalk.org/index.php?topic=1935098.msg45269764#msg45269764

Hello

It took longer than we planned but service is working now. Sorry about that.

Low value chips are being refilled. Sweeps are working now.

You can redeem your vouchers now.

If you encounter problems - send e-mail to support.

EDIT:

We still have problems with clearnet captcha. .onion link works correct.

Captcha issue has been fixed.

Hello

There are some issues with our service (sweeping and low chips) and they will be resolved in next 24 hours.

If you have an active session:
Please extend your session or use "withdraw as voucher option".

If you do not have an active session:
Please delay use of our service for 24 hours (or try our competition).

Both issues fixed. If your deposit still does not show - send us an email.

4 @ 0.10

You need read more

Yes. This is kind of only reason to DDoS a mixer, eh?