BiblePay - New Coin Launch - Official Thread

[inblue]

Today we have 3 fresh issues.
One, the Ddos is sort of under control, but the issue is becoming complicated, because there are a few type of attacks going on. 
To isolate the problem, I upgraded the pool solution packet in the wallet in 1.0.3.7 - this is necessary anyway for technical reasons.

Id appreciate if some of the linux users can upgrade to 1037.  Windows is compiling.

I have no time to change my linux machines yet, can I still continue to use 1034 or 1035 for solo mining?

Do you get any blocks in solo mining?

I don't know if I'm lucky or not, I remember I need a few days to get 1 block last time, but I got 2 blocks in last few hours today 

I think you're not lucky, because the pool went down a few hours ago and kicked everyone, so maybe that's why it was much easier for you to find blocks. Congrats btw.

[tiras]

same problem with static ip= banned , others machines without problem

@bible_pay will ve fixed that huge range of banned ip? thx

NONE of my boxes can connect to the pool atm.  

I have VPSs both in EU an NA and none of them work.

was there an announcement that pool is going down for troubleshooting or anything ?


upgrading linux ones to the curr version .


update :
>>   just switched to pool.biblepay.org from pool2  and  got back in the pool

[Minucius]

I've got like 700K coins solo mining today. It more than 200 times I used to get when pool mining. Is there something wrong? :O

[nananaminer]

I've got like 700K coins solo mining today. It more than 200 times I used to get when pool mining. Is there something wrong? :O

You're probably on the wrong chain, try stopping and reindexing it.

[inblue]

same problem with static ip= banned , others machines without problem

@bible_pay will ve fixed that huge range of banned ip? thx

NONE of my boxes can connect to the pool atm.  

I have VPSs both in EU an NA and none of them work.

was there an announcement that pool is going down for troubleshooting or anything ?

upgrading linux ones to the curr version .

Yeah, the leaderboard is empty since a few hours ago and the pool address didn't receive coins, so someone else did.

I've got like 700K coins solo mining today. It more than 200 times I used to get when pool mining. Is there something wrong? :O

Could you post a hash of block 7900 for example, let's see if you're on the right chain. Command is getblockhash 7900

The output should be:

Code:

9d65b7f97a9cae49c064df76231f2259987d7f2765391834758ce4ebb987b1b1

[togoshigekata]

Today we have 3 fresh issues.
One, the Ddos is sort of under control, but the issue is becoming complicated, because there are a few type of attacks going on.  
To isolate the problem, I upgraded the pool solution packet in the wallet in 1.0.3.7 - this is necessary anyway for technical reasons.

Id appreciate if some of the linux users can upgrade to 1037.  Windows is compiling.

I cant access http://pool.biblepay.org/ in web browser

"This site can’t be reached
pool.biblepay.org took too long to respond.
ERR_CONNECTION_TIMED_OUT"

Upgrading my linux miner to version 1.0.3.7

[Minucius]

same problem with static ip= banned , others machines without problem

@bible_pay will ve fixed that huge range of banned ip? thx

NONE of my boxes can connect to the pool atm.  

I have VPSs both in EU an NA and none of them work.

was there an announcement that pool is going down for troubleshooting or anything ?

upgrading linux ones to the curr version .

Yeah, the leaderboard is empty since a few hours ago and the pool address didn't receive coins, so someone else did.

I've got like 700K coins solo mining today. It more than 200 times I used to get when pool mining. Is there something wrong? :O

Could you post a hash of block 7900 for example, let's see if you're on the right chain. Command is getblockhash 7900

The output should be:

Code:

9d65b7f97a9cae49c064df76231f2259987d7f2765391834758ce4ebb987b1b1

Block height out of range...

Note: I'm still using 1.0.3.1. Tried 1.0.3.5 but it wouldn't sync. Where kind I find the "correct version" for windows?
Thanks

[Shoko943]

There was a new mandatory a few days ago so 1.0.3.4 and above would be the "correct" version.

You may want to try to to delete the "blocks" folder and "chainstate" folder.

I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.

[tiras]

Today we have 3 fresh issues.
One, the Ddos is sort of under control, but the issue is becoming complicated, because there are a few type of attacks going on.  
To isolate the problem, I upgraded the pool solution packet in the wallet in 1.0.3.7 - this is necessary anyway for technical reasons.

Id appreciate if some of the linux users can upgrade to 1037.  Windows is compiling.

I cant access http://pool.biblepay.org/ in web browser

"This site can’t be reached
pool.biblepay.org took too long to respond.
ERR_CONNECTION_TIMED_OUT"

Upgrading my linux miner to version 1.0.3.7

I'm hitting the pool but getting :

  "poolinfo2": "Submitting Solution 09-16-2017 16:09:45;
  "poolinfo3": "BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_S
TALE; BLOCK_IS_STALE; BLOCK_IS_STALE; ",

[canonical]

On linux, I compiled from github, deleted 'blocks' and 'chainstate' folders, ran biblepayd and let the blockchain sync (very fast).

'getmininginfo' returns 'BLOCK_IS_STALE'.

'getblockhash 7900' is '9d65b7f97a9cae49c064df76231f2259987d7f2765391834758ce4ebb987b1b1'

[inblue]

@happy_merchant:

This is the new pool address, so could you update the label to be on this address? It seems like all funds were transferred yesterday from the old address and that address stopped receiving block rewards.

[PhaseshiftUK]

Today we have 3 fresh issues.
One, the Ddos is sort of under control, but the issue is becoming complicated, because there are a few type of attacks going on. 
To isolate the problem, I upgraded the pool solution packet in the wallet in 1.0.3.7 - this is necessary anyway for technical reasons.

Id appreciate if some of the linux users can upgrade to 1037.  Windows is compiling.

I've been running the 1.0.3.7 for an hour or two, but my client is not appearing on the pool.  However, as the leaderboard is empty (and from the other posts), I presume that there is a separate issue there.

On a side note, I still occasionally get:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

when running ./biblepay-cli stop

Thanks

[PhaseshiftUK]

I'm hitting the pool but getting :

  "poolinfo2": "Submitting Solution 09-16-2017 16:09:45;
  "poolinfo3": "BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_S
TALE; BLOCK_IS_STALE; BLOCK_IS_STALE; ",

Same issue here, both with the new 1.0.3.7 under Linux and the Windows 1.0.3.5:

biblepay-cli getmininginfo
{
  "blocks": 7905,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 640.6745868486712,
  "errors": "",
  "genproclimit": 8,
  "networkhashps": 75282662533.70592,
  "hashps": 47789.31395525282,
  "minerstarttime": "09-16-2017 16:23:10",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
  "poolinfo2": "Submitting Solution 09-16-2017 16:23:24; Submitting Solution 09-16-2017 16:23:39; Submitting Solution 09-16-2017 16:23:38; Submitting Solution 09-16-2017 16:23:21; Submitting Solution 09-16-2017 16:23:33; Submitting Solution 09-16-2017 16:23:39; Submitting Solution 09-16-2017 16:23:33; Submitting Solution 09-16-2017 16:23:40; ",
  "poolinfo3": "BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_STALE; BLOCK_IS_STALE; ",
  "miningpulse": 173,
  "poolmining": true
}


getmininginfo
{
  "blocks": 7906,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 920.1370789232158,
  "errors": "",
  "genproclimit": 3,
  "networkhashps": 69367553836.83989,
  "hashps": 3540.572663425176,
  "minerstarttime": "09-16-2017 16:29:18",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
  "poolinfo2": "RMC_09-16-2017 16:29:26; RMC_09-16-2017 16:29:26; Submitting Solution 09-16-2017 16:29:46; ",
  "poolinfo3": "BLOCK_IS_STALE; ",
  "miningpulse": 3,
  "poolmining": true
}

[bileq]

i can not withdraw from pool to my wallet.
it says invalid destination address.
whats wrong?

[Minucius]

There was a new mandatory a few days ago so 1.0.3.4 and above would be the "correct" version.

You may want to try to to delete the "blocks" folder and "chainstate" folder.

I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.

Ok, so the 900K i mined on the other chain is worthless I guess? Deleted the blocks folder and chainstate, downloaded an installed 1.0.3.5, and all those coins are "gone" from my wallet.

[togoshigekata]

@bible_pay
Linux miner updated to v1.0.3.7 and mining
config set to pool.biblepay.org,
poolmining=false
block 7909
8 peers, only 1 peer v1.0.3.7

[Shoko943]

There was a new mandatory a few days ago so 1.0.3.4 and above would be the "correct" version.

You may want to try to to delete the "blocks" folder and "chainstate" folder.

I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.

Ok, so the 900K i mined on the other chain is worthless I guess? Deleted the blocks folder and chainstate, downloaded an installed 1.0.3.5, and all those coins are "gone" from my wallet.

Yup unfortunately Did you manage to get your wallet to sync again?

[nananaminer]

@bible_pay
Linux miner updated to v1.0.3.7 and mining
config set to pool.biblepay.org,
poolmining=false
block 7909
8 peers, only 1 peer v1.0.3.7

I'm on 1.0.3.7 as well for an hour, Pool is down so solo mining at this point.(Just found a block!)

Edit: One thing I also noticed is, all the solo blocks my miners found so far are when the miner was in pool and switched to solo by itself, haven't found a block while only mining solo. Is this is a coincidence or are there any parameters in play here?

[Minucius]

There was a new mandatory a few days ago so 1.0.3.4 and above would be the "correct" version.

You may want to try to to delete the "blocks" folder and "chainstate" folder.

I'm not sure about it but it could be possible that all the other nodes temporarily banned you since you were spamming them with the wrong version.

Ok, so the 900K i mined on the other chain is worthless I guess? Deleted the blocks folder and chainstate, downloaded an installed 1.0.3.5, and all those coins are "gone" from my wallet.

Yup unfortunately Did you manage to get your wallet to sync again?

Yes, now I'm on block 7911, with 54 K  in my wallet, instead of 1.2 Millions :/
Thanks anyways

[calxibe]

Is 1.0.3.7 for windows released?