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

[Rob Andrews]

That doesn't appear to work either, I just downloaded the latest windows wallet also. There is nothing in debug after I ran the command, no new transactions either.

exec podcupdate true

{
  "Command": "podcupdate",
  "PODCUpdate": ""
}

The empty string means no errors occurred.  Are you sure your txlist does not have a new tx?  You might have it sorted wrong.
Maybe try the zapwallettxes first, then do it, then sort txlist by Received descending, then look for it?

I just grabbed that win wallet and repaired mine ( I had a 50% weight and it just worked for me ).

If then all that doesnt work then lets see if you have a debug entry.

[znffal]

Hmm, how bout try polpercentage=90, just to see if the math of 100 is causing it to try to send more than the total including the tx fee?

EDIT: Also you can try 'sendtoaddress your_bbp_address 1' just to ensure it goes out successfully first.

Thanks Rob.

I did that (and sent in another 10 BBP to my CPID address from my main wallet). Ran again

exec podcupdate true

Code Select Expand

"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Rob is it possible that this is an issue: My default wallet address is different to my CPID associated one?
When I was trying to help someone figure out the command to find an address balance i think I accidentally created a new one. Now when I type

getaccountaddress ""

I get a different address (still in my wallet) but different to the one assigned to my CPID.
Stake is in CPID address though.

[T-Mike]

The empty string means no errors occurred.  Are you sure your txlist does not have a new tx?  You might have it sorted wrong.
Maybe try the zapwallettxes first, then do it, then sort txlist by Received descending, then look for it?

I just grabbed that win wallet and repaired mine ( I had a 50% weight and it just worked for me ).

If then all that doesnt work then lets see if you have a debug entry.

OK, it finally worked after I upgraded the wallet to 1.1.0.4 and did zapwallettxes=1, not sure which one fixed it. Thanks!

When will the magnitude start going up?

[jaapgvk]

Thanks Rob.

I did that (and sent in another 10 BBP to my CPID address from my main wallet). Ran again

exec podcupdate true

Code Select Expand

"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Rob is it possible that this is an issue: My default wallet address is different to my CPID associated one?
When I was trying to help someone figure out the command to find an address balance i think I accidentally created a new one. Now when I type

getaccountaddress ""

I get a different address (still in my wallet) but different to the one assigned to my CPID.
Stake is in CPID address though.

It's not a well informed suggestion from my part, but did you already try the 'zapwallet' command? It solved my problems at least (had the same problem Orbis had, with the 'insufficient funds' error).

Anyway, I'm going to get some sleep now guys. It's been an exhilarating couple of days, but let's try and not make this a regular thing, haha!

Rob: thank you for all your hard work and perseverance.  Let's make Biblepay something to reckon with!

[Rob Andrews]

It's not a well informed suggestion from my part, but did you already try the 'zapwallet' command? It solved my problems at least (had the same problem Orbis had, with the 'insufficient funds' error).

Anyway, I'm going to get some sleep now guys. It's been an exhilarating couple of days, but let's try and not make this a regular thing, haha!

Rob: thank you for all your hard work and perseverance.  Let's make Biblepay something to reckon with!

Thanks, and have a good nights sleep.

[Rob Andrews]

OK, it finally worked after I upgraded the wallet to 1.1.0.4 and did zapwallettxes=1, not sure which one fixed it. Thanks!

When will the magnitude start going up?

Once the first superblock hits:  block 33620. 

That reminds me we need to test the testvote again, one minute.

[znffal]

It's not a well informed suggestion from my part, but did you already try the 'zapwallet' command? It solved my problems at least (had the same problem Orbis had, with the 'insufficient funds' error).

Anyway, I'm going to get some sleep now guys. It's been an exhilarating couple of days, but let's try and not make this a regular thing, haha!

Rob: thank you for all your hard work and perseverance.  Let's make Biblepay something to reckon with!

Thanks! I just tried and upfortnately I still have UTXO weight 25 and exec podcupdate true giving

Code Select Expand

"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Should I reassociate my cpid again? Totally delete wallet and start again?

EDIT: Oh I see there is a new version. I will try updating to that first

[Rob Andrews]

Great news, block 33460 & 33461 were both signed by CPIDS!

CPID 7c9264559fef3c1c689ee9fc3ff42494 was awarded for our first PODC - CPID heat payment: 555 BBP!  Congrats!


showblock 33460 to see the blocks CPID info.

[Rob Andrews]

Thanks! I just tried and upfortnately I still have UTXO weight 25 and exec podcupdate true giving

Code Select Expand

"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Should I reassociate my cpid again? Totally delete wallet and start again?

EDIT: Oh I see there is a new version. I will try updating to that first

Luke- I have to take a look at the code that actually spends the podcupdate.  In the mean time, you said you had two addresses one unlabled and one default I think, but to clarify, ensure the 'getboincinfo' receive addresses is one actually contained in your File | Receiving Addresses list?

If so you do not have to reassociate.  I would try instantsending your balance back to your default address, and then retry the exec podcupdate.

Ill check that "spend" code asap to see if this is going to be a nuisance.

[znffal]

Luke- I have to take a look at the code that actually spends the podcupdate.  In the mean time, you said you had two addresses one unlabled and one default I think, but to clarify, just ensure the actual wallet.dat has the receiveing address corresponding to your CPID?  Another words exec getboincinfo should show a row for the receive address.  Ensure that is one of that particular wallet.dat receiving address.

If so you do not have to reassociate.  I would try instantsending your balance back to your default address, and then retry the exec podcupdate.

Ill check that "spend" code asap to see if this is going to be a nuisance.

Thanks Rob. Just installing the new version then I will try those thing.
Thanks
Luke

[znffal]

Luke- I have to take a look at the code that actually spends the podcupdate.  In the mean time, you said you had two addresses one unlabled and one default I think, but to clarify, ensure the 'getboincinfo' receive addresses is one actually contained in your File | Receiving Addresses list?

If so you do not have to reassociate.  I would try instantsending your balance back to your default address, and then retry the exec podcupdate.

Ill check that "spend" code asap to see if this is going to be a nuisance.

Wow it was a quick update.

exec getboincinfo

Code Select Expand

Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD...etc etc",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
etc etc


My receiving addresses are in the attachment. I assume this is correct?
I will send myself some coins now

Thanks

[Rob Andrews]

Wow it was a quick update.

exec getboincinfo

Code Select Expand

Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD...etc etc",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
etc etc


My receiving addresses are in the attachment. I assume this is correct?
I will send myself some coins now

Thanks

Yeah, your receive address on file matches the boinc address, so that means you can sign for that CPID.

So it must be a matter of the wallet picking the wrong spending account, please try sending the money into the top address then resending the podcupdate, lets see if that works.

[Rob Andrews]

So we are going relatively good now, but I found an issue.  Im looking at the exec testvote output on my sanc, and on the bright side, its generally good and 3 people already voted for it (it needs 5 votes minimum in prod which Im sure it would get eventually), but anyway, the other good news is most of the cpids look like they will have the correct magnitude (we can see the upcoming magnitude by looking in the /SAN directory at the magnitude file), (this is created by our sanc btw), anyway there is a problem with Togo.

Togos magnitude = 0.  It looks like its because his tasks are showing as "tampered" with.  I will look into this issue now.  Oh we were on a roll! LOL.  We'll figure it out before tomorrow gets here.

This might mean a system wide update is required.  Let me debug...

[Ichthus220]

Just updated to 1104. Can someone tell me if all is correct?

getmininginfo

Code Select Expand


19:29:01

getmininginfo


19:29:01

{
  "blocks": 33386,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 0.889502687442315,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 73878209.24980666,
  "hashps": 57.82132996155136,
  "minerstarttime": "03-08-2018 01:26:25",
  "hashcounter": 8963,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 24,
  "poolmining": true,
  "pool_url": "http://pool.biblepay.org",
  "poolmining_use_ssl": false
}


exec getboincinfo

Code Select Expand


19:33:40

exec getboincinfo


19:33:41

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422353,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2726.94,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2726.94,
  "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
}


[togoshigekata]

Togos magnitude = 0.  It looks like its because his tasks are showing as "tampered" with.  I will look into this issue now.

Uh oh!
a few days ago
I overclocked one machine and caused cpu to become unstable, and got a computation error in BOINC, so I aborted that task,
That same machine was also not running for a few days and I had to abort some tasks that were past due

Only thing I can think of recently in the past day
is that I have "merged" some aws machines in BOINC website (because the old ones got terminated)
hope that is not causing issues

I basically just run 4 linux commands and never touch these machines again LOL

So far today I:
1. Sent coins for CPID Burn and Staking
2. Performed CPID Burn through GUI
3. Added polpercentage to config

Were there any commands I needed to run?