Sorry for the late response. We are living in China. The government puts a strict limit on the networks. We'll have to use some kind of a proxy to visit bitcointalk.org. That's why we are not responding in time. Sorry.

It's a good advice that you brought to us. We will discuss it. Thank you for your support.

Eh, Bither is meant to be working right on Yosemite. We all use Yosemite in the team. How did you upgrade from Mavericks? Did you erase all your data? Bither's data is stored in this folder ~/Library/Application Support/Bither . You can go and check if your data is still there.

Thank you for trying to use Bither as your wallet. I'm one of the developers. I can see you are already on the right track. If you have any further questions, feel free to ask me. We will try to increase the sync speed in the next version.

Thank you so much for taking Bither in consideration. We will keep improving Bither.

The hot wallet needs to store an encrypted token authenticated via BitID by the cold to the HDM server to ask the server to cosign.

'Reset HDM Server Authentication' will ask cold wallet to authenticate a new token, and revoke the old one.

Usually you don't need to manually use this function. This is only useful when you try to use your hot wallet to send transactions if you has tried the recovery of your HDM account and yet you still have your original hot wallet in your hand. The recovery will revoke the token on the original hot wallet. Therefore the hot wallet needs a reset of the authentication.

Is your hot HDM account already set up? In anther word, is the triangle completed? If your hot HDM account is already set up, the HDM server button should not respond to any taps. If not, please let us know. Thank you for your feedback.

When using addresses other than HD account, we can still send changes in the old way.



We're planning to do this in the next few versions. No ETA yet. It's a good advice to add a "+" button. Thank you for your advice.

Thank you for your supporting Bither.

HD account will use a new address every time you want to receive a payment or send a transaction with change.

We are considering maybe supporting multiple outputs transaction in some kind of a plugin.

I'm wondering if reprogramming some used FPGA miner to generate vanity addresses will be possible.

Maybe some FPGA miner can help us accelerate the calculation.

Currently Bither just uses Vanitygen to generate vanity addresses. GPU acceleration is supported. But over clocking is not a thing on the software side, it may be done by the user using some other system utils.

We are planning to keep improving the Vanitygen project. In the future versions of Bither, there may be more optimization.

I'm one of Bither's developers. I can't generate vanity address with the integrated GPU on my Macbook either. After some digging, it turns out that there are some bugs in Apple's OpenCL driver. Unless Apple fixes this problem, we won't be able to use our integrated GPU for OpenCL computation. We'll continue digging into this. Thank you for trying our wallet.

Yeah, you are right. We should make this error message clearer.


I've run some tests upon this and checked the code. It comes out that the BIP39 calculation speed is what differs between iOS & Android. My iPhone5s does this nearly 10 times faster than my middle end Android phone. You have no need to worry about your entropy.

Thank you for using Bither and giving advices.

Each HDM seed is generated separately on its own device. Server key and the Hot key are NOT derived from the Cold key. The Cold key is used for HDM Server's BitID access control. In this way, if you lose your hot phone, you can use your cold phone and server to recover bitcoins, and if Bither server is down, you can use your hot and cold phone to recover bitcoins. Generally, you only need to backup the cold seed.



Currently we do not support importing seeds, because importing will make the HDM account generating process too complicated, we haven't found an elegant way to do this. We only support recover cold seed from backup at this point.

One free VPS does not seem to have the enough space to run a Bitcoin full node. I think he is doing some other kind of work but appears as full nodes on the Bitcoin networks.

Yes, my tx is standard. And when I send it to other nodes, it gets confirmed soon.



I'm wondering too.

These nodes with IP address 46.105.210.* suddenly came out from nowhere.

These nodes all seem normal. They have the latest blocks and the version code 0.9.3. You can ask blocks from them. But you can not send transactions through them. When you send Tx hash to them, they never come back to you for the Tx detail.

Is there any thing special that nodes like these are made for?

1. Modern operating systems on mobile phones like iOS and Android run apps in sandboxes. One app can hardly become malicious if the user has not rooted or jailbroke his device.

2. The hacker who do his best effort to get control over HOT can not benefit directly from his work. He can only give the miners more bitcoins but leave no extra income for himself.

Bither was made half a year before.

So when you mention existing protocol, we should consider Bither's.