Bitcoin Forum
May 25, 2024, 03:33:26 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 164 »
  Print  
Author Topic: BiblePay - New Coin Launch - Official Thread  (Read 119795 times)
Voltaje
Sr. Member
****
Offline Offline

Activity: 350
Merit: 250


View Profile
July 25, 2017, 05:57:29 PM
 #181

Hi, guys, the project is getting bigger bit by bit, and I'm still mining well, sooo, what immature means? I have 1 block that says is immature and nothing in my available, why is that? thanks in advance.
gigabyted
Hero Member
*****
Offline Offline

Activity: 906
Merit: 500



View Profile
July 25, 2017, 06:43:12 PM
 #182

Hi, guys, the project is getting bigger bit by bit, and I'm still mining well, sooo, what immature means? I have 1 block that says is immature and nothing in my available, why is that? thanks in advance.

It takes around 100 blocks to mature, and each block takes around 7 mins, so this means you'll have your coin (free to be moved) in about 700 mins (pretty much 12 hours)
prettybuds
Full Member
***
Offline Offline

Activity: 280
Merit: 100


View Profile
July 25, 2017, 06:44:58 PM
 #183

Mining it seems impossible on my hardware, it's been running for a couple hours but Zero

I'll keep running it, hopefully I get a block or two.
Voltaje
Sr. Member
****
Offline Offline

Activity: 350
Merit: 250


View Profile
July 25, 2017, 06:58:41 PM
 #184

Mining it seems impossible on my hardware, it's been running for a couple hours but Zero

I'll keep running it, hopefully I get a block or two.

I've got it running for 2 days, and I have 1 block, its solo mining, not a pool.
gigabyted
Hero Member
*****
Offline Offline

Activity: 906
Merit: 500



View Profile
July 25, 2017, 07:01:29 PM
 #185

Mining it seems impossible on my hardware, it's been running for a couple hours but Zero

I'll keep running it, hopefully I get a block or two.

Be patient, if you're hardware gives you 1% of the whole hashrate it would still take around 12 hours to hit a single block.  Add luck into that and you can hit a few in a row or no block at all for a couple of days...  it all depends
jc12345
Legendary
*
Offline Offline

Activity: 1638
Merit: 1013


View Profile
July 25, 2017, 07:09:35 PM
 #186

Is 1.0.5 still the latest wallet? Setgenerate drops on all cores after some time which is very annoying.
prettybuds
Full Member
***
Offline Offline

Activity: 280
Merit: 100


View Profile
July 25, 2017, 07:19:19 PM
 #187

Mining it seems impossible on my hardware, it's been running for a couple hours but Zero

I'll keep running it, hopefully I get a block or two.

Be patient, if you're hardware gives you 1% of the whole hashrate it would still take around 12 hours to hit a single block.  Add luck into that and you can hit a few in a row or no block at all for a couple of days...  it all depends

Okay thanks mate I'll just keep going and maybe I will get a block or three. Smiley Would be quite nice to see some Biblepay in my wallet.
jc12345
Legendary
*
Offline Offline

Activity: 1638
Merit: 1013


View Profile
July 25, 2017, 07:28:31 PM
 #188

Ill buy some BBP. PM me your offers.
PewPewGoesTheDuck
Full Member
***
Offline Offline

Activity: 200
Merit: 101



View Profile
July 25, 2017, 09:06:25 PM
 #189

It crashed again. This time running with just setgenerate true -1

Code:
2017-07-25 20:03:28 ProcessNewBlock : ACCEPTED
2017-07-25 20:03:35 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-25 20:03:35 ThreadSocketHandler -- removing node: peer=40 addr=[2001:0:4137:9e76:18e7:39dd:b650:4f13]:40000 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2017-07-25 20:04:26 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:04:26 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=66.192.27.235:52986, peer=41
2017-07-25 20:04:26 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:04:32 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-25 20:04:32 ThreadSocketHandler -- removing node: peer=38 addr=174.138.32.249:40000 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2017-07-25 20:04:40 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:04:40 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=66.192.27.235:53007, peer=42
2017-07-25 20:04:40 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:05:59 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:05:59 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=66.192.27.235:53104, peer=43
2017-07-25 20:05:59 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:06:20 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-25 20:06:20 ThreadSocketHandler -- removing node: peer=42 addr=174.138.34.71:40000 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2017-07-25 20:06:20 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-25 20:06:20 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-07-25 20:06:20 ThreadSocketHandler -- removing node: peer=41 addr=97.99.69.33:40000 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2017-07-25 20:06:20 ThreadSocketHandler -- removing node: peer=43 addr=165.227.20.72:40000 nRefCount=1 fNetworkNode=1 fInbound=0 fMasternode=0
2017-07-25 20:06:32 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:06:32 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=76.242.25.250:53265, peer=44
2017-07-25 20:06:32 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:06:50 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:06:50 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=76.242.25.250:53353, peer=45
2017-07-25 20:06:50 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:02 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:02 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=76.242.25.250:53370, peer=46
2017-07-25 20:07:02 AdvertiseLocal: advertising address 76.242.25.250:40000
2017-07-25 20:07:08 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:08 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=76.242.25.250:53381, peer=47
2017-07-25 20:07:08 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:09 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:09 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=[2001:0:9d38:90d7:10ce:1118:b30d:e605]:53385, peer=48
2017-07-25 20:07:09 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:23 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:23 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=[2001:0:9d38:90d7:10ce:1118:b30d:e605]:53420, peer=49
2017-07-25 20:07:23 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:28 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:07:28 receive version message: /Biblepay Core:1.0.1.4/: version 70707, blocks=297, us=[2001:0:9d38:90d7:10ce:1118:b30d:e605]:53439, peer=50
2017-07-25 20:07:28 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:08:21 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:08:21 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=297, us=76.242.25.250:53491, peer=51
2017-07-25 20:08:21 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:21:57 UpdateTip: new best=0000100ef84faa3cb3ee65e46b68d09e7263568cc1984a800e74e2d2ae3c4504  height=298  log2_work=26.911323  tx=306  date=2017-07-25 20:21:56 progress=0.999996  cache=0.0MiB(32tx)
2017-07-25 20:21:57 ProcessNewBlock : ACCEPTED
2017-07-25 20:22:03 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:22:44 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=298, us=[2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000, peer=52
2017-07-25 20:22:44 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 20:24:20 UpdateTip: new best=000000b2da35e3e5c546986c78c62ef75abfdf11506b25932875beba637479f3  height=299  log2_work=26.916016  tx=307  date=2017-07-25 20:24:18 progress=0.999992  cache=0.0MiB(33tx)
2017-07-25 20:24:20 ProcessNewBlock : ACCEPTED
2017-07-25 20:24:26 CMasternodeSync::CheckNodeHeight -- skipping stuck peer, nHeight=299, nCommonHeight=297, peer=45
2017-07-25 20:24:26 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:26:52 UpdateTip: new best=00001083e5679032cf61127e62bcf909cd1886580b390aafaf6715f9c4672ef3  height=300  log2_work=26.920318  tx=308  date=2017-07-25 20:26:50 progress=0.999992  cache=0.0MiB(34tx)
2017-07-25 20:26:52 ProcessNewBlock : ACCEPTED
2017-07-25 20:26:58 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:55:37 UpdateTip: new best=000002d78c2e04bc08e3866e3e15c8f148227b3c3c8d62dbd3d875564f16baae  height=301  log2_work=26.927094  tx=309  date=2017-07-25 20:55:34 progress=0.999989  cache=0.0MiB(35tx)
2017-07-25 20:55:37 ProcessNewBlock : ACCEPTED
2017-07-25 20:55:43 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:55:52 UpdateTip: new best=0000244cc748269d626a5611f5db8288dc2e65e9cff7d0b48f4d9981f218b1af  height=302  log2_work=26.93184  tx=310  date=2017-07-25 20:55:49 progress=0.999989  cache=0.0MiB(36tx)
2017-07-25 20:55:52 ProcessNewBlock : ACCEPTED
2017-07-25 20:55:58 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:56:12 UpdateTip: new best=000004075b6f35a16754787339efaf062d872b1948fe9d73d49341c559242d50  height=303  log2_work=26.936184  tx=311  date=2017-07-25 20:56:11 progress=0.999996  cache=0.0MiB(37tx)
2017-07-25 20:56:12 ProcessNewBlock : ACCEPTED
2017-07-25 20:56:18 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:57:24 UpdateTip: new best=00000d5d1d1992dd77014b124910e2fd88ddbe5c93a5dfa014dd338e318e81b4  height=304  log2_work=26.94069  tx=312  date=2017-07-25 20:57:22 progress=0.999993  cache=0.0MiB(38tx)
2017-07-25 20:57:24 ProcessNewBlock : ACCEPTED
2017-07-25 20:57:30 CMasternodeSync::CheckNodeHeight -- skipping stuck peer, nHeight=304, nCommonHeight=302, peer=47
2017-07-25 20:57:30 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 20:59:31 UpdateTip: new best=000003a1c119e3ebcb390d3d41dd1324a8ba4502761d2768254925e1f8a89a11  height=305  log2_work=26.950296  tx=313  date=2017-07-25 20:59:28 progress=0.999989  cache=0.0MiB(39tx)
2017-07-25 20:59:31 ProcessNewBlock : ACCEPTED
2017-07-25 20:59:37 CMasternodeSync::IsBlockchainSynced -- found enough peers on the same height as we are, done
2017-07-25 21:01:38 UpdateTip: new best=000006e1df88883f23da96d827af8832e05e2dbf36fbacff0ea1ceaeed7c1237  height=306  log2_work=26.961625  tx=314  date=2017-07-25 21:01:37 progress=0.999996  cache=0.0MiB(40tx)
2017-07-25 21:01:38  Rebooting wallet - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip()));  ** ConnectBlock: PrevBlock != BestBlock; Rebooting Node.ProcessNewBlock : ACCEPTED
2017-07-25 21:01:38

BiblepayMiner -- runtime error: CreateNewBlock: TestBlockValidity failed:  (code 0)
2017-07-25 21:01:38 keypool return 5
2017-07-25 21:01:38

 ** Rebooting Wallet Now **

2017-07-25 21:01:38 addcon thread interrupt
2017-07-25 21:01:38 mnbcon thread interrupt
2017-07-25 21:01:38 opencon thread interrupt
2017-07-25 21:01:38 scheduler thread interrupt
2017-07-25 21:01:38 msghand thread interrupt
2017-07-25 21:01:38 net thread interrupt
2017-07-25 21:01:38 PrepareShutdown: In progress...
2017-07-25 21:01:38 StopNode()
2017-07-25 21:01:38

BiblepayMiner -- terminated
2017-07-25 21:01:38 keypool return 4
2017-07-25 21:01:38 Verifying mncache.dat format...
2017-07-25 21:01:38 Loaded info from mncache.dat  1ms
2017-07-25 21:01:38      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-25 21:01:38 Writting info to mncache.dat...
2017-07-25 21:01:38 Written info to mncache.dat  2ms
2017-07-25 21:01:38      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-25 21:01:38 mncache.dat dump finished  3ms
2017-07-25 21:01:38 Verifying mnpayments.dat format...
2017-07-25 21:01:38 Loaded info from mnpayments.dat  0ms
2017-07-25 21:01:38      Votes: 0, Blocks: 0
2017-07-25 21:01:38 Writting info to mnpayments.dat...
2017-07-25 21:01:38 Written info to mnpayments.dat  1ms
2017-07-25 21:01:38      Votes: 0, Blocks: 0
2017-07-25 21:01:38 mnpayments.dat dump finished  1ms
2017-07-25 21:01:38 Verifying governance.dat format...
2017-07-25 21:01:38 Loaded info from governance.dat  0ms
2017-07-25 21:01:38      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-07-25 21:01:38 Writting info to governance.dat...
2017-07-25 21:01:38 Written info to governance.dat  3ms
2017-07-25 21:01:38      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-07-25 21:01:38 governance.dat dump finished  4ms
2017-07-25 21:01:38 Verifying netfulfilled.dat format...
2017-07-25 21:01:38 Loaded info from netfulfilled.dat  0ms
2017-07-25 21:01:38      Nodes with fulfilled requests: 0
2017-07-25 21:01:38 Writting info to netfulfilled.dat...
2017-07-25 21:01:38 Written info to netfulfilled.dat  3ms
2017-07-25 21:01:38      Nodes with fulfilled requests: 0
2017-07-25 21:01:38 netfulfilled.dat dump finished  3ms
2017-07-25 21:01:38

BiblepayMiner -- terminated
2017-07-25 21:01:38 keypool return 2
2017-07-25 21:01:38 torcontrol thread exit
2017-07-25 21:01:38 tor: Thread interrupt
2017-07-25 21:01:38 Shutdown: done
2017-07-25 21:01:40



















2017-07-25 21:01:40 Biblepay Core version 1.0.1.5 (2017-07-24 14:29:06 -0500)
2017-07-25 21:01:40 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-07-25 21:01:40 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-25 21:01:40 GUI: "registerShutdownBlockReason: Successfully registered: Biblepay Core didn't yet exit safely..."
2017-07-25 21:01:40 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-07-25 21:01:40 Default data directory C:\Users\Loone\AppData\Roaming\BiblepayCore
2017-07-25 21:01:40 Using data directory C:\Users\Loone\AppData\Roaming\BiblepayCore
2017-07-25 21:01:40 Using config file C:\Users\Loone\AppData\Roaming\BiblepayCore\biblepay.conf
2017-07-25 21:01:40 Using at most 125 connections (2048 file descriptors available)
2017-07-25 21:01:40 Using 4 threads for script verification
2017-07-25 21:01:40 scheduler thread start
2017-07-25 21:01:40 Creating backup of C:\Users\Loone\AppData\Roaming\BiblepayCore\wallet.dat -> C:\Users\Loone\AppData\Roaming\BiblepayCore\backups\wallet.dat.2017-07-25-21-01
2017-07-25 21:01:40 Using wallet wallet.dat
2017-07-25 21:01:40 init message: Verifying wallet...
2017-07-25 21:01:40 CDBEnv::Open: LogDir=C:\Users\Loone\AppData\Roaming\BiblepayCore\database ErrorFile=C:\Users\Loone\AppData\Roaming\BiblepayCore\db.log
2017-07-25 21:01:40 Bound to [::]:40000
2017-07-25 21:01:40 Bound to 0.0.0.0:40000
2017-07-25 21:01:40 init message: Init KJV Bible...
2017-07-25 21:01:40 init message: Loading KJV Bible...
2017-07-25 21:01:40 s1 e5aff8cff54256fe8ee133467eed3af0, s2 e409eb2ba6eb6801f52763ae370c350e

2017-07-25 21:01:40 Cache configuration:
2017-07-25 21:01:40 * Using 12.5MiB for block index database
2017-07-25 21:01:40 * Using 29.9MiB for chain state database
2017-07-25 21:01:40 * Using 57.6MiB for in-memory UTXO set
2017-07-25 21:01:40 init message: Loading block index...
2017-07-25 21:01:40 Opening LevelDB in C:\Users\Loone\AppData\Roaming\BiblepayCore\blocks\index
2017-07-25 21:01:40 Opened LevelDB successfully
2017-07-25 21:01:40 Using obfuscation key for C:\Users\Loone\AppData\Roaming\BiblepayCore\blocks\index: 0000000000000000
2017-07-25 21:01:40 Opening LevelDB in C:\Users\Loone\AppData\Roaming\BiblepayCore\chainstate
2017-07-25 21:01:40 Opened LevelDB successfully
2017-07-25 21:01:40 Using obfuscation key for C:\Users\Loone\AppData\Roaming\BiblepayCore\chainstate: e5b825f258ee6e27
2017-07-25 21:01:40 LoadBlockIndexDB: last block file = 0
2017-07-25 21:01:40 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=308, size=60124, heights=0...306, time=2017-06-01...2017-07-25)
2017-07-25 21:01:40 Checking all blk files are present...
2017-07-25 21:01:40 LoadBlockIndexDB: transaction index enabled
2017-07-25 21:01:40 LoadBlockIndexDB: address index disabled
2017-07-25 21:01:40 LoadBlockIndexDB: timestamp index disabled
2017-07-25 21:01:40 LoadBlockIndexDB: spent index disabled
2017-07-25 21:01:40 LoadBlockIndexDB: hashBestChain=000006e1df88883f23da96d827af8832e05e2dbf36fbacff0ea1ceaeed7c1237 height=306 date=2017-07-25 21:01:37 progress=0.999989
2017-07-25 21:01:40 init message: Verifying blocks...
2017-07-25 21:01:40 Verifying last 288 blocks at level 3
2017-07-25 21:01:40 No coin database inconsistencies in last 289 blocks (296 transactions)
2017-07-25 21:01:40  block index             280ms
2017-07-25 21:01:40 init message: Loading wallet...
2017-07-25 21:01:40 nKeysLeftSinceAutoBackup: 1025
2017-07-25 21:01:40 nFileVersion = 1000105
2017-07-25 21:01:40 Keys: 1026 plaintext, 0 encrypted, 1026 w/ metadata, 1026 total
2017-07-25 21:01:40  wallet                   29ms
2017-07-25 21:01:40 init message: Activating best chain...
2017-07-25 21:01:40 Using masternode config file C:\Users\Loone\AppData\Roaming\BiblepayCore\masternode.conf
2017-07-25 21:01:40 fLiteMode 0
2017-07-25 21:01:40 nInstantSendDepth 5
2017-07-25 21:01:40 PrivateSend rounds 2
2017-07-25 21:01:40 PrivateSend amount 1000
2017-07-25 21:01:40 init message: Loading masternode cache...
2017-07-25 21:01:40 Reading info from mncache.dat...
2017-07-25 21:01:40 Loaded info from mncache.dat  0ms
2017-07-25 21:01:40      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-25 21:01:40 Read: Cleaning....
2017-07-25 21:01:40      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-25 21:01:40 init message: Masternode cache is empty, skipping payments and governance cache...
2017-07-25 21:01:40 init message: Loading fulfilled requests cache...
2017-07-25 21:01:40 Reading info from netfulfilled.dat...
2017-07-25 21:01:40 Loaded info from netfulfilled.dat  0ms
2017-07-25 21:01:40      Nodes with fulfilled requests: 0
2017-07-25 21:01:40 Read: Cleaning....
2017-07-25 21:01:40      Nodes with fulfilled requests: 0
2017-07-25 21:01:40 init message: Memorizing Prayers...
2017-07-25 21:01:40 mapBlockIndex.size() = 308
2017-07-25 21:01:40 chainActive.Height() = 306
2017-07-25 21:01:40 setKeyPool.size() = 1025
2017-07-25 21:01:40 mapWallet.size() = 0
2017-07-25 21:01:40 mapAddressBook.size() = 1
2017-07-25 21:01:40 init message: Loading addresses...
2017-07-25 21:01:40 torcontrol thread start
2017-07-25 21:01:40 ERROR: Read: Failed to open file C:\Users\Loone\AppData\Roaming\BiblepayCore\banlist.dat
2017-07-25 21:01:40 Invalid or missing banlist.dat; recreating
2017-07-25 21:01:40 Loaded 2341 addresses from peers.dat  10ms
2017-07-25 21:01:40 AddLocal([2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000,1)
2017-07-25 21:01:40 Discover: DESKTOP-7U88A3K - 2001:0:9d38:90d7:10ce:1118:b30d:e605
2017-07-25 21:01:40 dnsseed thread start
2017-07-25 21:01:40 net thread start
2017-07-25 21:01:40 init message: Done loading
2017-07-25 21:01:40 addcon thread start
2017-07-25 21:01:40 opencon thread start
2017-07-25 21:01:40 mnbcon thread start
2017-07-25 21:01:40 msghand thread start
2017-07-25 21:01:40 GUI: Platform customization: "windows"
2017-07-25 21:01:40 GUI: PaymentServer::LoadRootCAs: Loaded  42  root certificates
2017-07-25 21:01:40 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:40 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=306, us=76.242.25.250:55715, peer=1
2017-07-25 21:01:40 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:41 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:41 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=306, us=76.242.25.250:55716, peer=2
2017-07-25 21:01:41 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:41 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:41 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=306, us=76.242.25.250:55717, peer=3
2017-07-25 21:01:41 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:51 P2P peers available. Skipped DNS seeding.
2017-07-25 21:01:51 dnsseed thread exit
2017-07-25 21:01:53 ProcessMessages: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
2017-07-25 21:01:53 receive version message: /Biblepay Core:1.0.1.5/: version 70707, blocks=306, us=[2001:0:9d38:90d7:10ce:1118:b30d:e605]:55731, peer=4
2017-07-25 21:01:53 AdvertiseLocal: advertising address [2001:0:9d38:90d7:10ce:1118:b30d:e605]:40000
jc12345
Legendary
*
Offline Offline

Activity: 1638
Merit: 1013


View Profile
July 25, 2017, 09:08:21 PM
 #190

It crashed again. This time running with just setgenerate true -1

It does crash. You cannot leave it alone for too long then you have to setgenerate again.
happy_merchant
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
July 25, 2017, 09:25:20 PM
 #191


01   BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM   599921.77006080
02   BBvVRf3ADD8jkdRFmR9DaWBvo5azNi5H96   399942.00000000
03   BHEuyEV5L8ENnHNUeQ5J6fCAtp3dAFX5fd   120000.00000000
04   BEkTceA4VREFs9JTxNLmhA5hyHcGkCc5UA   100000.00000000
05   B5NpJT7CSMhEvGCQBJf4828Hg66uuvupbJ   99969.00000000
06   BQf21m7s45beQEdZ8wAgyfDqYYFbxipJJs   99965.00010640
07   BHQewwDWGjKh4k72omV5Sz33vJLmncrKTq   79998.00000000
08   BRpDN41joo1hfzqooX4XTYXzz25mAVwBj6   79995.00000000
09   BND53AsMhu5bHTEajMHvgNSbiDWTSCsDe5   79991.00000000
10   BD9bH4HPaCPggi5krL9P1MStL2W1MxmxQH   60000.00000000


Working on a block explorer, here's the current top 10 wallets. A couple people have really been going at it.

--edit--
Actually, it's kind of strange, the #1 wallet has mined block 10, 20, 30... and so on and continuing even now. Every single 10th block, and no others?  Huh
bible_pay (OP)
Full Member
***
Offline Offline

Activity: 1176
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
July 25, 2017, 09:42:25 PM
 #192


01   BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM   599921.77006080
02   BBvVRf3ADD8jkdRFmR9DaWBvo5azNi5H96   399942.00000000
03   BHEuyEV5L8ENnHNUeQ5J6fCAtp3dAFX5fd   120000.00000000
04   BEkTceA4VREFs9JTxNLmhA5hyHcGkCc5UA   100000.00000000
05   B5NpJT7CSMhEvGCQBJf4828Hg66uuvupbJ   99969.00000000
06   BQf21m7s45beQEdZ8wAgyfDqYYFbxipJJs   99965.00010640
07   BHQewwDWGjKh4k72omV5Sz33vJLmncrKTq   79998.00000000
08   BRpDN41joo1hfzqooX4XTYXzz25mAVwBj6   79995.00000000
09   BND53AsMhu5bHTEajMHvgNSbiDWTSCsDe5   79991.00000000
10   BD9bH4HPaCPggi5krL9P1MStL2W1MxmxQH   60000.00000000


Working on a block explorer, here's the current top 10 wallets. A couple people have really been going at it.

--edit--
Actually, it's kind of strange, the #1 wallet has mined block 10, 20, 30... and so on and continuing even now. Every single 10th block, and no others?  Huh

Nice work happy!

So BB2 is the orphan foundations cold wallet.  It receives all the tithes.  Thats why it always receives blocks mod 10 (that is the 10% tithe of the blockchain emission, btw).  Just on a side note, when I run the tithe report in about 29 days, the amount in that wallet actually gets entirely dumped to compassion.com.  I will post pictures of the orphans we sponsor here on the board, and also, we are going to have a web site that shows orphan ID #s and stuff so it is auditable.  It should be really cool.

As far as the crashes, I was not aware this was happening, we must be exploiting a difference on the intel processor (vs my experiences with AMD on my two biblepay nodes).  Anyway, I do see some things in the logs and will be investigating this ASAP.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
happy_merchant
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
July 25, 2017, 09:59:47 PM
 #193

So BB2 is the orphan foundations cold wallet.  It receives all the tithes.  Thats why it always receives blocks mod 10 (that is the 10% tithe of the blockchain emission, btw).  Just on a side note, when I run the tithe report in about 29 days, the amount in that wallet actually gets entirely dumped to compassion.com.  I will post pictures of the orphans we sponsor here on the board, and also, we are going to have a web site that shows orphan ID #s and stuff so it is auditable.  It should be really cool.

Okay, I was thinking it might be related to that since it worked out to 10%.

Is that really the best way to go about collecting the tithe, though? There still seems to be a ~7 minute block time for the 10th block. If that block is going to automatically be assigned to the foundation wallet, I think you'll see issues with people pool jumping to mine other coins every 10th block then jumping back after it's been mined. If BiblePay ends up attracting the attention of some of the big crypto miners who would definitely exploit this, that sudden drop in network hashrate every 10th block seems like it could be an issue.

If possible, I'd think that simply redirecting 10% of each block reward to the foundation wallet would avoid some issues in the long run.
bible_pay (OP)
Full Member
***
Offline Offline

Activity: 1176
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
July 25, 2017, 10:07:17 PM
 #194

So BB2 is the orphan foundations cold wallet.  It receives all the tithes.  Thats why it always receives blocks mod 10 (that is the 10% tithe of the blockchain emission, btw).  Just on a side note, when I run the tithe report in about 29 days, the amount in that wallet actually gets entirely dumped to compassion.com.  I will post pictures of the orphans we sponsor here on the board, and also, we are going to have a web site that shows orphan ID #s and stuff so it is auditable.  It should be really cool.

Okay, I was thinking it might be related to that since it worked out to 10%.

Is that really the best way to go about collecting the tithe, though? There still seems to be a ~7 minute block time for the 10th block. If that block is going to automatically be assigned to the foundation wallet, I think you'll see issues with people pool jumping to mine other coins every 10th block then jumping back after it's been mined. If BiblePay ends up attracting the attention of some of the big crypto miners who would definitely exploit this, that sudden drop in network hashrate every 10th block seems like it could be an issue.

If possible, I'd think that simply redirecting 10% of each block reward to the foundation wallet would avoid some issues in the long run.
Yes, I agree with you, I will check the safest way to do it also.  We might end up lowering the difficulty on the 10th block 95%, or something we will see, this can be deployed during a mandatory, but Ill see if I can get it working in testnet.

So, on this crash or reboot issue, I have a potential fix being released with the hashmeter.  This probably wont be released until 9pm.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
Keeinj
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
July 25, 2017, 11:01:58 PM
 #195

Been mining since around 100. I've hit on quite a few blocks. Going to keep an eye on this coin.
tasrep
Jr. Member
*
Offline Offline

Activity: 121
Merit: 1


View Profile
July 26, 2017, 12:23:03 AM
 #196

I strongly agree with this development, hopefully this continues, dev very good, hopefully for the future better and always successful. thanks.

Crypto-Court
Universal Cryptocurrency Platform
https://cryptocourt.online/
Shews
Full Member
***
Offline Offline

Activity: 177
Merit: 100


View Profile
July 26, 2017, 02:01:28 AM
 #197

24hrs + and no block... hashrate and difficulty increasing.... I might have missed the boat!
gigabyted
Hero Member
*****
Offline Offline

Activity: 906
Merit: 500



View Profile
July 26, 2017, 02:14:50 AM
 #198

24hrs + and no block... hashrate and difficulty increasing.... I might have missed the boat!

Hang on solo mining is a long journey, just make sure to keep your wallet mining and active more threads of your CPU can handle it!  That way you might have more chances...
Shews
Full Member
***
Offline Offline

Activity: 177
Merit: 100


View Profile
July 26, 2017, 02:21:01 AM
 #199

24hrs + and no block... hashrate and difficulty increasing.... I might have missed the boat!

Hang on solo mining is a long journey, just make sure to keep your wallet mining and active more threads of your CPU can handle it!  That way you might have more chances...

Thanks man, got my CPU maxin. Think it can tell I want in too much!
Charloz24
Hero Member
*****
Offline Offline

Activity: 966
Merit: 501



View Profile
July 26, 2017, 02:22:46 AM
 #200

Pool mining would be great now, I think many have dropped it because of nomreward.
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 164 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!