Bible Pay

Read 168903 times

  • jaapgvk
  • Hero Member

    • 552


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
You only need to backup your wallet once I believe, even if you added new addresses or had transactions after you backed it up.

That is not necessarily true. As far as I know, the wallet creates a new batch of keys after a certain number have been used (I think it's default number is 1000?), so if you do a lot of transactions, you have to redo your updates.

Also, if you have an unencrypted wallet.dat, and you encrypt it, you have to make a new backup, because the old wallet.dat becomes unusable as I understand it.


  • T-Mike
  • Sr. Member

    • 375


    • 2
    • February 06, 2018, 06:12:58 PM
    more
That is not necessarily true. As far as I know, the wallet creates a new batch of keys after a certain number have been used (I think it's default number is 1000?), so if you do a lot of transactions, you have to redo your updates.

Also, if you have an unencrypted wallet.dat, and you encrypt it, you have to make a new backup, because the old wallet.dat becomes unusable as I understand it.

I think Biblepay usese deterministic wallets so this does not apply. Rob, can you confirm this?


  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I think Biblepay usese deterministic wallets so this does not apply. Rob, can you confirm this?
On walletbackups, the dash subsystem does create a copy of wallet.dat once per boot and copies this file into \backups.  Something like mmddyyyy.dat. 
I recommend keeping a copy of a good wallet offsite - maybe on a CD and USB flash if possible in a safe.

Anyway regarding the necessity to make constant backups:  There is truth to both sides but let me explain this nuance.
It is true, that if you only have one plain vanilla address with all your BBP allocated to that address, no matter how big the physical wallet.dat file gets, you can always get back all your bbp, if you had a backup of that original small file somewhere.  The wallet will expand in size as you resync the chain and you will gain all your BBP back.

The specific issue that requires you to back your wallet more often is this:  If you *add* a receiving address to the wallet, it comes with 1000 keys, if you have been mining for a while, if the action of creating a new address (doing that creates a keypair - a private key and a public wallet address), if that resulted in creating a new keypair that was *not* in the original backup, *and* you send BBP from somewhere to that new address, now that part of your balance is *not* in the original wallet.  Now you need a new backup.

So you either have to cognizently re-send your BBP periodically to your *original* address, and then you are fine, *or* keep backing it up.

Btw, an easy way to understand this is if you loop through your addresses and balances, if you were to type:
dumpprivkey publicbbpaddress
For each address with a balance, you could print those keys out to a printer and have a way to gain access to the BBP if you ever lost the cold wallet backup...

Its also beneficial to consolidate your wallet as the core will run faster, but it also risks a loss of privacy.  The reason the devs made so many keys it to obfuscate your identity.  If you dont care about anonymity, by all means send it all back to one address.  If you do care about anonymity let it bloat and keep backing it up on a regular basis.



  • T-Mike
  • Sr. Member

    • 375


    • 2
    • February 06, 2018, 06:12:58 PM
    more
On walletbackups, the dash subsystem does create a copy of wallet.dat once per boot and copies this file into \backups.  Something like mmddyyyy.dat. 
I recommend keeping a copy of a good wallet offsite - maybe on a CD and USB flash if possible in a safe.

Anyway regarding the necessity to make constant backups:  There is truth to both sides but let me explain this nuance.
It is true, that if you only have one plain vanilla address with all your BBP allocated to that address, no matter how big the physical wallet.dat file gets, you can always get back all your bbp, if you had a backup of that original small file somewhere.  The wallet will expand in size as you resync the chain and you will gain all your BBP back.

The specific issue that requires you to back your wallet more often is this:  If you *add* a receiving address to the wallet, it comes with 1000 keys, if you have been mining for a while, if the action of creating a new address (doing that creates a keypair - a private key and a public wallet address), if that resulted in creating a new keypair that was *not* in the original backup, *and* you send BBP from somewhere to that new address, now that part of your balance is *not* in the original wallet.  Now you need a new backup.

So you either have to cognizently re-send your BBP periodically to your *original* address, and then you are fine, *or* keep backing it up.

Btw, an easy way to understand this is if you loop through your addresses and balances, if you were to type:
dumpprivkey publicbbpaddress
For each address with a balance, you could print those keys out to a printer and have a way to gain access to the BBP if you ever lost the cold wallet backup...

Its also beneficial to consolidate your wallet as the core will run faster, but it also risks a loss of privacy.  The reason the devs made so many keys it to obfuscate your identity.  If you dont care about anonymity, by all means send it all back to one address.  If you do care about anonymity let it bloat and keep backing it up on a regular basis.

Cool, thanks for the clarification.

https://bitcoin.org/en/secure-your-wallet says you don't need to do this anymore in the future. (When is the future?)
https://wiki.bitcoin.com/w/Securing_your_wallet says only 3 wallet types support BIP32 right now.
https://bitcointalk.org/index.php?topic=2484895.0 does say you need to backup. (Not sure about HD wallets.)
https://www.reddit.com/r/dashpay/comments/5wn16h/backups_of_dash_core_how_frequently/ does say you need to back up.

I think it just comes down to if BIP 0032 was implemented.
« Last Edit: March 05, 2018, 07:34:52 AM by T-Mike »


  • T-Mike
  • Sr. Member

    • 375


    • 2
    • February 06, 2018, 06:12:58 PM
    more
My UTXO is still zero after 9 hours, I think I remember you saying I need to wait 24 hours? I updated my production sanctuary and wallet and everything seems to be working fine. I'll let you know when I receive a Sanctuary payment.

Code: [Select]


exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422293,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 4746.2,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 4746.2,
  "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
}

exec datalist dcc

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 13:22:45)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}
« Last Edit: March 05, 2018, 09:00:30 AM by T-Mike »


  • togoshigekata
  • Sr. Member

    • 493


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more

Biblepay 1.0.9.8
Mandatory Upgrade for Testnet


- Handle Rosetta Teams properly - to avoid CPIDs from being skipped in the superblock

** Windows is compiling **

I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet


  • jaapgvk
  • Hero Member

    • 552


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet

I'm updating my sanctuary as we speak...


  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet

Yeah I only updated one of my two so far, but I did jump in 15 mins ago to see how 1.0.9.8 is propagating on the sancs, to see if your CPID, the 9313 made it into any contracts yet, and so far I see since all these sancs are supermajority the old version you have not yet been included- But, I see the next contract : at block 16236, looks like it will have you in it.  I was waiting for this to happen before recommending anyone upgrade Prod sancs.

Ill go ahead and upgrade my other testnet sanc, and wait til we see you receive payment, then if no other bugs occur, we can try to upgrade some of our prod sancs.

Mike, UTXO weight shold not take long - should take 6 blocks - let me do some testing on that before I reply, it might be the conditions in Prod are different - are you referring to your UTXO weight in prod or test?



  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet

Nice avatar Togo, thats wild!


1.0.9.8 is out there now for windows...




  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
My UTXO is still zero after 9 hours, I think I remember you saying I need to wait 24 hours? I updated my production sanctuary and wallet and everything seems to be working fine. I'll let you know when I receive a Sanctuary payment.

Code: [Select]


exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422293,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 4746.2,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 4746.2,
  "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
}

exec datalist dcc

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 13:22:45)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}

Mike-
In testnet your e94 CPID has a 100 weight as of a few hours ago: E94C1704C75F731F8BFDE303F08408EE (03-05-2018 12:31:08)": "100
(exec datalist utxoweight) alluding to the fact that since you have multiple cpids, you probably didnt leave the controller wallet on long enough to send 5 UTXO's out.  Each CPID requires a separate UTXO.  So it might have looped through 4 of your CPIDS and Failed to send the 5th until you manually triggered  it a few hours ago... 

This is a good reason in Prod we should have One cpid, of course for testing, I realize this is why we have multiple CPIDs.



  • jaapgvk
  • Hero Member

    • 552


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Yeah I only updated one of my two so far, but I did jump in 15 mins ago to see how 1.0.9.8 is propagating on the sancs, to see if your CPID, the 9313 made it into any contracts yet, and so far I see since all these sancs are supermajority the old version you have not yet been included- But, I see the next contract : at block 16236, looks like it will have you in it.  I was waiting for this to happen before recommending anyone upgrade Prod sancs.

Ill go ahead and upgrade my other testnet sanc, and wait til we see you receive payment, then if no other bugs occur, we can try to upgrade some of our prod sancs.

Mike, UTXO weight shold not take long - should take 6 blocks - let me do some testing on that before I reply, it might be the conditions in Prod are different - are you referring to your UTXO weight in prod or test?

I think I'm having the same problems that Mike has (in prod): I can't use the 'podcupdate' command and don't get Task/UTXO weight after 6+ blocks.

Code: [Select]
16:11:48

exec podcupdate


16:12:28

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

Code: [Select]

16:08:10

exec getboincinfo


16:08:12

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 422295,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 5973.38,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 0,
  "Total_RAC": 5973.38,
  "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
}


The log says:

" PODCUpdate::Error: Insufficient funds. "

Which is weird, because I can make normal payments. I also send some funds to the Rosetta adress (BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD) and tried podcupdate, but it didn't help.

I must say that I was on a 1.0.9.7. wallet when I associated my CPID. Now I tried to associate my rosetta account on an different wallet with 1.0.9.8. and I'm going to wait for a minimum of six blocks to see I if I can get some UTXO/Task Weight there.
« Last Edit: March 05, 2018, 10:07:51 AM by jaapgvk »


  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Heres another thing that sheds light on part of the problem in prod, giving the false perception that utxo weight is taking long long time to confirm:

In one of the prior versions of PODC between 1092-1095 or so, we expanded the size of the vout transaction message field for PODC tasks.  However most of Prod is running the old version (68% on 1.0.81 and 23% on 1087), heinously bad situation, so basically Prod will not propagate the long fields required for PODC updates.  Until we start getting some updates going.  So we are sort of DOA in prod until we take action.  Note, the short PODC updates will propagate that explains why some work.

In reality, a PODC update should propagate in 6 confirms.  Then everyone sees the UTXO weight as 100 on block #7.

As far as requiring the actual wallet address of the CPID to be filled with BBP, thats probably happening without me realizing that that particular "feature" was programmed in - its kind of important, as otherwise UTXOs will fail to send, Ill have to take a look at that in detail.  Maybe we should allow it to choose any coin available.



  • jaapgvk
  • Hero Member

    • 552


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more

As far as requiring the actual wallet address of the CPID to be filled with BBP, thats probably happening without me realizing that that particular "feature" was programmed in - its kind of important, as otherwise UTXOs will fail to send, Ill have to take a look at that in detail.  Maybe we should allow it to choose any coin available.

Well actually, I sent BBP to the CPID wallet address because it seemed to work with Mike, but it made no difference in my case. It still returns the ' Insufficient funds' error.


  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I just remembered "why" its sending the UTXO stake amount from the CPID wallet address.
Its for security - we check the signature of the sender to ensure the senders address owns the CPID that sent the coinstake, and we check the CPID is related to the association tx, and we check the signature of the message is a valid sig for the cpid.  So this gives us the integrity of Address->UTXO->CPID->Tasks and the validation. 

We will need to add something to the instructions to send 60K or so over from yourself to the primary CPID BBP address on file.  As the CPID receives rewards it will be less of a problem.

Ill add the BBP address to getboincinfo, so we can see the addresses easier.




  • Rob Andrews
  • Administrator

    • 2617


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Well actually, I sent BBP to the CPID wallet address because it seemed to work with Mike, but it made no difference in my case. It still returns the ' Insufficient funds' error.

Try doing exec datalist dcc, picking your address to the clipboard for that particular CPID, then send some BBP to that address with
sendtoaddress address amount
Then doing the exec podcupdate again?

Im adding a feature now to show your address per cpid in exec getboincinfo, so this will be easier in prod.