Messages

61

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 09:00:13 PM »

Can you please double click on the PODC Update transaction it sent and paste the txid? 

I dont think switching CPID (addresses) will help, it sounds as if yours needs -zapwallettxes first, then wait for 6 confirms, then send all at once?
This is strange  - I dont mind putting more diagnostic harnesses in exec podcupdate, but I think we will figure this out pretty easily.

Hi Rob, my wallet is updating but I got it from here
https://biblepay-explorer.org/address/BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM

38675844148c7aac09169282d280acdd7aeca210b1630df9e29104cbac1e24a3

Many thanks!

62

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 08:33:41 PM »

Luke,
There is a secret command, this is only good for internal use not network use, try this:
'exec memorizeprayers', 'exec datalist utxoweight'.  The memorizeprayers forces the client to load any unconfirmed tx into memory (as if 6 went by), let me know if it goes up to 100 after that.

Hi Rob.
Unfortunately I am still on 25 for UTXO weight.
Is there a way to delete the other wallet receiving address?
 
Thanks

EDIT: just for clarity, I did the memorizeprayers command

63

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 08:18:15 PM »

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.

Hi Rob,

before I saw you posted this I had already sent a transaction to myself to my CPID address.

After 6 confirmations:

Code: [Select]

"Command": "podcupdate",
  "PODCUpdate": "true"
Great!

Code: [Select]

"Command": "stakebalance",
  "StakeBalance": 109919
looking good

Code: [Select]

"8f273b30f8e0a298ed26e242762df701_RAC": 41662.59,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 41662.59,
Oh so close!
So UTXO is still 25. Should I just give it a bit of time, or should I try sending to the other address?

Thanks!
Luke

64

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 07:09:22 PM »

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]

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

65

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 07:03:29 PM »

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

66

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 06:58:53 PM »

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]

"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

67

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 06:39:16 PM »

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]

"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.

68

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 06:09:46 PM »

Ok so updated!
I am on linux qt, unlocked wallet

exec podcupdate true

Code: [Select]

{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}
exec stakebalance

Code: [Select]

{
  "Command": "stakebalance",
  "StakeBalance": 110009
}

exec getboincinfo

Code: [Select]

"8f273b30f8e0a298ed26e242762df701_RAC": 41174.76,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 41174.76,

Hmmm, not sure what is going on. Should i try sending my coins from the wallet and then back in again?

Thanks

69

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 05:39:45 PM »

Yes, please try 'exec stakebalance' first, then set polpercentage to the correct percent, then grab the latest version, then after it starts and wallet is unlocked, try :

exec podcupdate true

The true = force, then double click on the sent Tx, and see if its high enough to make UTXO =100 (50K).

Good luck.


Edit: windows is compiling but almost finished.

Awesome

Code: [Select]

"Command": "stakebalance",
  "StakeBalance": 110009
Config file

Code: [Select]

addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network 
gen=1
genproclimit=1
polpercentage=100
I'll update now.
Thanks

70

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 05:29:59 PM »

Hi Rob, since my UTXO is stuck at 25, should I try downloading the new version and  "exec podcupdate force"?
 

71

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 04:19:17 PM »

Welcome back Luke!

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC?

->  Were still ensuring this PODC chain has integrity,  we should know within 25 more blocks or so that it appears solid.  Then we can ask Togo if hes on the same chain as us.


2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet?
->  Actually this leisure is just a couple small items to show more info in exec podcupdate, dont worry about it now, because Im going to be adding another option now for exec podcupdate....  Sancs do not need to upgrade.


3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet?
-> Only if you have orphaned transactions in your wallet.


4. Anything else I should be doing now?
-> Just check exec getboincinfo to ensure you have full weight on both.

Awesome thanks Rob.

getblockhash 33445

Code: [Select]

201ce2c68c5d520873037429fa644ca1180569a059f052621030e7152f4c5fd3
So I seem to be on the correct chain

exec stakebalance

Code: [Select]

"Command": "stakebalance",
  "StakeBalance": 110009
So I have plenty of stake

exec getboincinfo

Code: [Select]

"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422350,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 40580.95,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 40580.95,

TaskWeight is good!
But still confused as to why UTXOWeight is not 100.

Thanks!

72

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 03:35:41 PM »

i zapped all of mine just to be sure.

Awesome, thanks. I just realised that I have some addnodes in my config. This was from my old PoBH wallet. But some of these nodes could be on different chains?

What addnode addresses should I have in my config?

73

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 03:31:50 PM »

Thanks mike. Should I be zapping all 3 wallets or just PoDC one?

74

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 03:00:08 PM »

Hi guys,
Woke up this morning excited to see how we go today!

Lot's of posts! Can I please ask the following for clairty's sake:

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC?

2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet?

3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet?

4. Anything else I should be doing now?

Many thanks

75

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 07, 2018, 06:10:54 AM »

33400 should be when the new protocol kicks off. But there is already been a fork between those who upgraded and those who didn't for other reasons. So if you upgraded, you are already on a new chain.

Edit:

Just to make to make it clear. It's not (or shouldn't be PoDC yet), it just forked for other reasons. Probably by forcing new clients to drop the connection from old clients. Both chains should still be exclusively PoBH right now.

Awesome, thanks. That's clear and makes sense.