Topic: BiblePay - New Coin Launch - Official Thread - page 93. (Read 119833 times)

There are REAL WORLD uses for this coin!  Those who are less fortunate than most are getting some well needed care.  Most coins do not even have a purpose....this coin may never be $100...but it is worth that much and more to those it helps!

1. After F7000, I noticed a lot of these message, what is this about?

2. And I have a machine in ubuntu stopped working after 7000, I restart it, error message said index database corrupted, I removed .biblepaycore and reload all database, but it stucked at 7022, same message as SquidConqueror did. Then I did a tricky solution which is to copy .biblepaycore from my other ubuntu machine, problem solved. But then my hashrate dropped from 400k to 40k, my other machine remain same hashrate as previous.

3. I restart wallet in my i7 windows machine, hashrate dropped from 160k to 5k, whereas my other windows machine remain same hashrate as previous (I did not restart the wallet). And yet, after restarting my i7 wallet, it is very laggy, some new calculation required more cpu power?

Thanks  

Not even a billion in circ, you want to see a coin with billions already, go to Linda.  Started about the same time and WAAYYYY ahead coin wise but not in the 1 satoshi range yet.  BBP probably never going to break out and be a $100 coin, but to think it'll drop below 1 sat is very pessimistic.

Ok, things are looking better than they appear behind the scenes... From the pool it appears that there is a huge disparity between the big dogs and the small miners, but this appears to be a farce... Im doing some more checking before I post an update as to why this is occurring.  It appears to be RAID related.

Also, the errors in the debug: I believe a workaround exists.  More checking required.

Ill be back in 15 minutes.

You are more than welcome.  I was hoping it would help...let me know if any other info on my end can assist.

Thanks, this looks severe, checking now,  from a high level, this might go away at block 7256, possibly, and possibly be minor, but let me do some in depth checking.

This could be why the hashing is slow also.

Pool is not completely fixed yet either.

Here is the end of my  "debug" file

2017-09-11 00:32:37 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3002649)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6959.000000 pindexPrev 00000111692e6cdff17ce09657e626d585934061ce86d3c2a916ffbebd0814fe
2017-09-11 00:32:37 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3040170)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6859.000000 pindexPrev 000000f38c22bcefbfbc614c84cdad58618b8c6ad0b318b651a1038ef2b2811c
2017-09-11 00:32:37 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3000615)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6986.000000 pindexPrev 000001365da91347db20cd1c3039b47a7ad69af56c889f75a81e8e86ff343602
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3051107)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6994.000000 pindexPrev 0000000119481d0bcea56b899146d2d329a4ce0e118c79d7c1c79599d539833a
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3053373)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6832.000000 pindexPrev 0000015063000b230df20aa6a4b7257a75408c5b7e27bf3a8d59cb16e7f0633a
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=2990354)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6920.000000 pindexPrev 00000043e2e9e7923a282ad18f069afc778c4b084e3fedcacc0e5e4718a4289d
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3020905)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6881.000000 pindexPrev 0000009fae6eb0daecfbfeb279bf1349d9f24f660e32dd3b5d114fd19ff4cb7b
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3007520)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6895.000000 pindexPrev 00000060d27f8e07271a833962d88cb529cb33a71818a72c65835937fe3c8da3
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3013257)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6945.000000 pindexPrev 0000022fd758669b7335130a22ba1cfba7b8cbf21774ef8d637d38069f8627f2
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3033150)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6861.000000 pindexPrev 00000038eb1ac7d34b9c6e15b6c82320cac7be9641df3b11f92c28b8e92b2732
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3001013)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6777.000000 pindexPrev 00000029d3af7701fbc99545d9c5a690ffb108be6b64dcabdde4e33908ae5e4e
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=2960466)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6965.000000 pindexPrev 0000036e34fb5536933fabe235968b40261baf8d91af432b5e60761d5ffef2da
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3041632)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6884.000000 pindexPrev 0000009dd3f9b134ff8244a2f3c3f93fd49fead18028e3a933302d60fa5354e6
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3008137)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6826.000000 pindexPrev 00000022024f700f4fe83a8426f8d2c24f7ca9e0cc473cc68eee2dc69e6ca055
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=2982319)ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 6934.000000 pindexPrev 00000051caa15dc6e469f3c0051e0801f37e298ff6d370dc6fc8fce7af214648
2017-09-11 00:32:38 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3026573)

I uninstalled...reinstalled and downloaded the whole chain again.  Same results.

Awesome!  Thank you for being on top of it.   I have the new wallet on both machines....let's hope my hashrate gets better...it just seems like a huge cut...good luck on the fixes!  =)

I am comparing before and after hashrate of other miners and it seems like mine has suffered a huge cut compared to others I have looked at...it even seem like some have hashrates close to the old one.

Yeah, the pool is going crazy on the back end.
It was pegged for a while, there are multiple things going on.  The biggest problem is the nodes who didnt upgrade are hitting it with invalid solutions that they think are valid because internally, the biblehash didnt contain the deterministic suffix so they keep resubmitting the hash, and the pool is getting pounded.

Im working on a patch right now to fix that.

Like happy said though, the lower hashrate is OK.

There is one other issue where the older clients will crash when the pool responds a certain way.  I guess that is a positive "feature" right now.

I believe this can be fixed within an hour though, because the pool does receive the clientversion handshake, so we can tailor the code to respond to this situation, thank God.

I knew this was going to happen...but I went from getting around 200,000 without pushing my 8350 too much....to under 4000...

My other machine was getting around 70,000...now it is getting 650

that is one heck of a difference...

right now   "networkhashps": 1039681.905668668,...still going up

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.

Patience, I am sure that there is A LOT on the backend to this switch.

SOO unstable.... 

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.

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.

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.

Yeah that is a good question, before making any assumptions, let me call compassion and ask them.
One thing I know about 2 year olds for example, is they are brought by their guardian to the local church or wherever the local compassion field office is for a weekly one hour meeting and if they cant write, the teacher talks to the child and writes the feelings down for that child (because I receive monthly letters from 1 year olds that says it was so), so I am assuming when a 1 year old receives a letter, the teacher reads it to the child in that same class.  But anyway, yeah I will ask compassion that.  Feel free to call the 1-800 number also if you want to get more on it for us , good question.

Idea is not bad but how much billions circulating now? I afraid that soon this coin will be priced at very low than 1 satoshi

Thank you for the response. You're right, I was looking at the old IP. Interesting about the report showing the last day of blocks solved by version.

Regarding the letters, what about the children who are only 1-2 years old? Maybe they can understand some simple words, but not where does the letter come from and what does it mean to get a sponsor. So in these cases should the writings be addressed to the parents instead?

There are no viruses, nor are there any virus alerts.

Feel free to scan our software on Virustotal, which supports over 50 virus scanners and gives a true reading.



-=-=-=-=-=-=-=-


I am going to recommend your account be banned if you continue posting FUD here.