Hello, dear friends! In few hours we are going to release ours, written by us, block explorer. We tried our best to create really comfortable tool for analyze. It could not only display blocks, transactions and rich list. It allows you predict market cap changes taking into account lucky stake, take into account different price in different time and showing full quantity of sent money not only in BT, but also in BTC, USD and PLN (just kidding). We are creating statistic of price since coin was released, so you could track the whole history up to the first block. But this isn't all. Stay tuned and you will be surprised
We are working on this problem at the moment. For successful synchronization you have to follow the next steps: 1. Remove all files except wallet.dat at %AppData%\BitcoinT folder 2. Download blockchain at: https://mega.co.nz/#!hYszGZaK!eFPodQScoLaOeoh0shq386MuJU5ddme_drmbUxTE9kY 3. Unzip it to folder %AppData%\BitcoinT 4. Run the wallet
We are ready to make POD 5+ later, but we will not give real contact information. we want to save privacy. We don't know how companies, where we are working at the moment, will react on our project
But now i have this one: make: *** [build/key.o] Error 1
Did you sudo make install for libsecp256k1?
pls PM me output of ls -la /usr/local/lib/libsecp*
I also have problems compiling after installing secp256k1
Code:
src/key.cpp:29:25: error: use of undeclared identifier 'SECP256K1_START_SIGN' secp256k1_start(SECP256K1_START_SIGN); ^ src/key.cpp:32:9: error: use of undeclared identifier 'secp256k1_stop' secp256k1_stop(); ^ src/key.cpp:469:10: error: no matching function for call to 'secp256k1_ec_privkey_import' if (!secp256k1_ec_privkey_import((unsigned char*)begin(), &privkey[0], privkey.size()))
There was commit in project secp256k1 recently where were made changes, which arent considered in our coin yet, but doesnt affect on wallet/daemon functional
if you want to compile wallet/daemon, you have to make reverse commit to d5b53aa81816214aa7c9e1095ff6ee1d4c13f9d2 библиoтeки secp256k1: git clone https://github.com/bitcoin/secp256k1 cd ./secp256k1 git checkout d5b53aa81816214aa7c9e1095ff6ee1d4c13f9d2 ./autogen.sh ./configure make sudo make install and after all of this you're able to build wallet/daemon
If you have a certain amount of coins, you've got a chance to catch a block with higher reward. There are three levels of lucky blocks: 1st level: from 50 000 coins (max. 24 lucky blocks per day with a reward for 5000 coins) 2nd level: from 100 000 coins (max. 3 lucky blocks per day with a reward for 15000 coins) 3rd level: from 300 000 coins (max. 1 lucky blocks per day with a reward 60000 coins) Everyone has equal chance to win. You just need to have equal or more coins on your balance (with accordance to chosen level). For example, wallets with 50000 and 99000 coins have the same chances to win. Take into account that lucky stake sum should be sent to your address in one tx. So if u have 2 incoming transactions for instance 30k BT and 20k BT you need to send (30+20)k BT in one tx to one your address to participate in lottery. Lottery will be active during 30 days and will be deactivated at a certain block.
If you have a certain amount of coins, you've got a chance to catch a block with higher reward. There are three levels of lucky blocks: 1st level: from 50 000 coins (max. 24 lucky blocks per day with a reward for 5000 coins) 2nd level: from 100 000 coins (max. 3 lucky blocks per day with a reward for 15000 coins) 3rd level: from 300 000 coins (max. 1 lucky blocks per day with a reward 60000 coins) Everyone has equal chance to win. You just need to have equal or more coins on your balance (with accordance to chosen level). For example, wallets with 50000 and 99000 coins have the same chances to win. Take into account that lucky stake sum should be sent to your address in one tx. So if u have 2 incoming transactions for instance 30k BT and 20k BT you need to send (30+20)k BT in one tx to one your address to participate in lottery. Lottery will be active during 30 days and will be deactivated at a certain block.