BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

yes there are more "double, triple" blocks... those are tx, not blocks...
But.. now I've created new clean wallet without pwd.
Trying send there some BBP, but the network refused it:

Code: [Select]

Status: 0/unconfirmed (InstantSend verification failed), broadcast through 16 nodes
Date: 06.03.2018 18:58
To: PODC BALzAYQ9hKU2CziuRxXWf4R3ceAbAkpBLP
Debit: -10.00000000 Biblepay
Transaction fee: -0.00100000 Biblepay
Net amount: -10.00100000 Biblepay

MESSAGE:
Transaction ID: 1990c18555577a7b72dab323fe5ed88cf803bcb4a06267e595b9882714bc73c4-000

Please try sending it without instant send - I could see the sancs being in a sad state of affairs right now.

Rob,
please can you give me some good node address?
Sending without instant send  but still not successful.

I have:
addnode=node.biblepay.org 
addnode=biblepay.inspect.network 

Rob,
please can you give me some good node address?
Sending without instant send  but still not successful.

I have:
addnode=node.biblepay.org 
addnode=biblepay.inspect.network

I haven't been able to transfer any funds either, 0 confirmations.

I haven't been able to transfer any funds either, 0 confirmations.

Srry, Havent even read all my emails yet this morning, this is crazy.

Let me give that a try in prod.

Looks like most of the problem is 87% of our network is still on 1.0.8.7 and down.
Thats heinously bad for PODC, since any tx larger than 1K is rejected (and a lot are bigger than that, when we have task count like Togo has).

So I think we are going to need to march forward and go with a mandatory and pray for the best, pray that we caught all the major bugs and that anything we find going forward is a leisure fix.

Ill get ready to announce a mandatory upgrade in prod.

Looks like most of the problem is 87% of our network is still on 1.0.8.7 and down.
Thats heinously bad for PODC, since any tx larger than 1K is rejected (and a lot are bigger than that, when we have task count like Togo has).

So I think we are going to need to march forward and go with a mandatory and pray for the best, pray that we caught all the major bugs and that anything we find going forward is a leisure fix.

Ill get ready to announce a mandatory upgrade in prod.

OK, so I'm assuming we just keep going on the current version or will there be a new version?

Right now my CPID is still attached to my old wallet even though I have already moved it.

Code: [Select]


14:55:18

exec getboincinfo


14:55:18

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422323,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 10694.06,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 0,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 10694.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

But on Rosetta it is showing my new wallet's address:
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1981209

Not sure if the network will automatically correct everything.

Looks like most of the problem is 87% of our network is still on 1.0.8.7 and down.
Thats heinously bad for PODC, since any tx larger than 1K is rejected (and a lot are bigger than that, when we have task count like Togo has).

So I think we are going to need to march forward and go with a mandatory and pray for the best, pray that we caught all the major bugs and that anything we find going forward is a leisure fix.

Ill get ready to announce a mandatory upgrade in prod.

I was trying to send 1BBP, 10BBP, but still without success.

I was trying to send 1BBP, 10BBP, but still without success.

I confirm, I cannot get my BBP to be inducted into a block either- it says confirmed by 8 peers but sits unconfirmed.

The good news is at block 33400, we require a signed CPID.  So otherwise I would offer to create a version with 1102+ blocks only, but its fruitless as for one, we have most of the network upgrading now, and 2) PODC basically does that during the hard fork.  I suppose we can let the botnet get the last 98 more blocks and with optimism, make it through 33400 and start confirming.

I obviously wish with upgrades over the next 2 hours we start confirming again.

I see there are 109 transactions in the memory pool - they are piling up.  The botnet miners are not accepting our transactions, but they have the supermajority hashpower.

Hi Rob, all,

Sorry Rob I was asleep (we are in a funny time zone here at the bottom of the world!).

Firstly, this is an exciting day! Rob, you are doing a great job of what must be very busy, challenging, and potentially stressful. Thank you for your time and effort for what I think will be very very worthwhile.

Ok so this morning I checked and my TaskWeight =100 but my UTXO =0.
I have been in prod for with PoDC for the last two days over various versions and everntually taskweight always goes to 100, but I have never had UTXO anything other than 0, despite having plenty of funds in my address.

This morning I woke up, updated my PoDC wallet to the latest version, updated my sanctuary wallet (is now pre-enabled), and my controller wallet. So hopefully I am doing my share!

Ok, now that my PoDC wallet is updated, a few tests:

1.  exec getboincinfo

Code: [Select]

"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422324,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 34231.68,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 34231.68,
(I shortened the output here)
2. exec podcupdate

Code: [Select]

"Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance too low."
3. exec stakebalance

Code: [Select]

"Command": "stakebalance",
  "StakeBalance": 0


As noted above, my receiving address which is linked to my CPID is   "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",.
Just to prove it has funds:
http://explorer.biblepay.org:3001/address/BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq


So I am not sure what the problem is... I must admit to being a little nervous.

Some thoughts, Rob I would appreciate advice as you have time.

A) Perhaps I should re-associate my CPID? I associated it in prod around 3 or 4 wallet versions ago. But Have never had UTXO...
B) If I type getaccountaddress ""  I get

Code: [Select]

B9a1HK9QxmpFRvUffcN7FjXT3odPdFBBJa
Which is a different one from my CPID address. Is this an issue for my UTXO?

Thanks

I confirm, I cannot get my BBP to be inducted into a block either- it says confirmed by 8 peers but sits unconfirmed.

The good news is at block 33400, we require a signed CPID. 

Ok. So, if I have signed CPID, but task and UTXO are 0 it will be ok?

I see there are 109 transactions in the memory pool - they are piling up.  The botnet miners are not accepting our transactions, but they have the supermajority hashpower.

And what will be with those tx after block 33400? They would be accepted? Because I've tried to send something many times. I hope now, that those tx will be dissapeared

Hi Rob, all,

Sorry Rob I was asleep (we are in a funny time zone here at the bottom of the world!).

Firstly, this is an exciting day! Rob, you are doing a great job of what must be very busy, challenging, and potentially stressful. Thank you for your time and effort for what I think will be very very worthwhile.

Ok so this morning I checked and my TaskWeight =100 but my UTXO =0.
I have been in prod for with PoDC for the last two days over various versions and everntually taskweight always goes to 100, but I have never had UTXO anything other than 0, despite having plenty of funds in my address.

This morning I woke up, updated my PoDC wallet to the latest version, updated my sanctuary wallet (is now pre-enabled), and my controller wallet. So hopefully I am doing my share!

Ok, now that my PoDC wallet is updated, a few tests:

1.  exec getboincinfo

Code: [Select]

"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422324,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 34231.68,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 34231.68,
(I shortened the output here)
2. exec podcupdate

Code: [Select]

"Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance too low."
3. exec stakebalance

Code: [Select]

"Command": "stakebalance",
  "StakeBalance": 0


As noted above, my receiving address which is linked to my CPID is   "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",.
Just to prove it has funds:
http://explorer.biblepay.org:3001/address/BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq


So I am not sure what the problem is... I must admit to being a little nervous.

Some thoughts, Rob I would appreciate advice as you have time.

A) Perhaps I should re-associate my CPID? I associated it in prod around 3 or 4 wallet versions ago. But Have never had UTXO...
B) If I type getaccountaddress ""  I get

Code: [Select]

B9a1HK9QxmpFRvUffcN7FjXT3odPdFBBJa
Which is a different one from my CPID address. Is this an issue for my UTXO?

Thanks

Thanks Luke, I appreciate it.

Jumping to the issue : exec podcupdate, with response: balance too low.
(Your right, the exec stakebalance is what podcupdate uses to make a utxo, so we need to get that > 0 first).
Could you please check the following, the stakebalance calculation is : Any unlocked coin with more than 5 confirmations.
Please go to coin control and loop through your Unlocked coin entries, there is a confirmations count on the right, see if you have any that are deeper than 5?  This will be interesting

So I am not sure what the problem is... I must admit to being a little nervous.

Some thoughts, Rob I would appreciate advice as you have time.

A) Perhaps I should re-associate my CPID? I associated it in prod around 3 or 4 wallet versions ago. But Have never had UTXO...
B) If I type getaccountaddress ""  I get

Code: [Select]

B9a1HK9QxmpFRvUffcN7FjXT3odPdFBBJa
Which is a different one from my CPID address. Is this an issue for my UTXO?

Thanks

Hi, we are little bit stressed too
We have same problems like you. We're not able to send any tx, because the botnet with old wallets have supermajority and he didn't accept new wallet version.
So we've must wait till block 33400 and hoping in bright future

Thanks Luke, I appreciate it.

Jumping to the issue : exec podcupdate, with response: balance too low.
(Your right, the exec stakebalance is what podcupdate uses to make a utxo, so we need to get that > 0 first).
Could you please check the following, the stakebalance calculation is : Any unlocked coin with more than 5 confirmations.
Please go to coin control and loop through your Unlocked coin entries, there is a confirmations count on the right, see if you have any that are deeper than 5?  This will be interesting

Hi Rob,

I'm not sure how to do the coin control loop thing. But If I go to the transactions tab (Linux, qt mode) then I can see that my 110k transaction has >200 confirmations (image attached).

Since then the wallet has tried to send tiny payments to itself 3 times. All three of these have 0 confirmations. Again please see images attached.

Is that what you wanted to see? Otherwise could someone please help me to see how to do coin control and looping?

Thanks

Ok. So, if I have signed CPID, but task and UTXO are 0 it will be ok?
And what will be with those tx after block 33400? They would be accepted? Because I've tried to send something many times. I hope now, that those tx will be dissapeared

No problem on the double spend- the wallet will only spend your old UTXO once - because it originates in only one place - the source of the funds is in one block, one txid, one vout, and one position only.
So the *later* spend on the vout would stay conflicted and orphaned in your txlist until you reboot with -zapwallettxes

I was just thinking, we probably shot ourselves in the foot a little by forcing the mandatory version and not having a rule to reject blocks < 1100.  Its a little too late to talk about that, only 97 blocks to go now.

Anyway, I believe the problem is due to network segmentation, the botnets miners will not honor our transactions!

No problem on the double spend- the wallet will only spend your old UTXO once - because it originates in only one place - the source of the funds is in one block, one txid, one vout, and one position only.
So the *later* spend on the vout would stay conflicted and orphaned in your txlist until you reboot with -zapwallettxes

I was just thinking, we probably shot ourselves in the foot a little by forcing the mandatory version and not having a rule to reject blocks < 1100.  Its a little too late to talk about that, only 97 blocks to go now.

Anyway, I believe the problem is due to network segmentation, the botnets miners will not honor our transactions!

But I'm afraid of that after 33400 will my BBPs flows to other wallets and I won't be able to have UTXO 100 because of that
50 blocks later I was calm, but after 33400 won't be time to take my BBP back to be counted