BiblePay - New Coin Launch - Official Thread

[PhaseshiftUK]

So basically, 1.0.3.1-1.0.3.3 was a failure.  

This version contains a bad LogPrint message, that causes the entire wallet to die.

The new version is almost ready.  I just tested it and it works on Debian and raises the subsidy back up to normal at block 7500.

I was just looking into why 1.0.3.3 didn't work.  Thanks for sorting it so quickly.

Not really a priority, but hopefully can be fixed for a later version, whenever I issue the stop command to the server I get an error:
"terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
terminate called recursively"

https://github.com/biblepay/biblepay/issues/5

Thanks

[1715140616]

1715140616

[1715140616]

1715140616

[1715140616]

1715140616

[1715140616]

1715140616

[jobetheminer]

Thank you for your hard work bible_pay!!

[brimdor]

Thank you for the hard work. I couldn't do what you do so it is much appreciated.

[tiras]

Alright, lets rewind the whole day back to about 7 AM and try this again.

Version 1.0.3.4 (the future mandatory) is now checked in for linux only.  This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions.  If anyone on linux wants to upgrade now and start pre-testing go for it.

Win is compiling and will be ready in two hours.

In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.

does it mean we have to flush blocks and chainstate directories ?


I did that on 1 upgraded box . 

it's now on 7188  and doing nothing:

blocks": 7188,

"blocks": 7188,
  "currentblocksize": 0,
  "currentblocktx": 0,
  "difficulty": 40.48123000304026,
  "errors": "",
  "genproclimit": 32,
  "networkhashps": 2275758480.220703,
  "hashps": 0,
  "minerstarttime": "09-13-2017 19:49:22",
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 0,
  "poolmining": false



other upgraded boxes are at diff levels :
   
     blocks": 7460, 
    "blocks": 7475,
     "blocks": 7447,

showing activity but again not hitting the pool :

smthing like this :

Code:

	  "poolinfo2": "Submitting Solution 09-13-2017 20:11:26; Submitting Solution 09-13-2017 20:12:21; RMC_09-13-2017 20
:12:31; Submitting Solution 09-13-2017 20:12:23; Submitting Solution 09-13-2017 20:12:26; Submitting Solution 09-13
-2017 20:12:29; Submitting Solution 09-13-2017 20:11:28; RM_09-13-2017 20:12:30; Submitting Solution 09-13-2017 20:
12:16; Submitting Solution 09-13-2017 20:12:15; Submitting Solution 09-13-2017 20:12:20; Submitting Solution 09-13-
2017 20:12:26; Submitting Solution 09-13-2017 20:12:09; Submitting Solution 09-13-2017 20:12:29; Submitting Solutio
n 09-13-2017 20:12:18; Submitting Solution 09-13-2017 20:12:22; ",
  "poolinfo3": "HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_D
OWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; ",

[svirusxxx2]

I'am on good chain ?
all my nodes now running on block 7476 with hash b902dbafd8b12647a990354877a27ba2e8a2d7b35fc572eff2d18edf9584f32a

[tylerbastyan]

To give real service, you must add something which cannot be bought or measured with money, and that is sincerity and integrity.

[p3ppymon]

I'am on good chain ?
all my nodes now running on block 7476 with hash b902dbafd8b12647a990354877a27ba2e8a2d7b35fc572eff2d18edf9584f32a

Block 7477 at the moment.

[svirusxxx2]

I'am on good chain ?
all my nodes now running on block 7476 with hash b902dbafd8b12647a990354877a27ba2e8a2d7b35fc572eff2d18edf9584f32a

Block 7477 at the moment.

can any post hash of 7477 ?
my is : 7949267ffbd7a358550cafc6d5aca38b6ac63d11e82468209d650225146787b7

from debug conosle

Code:

getblockhash 7477

[inblue]

I'am on good chain ?
all my nodes now running on block 7476 with hash b902dbafd8b12647a990354877a27ba2e8a2d7b35fc572eff2d18edf9584f32a

Block 7477 at the moment.

can any post hash of 7477 ?
my is : 7949267ffbd7a358550cafc6d5aca38b6ac63d11e82468209d650225146787b7

from debug conosle

Code:

getblockhash 7477

http://biblepay.inspect.network/

[p3ppymon]

I'am on good chain ?
all my nodes now running on block 7476 with hash b902dbafd8b12647a990354877a27ba2e8a2d7b35fc572eff2d18edf9584f32a

Block 7477 at the moment.

can any post hash of 7477 ?
my is : 7949267ffbd7a358550cafc6d5aca38b6ac63d11e82468209d650225146787b7

from debug conosle

Code:

getblockhash 7477

http://biblepay.inspect.network/

block 7477 hash = a10815a4f432828b67538cdbaa1a7fd4afebfb6ae63d6667392d72ee28a10260

[lilaj4de]

In addition to c-cex, what are the plans to be listed on other exchanges. And which ones will be listed?

[bible_pay]

Biblepay 1.0.3.4-Mandatory Upgrade
www.biblepay.org

- Fix ST13 Error
- Fix f7000 Low-Subsidy based on High-Diff calculation
- Fix Pool banning issue
- Fix Read Disk error

- At block 7500, we raise the subsidy back to ~18,000.

[bible_pay]

In addition to c-cex, what are the plans to be listed on other exchanges. And which ones will be listed?

I think what we should do is focus on testing the Sanctuary version in testnet, and debug it in full, add our beta software to the web site for governance, then talk about more exchanges. 

The next exchanges are bittrex and poloniex.

[bible_pay]

To give real service, you must add something which cannot be bought or measured with money, and that is sincerity and integrity.

+++

[bible_pay]

Code:

[quote author=tiras link=topic=2042657.msg21805705#msg21805705 date=1505333967]



  "poolinfo3": "HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_D
OWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; ",

[/quote]

Hi Tiras,

Pool is not updated yet to 1.0.3.4.  Working on that next.

It has to be upgraded to answer the calls properly.

[bible_pay]

Nice a new version :-D
But wat about the mining and transaction from today ...
I understand that a role back will take this away?

I made my first transaction today lol

(Just a minor miner on a old laptop )

It depends on if the chain you mined it on stays the longest chain.  Everyones upgrading to 1034 now.  If you mined it on 1034, it might stick.

Anyway if it dissapears, the tx in the txlist will become an orphan and have a different icon.

[happy_merchant]

http://biblepay.inspect.network/

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.

[bible_pay]

http://biblepay.inspect.network/

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.

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.

[x5650]

2 hours behind, not synchronizing atm...

[maarekelets]

Biblepay 1.0.3.4-Mandatory Upgrade
www.biblepay.org

- Fix ST13 Error
- Fix f7000 Low-Subsidy based on High-Diff calculation
- Fix Pool banning issue
- Fix Read Disk error

- At block 7500, we raise the subsidy back to ~18,000.

Clean blocks, chainstate and banlist install on Windows and it loaded fine with no errors. Seems to be back up and mining. I think I see a light at the end of the tunnel here. (OK so the pool is down, but at least my systems are working ok).