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

Started by Rob Andrews, February 06, 2018, 04:00:36 PM

Previous topic - Next topic

Rob Andrews

Quote from: jaapgvk on March 08, 2018, 03:32:56 PM
Yes, it was made from the pool. You were surprised that it worked at the time because it the pool wasn't upgraded yet (don't know which wallet the pool was on but it was at least pre 1.0.9.9. I think).
Hi Jaap,
I think that is the problem; looking at the burn record, its missing a field.  The pool was running old software when we created the "unbanked" protocol version.  So it signed the CPID the old way.  I just upgraded the pool server to 1106.

Will you please try to re-associate your unbanked CPID from the pool now?

Then after 5 confirms, lets look at this again and see if the exec dcc actually pulls the unbanked cpid in.

It will be interesting how many votes your contract gets vs. the prod contract.


jaapgvk

Quote from: Rob A. on March 08, 2018, 03:45:30 PM
Hi Jaap,
I think that is the problem; looking at the burn record, its missing a field.  The pool was running old software when we created the "unbanked" protocol version.  So it signed the CPID the old way.  I just upgraded the pool server to 1106.

Will you please try to re-associate your unbanked CPID from the pool now?

Then after 5 confirms, lets look at this again and see if the exec dcc actually pulls the unbanked cpid in.

It will be interesting how many votes your contract gets vs. the prod contract.

Hi Rob,

I just tried and it said:
"RPC Error"

Rob Andrews

Quote from: jaapgvk on March 08, 2018, 04:42:59 PM
Hi Rob,

I just tried and it said:
"RPC Error"

Oh wow, OK, please ensure the screen says v1.2 and please try again?


jaapgvk

Quote from: Rob A. on March 08, 2018, 04:52:20 PM
Oh wow, OK, please ensure the screen says v1.2 and please try again?

Forgot to refresh :o It said 1.2 now (but the confirmation screen still says 1.1).

It now said: "private key not available" (see screenshot).

Rob Andrews

Congratulations and thank you all for a successful PODC Go-Live!


(I'll keep this thread open so we can finish the finer details...)


Rob Andrews

Quote from: jaapgvk on March 08, 2018, 04:56:51 PM
Forgot to refresh :o It said 1.2 now (but the confirmation screen still says 1.1).

It now said: "private key not available" (see screenshot).


Hmm, OK Ill check further in a little bit.

Ichthus220

I change utxoweight to 50001 and utxo is still showing 75. Any ideas?

T-Mike

Quote from: Ichthus220 on March 08, 2018, 06:45:43 PM
I change utxoweight to 50001 and utxo is still showing 75. Any ideas?
utxoamount=50001
then do exec podcupdate true
and wait a few blocks

T-Mike

Shouldn't the network hashrate be lower than 7.6 ghs/s? Is solo mining feasible now?

Ichthus220

Quote from: T-Mike on March 08, 2018, 06:54:53 PM
utxoamount=50001
then do exec podcupdate true
and wait a few blocks

This is what I get when I try to exec podcupdate true. I have 50010.99 in my wallet.


19:01:52

exec podcupdate true


19:02:00

{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (10.00) less than target UTXO (50001.00)."
}

T-Mike

Quote from: Ichthus220 on March 08, 2018, 07:04:21 PM
This is what I get when I try to exec podcupdate true. I have 50010.99 in my wallet.


19:01:52

exec podcupdate true


19:02:00

{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (10.00) less than target UTXO (50001.00)."
}


The staking BBP needs to have 6 or more confirmations. try exec stakebalance and see if it's 50,001 or above or go into coin control and see if you have more than 50,001 BBP that have more than 6 confirmations.

Ichthus220

Quote from: T-Mike on March 08, 2018, 07:11:05 PM
The staking BBP needs to have 6 or more confirmations. try exec stakebalance and see if it's 50,001 or above.

Staking showed over 50k so I ran exec podcupdate true. I will wait 6 confirmations and check utxo again.


19:12:32

exec podcupdate true


19:12:41

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (25) over 1 CPID(s) successfully."
}

T-Mike

Quote from: Ichthus220 on March 08, 2018, 07:14:27 PM
Staking showed over 50k so I ran exec podcupdate true. I will wait 6 confirmations and check utxo again.


19:12:32

exec podcupdate true


19:12:41

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (25) over 1 CPID(s) successfully."
}


Look at the podcupdate transaction, how much did it send to yourself?

Ichthus220

Quote from: T-Mike on March 08, 2018, 07:41:30 PM
Look at the podcupdate transaction, how much did it send to yourself?

Thanks! Already showing UTXO 100.
Status: 2/unconfirmed
Date: 3/8/2018 19:12
Source: PODC-Update
Total debit: -50 001.00000000 Biblepay
Total credit: 50 001.00000000 Biblepay
Transaction fee: -0.00042040 Biblepay
Net amount: -0.00042040 Biblepay

Height: 33628
Difficulty: 90.597458
Time: 03-09-2018 01:19:59
Subsidy: 554.3015

T-Mike

Quote from: Ichthus220 on March 08, 2018, 07:45:30 PM
Thanks! Already showing UTXO 100.
Status: 2/unconfirmed
Date: 3/8/2018 19:12
Source: PODC-Update
Total debit: -50 001.00000000 Biblepay
Total credit: 50 001.00000000 Biblepay
Transaction fee: -0.00042040 Biblepay
Net amount: -0.00042040 Biblepay

Height: 33628
Difficulty: 90.597458
Time: 03-09-2018 01:19:59
Subsidy: 554.3015


Oh good that's correct. So just wait a little bit.