Search content
Sort by
Showing 20 of 398 results by dragos_bdi
0.30.19.10 - MANDATORY UPDATE !!!!
* Fix "basenode start-many" !
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.10.7z
Those who want to maintain from a single wallet all hosted BN's could do now using basenode.conf, who must be created in the same folder as bitcredit.conf
The basenode.conf file structure is:
BN01 11.22.33.44:5555 5HqVL3Eez2T1SaWRNEa27fP9szp9okbfWZThjTmLRFxZHmraHCD 385bdd6134862ca04382f2f72093f7e8433497050e6e781dc554090df0bec3ba 0
BN02 11.22.33.44:6666 5Kf41p6JUMy3U8BpNEzeGic6N2PAczqz4EhFDjEsa3Mhc6k5nZN 3db50ed17601733994baaf20c817f92005ff1b959eef44cad75e0c828cc69324 1
The is generated by command "basenode genkey".
The and are found using "basenode outputs" command, that gives you the following example output:
{
"385bdd6134862ca04382f2f72093f7e8433497050e6e781dc554090df0bec3ba" : "0",
"3db50ed17601733994baaf20c817f92005ff1b959eef44cad75e0c828cc69324" : "1",
}
After you create this file, you can start all basenodes, issuing "basenode start-many".
* Fix "basenode start-many" !
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.10.7z
Those who want to maintain from a single wallet all hosted BN's could do now using basenode.conf, who must be created in the same folder as bitcredit.conf
The basenode.conf file structure is:
BN01 11.22.33.44:5555 5HqVL3Eez2T1SaWRNEa27fP9szp9okbfWZThjTmLRFxZHmraHCD 385bdd6134862ca04382f2f72093f7e8433497050e6e781dc554090df0bec3ba 0
BN02 11.22.33.44:6666 5Kf41p6JUMy3U8BpNEzeGic6N2PAczqz4EhFDjEsa3Mhc6k5nZN 3db50ed17601733994baaf20c817f92005ff1b959eef44cad75e0c828cc69324 1
The is generated by command "basenode genkey".
The and are found using "basenode outputs" command, that gives you the following example output:
{
"385bdd6134862ca04382f2f72093f7e8433497050e6e781dc554090df0bec3ba" : "0",
"3db50ed17601733994baaf20c817f92005ff1b959eef44cad75e0c828cc69324" : "1",
}
After you create this file, you can start all basenodes, issuing "basenode start-many".
0.30.19.9.4 - Fixes build
* Fix Bids not being payout !
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.9.4.7z
* Fix Bids not being payout !
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.9.4.7z
0.30.19.9.3 - Fixes build
* Fix SQL Demo message.
* Fix wallet stuck not receiving blocks after a crush. The only fix was bootstrapping.
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.9.3.7z
Please use reconsiderblock in case of the block is marked invalid.
1. Open console.
2 getblockhash
3 reconsiderblock
* Fix SQL Demo message.
* Fix wallet stuck not receiving blocks after a crush. The only fix was bootstrapping.
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.9.3.7z
Please use reconsiderblock in case of the block is marked invalid.
1. Open console.
2 getblockhash
3 reconsiderblock
Bootstrap @321605: https://mega.nz/#!CtczEASL!NAaHCVYPVGneACHvuZyO1wT1uv9B-vzwP8BiN7Jqm7Y
The bootstrap link on mega doesn't work for me, and I'm stuck on block 321399 without it. Thanks!
You need to update the binaries too !!!
Any old wallet will not accept blocks after 321399.
0.30.19.9 Mandatory Update
* Removed 40block rule
* Removed 50k check for miners
* New Payouts:
1BCR - Miner (we do not encourage users to mine with any GPU - the maximum you could obtain per day will be 200-300 BCR, but use wallet internal miner "setgenerate true )
4.5BCR - BANK
4.5BCR - RESERVE
18BCR - BN's (if no BN are online, BANK receive +18BCR)
0.4BCR * 5 = 2 BCR - Ratings Votes System
20BCR - Bidders (if there are no Bidders, BANK receive +20BCR)
Blockchain Explorer: http://www.bitcredit.work:3001/
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.9.2.7z (because I did not succeed in compiling with SQlite support, there will be an error at start and ID Browser will not work. It's safe to pass this error!!!)
Bootstrap @321605: https://mega.nz/#!CtczEASL!NAaHCVYPVGneACHvuZyO1wT1uv9B-vzwP8BiN7Jqm7Y
* Removed 40block rule
* Removed 50k check for miners
* New Payouts:
1BCR - Miner (we do not encourage users to mine with any GPU - the maximum you could obtain per day will be 200-300 BCR, but use wallet internal miner "setgenerate true )
4.5BCR - BANK
4.5BCR - RESERVE
18BCR - BN's (if no BN are online, BANK receive +18BCR)
0.4BCR * 5 = 2 BCR - Ratings Votes System
20BCR - Bidders (if there are no Bidders, BANK receive +20BCR)
Blockchain Explorer: http://www.bitcredit.work:3001/
Linux users: compile from git: https://github.com/bitcreditscc/bitcredit.git
Windows 64bit Users: http://www.bitcredit.work/downloads/win64-0.30.19.9.2.7z (because I did not succeed in compiling with SQlite support, there will be an error at start and ID Browser will not work. It's safe to pass this error!!!)
Bootstrap @321605: https://mega.nz/#!CtczEASL!NAaHCVYPVGneACHvuZyO1wT1uv9B-vzwP8BiN7Jqm7Y
how do we bid on the chain
From the HowTO written by jasemoney-thesherpa:
How to Bid
To bid you must send Bitcoins from a Bitcoin address whose private key you control. Do not send from an exchange. It is recommended to use coin control so you know which address you are sending from and can dump the right private keys to transfer over to Bitcredit-QT. If you do not use coin control check a Bitcoin explorer for your transaction and dump private keys for the address(s) used as inputs for your transaction.
1) Inside the Block Auction page of Bitcredit-QT you can see when the next bids cycle will begin by updating the data. Remember the bids cycle starts fresh at 00:00GMT so it is recommended to bid as close to this time as possible to get as close to a full 24 hours of payouts as possible.
2) Send some Bitcoin to the bid address. Currently both Bitcoin Core and Electrum private keys work but please test with small amounts, the minimum is 0.001BTC for bids.
3) Double check your transaction and dump the private key of your sending address
a. in bitcoin core console unlock your wallet: "walletpassphrase 300"
b. -then "dumpprivkey " copy this key
4) In your Bitcredit-QT import the private key of the BTC address you bid from.
- -in the Bitcredit-QT console unlock your wallet: "walletpassphrase 300"
- then "importprivkey
5) Wait until the next bid assessment block passes and you will begin receiving your share of the daily bid's BCR coins
Tips:
-Your bitcoin client will send your Bitcoin change if there is any to a new different address, if you bid again you will have to find the new address your client sent from and import that private key into Bitcredit-QT. This can be avoided with coin control to send change to a specific address (input here same as spending address.) Generally this is not a Bitcoin wallet best practice but does simplify the BCR bid process.
- I usually put in "bid"+"date" so it looks like this "importprivkey bid121015" in this way I can use coin control in Bitcredit-QT and see the full payout for my bid on December 10th.
There was some multiple forks today. Please use the bootstrap to recover.
A more updated bootstrap. http://www.bitcredit.work/downloads/bootstrap.tar.bz2
Seems to have done the trick, wallet has been updating fine AFAICT for a couple hours after using that bootstrap
yeeeeyHere it is a bootstrap till block 309392. https://mega.nz/#!uwk3RQ5D!AWRuqJScrefXI-bB8uoL0aNE3CmxUl185JIHwFTbNyQ
To speed up, you can use this.
To speed up, you can use this.
Tried the bootstrap from git (https://github.com/bitcreditscc/bootstrap), which got me to height 299611, got 4 connections and new blocks slowly coming in (mega links are not very practical on linux servers... though the bootstrap git is getting huge)
edit: no luck, daemon got stuck at 304039
edit 2: downloaded the mega file, but it's not a bootstrap, but a full download (ie. it will not be verified for correctness by the daemon), PM'ed to bitcreditscc for confirmation it's valid
If blockchain will stuck you could also use "reconsiderblock blockhash" so for block 304039 it would be : "reconsiderblock 0003e19a92200c348b3fe4e075d14c26b15100af1ba737f405517e5f65e6e8a9" if you are using latest client then it should start further, if older - you got to stop your client and start again after that.
hmm reconsider and restarting was not enough to unstuck the daemon, it is still stuck and debug log says
Code:
2016-02-04 20:15:46 InvalidChainFound: invalid block=00003c42eeb2f60dcf787726ce4e5bc5b8adf40f655297bd9d0378d8c1201863 height=309395 log2_work=35.952097 date=2016-02-04 15:10:48
2016-02-04 20:15:46 InvalidChainFound: current best=001014e824b8baf8c161e8bf2a950178c98a8a062df52e0a44794697cf355005 height=309394 log2_work=35.952097 date=2016-02-04 15:06:27
2016-02-04 20:15:46 InvalidChainFound: current best=001014e824b8baf8c161e8bf2a950178c98a8a062df52e0a44794697cf355005 height=309394 log2_work=35.952097 date=2016-02-04 15:06:27
Yeah, sometimes got to use it few times "reconsiderblock 001014e824b8baf8c161e8bf2a950178c98a8a062df52e0a44794697cf355005" , maybe there was some problem with these blocks, fork or whatever ...
still not working,,, any other ideas?
A more updated bootstrap. http://www.bitcredit.work/downloads/bootstrap.tar.bz2
Here it is a bootstrap till block 309392. https://mega.nz/#!uwk3RQ5D!AWRuqJScrefXI-bB8uoL0aNE3CmxUl185JIHwFTbNyQ
To speed up, you can use this.
To speed up, you can use this.
Tried the bootstrap from git (https://github.com/bitcreditscc/bootstrap), which got me to height 299611, got 4 connections and new blocks slowly coming in (mega links are not very practical on linux servers... though the bootstrap git is getting huge)
edit: no luck, daemon got stuck at 304039
edit 2: downloaded the mega file, but it's not a bootstrap, but a full download (ie. it will not be verified for correctness by the daemon), PM'ed to bitcreditscc for confirmation it's valid
you must delete folders "blocks", "chainstate", "ratings" and if it is "database", also "peers.dat". Put the 3 folders from archive and reopen the wallet.
Was about to ask the same question, it has been down for 3 days now.
https://chainz.cryptoid.info/bcr/
https://chainz.cryptoid.info/bcr/
Daemon is up and responding but not seeing any blocks, what should be done? Is a full resync required?
debug.log shows a lot of lines like
Code:
2016-02-04 14:26:26 dseep - Asking source node for missing entry CTxIn(COutPoint(f6264d426f, 1), scriptSig=)
2016-02-04 14:26:27 dseep - Asking source node for missing entry CTxIn(COutPoint(5b00c67ece, 1), scriptSig=)
2016-02-04 14:26:28 dsee - Got mismatched pubkey and vin
2016-02-04 14:26:28 Misbehaving: 94.42.21.19:8090 (1 -> 101) BAN THRESHOLD EXCEEDED
2016-02-04 14:26:49 connect() to 41.191.238.189:8877 failed after select(): Connection refused (111)
2016-02-04 14:27:57 connection from 173.193.56.186:57480 dropped (banned)
2016-02-04 14:28:51 connect() to 41.191.238.189:8877 failed after select(): Connection refused (111)
2016-02-04 14:30:53 connect() to 41.191.238.189:8877 failed after select(): Connection refused (111)
2016-02-04 14:30:55 connection from 173.193.56.186:57860 dropped (banned)
2016-02-04 14:31:09 connect() to 79.188.66.194:8877 failed after select(): No route to host (113)
2016-02-04 14:26:27 dseep - Asking source node for missing entry CTxIn(COutPoint(5b00c67ece, 1), scriptSig=)
2016-02-04 14:26:28 dsee - Got mismatched pubkey and vin
2016-02-04 14:26:28 Misbehaving: 94.42.21.19:8090 (1 -> 101) BAN THRESHOLD EXCEEDED
2016-02-04 14:26:49 connect() to 41.191.238.189:8877 failed after select(): Connection refused (111)
2016-02-04 14:27:57 connection from 173.193.56.186:57480 dropped (banned)
2016-02-04 14:28:51 connect() to 41.191.238.189:8877 failed after select(): Connection refused (111)
2016-02-04 14:30:53 connect() to 41.191.238.189:8877 failed after select(): Connection refused (111)
2016-02-04 14:30:55 connection from 173.193.56.186:57860 dropped (banned)
2016-02-04 14:31:09 connect() to 79.188.66.194:8877 failed after select(): No route to host (113)
Your daemon has been banned because was left behind or it's on wrong chain.
You can do a full sync, but will take a day.
Here it is a bootstrap till block 309392. https://mega.nz/#!uwk3RQ5D!AWRuqJScrefXI-bB8uoL0aNE3CmxUl185JIHwFTbNyQ
To speed up, you can use this.
Aha. Thanks.
Two more questions.
1. For redeem, amount is coming in small portions or big?
2. May i bid everytime from one BTC address or everytime i need to change it (including priv key)?
Two more questions.
1. For redeem, amount is coming in small portions or big?
2. May i bid everytime from one BTC address or everytime i need to change it (including priv key)?
1. Small
2. Preferably from one address. Even that you do this, the wallet could send from other that you know. Everytime when you make a payment, the bitcoin wallet creates a new address. To be sure, check the incoming address of the payment in transactions (https://btc.blockr.io/address/info/1BCRbid2i3wbgqrKtgLGem6ZchcfYbnhNu) and if it's not that you do know, do a "dumpprivkey address" on bitcoin wallet and then import the privkey in bitcredit wallet.
In this case, seems ok.
Just to point out. On one address with more than 50000, you can mine once in 40 blocks. That's why it stops after he found one.
You must get more nodes connected to you wallet:
addnode 82.211.1.181 add
addnode 91.230.123.5 add
addnode 91.230.123.11 add
addnode 91.230.123.81 ... till 88 add
addnode 91.230.123.131 ... till 140 add
enjoy !
EDIT!. The wallet freeze from the fact that "debug.log" is spammed with messages, when you left out with addresses that could mine till he found one valid. Check the debug.log
Just to point out. On one address with more than 50000, you can mine once in 40 blocks. That's why it stops after he found one.
You must get more nodes connected to you wallet:
addnode 82.211.1.181 add
addnode 91.230.123.5 add
addnode 91.230.123.11 add
addnode 91.230.123.81 ... till 88 add
addnode 91.230.123.131 ... till 140 add
enjoy !
EDIT!. The wallet freeze from the fact that "debug.log" is spammed with messages, when you left out with addresses that could mine till he found one valid. Check the debug.log
Till point 3, that seems ok, there are point 1 and 2....
1. wallet is well synced, but during mining there is stop for a few blocks in syncing, and than again wallet continue to sync
2. Yes, i have address with 50000+ blocks. This address in the .dat file in config
If you see in the miner i have like two blocks found in a few min, but one of them coming to my wallet and than gone, but the second stay
1. Version of the wallet ?
2. 50000+ blocks ?!?! probably BCR !, adress is miningkeys.dat, or in what config ?!
3. How many connections have in your wallet ? (getconnectioncount)
4. Port is default (8877) ? It is open in your firewall ?
Everythingis set for mining because some amount is coming to my wallet during mining but many mined bcr are fake as well. Showing up to mu wallet and after sometime gone by it self
Are you sure that everything is setup ok ?
1. Check if your wallet is synced. Open the console and type "getblockcount". Check against > http://www.bitcredit.work:3001/
2. In console, type "listaddressgroupings". In all addresses that you see is there anyone with +50000 BCR ? Is that (those) address (addresses) in %appdata%\Bitcredit\miningkeys.dat ?
3. Are you sure that pts-getwork is properly configured ?
For every address with +50000 BCR, you can mine only one block in a 40 block interval!!!
Please post every piece of information/config here so the community can help !!!
I wonder how long it will take for the count to breach 200
There are 5 wallets on bittrex with more than 200k. 31 Nodes.yeah, but those guys likely won't do it, they have been holding them in the exchange for a very long time.
Who knows, maybe they will come around, and rent some hosting nodes
I wonder how long it will take for the count to breach 200
There are 5 wallets on bittrex with more than 200k. 31 Nodes.