Promotion has ended. Thank you for your continuous support!

We are currently running a promotion for the eWallet: Buy over 5 pcs, get them at half price on our website:

https://www.blackarrowsoftware.com/store/ewallet.html

14nm chip has been cancelled.

11.3 The Purchaser understands and agrees that we will use his payment in order to purchase the necessary materials or pay workmanship required to fulfill his pre-order which will be non-refundable if cancelled. For this reason, the purchaser hereby gives us the right and agrees with our decision to decline any requests from him or third parties to cancel his pre-order.

 Please place your order on our website: https://www.blackarrowsoftware.com/store/ewallet.html

The addresses are generated by the wallet. It would be insecure to use keys generated by the computer.

Did you confirm your shipping address? All X1 have been in stock for the last 4-5 months.

Sorry, we did not had time to set this up but we will shortly.
We can now offer the wallet without firmware and without bootloader for customers who wish to upload their own firmware.

Yes, we've changed the logo and the name in order not to infringe any trademarks. Please update from Trezor's website with their own binaries if you are not happy with it.

Due to lack of time we have not set up (yet) a git repository or the ledwallet.com website. We'll do that soon.

I agree that it is funny. However, it is not true. As explained in the news posted several months ago, only few miners had an issue that caused the mosfet to short-circuit itself. This was due to a poor design made in cooperation an Onsemi FAE. After working with Vishay's engineers we have fixed the issue.

We have been replacing under warranty all miners and/or boards affected.

We are working on a new miner. We'll offer compensation to those interested and who did not put defamatory posts on the internet as soon as it becomes available.

Dear Customer,

Your product, as it has been manufactured based on your order, is non refundable.  However, if you do not want your miner, we can refund the DHL fee and dispose of your product for free. Please contact our customer support if you wish to receive your shipping fee back.

Regards!

1. Our technical competence has been considerably improved. The staff responsible of our delays has been let go.
2. We're working on that, please move this question to the correct thread.
3. Although the claims mentioned are in error, you don't need to trust us as we run unchanged Trezor firmware. You can update the firmware from their website.

NEW!

We are currently running a promotion for the eWallet: Buy over 5 pcs, get them at half price on our website:

https://www.blackarrowsoftware.com/store/ewallet.html

---

Black Arrow is launching a new product:

eWallet - hardware Bitcoin wallet

• 100% Trezor compatible.
• Does not require a cable to connect to your laptop
• Smaller than Trezor
• Open source code available for auditing in order to ensure that there are no backdoors
• Can be used on a virused computer even with keylogger installed
• This wallet never exposes the private keys to the outside world to keep your coins always safe. All transactions are signed by the wallet.
• Embedded screen ensures that you sign the transaction that you really intend to.
• Available on request without firmware or bootloader for customers who wish to upload their own firmware

Now in stock.

Order here: https://www.blackarrowsoftware.com/store/ewallet.html

Stay away from Minersource. They have stolen $1050000 from us, we're currently discussing with the police and lawyers.

Dear Bitcoin Developers,

We would like to propose a feature in Bitcoin protocol in order to reduce the number of Bitcoin thefts.

Real world scenario: attacker installs a trojan into your computer, downloads the Bitcoin wallet and keylogs your computer to get the password. The attacker can and will spend all your money and there's nothing you can do about it.

So, we would like to propose this feature to be added to Bitcoin protocol:

A "Time Lock" command for Bitcoin addresses.

    This will function in the same way as a safe does: The owner of the address will announce the network that he/she wishes to lock this address and will require X amount of minutes/days to be unlocked.
     This would mean that the Bitcoin network will require the user to issue the unlock command and wait for the timer to expire before allowing him/her to spend the money from that address. The GUI client must announce the owner that his address has been unlocked and display a countdown timer so he has a chance to take action.

     There's a problem with the above scenario: as the hacker has access to the keys, the owner still cannot stop spending because he/she can lock the money again but the attacker can unlock them, triggering a race that leads only to a draw (permanent lock of the funds) or the attacker to win (as the hackers are dedicated to make software that will trigger their transaction faster or will spend higher commissions to get the transaction processed quicker etc).

Here is the solution to this problem:

    Lock command will also require an emergency backup address. A 2nd lock command issued will not allow to change the emergency backup address. If the attacker triggers the unlock command and the real owner wants the money back, he/she can issue an emergency recover command and the network will send the money to the emergency address (that was set-up when the first lock command was issued).  It is important that transfer will be completed only after the lock timeout expires and the new address will be locked again for the original timeout. This is required in order to give a chance to the real owner to issue the last and final command (if the hacker had managed to get access to the 2nd address as well).
    The last and final command that can be issued by the real owner of the new address will be to destroy the funds. The funds will be destroyed, not sent to the miners. This is important in order to deter the hackers to develop any other techniques to steal the money (for example few days ago I read that they hacked 6 ISPs and redirected the whole hashing power towards themselves). If we do not destroy the funds, we are inviting them to hack our hashing power.


To summarize:

   lock(address, delay, emergency address)
      note: a new lock command, issued while the lock is active, will not accept to change the emergency address or the delay.
   unlock(address, where_to_spend);
      note: a new unlock command will refresh the timer to the original lock command. If a previous unlock command was issued with no address to spend, there will not be accepted any new addresses
   issue_emergency(address);
       will cancel any unlock commands and send the money to the emergency address set with original lock(). emergency address will be locked for the same amount of time as issued by original lock(). No further unlock commands are accepted.
   destroy(emergency_address);
       can be issued only on emergency addresses that are locked. it is important that this transaction to be signed by emergency_address only as we do not want the hacker that has access to our original address to be able to destroy our saved funds.

   

Regards!

This is interesting.

Let me get this clear: We are not mining. It would be impossible to mine as we only have 5kw of power in our office.

You can ask Joshua where is our mining facility and we will be happy to this this address to check.

If you have our customer database it is stolen. We will now announce the police to get to the bottom of this.

No one from our staff changes passwords or disables accounts. Please let me know by private message what is your email if you still have issues logging into your account in order to help you fix this issue.

Please let me know your order number and email address via PM so I can look into your case.