BiblePay - New Coin Launch - Official Thread - page 152.

kamo13

newbie

Activity: 37

Merit: 0

Quote from: happy_merchant on July 26, 2017, 12:49:20 PM

Quote from: kamo13 on July 26, 2017, 12:45:22 PM

What do you mean? Block or reward? If it is blocks,then my wallet found about 100 blocks

I meant I haven't personally mined a block in that time. Got a few during the first couple days, though. Just bad luck. It'll all smooth out with enough time, or once BBP gets a mining pool.

I never had similar problems with 3 days ago created coins with only 400 blocks and low difficulty.That's all

Zellko

newbie

Activity: 23

Merit: 0

There is already a way to mine with GPU / pool ? Tongue

albusxx

copper member

Activity: 50

Merit: 0

You should make sure no more than 30 coins exist

happy_merchant

member

Activity: 70

Merit: 10

Quote from: kamo13 on July 26, 2017, 12:45:22 PM

What do you mean? Block or reward? If it is blocks,then my wallet found about 100 blocks

I meant I haven't personally mined a block in that time. Got a few during the first couple days, though. Just bad luck. It'll all smooth out with enough time, or once BBP gets a mining pool.

kamo13

newbie

Activity: 37

Merit: 0

Quote from: happy_merchant on July 26, 2017, 12:36:39 PM

Quote from: kamo13 on July 26, 2017, 12:19:34 PM

Two days running.Number of blocks increased from 326 to 427 and no transactions.getmininginfo:
  "blocks": 427,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.002369640862025556,
  "errors": "",
  "genproclimit": 25,
  "networkhashps": 1569.635801700892,
  "hashps": 5232.685032774519,
  "minerstarttime": 1501071883889,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true

What is wrong?

You're only providing 0.33% of the total network hashing power. The chance of finding a block solo at that rate is unfortunately pretty low at this point.

If it makes you feel any better, I'm mining at ~14x that amount haven't found a block in over 24 hours Grin

< I'm mining at ~14x that amount haven't found a block in over 24 hours > .What do you mean? Block or reward? If it is blocks,then my wallet found about 100 blocks

happy_merchant

member

Activity: 70

Merit: 10

Quote from: kamo13 on July 26, 2017, 12:19:34 PM

Two days running.Number of blocks increased from 326 to 427 and no transactions.getmininginfo:
  "blocks": 427,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.002369640862025556,
  "errors": "",
  "genproclimit": 25,
  "networkhashps": 1569.635801700892,
  "hashps": 5232.685032774519,
  "minerstarttime": 1501071883889,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true

What is wrong?

You're only providing 0.33% of the total network hashing power. The chance of finding a block solo at that rate is unfortunately pretty low at this point.

If it makes you feel any better, I'm mining at ~14x that amount haven't found a block in over 24 hours Grin

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: kamo13 on July 26, 2017, 12:19:34 PM

Quote from: jc12345 on July 26, 2017, 12:05:55 PM

Quote from: kamo13 on July 26, 2017, 10:58:42 AM

Hello everyone!!!! I have questions: How much to wait before receiving coins from mining? Is anybody got his coins? Thank's!!!

It can take half a day to a day for a block for an average CPU.

Two days running.Number of blocks increased from 326 to 427 and no transactions.getmininginfo:
  "blocks": 427,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.002369640862025556,
  "errors": "",
  "genproclimit": 25,
  "networkhashps": 1569.635801700892,
  "hashps": 5232.685032774519,
  "minerstarttime": 1501071883889,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true

What is wrong?

There are 2 important aspects:

1. What are the specs of your CPU? You need at least 8 cores i5/7 or AMD equivalent to stand a chance.
2. Download HWmonitor from CPUID and monitor the performance of your cores. You will see that from time to time the setgenerate crashes and your cores sit idle. If that happens restart your setgenerate. This happens at least every hour or two. Increase the thread count until all your cores are at 100%.

I would say that your CPU has been sitting idle for the last 2 days because you have probably been flying blind.

kamo13

newbie

Activity: 37

Merit: 0

Quote from: jc12345 on July 26, 2017, 12:05:55 PM

Quote from: kamo13 on July 26, 2017, 10:58:42 AM

Hello everyone!!!! I have questions: How much to wait before receiving coins from mining? Is anybody got his coins? Thank's!!!

It can take half a day to a day for a block for an average CPU.

Two days running.Number of blocks increased from 326 to 427 and no transactions.getmininginfo:
  "blocks": 427,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 0.002369640862025556,
  "errors": "",
  "genproclimit": 25,
  "networkhashps": 1569.635801700892,
  "hashps": 5232.685032774519,
  "minerstarttime": 1501071883889,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true

What is wrong?

jc12345

legendary

Activity: 1638

Merit: 1013

Quote from: kamo13 on July 26, 2017, 10:58:42 AM

Hello everyone!!!! I have questions: How much to wait before receiving coins from mining? Is anybody got his coins? Thank's!!!

It can take half a day to a day for a block for an average CPU.

kamo13

newbie

Activity: 37

Merit: 0

Hello everyone!!!! I have questions: How much to wait before receiving coins from mining? Is anybody got his coins? Thank's!!!

Voltaje

sr. member

Activity: 350

Merit: 250

PewPewGoesTheDuck

full member

Activity: 200

Merit: 101

Crashed again. Haven't had this issue with mining from other wallets. Is anyone having any luck while running windows? Wondering if the linux wallet is more stable. Below is my log file.

Code:

2017-07-26 14:40:03 UpdateTip: new best=00000a4adf7ba6f4950eb1e20d86799b199bf7920c030704622d23b641a51a50  height=410  log2_work=27.787221  tx=444  date=2017-07-26 14:40:00 progress=0.999992  cache=0.0MiB(10tx)
2017-07-26 14:40:03  TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); 

BiblepayMiner -- runtime error: CreateNewBlock: TestBlockValidity failed:  (code 0)
2017-07-26 14:40:03 ProcessNewBlock : ACCEPTED
2017-07-26 14:40:03 keypool return 83
2017-07-26 14:40:03 ERROR: CheckProofOfWork(): BibleHash does not meet POW level
2017-07-26 14:40:03 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=89458)

** ProcessGetData:Cannot load block from disk.

2017-07-26 14:40:03 

 ** Rebooting Wallet Now ** 

2017-07-26 14:40:03 mnbcon thread interrupt
2017-07-26 14:40:03 scheduler thread interrupt
2017-07-26 14:40:03 addcon thread interrupt
2017-07-26 14:40:03 opencon thread interrupt
2017-07-26 14:40:03 msghand thread interrupt
2017-07-26 14:40:03 net thread interrupt
2017-07-26 14:40:03 PrepareShutdown: In progress...
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 StopNode()
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 34
2017-07-26 14:40:03 keypool return 6
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 70
2017-07-26 14:40:03 keypool return 87
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 84
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 44
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 71
2017-07-26 14:40:03 keypool return 40
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 22
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 51
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 8
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 93
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 94
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 56
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 57
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 58
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 59
2017-07-26 14:40:03 keypool return 86
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 61
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 60
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 79
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 48
2017-07-26 14:40:03 keypool return 7
2017-07-26 14:40:03 keypool return 80
2017-07-26 14:40:03 keypool return 63
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 64
2017-07-26 14:40:03 keypool return 68
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 9
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 81
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 82
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 90
2017-07-26 14:40:03 keypool return 72
2017-07-26 14:40:03 keypool return 69
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 85
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 42
2017-07-26 14:40:03 keypool return 92
2017-07-26 14:40:03 keypool return 32
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 74
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 75
2017-07-26 14:40:03 keypool return 50
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 45
2017-07-26 14:40:03 keypool return 88
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 77
2017-07-26 14:40:03 keypool return 89
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 24
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 25
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 31
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 78
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 66
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 97
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 39
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 26
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 27
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 10
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 37
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 29
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 28
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 12
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 30
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 43
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 13
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 15
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 49
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 47
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 14
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 16
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 52
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 20
2017-07-26 14:40:03 keypool return 19
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 53
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 18
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 21
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 95
2017-07-26 14:40:03 keypool return 96
2017-07-26 14:40:03 keypool return 54
2017-07-26 14:40:03 keypool return 2
2017-07-26 14:40:03 keypool return 62
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 46
2017-07-26 14:40:03 keypool return 67
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 23
2017-07-26 14:40:03 keypool return 91
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 35
2017-07-26 14:40:03 keypool return 41
2017-07-26 14:40:03 keypool return 17
2017-07-26 14:40:03 keypool return 3
2017-07-26 14:40:03 keypool return 4
2017-07-26 14:40:03 keypool return 76
2017-07-26 14:40:03 keypool return 55
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 65
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 73
2017-07-26 14:40:03 Verifying mncache.dat format...
2017-07-26 14:40:03 Loaded info from mncache.dat  0ms
2017-07-26 14:40:03      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-07-26 14:40:03 Writting info to mncache.dat...
2017-07-26 14:40:03 Written info to mncache.dat  1ms
2017-07-26 14:40:03      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 mncache.dat dump finished  1ms
2017-07-26 14:40:03 keypool return 11
2017-07-26 14:40:03 Verifying mnpayments.dat format...
2017-07-26 14:40:03 Loaded info from mnpayments.dat  0ms
2017-07-26 14:40:03      Votes: 0, Blocks: 0
2017-07-26 14:40:03 Writting info to mnpayments.dat...
2017-07-26 14:40:03 Written info to mnpayments.dat  1ms
2017-07-26 14:40:03      Votes: 0, Blocks: 0
2017-07-26 14:40:03 mnpayments.dat dump finished  3ms
2017-07-26 14:40:03 Verifying governance.dat format...
2017-07-26 14:40:03 Loaded info from governance.dat  0ms
2017-07-26 14:40:03      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-07-26 14:40:03 Writting info to governance.dat...
2017-07-26 14:40:03 Written info to governance.dat  2ms
2017-07-26 14:40:03      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-07-26 14:40:03 governance.dat dump finished  2ms
2017-07-26 14:40:03 Verifying netfulfilled.dat format...
2017-07-26 14:40:03 Loaded info from netfulfilled.dat  0ms
2017-07-26 14:40:03      Nodes with fulfilled requests: 0
2017-07-26 14:40:03 Writting info to netfulfilled.dat...
2017-07-26 14:40:03 Written info to netfulfilled.dat  2ms
2017-07-26 14:40:03      Nodes with fulfilled requests: 0
2017-07-26 14:40:03 netfulfilled.dat dump finished  2ms
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 33
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 38
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 36
2017-07-26 14:40:03 

BiblepayMiner -- terminated
2017-07-26 14:40:03 keypool return 5
2017-07-26 14:40:03 torcontrol thread exit
2017-07-26 14:40:03 tor: Thread interrupt
2017-07-26 14:40:03 Shutdown: done
2017-07-26 14:40:04 



















2017-07-26 14:40:04 Biblepay Core version 1.0.1.6 (2017-07-25 19:26:18 -0500)
2017-07-26 14:40:04 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-07-26 14:40:04 GUI: setGeometryDp: Unable to set geometry 5x13+1400+460 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry:  120x13+1400+460 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
2017-07-26 14:40:04 GUI: "registerShutdownBlockReason: Successfully registered: Biblepay Core didn't yet exit safely..."
2017-07-26 14:40:04 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-07-26 14:40:04 Default data directory C:\Users\Loone\AppData\Roaming\BiblepayCore
2017-07-26 14:40:04 Using data directory C:\Users\Loone\AppData\Roaming\BiblepayCore
2017-07-26 14:40:04 Using config file C:\Users\Loone\AppData\Roaming\BiblepayCore\biblepay.conf
2017-07-26 14:40:04 Using at most 125 connections (2048 file descriptors available)
2017-07-26 14:40:04 Using 4 threads for script verification

PewPewGoesTheDuck

full member

Activity: 200

Merit: 101

Downloaded the new version and set it to mine. I'll keep an eye on it and report back if it crashes again. Also can I suggest that you put revision numbers on the executables. That way we know exactly what version we have and are installing.

Shoko943

newbie

Activity: 27

Merit: 0

Quote from: bible_pay on July 26, 2017, 07:31:46 AM

So Im #4 on the list, no crazy hash power being thrown at it.
Everything looks good, a normal distribution curve (since we know #1 will be emptied out every 30 days), except wallet #2: he has received
6.8% of all the blocks. Thats not me. I did receive a message that someone was running 30 nodes in the cloud, but I would assume if one does that, each node has a different address. So my point is how is someone running such high hash power on #2? Do they have a supercomputer?

Does the person want to come forward and help us understand so we can make the best coin possible?

Here is the address:
BBvVRf3ADD8jkdRFmR9DaWBvo5azNi5H96

That would be me D:

I didn't think I was doing anything special. I had some spare capacity so I thought it would be nice to do something with it. I won't be able to keep all of my nodes running forever as it wouldn't be really sustainable right now but I do plan on keeping a certain amount running as long as the project is still alive.

For the ratio of addresses per node, the only thing I did was to keep the same wallet.dat file on all my nodes. It did create a few addresses however (around 5 I think) but nowhere near the number of nodes running. I'm assuming all of them are actually working but I haven't really checked it to be honest.

Hopefully this will shed some light on the person with 30 nodes in the cloud Tongue

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: ?? on ??

I'm here alone on a new version of the wallet?

Why u say alone, because of peer list?
U might have an unlucky peer list. On my external node I have about 125 connections and about 30 have upgraded.
Yeah, Ill look into the versionreport asap.

Come on supermajority!

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: happy_merchant on July 26, 2017, 02:08:57 AM

Set up a BiblePay block explorer temporarily at http://138.68.227.166:3001

First time configuring Iquidus so let me know if you notice anything broken.

This is really nice! Great Job! Thanks.

So Ive been poking around on it, and this is a good auditing tool to ensure the subsidies are being shared evenly.
Nice label on the orphan foundation btw.

So Im #4 on the list, no crazy hash power being thrown at it.
Everything looks good, a normal distribution curve (since we know #1 will be emptied out every 30 days), except wallet #2: he has received
6.8% of all the blocks. Thats not me. I did receive a message that someone was running 30 nodes in the cloud, but I would assume if one does that, each node has a different address. So my point is how is someone running such high hash power on #2? Do they have a supercomputer?

Does the person want to come forward and help us understand so we can make the best coin possible?

Here is the address:
BBvVRf3ADD8jkdRFmR9DaWBvo5azNi5H96

I like how it will pick up the BBP price also - I wonder where it gets the quote.

Anyway, thank you so much and I sent a donation. Double click on it to read it btw, I just want everyone to know we have messaging in transactions.

jc12345

legendary

Activity: 1638

Merit: 1013

Ill look into adding threads but until that is sorted (or figured out) I will use 1.0.1.5. Ill switch at 499 however.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

@Shews:
Thanks for the update. getmininginfo is telling me my hashrate is almost as high as the networkhashrate, or is that number in Khash?

The networkhashps is in Khash while the hashps is in hashes per sec - its just always been that way since the bitcoin client had a miner.

I think we can name it networkkilohashps, to remove the confusion. We do have about 200 miners, so the math does make sense.

@Kotbi:
what does the mandatory mean here. If I still use the older version, it will not mine any more?

The mandatory BL rule goes in at block 500 that just makes the tithes block easy to mine, so that if we ever have a pool, no one tries to remove hash power on the tithe blocks. If you dont upgrade we risk a Fork. The reason I did not force the upgrade is I feel we will have a
supermajority by then and possibly more releases. Im here to support the coin if something goes wrong at that time also, for instance if we have to force the upgrade. Im going to add features from other coins that allow us to run reports on how much of the network is on each version - Ill put that on my list ASAP. Just please upgrade for now so we dont fork.

@jc12345:
It seems update 1.0.1.6 is worse than 1.0.1.5 and engages less of the cores hashing power.

I expected it to be miniscule but here is what happened. The old version, we tried to mine for a whole minute at a time consuming all processor in the thread and then update the block timestamps and all the boring stuff. In the new version to enable the hashmeter, I needed to take a break every 4 seconds or so and update the stats. So its probably resulting in 1% less hash power (not 20%) but is exaggerated due to the thread activity another words if you add more threads you can still get almost all hash power as before, its sort of a tradeoff on measuring, but honestly if you look at the code it is just one integer being incremented in the hash loop, and it breaks out after about 4 seconds of constant work to update the hashmeter.

@muf18
Dev - would you address my issue with PoB?

Hi Muf, so that is a very good concern as we need to have the correct terminology not confused with other coins.
I like the idea of PoBh instead of PoB (proof of burn), and that might stick. Around the time we look to go live on the exchange we will update the terminology on the web site, and come up with a distinct acronym. Thank you for pointing this out.

solarisnoob

newbie

Activity: 34

Merit: 0

is it possible to mine this now? can anyone direct me on how i can mine this? thanks.

kotbi

full member

Activity: 210

Merit: 100

Quote from: Tipstar on July 26, 2017, 03:17:44 AM

Quote from: kotbi on July 26, 2017, 02:57:01 AM

I think there might be some problems with the decimal place. On the screen , look at the difficulty level on the screen. and then type getmininginfo and look at the difficulty level again. One is 10 times higher. Also the network hashrate is 1519. While on the explorer website it is 1.519k. Please take a look at the decimal point.

1519 is 1.519k.

When will be biblepay available to trade. It's really hard to get a block now.

I just realized that. lol. they are the same. I guess what I was trying to say is the total hashrate was 1519 and my hashrate was like 5000

Topic: BiblePay - New Coin Launch - Official Thread - page 152. (Read 119850 times)