Search content
Sort by
Showing 20 of 140 results by happy_merchant
Is this for real or what? and why hashes is so small? i mean with a 24 cpu i get just ~ 7000 hps
I disabled the network hashrate field on the block explorer because it's not accurately reporting the network hashrate, so it doesn't really offer useful information on its own and would just confuse people to see a massive number there. The difficulty is being shown with an incorrect decimal place due to a bug in the value returned by biblepayd and I haven't had a chance to patch the Iquidus source yet as a temporary fix.
You can just use the getmininginfo command if you want to see those values.
-edit-
Difficulty field should be reporting correctly now.
Hmm, two of my nodes went down at the same time. Other nodes were unaffected.
I was able to just restart biblepayd with no apparent issues and they're fully synced with the network again.
Code:
2017-09-13 22:40:50 ProcessNewBlock : ACCEPTED
2017-09-13 22:40:50 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7491.000000 pindexPrev 64$2017-09-13 22:40:50 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3269787)*** Failed to read$2017-09-13 22:40:50 Error: Error: A fatal internal error occurred, see debug.log for details
2017-09-13 22:40:50 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-09-13 22:40:50 tor: Thread interrupt
2017-09-13 22:40:50 msghand thread interrupt
2017-09-13 22:40:50 torcontrol thread exit
2017-09-13 22:40:50 scheduler thread interrupt
2017-09-13 22:40:50 addcon thread interrupt
2017-09-13 22:40:50 opencon thread interrupt
2017-09-13 22:40:50 mnbcon thread interrupt
2017-09-13 22:40:50 net thread interrupt
2017-09-13 22:40:50 PrepareShutdown: In progress...
2017-09-13 22:40:50 StopNode()
2017-09-13 22:40:50 Verifying mncache.dat format...
2017-09-13 22:40:50 Loaded info from mncache.dat 0ms
2017-09-13 22:40:50 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list:$
2017-09-13 22:40:50 Writting info to mncache.dat...
2017-09-13 22:40:50 Written info to mncache.dat 1ms
2017-09-13 22:40:50 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list:$2017-09-13 22:40:50 mncache.dat dump finished 1ms
2017-09-13 22:40:50 Verifying mnpayments.dat format...
2017-09-13 22:40:50 Loaded info from mnpayments.dat 0ms
2017-09-13 22:40:50 Votes: 0, Blocks: 0
2017-09-13 22:40:50 Writting info to mnpayments.dat...
2017-09-13 22:40:50 Written info to mnpayments.dat 1ms
2017-09-13 22:40:50 Votes: 0, Blocks: 0
2017-09-13 22:40:50 mnpayments.dat dump finished 1ms
2017-09-13 22:40:50 Verifying governance.dat format...
2017-09-13 22:40:50 Loaded info from governance.dat 0ms
2017-09-13 22:40:50 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-13 22:40:50 Writting info to governance.dat...
2017-09-13 22:40:50 Written info to governance.dat 2ms
2017-09-13 22:40:50 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-13 22:40:50 governance.dat dump finished 3ms
2017-09-13 22:40:50 Verifying netfulfilled.dat format...
2017-09-13 22:40:50 Loaded info from netfulfilled.dat 0ms
2017-09-13 22:40:50 Nodes with fulfilled requests: 0
2017-09-13 22:40:50 Writting info to netfulfilled.dat...
2017-09-13 22:40:50 Written info to netfulfilled.dat 1ms
2017-09-13 22:40:50 Nodes with fulfilled requests: 0
2017-09-13 22:40:50 netfulfilled.dat dump finished 1ms
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50 Shutdown: done
2017-09-13 22:45:05
2017-09-13 22:40:50 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7491.000000 pindexPrev 64$2017-09-13 22:40:50 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3269787)*** Failed to read$2017-09-13 22:40:50 Error: Error: A fatal internal error occurred, see debug.log for details
2017-09-13 22:40:50 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-09-13 22:40:50 tor: Thread interrupt
2017-09-13 22:40:50 msghand thread interrupt
2017-09-13 22:40:50 torcontrol thread exit
2017-09-13 22:40:50 scheduler thread interrupt
2017-09-13 22:40:50 addcon thread interrupt
2017-09-13 22:40:50 opencon thread interrupt
2017-09-13 22:40:50 mnbcon thread interrupt
2017-09-13 22:40:50 net thread interrupt
2017-09-13 22:40:50 PrepareShutdown: In progress...
2017-09-13 22:40:50 StopNode()
2017-09-13 22:40:50 Verifying mncache.dat format...
2017-09-13 22:40:50 Loaded info from mncache.dat 0ms
2017-09-13 22:40:50 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list:$
2017-09-13 22:40:50 Writting info to mncache.dat...
2017-09-13 22:40:50 Written info to mncache.dat 1ms
2017-09-13 22:40:50 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list:$2017-09-13 22:40:50 mncache.dat dump finished 1ms
2017-09-13 22:40:50 Verifying mnpayments.dat format...
2017-09-13 22:40:50 Loaded info from mnpayments.dat 0ms
2017-09-13 22:40:50 Votes: 0, Blocks: 0
2017-09-13 22:40:50 Writting info to mnpayments.dat...
2017-09-13 22:40:50 Written info to mnpayments.dat 1ms
2017-09-13 22:40:50 Votes: 0, Blocks: 0
2017-09-13 22:40:50 mnpayments.dat dump finished 1ms
2017-09-13 22:40:50 Verifying governance.dat format...
2017-09-13 22:40:50 Loaded info from governance.dat 0ms
2017-09-13 22:40:50 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-13 22:40:50 Writting info to governance.dat...
2017-09-13 22:40:50 Written info to governance.dat 2ms
2017-09-13 22:40:50 Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-13 22:40:50 governance.dat dump finished 3ms
2017-09-13 22:40:50 Verifying netfulfilled.dat format...
2017-09-13 22:40:50 Loaded info from netfulfilled.dat 0ms
2017-09-13 22:40:50 Nodes with fulfilled requests: 0
2017-09-13 22:40:50 Writting info to netfulfilled.dat...
2017-09-13 22:40:50 Written info to netfulfilled.dat 1ms
2017-09-13 22:40:50 Nodes with fulfilled requests: 0
2017-09-13 22:40:50 netfulfilled.dat dump finished 1ms
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50 Shutdown: done
2017-09-13 22:45:05
I was able to just restart biblepayd with no apparent issues and they're fully synced with the network again.
Are we on the same chain now:
16:47:30

getblockhash 7480
16:47:30

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2
Two of mine agree now, the third is syncing.
16:47:30

getblockhash 7480
16:47:30

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2
Two of mine agree now, the third is syncing.
That's what all my nodes are reporting.
Yeah, could be that node.biblepay.org is running the old version and the new version requires a protocol upgrade.
Let me upgrade that now, then the pool. Give me about 7 mins.
Let me upgrade that now, then the pool. Give me about 7 mins.
Everything seems to be syncing now and it looks like blocks are being mined. Updating the block explorer now.
I'm really not sure if the block explorer is correct or not. It's running 1.0.3.1 still until the mandatory updates get ironed out. I'm still having trouble getting 1.0.3.4 to sync properly on any of my rigs, so I don't have anything to cross-reference it with.
I have some experience with this. The only thing you need to be careful with is not to "run out of keys". The wallet file has 1000 pre-generated private keys with biblepay that are used for every new address you generate. Once you used all the keys, it automatically starts generating new keys for the new addresses.
So if you start mining on a lot of PCs and they suddenly run out keys and start generating new ones, the wallet.dat you kept may not contain these new keys!
The way to mitigate this could be to start with a wallet.dat with a bigger pool of pre-generated keys (can do that with biblepay-cli keypoolrefill x where x is the amount of pre-generated keys you want. You need to be careful as you wallet.dat file can become quite big!)
So if you start mining on a lot of PCs and they suddenly run out keys and start generating new ones, the wallet.dat you kept may not contain these new keys!
The way to mitigate this could be to start with a wallet.dat with a bigger pool of pre-generated keys (can do that with biblepay-cli keypoolrefill x where x is the amount of pre-generated keys you want. You need to be careful as you wallet.dat file can become quite big!)
Ah, I had never really considered that before since I've never come close to using up the keypools in any of my crypto wallets. I should probably go through and make sure my more frequently used wallets have plenty of reserved keys left.
Just noticed the block explorer is reporting a really high difficulty, too.
getmininginfo -> "difficulty": 419.2772529614635,
getdifficulty -> 4192.772529614635
Seems to be a decimal point out of place. The block explorer uses getdifficulty to retrieve the value. I take it the lower value is the correct one?
getmininginfo -> "difficulty": 419.2772529614635,
getdifficulty -> 4192.772529614635
Seems to be a decimal point out of place. The block explorer uses getdifficulty to retrieve the value. I take it the lower value is the correct one?
Yeah, I havent actually done that myself yet, but I have 'one' piece of info on that. Blue said he copied his one wallet.dat file over to 10 machines, and now on his desktop he receives notifications when any machine mines a block (IE the txlist updates). So he has one consolidated wallet.
I was going to add: In POW, since coins can be received in a locked wallet, you can encrypt and lock your wallet and still receive rewards from any POW device out there mining into that single wallet.
I was going to add: In POW, since coins can be received in a locked wallet, you can encrypt and lock your wallet and still receive rewards from any POW device out there mining into that single wallet.
Definitely, wallets should always be encrypted, especially if you're going to be distributing it across multiple machines. You should also keep an encrypted backup copy in cloud storage or at least a USB or something. I'm sure there's even tools that would let you make a paper BBP wallet. As long as it's encrypted nobody can do anything with the wallet file even if it's stolen or compromised, and it protects you from losing your wallet to a HDD failure or laptop theft or anything else that can happen if you only have a single copy.
guys: can i mining with 2 machines to 1 wallet? or every machine must have own wallet always?
There's a wallet.dat file in your BiblepayCore directory (usually ~/.biblepaycore on linux or /AppData/Roaming/BiblepayCore on windows). Just copy whatever wallet.dat file you want to use from one machine and place it in the BiblepayCore directory on the other machine.
Block explorer is back on the main fork again.
I've also gone ahead and hid the network hashrate reporting for now so as to not cause confusion. The rpc getnetworkhashps method is giving a different value from the networkhashps from getmininginfo, and they're both reporting in the GH/s range which clearly isn't right, so I don't think they're really giving much useful info at present.
I've also gone ahead and hid the network hashrate reporting for now so as to not cause confusion. The rpc getnetworkhashps method is giving a different value from the networkhashps from getmininginfo, and they're both reporting in the GH/s range which clearly isn't right, so I don't think they're really giving much useful info at present.
What block are we currently on? I wasn't around yesterday so I just saw there was another mandatory update just now. The block explorer is still running 1.0.2.9 so it might need to be reindexed. Compiling 1.0.3.1 right now.
It's after block 7000! =) Anxiously waiting for an update. 
How much did the hashrate decrease for ya'll?
Mine is horrible...so horrible I am waiting for an update from the dev to see how things are going.
How much did the hashrate decrease for ya'll?
Mine is horrible...so horrible I am waiting for an update from the dev to see how things are going.
The algorithm changed so hashps was supposed to decrease. That affects all miners equally, so your contribution relative to the network is still the same.
It's interesting that the networkhashps skyrocketed, though. I wonder if it's approximating the network hashrate more accurately now? Still seems a little off. It's saying hetworkhashps=932333 and on this machine it's saying hashps=9088. If networkhashps is being reported in H, that seems a bit low. If it's being reported in KH, then it seems really high. It's still going up with every block so it might just need more blocks for an accurate approximation.
A very accurate equation to find the bottom of the barrel price is to figure the electric cost for 10,000 bbp per month and thats usually where the price will be on the exchange without forward growth. (IE the electric arb rate).
Since we are CPU mined, thats about $20 for 10,000 bbp.
It works because miners who pay $20 for something are reluctant to sell lower than this rate, therefore coins accumulate until the arb rate is at a minimum surpassed.
Since we are CPU mined, thats about $20 for 10,000 bbp.
It works because miners who pay $20 for something are reluctant to sell lower than this rate, therefore coins accumulate until the arb rate is at a minimum surpassed.
In the long run it should work out like that. That's the nice thing about PoW - there's a fiat cost associated with every coin that's mined which provides a degree of stability to its market value. Additionally, the more people that are actively mining, the higher that fiat cost per coin (coins are being generated at the same rate, but now there's more hashing power behind every coin representing a higher fiat cost going into each coin), so the higher their value.
Right now, there's a lot of people who mined a lot back when the difficulty was pretty low, though. If they think think they can increase their profits by investing that value elsewhere or by using it to margin trade, they'e going to be willing to dump at a lower value since they had negligible costs in the first place. I think we've already passed the "free coins" phase, though, so within a couple months anyone who was planning on dumping will probably have dumped.
im tested this on www.malwaretips.com tester machine for viruses and my zemana antilogger+malwarebyte 3.0+kaspersky+hitmanpro+NOD32+emsisoft+bitdefender all blocked 64Bit wallet= so no , thanks for shit SW 
https://github.com/biblepay/biblepay
You're free to run a diff between the Biblepay source and Dash from which it was forked and point out any malware insertions. Being cautious is fine, but there's no need for insults. You're not going to find many projects derived directly or indirectly from BTC that don't set off false positives in any number of malware detection programs for reasons stated above.
next ESET ENDPOINT virus too
Some antivirus are sensitive to anything that looks like a crypto miner since there's malware out there that install miners on users' PCs without their consent.
It's always a good practice to run anything crypto-related in a VM or a dedicated rig just to be safe, but at this point I think it's safe to say there's no malware in the Biblepay client. There's always a risk that any website could be compromised, so if you don't want to risk downloading the precompiled binaries you can always compile from source.
Im a little dissapointed on how many outgoing letters we have to our orphans. (We only had one person write one, and it doesnt even have enough upvotes to send it through the API).
Oh, I've been a little out of the loop lately, wasn't even aware that was added. I'll have to check it out.
What are the advantages by running an masternode/sanctuaries ?
What kind of cpu's/pc it is necessary for running one?
What kind of cpu's/pc it is necessary for running one?
I'm not sure what the devs have in mind, but it should be pretty similar to a Dash masternode which you can read about at https://www.dash.org/masternodes2/. Note that in Biblepay, masternodes will only receive 10% of the block rewards as opposed to Dash's 45% (if I'm reading the example in the original announcement correctly). I'm sure some of the other numbers will be tweaked as well since this is primarily a charity coin, but it should give you a general idea of what's involved.
And here I thought one of them is yours happy 
. By the way you and 616westwarmoth have been really helpful in this forum so just wanted to thank you both.
. By the way you and 616westwarmoth have been really helpful in this forum so just wanted to thank you both.Ha, I wish
I'm only sitting at like 1.1 million, and that's just because I got in early. My actual mining power is pretty low. Hopefully it'll be enough to start up a sanctuary, even if I have to buy a little more off the exchanges.It's a good project though so I'll be happy if it succeeds in any case.
I was doing a little research in the BBP Explorer and I'm somewhat worried by the current wealth distribution.
The top two addresses each hold nearly 10% of the supply (12,509,890 and 11,585,552)
http://biblepay.inspect.network/richlist
Based on the transaction amounts in those addresses I would assume both are big miners.
There isn't nearly enough liquidity on C-CEX to sustain large sells if either of those addresses decided to dump...
There also must be some serious equipment working for those addresses to have that many block rewards.
I'm a long-term holder so I'm not going to panic but I thought it should be mentioned here for your input.
The top two addresses each hold nearly 10% of the supply (12,509,890 and 11,585,552)
http://biblepay.inspect.network/richlist
Based on the transaction amounts in those addresses I would assume both are big miners.
There isn't nearly enough liquidity on C-CEX to sustain large sells if either of those addresses decided to dump...
There also must be some serious equipment working for those addresses to have that many block rewards.
I'm a long-term holder so I'm not going to panic but I thought it should be mentioned here for your input.
One of those I believe is the c-cex receiving address that the charity wallet gets dumped to every so often. You could pretty much just think of it as being c-cex, since it probably represents the majority of the BBP supply currently listed on (or just held at) c-cex. Trades on an exchange don't affect the distribution on the blockchain until funds are actually withdrawn.
The other is probably a mining operation. Not much you can do about that, happens with every coin. Even BTC and ETH have wallets out there with massive balances that could disrupt the market if dumped all at once. In any case, as more miners join the network, the proportion of the hash contributed by any single mining organization will be smaller relative to the network hash rate and the percentage of the total BBP supply held by any single miner or group will shrink (unless they invest a lot of money into additional hardware to keep up, which would also mean they'd be less likely to dump for a low price).