Thank you for the feedback, we will consider to do this in the future. But currently, we focus on Mobile APP.

NEW PROGRAM!
We plan to provide a 1: 1 cross-chain transfer service of stablecoin assets like #USDT on Ethereum to stablecoin assets on NervosNetwork

https://medium.com/bitpie/announcement-on-nervos-ckb-cross-chain-development-program-by-bitpie-wallet-7ff1fdd011

Interesting, seems people like to use desktop than mobile App. But, why? Isn`t mobile App much more easy to use?

"Don't Trust. Verify."

#BitHD is 100% open sourced. How to Verify BitHD Wallet Firmware Source Code???

Here is the tutorial: https://bitcointalk.org/index.php?topic=5235828.new#new

Now, based on the prepared firmware image, anyone can build the same signed image by signatures uploaded in code repository on https://github.com/bithd/bithd-mcu/blob/master/README.md

"Don't Trust. Verify."

#BitHD is 100% open sourced. How to Verify BitHD Razor Wallet Firmware Source Code???

Here is the tutorial: https://bitcointalk.org/index.php?topic=5235828.new#new

Now, based on the prepared firmware image, anyone can build the same signed image by signatures uploaded in code repository on https://github.com/bithd/bithd-mcu/blob/master/README.md

Thank you for your opinion sharing.
We will consider to support the batch sending on our hardware wallet BitHD. bithd.com

“Don’t trust. Verify.”



The best way to prove you didn`t has a backdoor of your product is to make it Open Source. It doesn`t means that will be 100% safe but means we can work with the whole geek community to avoid any attack.

Open Source means any users can compile the firmware by themselves. Therefore, BitHD hardware wallet team prepared this tutorial to guide you to verify the consistency of the codes between the firmware on GitHuband the actual firmware on the BitHD hardware wallet product being sold on Amazon and eBay.

Before We Start:
This tutorial is based on mac system operation, windows system users can download linux system to complete the operation process.

During the compilation process, please do not close the terminal program.



Open Terminal

You can find Terminal by search ‘Terminal’ in the Launchpad.



2. Install the compilation environment

2.1 Install Docker

https://docs.docker.com/install/


2.2 Input the following command in the terminal and hit ‘enter’ to install homebrew

ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"



2.3 Paste the following command in the terminal to install python3 and pipenv through homebrew

brew install python3 pipenv



Get BITHD firmware open source code
Create a new folder on the desktop and name it “BITHD”



2. Open terminal and input the following command to enter the folder directory

cd ./Desktop/BITHD/



3. Continue to input the following command in the terminal to get the open source code on GitHub

git clone https://github.com/bithd/bithd-mcu.git



4. After successful acquisition, a BITHD-mcu folder will be generated in the BITHD file



This folder is the open source BITHD firmware code on GitHub, and subsequent compilation operations will be performed in this file directory.

Compilation
This step requires high computer performance, and some steps will take a long time. Please do not close the terminal before the terminal completes the operation, and wait patiently for the terminal to finish compiling.

Input the following command in the terminal to enter the firmware code root directory

cd bithd-mcu



2. Input the following command in the terminal to compile the corresponding version firmware.

export TAG=v2.7.4; ./build-firmware.sh $TAG



After the compilation is completed, the compiled firmware file will be generated in the BITHD / BITHD-mcu / build folder. At this time, the compilation steps for the GitHub open source code have been completed.

Sign the compiled firmware
Input the following command to install designated python environment.

pipenv — python 3 install



2. Input the following command to generate a bin file to sign

pipenv run ./script/prepare_firmware.py -f ./build/bithd-$TAG-unsigned.bin



A file named bithd-v2.7.4-prepared.bin will be created in the folder BITHD/BITHD-mcu/build.

3. Input the following command at the terminal. Sign this file with the signing file provided by BITHD official.

The signing file is saved in the folder BITHD/BITHD-mcu/signatures

export TAG=v2.7.4
pipenv run ./script/build_signed_firmware.py -f ./build/bithd-$TAG-prepared.bin -s . signatures/$TAG.csv



After signing, a new file bithd-v2.7.4-signed will be generated in BITHD/BITHD-mcu/build. This file is the firmware we compiled and signed with the GitHub source coded and official signing file.

So far, we have completed all the steps of getting code from GitHub, compiling and signing. Then, we will verify the firmware.

Firmware Verification
Connect BITHD, choose to export the firmware in Bitpie APP. Tip: this exporting is only about firmware information and has nothing to do with your assets.



2. Through comparison, verify the consistency between the firmware in your hardware and the GitHub open-source firmware.

Input the following command in the terminal, and the comparison result will be shown as export

TAG=v2.7.4diff <(xxd build/bithd-$TAG-prepared.bin) <(xxd build/bithd-$TAG-firmware.bin)

Tip: please move the exported firmware file into folder BITHD/BITHD-mcu/build and edit the file name as same as the name in the command. E.g. the exported file name is bithd-wallet-firmware, we need to rename it as bithd-v2.7.4-firmware and put it into folder “build”. Otherwise the command would report an error.



By comparing the compiled firmware and the exported firmware, we can find the only difference is the first 256 signing information is different. Apart from that, all the remaining codes are all idential. That’s proved the two firmwares are totally the same.

3. Through Hash computing, verify the consistency between the firmware in hardware and the open-source firmware codes on GitHub.

3.1 Input the following command to compute the hash value of the exported firmware file.

shasum -a 256 ./build/bithd-$TAG-firmware.bin


3.2 Compare the hash value with the firmware codes on GitHub.



GitHud Address：https://github.com/bithd/bithd-mcu/releases

We can find the two hash values are identical. That demonstrates that the two firmware are exactly the same.

Find us on:

👉Twitter 👉 Telegram 👉Facebook 👉 Telegram HK 👉 News

"Don't Trust. Verify."

#BitHD is 100% open sourced. How to Verify BitHD Wallet Firmware Source Code???

Here is the tutorial: https://bitcointalk.org/index.php?topic=5235828.new#new

Now, based on the prepared firmware image, anyone can build the same signed image by signatures uploaded in code repository on https://github.com/bithd/bithd-mcu/blob/master/README.md

"Don't Trust. Verify."

#BitHD is 100% open sourced. How to Verify BitHD Wallet Firmware Source Code???

Here is the tutorial: https://bitcointalk.org/index.php?topic=5235828.new#new

Now, based on the prepared firmware image, anyone can build the same signed image by signatures uploaded in code repository on https://github.com/bithd/bithd-mcu/blob/master/README.md

BitHD Multisig function now support all the stable coins

USDT/USDC/PAX/HUSD/GUSD/TUSD/BUSD/USDK

BitHD Multisig function now support all the stable coins

USDT/USDC/PAX/HUSD/GUSD/TUSD/BUSD/USDK

Bitpie now support USDT-Tron But/Sell function

We are glad to announce that user can Buy/Sell USDT TRON in Bitpie wallet. USDT TRON has a much higher transaction speed and less fee cost. It is a good choice when you want to save money on transactions.

For many of the users who need to transfer their USDT/PAX/TUSD/USDC /BAT/DAI and any other ERC20 tokens to a group of people, such as your team members or employees or air drop etc, it is quite inconvenient. They usually have to copy each address one after another, and send to all the addresses one by one.

Today, I will introduce an easy way to solve the problem.
Step 1, Open the Bitpie Wallet and switch to ETH System, you can find the Series Transaction in the middle of the page.


Step 2, Click the ‘+’ button then choose ‘Get from Clipboard’


Step 3, Sort out the target addresses and paste to the Clipboard


Step 4, Click to send and finish the transaction.


See, it is quite easy to use and very efficient. With the help of Bitpie Series Transaction, you can save your time and set yourself free.

Attention: When you sort out the addresses, please follow the required format: Address,Amount

What is Free-gas-fee Token Sending?
Most of the popular tokens in the market are running on the Ethereum network (ERC20 protocol). Ethereum has a special feature: sending token needs ETH as gas fee.
Consequently, this special (but not so friendly) feature brings some difficulties for ERC20 token holders, especially green hands. To complete a transfer, one must learn what’s the usage of “gas fee”, how to own some ETH and how to set the gas fee while launching a sending. Honestly speaking, that’s tricky and time-consuming. Maybe you have the same annoying experience when you first enter into Ethereum world or as a project founder, get your community fans and investors on board.


Good news!
Now in Bitpie Wallet, any ERC20 Token can be transferred without ETH as gas fee. The sending will only consume the TOKEN as gas fee.
Bitpie Wallet now has made it real that you are free to send erc20 tokens with no ETH in your wallet as gas fee! It’s another technical breakthrough made by Bitpie Team!

2. Who are using this Free-gas-fee Token Sending service now?
Currently, many stable coins like USDT, PAX, USDC, TUSD, USDX, etc. can be sent without ETH as gas fee. This function has greatly reduced the threshold of users and the user numbers of these stable coin projects are also increasing very fast.


3. As a project founder, how can YOU make it happen on your token?
At present, except for the above-mentioned projects, the Free-gas-fee Sending function of other projects are off by default. This function can be turned on after the project team send us an application.

From now on, Bitpie officially opened the application channel of Free-gas-fee Sending.
To apply for this service, please fill in the following information and send it to support@bitpie.com

TOKEN Name:
TOKEN Icon (Png file):
Contract address:
Current price: 1ETH =? TOKEN
Listed exchange:
Contact: (Telegram / Phone)
All messages will be responded.

4. As a project founder, how do you pay for this service?
The standard charge for activating this feature is 50 ETH.
HOWEVER, if you apply now, the first 100 successful projects will get FREE activation rights. Details of the activation will be notified after the application.
Bitpie’s ETH-related Exclusive Features:

Generating 1000 ETH and TOKEN addresses;
Batch Sender (Series transaction) of ETH and TOKEN;
ETH gas fee GAS STATION function;
ERC20 TOKEN sending without ETH as gas fee;
BitHD Hardware Wallet supports multi-signature of ETH and ERC20 TOKENs

New Update!

You are now free to send #erc20 tokens with no ETH in your wallet as gas fee!

We welcome all projects founders applying for this user-firendly service in our wallet! check the article below:

https://medium.com/bitpie/how-to-make-your-erc20-token-be-sent-with-free-gas-fee-4c611b23a5a5

Use Bitpie Official channel verify function to prevent cheating.
https://www.youtube.com/watch?v=KFwWN_IJRuA

Crypto currency`s loan market is quite useful to users. People can borrow USDT to invest on other new blockchain start-ups to gain profits without losing their BTC if they can payback the margin.

Now, Bitpie Wallet has supported BTC, USDT borrow and lend function. And here is the instruction of how to use.

Before we start, you should download the newest Bitpie Wallet (bitpie.com) and install it on your phone.

Borrow USDT from the Loan Market

Step 1, find an order you need or create your own order.
When we enter the Loan Page, we can see different orders in the surface. You can view and choose an order that you need or you can Click the ‘Create AD’ button to customize your own order.


You can set the loan period, margin ratio and daily interest ratio by your own, to customize the perfect borrowing order.

Step 2, Find your ADs, Orders and reminding messages
After some one take your order, you can find it and check out the details in ADs, Orders and Message.


Step 3, deposit BTC into the Pie Bank to complete the order.
You can find Pie Bank inside ‘ More ’ and click the ‘ deposit ’ button. Once you have BTC in your Pie Bank, the system will calculate how much BTC you should pledge (Calculation method can be found in the ‘Related Agreements’) and deduct from your Pie Bank account. If you don`t have enough BTC in your Pie Bank account, the system will inform you with a warning message.
https://i.imgur.com/tWMIEm1.jpg

Once your order been taken and the system deduct your margin, the USDT will send to your Pie Bank USDT account, then you can withdraw to your address.


Lend USDT to others
The lending process is similar to borrowing, so I made it simplify .
Step 1, create an order for lending out USDT.


Step 2, check out your order and start getting interest


Step 3, Get the margin once the borrower fail to call margin and order been offset.


Most of the time, the borrower will pay back the principle and interest. But in case the BTC price drop sharply, and the borrower fail to call margin. The system will offset the order and give the BTC to the lender as compensate.

Bitpie now support Algorand ASA token

World`s first LTC Multisig Wallet.