BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 191.

afeno

jr. member

Activity: 175

Merit: 1

Quote from: ?? on ??

Quote from: capulo on March 15, 2019, 04:04:45 AM

Quote from: Lichtsucher on March 15, 2019, 03:40:57 AM

The older Ubuntu PPA compiles the new release right now. After that is finished, Purepool will be updated (again...)

what about other releases? i was trying some i think 17.04 ubuntu and there was only 1.1.3.8 or so ...

WHYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY.
WHY should anyone go to this forum thread and WASTING its precious time, energy and resources, going through this non-sense fucked up bullshit...

Because it brings me good memories... I enjoined BBP last year and I hope to have fun in the future.
And I have to admit that I took some advantage of the ups and downs to trade BBP on the exchange.

afeno

jr. member

Activity: 175

Merit: 1

Quote from: MIP on March 15, 2019, 04:02:11 AM

Quote from: afeno on March 15, 2019, 03:25:29 AM

Quote from: MIP on March 15, 2019, 12:39:19 AM

Quote from: bible_pay on March 14, 2019, 11:12:17 PM

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

MacOS version ready
Ubuntu PPAs currently building (will take a few hours)

I still can't see the Ubuntu Mandatory update available.

Code:

biblepayd is already the newest version (1.1.9.9g-xeniall).

For some reason it takes some time for the update system to obtain the latest version from the repo, even if compiling finished 1-2 hours ago.

In this particular case, right now all my linux nodes have "found" the latest version, so please try now.

Strange... I don't get the last version. What PPA are you using?

Is this the official one? : http://ppa.launchpad.net/biblepay/stable/ubuntu

capulo

newbie

Activity: 491

Merit: 0

Quote from: Lichtsucher on March 15, 2019, 03:40:57 AM

The older Ubuntu PPA compiles the new release right now. After that is finished, Purepool will be updated (again...)

what about other releases? i was trying some i think 17.04 ubuntu and there was only 1.1.3.8 or so ...

MIP

newbie

Activity: 362

Merit: 0

Quote from: afeno on March 15, 2019, 03:25:29 AM

Quote from: MIP on March 15, 2019, 12:39:19 AM

Quote from: bible_pay on March 14, 2019, 11:12:17 PM

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

MacOS version ready
Ubuntu PPAs currently building (will take a few hours)

I still can't see the Ubuntu Mandatory update available.

Code:

biblepayd is already the newest version (1.1.9.9g-xeniall).

For some reason it takes some time for the update system to obtain the latest version from the repo, even if compiling finished 1-2 hours ago.

In this particular case, right now all my linux nodes have "found" the latest version, so please try now.

Lichtsucher

jr. member

Activity: 219

Merit: 3

The older Ubuntu PPA compiles the new release right now. After that is finished, Purepool will be updated (again...)

afeno

jr. member

Activity: 175

Merit: 1

Quote from: MIP on March 15, 2019, 12:39:19 AM

Quote from: bible_pay on March 14, 2019, 11:12:17 PM

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

MacOS version ready
Ubuntu PPAs currently building (will take a few hours)

I still can't see the Ubuntu Mandatory update available.

Code:

biblepayd is already the newest version (1.1.9.9g-xeniall).

pagalo

newbie

Activity: 52

Merit: 0

I have just resynced a wallet that had almost 1.2M an now it shows only about 37K.

Where have gone all the other coins?

Is it possible that I was on wrong fork all that time (about 1+ year)?

pagalo

newbie

Activity: 52

Merit: 0

What is the node we use in conf file?

explorer.biblepay.org is correct?

It shows block 106827

capulo

newbie

Activity: 491

Merit: 0

Quote from: zthomasz on March 14, 2019, 09:35:40 PM

7 nodes total, 6 different block numbers, 2 nodes with the same number (107021).

overnight i got same result, i have 7 wallets, one crashed, others are on 5 different block numbers
going to try new release...

EDIT: all wallets goes back in time

block # is lower than yesterday

JennyR

newbie

Activity: 5

Merit: 0

Quote from: MIP on March 15, 2019, 12:39:19 AM

Quote from: bible_pay on March 14, 2019, 11:12:17 PM

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

MacOS version ready
Ubuntu PPAs currently building (will take a few hours)

And thank you too, MIP, for all you do. May the Lord reward your efforts!

SEO_Account

newbie

Activity: 94

Merit: 0

getblockhash 107111 d4eeec5f27d9b9b3c8744616f98a3aa5214f02d8a3814867d8df1e22cf4dce82 good?

MIP

newbie

Activity: 362

Merit: 0

Quote from: bible_pay on March 14, 2019, 11:12:17 PM

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

MacOS version ready
Ubuntu PPAs currently building (will take a few hours)

JennyR

newbie

Activity: 5

Merit: 0

Quote from: bible_pay on March 14, 2019, 11:10:05 PM

Quote from: bible_pay on March 14, 2019, 09:39:56 PM

Quote from: thesnat21 on March 14, 2019, 08:58:47 PM

Quote from: bible_pay on March 14, 2019, 08:32:29 PM

Ok it makes a little more sense now, I believe I see the lions share of the problem (IE bigger than reorganizing).

Ive got two nodes that dont agree here, both consider one of the forks valid but node 2 is following a shorter chain.
Looking at the log on node2, it feels the list of sanctuaries is different than node1. Another words, it has a view of sanctuary payments that differs from other parts of our network.

So basically the sanctuary payment is enforced with a hard rule - and this can cause a fork. We need to either A) Sync all the sancs, or B) Temporarily not enforce that sancs get paid properly.

Ill work on B at a network level now.

Sancs: Please try to sync to the top so your data can synchronize.

We will need to know what the "top" is.. I have 3 different chains i'm seeing

Ive confirmed we need a mandatory upgrade for the entire network to turn off the switch, then we sync to the top, the top stays the top, then in a couple days we will re-enable the spork.

So for now, please disregard my comment about the Top.

The new version will be out in less than one hour.

Thanks for everyones patience.

One other reason this happened is we have GIN hosting a fair amount of Sancs and they are on the old chain (as I really dont want to have them upgrade until we are synced) - exacerbating the problem. (Their sancs are not in agreement with heights from 1199 sancs, so no masternode winners can be calculated yet).

Thank you, Rob for your hard work. May the Lord grant you strength and His Holy Spirit to bring stability in this critical time. We need all of us to work together. May you bear the fruit of His Spirit, Gal 5:22-23 as a witness to our Risen Saviour.

alm-2000

newbie

Activity: 9

Merit: 0

Quote from: bible_pay on March 14, 2019, 04:49:58 PM

Quote from: alm-2000 on March 14, 2019, 02:42:17 PM

What happen with my BPP?
At 12.03 i have more than 40k bpp. Today i start 1.1.9.9g wallet and i have only 4 763 bpp.
I tried to restore the wallet from 2019-03-12-13, but the balance is the same

Coins mined on a fork are not yours.

Ok. I solve this problem. I do:
dumpwallet
delete wallet.dat
importwallet
And 24k of my coins return. The remaining coins seem to have been mined after POBH

harrisvan87

newbie

Activity: 81

Merit: 0

Quote from: bible_pay on March 14, 2019, 11:12:17 PM

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

No Source Block . Can you give the secure node to add in wallet conf

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

1.2.0.1 - BiblePay - Mandatory Upgrade

- Disable sanctuary payment verification until a future spork is activated

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bible_pay on March 14, 2019, 09:39:56 PM

Quote from: thesnat21 on March 14, 2019, 08:58:47 PM

Quote from: bible_pay on March 14, 2019, 08:32:29 PM

Ok it makes a little more sense now, I believe I see the lions share of the problem (IE bigger than reorganizing).

Ive got two nodes that dont agree here, both consider one of the forks valid but node 2 is following a shorter chain.
Looking at the log on node2, it feels the list of sanctuaries is different than node1. Another words, it has a view of sanctuary payments that differs from other parts of our network.

So basically the sanctuary payment is enforced with a hard rule - and this can cause a fork. We need to either A) Sync all the sancs, or B) Temporarily not enforce that sancs get paid properly.

Ill work on B at a network level now.

Sancs: Please try to sync to the top so your data can synchronize.

We will need to know what the "top" is.. I have 3 different chains i'm seeing

Ive confirmed we need a mandatory upgrade for the entire network to turn off the switch, then we sync to the top, the top stays the top, then in a couple days we will re-enable the spork.

So for now, please disregard my comment about the Top.

The new version will be out in less than one hour.

Thanks for everyones patience.

One other reason this happened is we have GIN hosting a fair amount of Sancs and they are on the old chain (as I really dont want to have them upgrade until we are synced) - exacerbating the problem. (Their sancs are not in agreement with heights from 1199 sancs, so no masternode winners can be calculated yet).

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: thesnat21 on March 14, 2019, 08:58:47 PM

Quote from: bible_pay on March 14, 2019, 08:32:29 PM

Ok it makes a little more sense now, I believe I see the lions share of the problem (IE bigger than reorganizing).

Ive got two nodes that dont agree here, both consider one of the forks valid but node 2 is following a shorter chain.
Looking at the log on node2, it feels the list of sanctuaries is different than node1. Another words, it has a view of sanctuary payments that differs from other parts of our network.

So basically the sanctuary payment is enforced with a hard rule - and this can cause a fork. We need to either A) Sync all the sancs, or B) Temporarily not enforce that sancs get paid properly.

Ill work on B at a network level now.

Sancs: Please try to sync to the top so your data can synchronize.

We will need to know what the "top" is.. I have 3 different chains i'm seeing

Ive confirmed we need a mandatory upgrade for the entire network to turn off the switch, then we sync to the top, the top stays the top, then in a couple days we will re-enable the spork.

So for now, please disregard my comment about the Top.

The new version will be out in less than one hour.

Thanks for everyones patience.

zthomasz

member

Activity: 489

Merit: 12

7 nodes total, 6 different block numbers, 2 nodes with the same number (107021).

eternalenvoy

newbie

Activity: 56

Merit: 0

However, No matter where you are on which chain, the process end automatically after a period of time, whether in LINUX or WINDOWS.

Tested by different machine with delete the biblepaycore folder completely every time.

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 191. (Read 243437 times)