BiblePay - New Coin Launch - Official Thread

[emdes]

I just finished upgrading to 1033 and I'm still getting the ST13 error.

************************
EXCEPTION: St13runtime_error      
tinyformat: Not enough conversion specifiers in format string      
biblepay in ProcessMessages()  
[/quote]

Same here on 2 PC's. Win10 and Win8.1 after reindex (stuck on 2 days behind)

EDIT: 1032

[1715294649]

1715294649

[kyvo]

the pool is stop working at block 7449 

[remtiwk]

My machines are at block 7463.. but are not showing up on the pool. 

[svirusxxx2]

Code:

2017-09-13 17:18:41 generated 18659.0000752
2017-09-13 17:18:41 89
BiblepayMiner -- runtime error: tinyformat: Not enough conversion specifiers in format string

and I don't see this block :/

EDIT
hehe, on other node I see this block:

Code:

  {
    "account": "",
    "address": "B8BFD922vjbFC3c69yUJBa26umzjBVsUi4",
    "category": "immature",
    "amount": 19207.00000000,
    "vout": 0,
    "confirmations": 1,
    "bcconfirmations": 1,
    "generated": true,
    "blockhash": "b40fcbbc031c1f6ff799d37db3db7100217b605b1857adcf5d71b6d5ac2567f1",
    "blockindex": 0,
    "blocktime": 1505323989,
    "txid": "039344ee004cff1df51d09549e13cd6b887f11e4438c4a702a8a67aa3ccd7b23",
    "walletconflicts": [
    ],
    "time": 1505323989,
    "timereceived": 1505323990,
    "bip125-replaceable": "no"
  }

[remtiwk]

the pool is stop working at block 7449 

I only see 5 miners in the pool leaderboard currently. 

[bible_pay]

Sorry, been gone debugging the problem with the new version.  Kind of hard to find the root cause.

You'll never believe how dumb the problem is- the issue is with changing the DGW parameter, in mid stream, a certain block header between 7100-7250 causes an unprintable log error, and that actually takes down the whole wallet.

The key is to set a future block number for the subsidy increase.  I obviously would have done that, but I was viewing this as Hey we need a mandatory lets just change it now.

Let me go back and set up the change and Ill get back in about 30 minutes.

[richus]

Hello. solo minig cannot synchronize with the network for 11 hours. What to do? purse Biblepay v1.0.3.2 version

[J1980]

  I just upgraded 5 min ago to 1.0.3.2 ..... no block souce available. ...

[tiras]

Hello. solo minig cannot synchronize with the network for 11 hours. What to do? purse Biblepay v1.0.3.2 version

start with adding this in your biblepay.conf  and restarting the wallet :

addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1

[svirusxxx2]

1.3.2 working
but I tried on one node upgrade to 1.3.3
make clean
./configure
make

and on 1.3.3

Code:

2017-09-13 17:46:42 init message: Activating best chain...
2017-09-13 17:46:42 

************************
EXCEPTION: St13runtime_error       
tinyformat: Not enough conversion specifiers in format string       
biblepay in AppInit()       

2017-09-13 17:46:42 PrepareShutdown: In progress...

gentoo Linux 4.7.10-hardened
gcc (Gentoo Hardened 4.9.3 p1.5, pie-0.6.4) 4.9.3

[richus]

Hello. solo minig cannot synchronize with the network for 11 hours. What to do? purse Biblepay v1.0.3.2 version

start with adding this in your biblepay.conf  and restarting the wallet :

addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1

Yes, it is spelled out in the config. No synchronization. after the restart, says the source blocks are not available. Although there are 5 active connections

[richus]

To date, the synchronization was working, today after restarting the wallet sync has stopped working

[tiras]

To date, the synchronization was working, today after restarting the wallet sync has stopped working

problems with the blockchain .  we'll have to wait for a resolution

[Iwuzhaxxed]

Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.

All of the computers running 1.0.3.1 do connect to nodes even after restarting them.

None are showing up on the pool.

[tiras]

Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.

All of the computers running 1.0.3.1 do connect to nodes even after restarting them.

None are showing up on the pool.

JUST WAIT 

[slovakia]

buddies how you upgrade your wallet?  
tried install newest wallet on new machine and same problem like you Windows 64bit file.  "A fatal error occurred. Biblepay Core can no longer safely continue and will quit."

[bible_pay]

Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.

All of the computers running 1.0.3.1 do connect to nodes even after restarting them.

None are showing up on the pool.

JUST WAIT 

Nice pic, thats what I feel like!


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.

[bible_pay]

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.

[slovakia]

bible_pay  can you post here how can we upgrade our wallet? pls dont waste our real time ...  and can you write on main web http://biblepay.org/ what version we downloading?

[J1980]

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.

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 )