Messages

1876

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 03:37:56 PM »

I am trying to sync testnet but I am stuck at block 17444. I see many peers so I don't know how to get it updated.
I will try to rescan and come back when ready

Actually if you are on 1.4.8.2, double check that, then delete 'instantsend.dat' and restart, and let us know?

Let me know if it still re-hangs.

1877

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 12:09:32 PM »

I will admit some posted issues have been duds. We can't be 100%    all the time -- only Jesus. If you feel some issues are not worth investigating, then it is your job to prioritize or ignore them. I hope you can appreciate just how many issues don't reach you because many of us address it before it gets to you.


> always ended up turning into non issues.


Why would say "always". That sounds very dismissive of my contributions. I got tired so I had to stop before finishing...


Here are some issues I posted in the past that required fixing...


GSC Transmission for CameroonONE occurs even with -1
https://github.com/biblepay/biblepay-evolution/issues/26


One Click Mining Configuration corrupts biblepay.conf
https://github.com/biblepay/biblepay-evolution/issues/21


InstantSend not working - always confirms to 1 of 6
https://github.com/biblepay/biblepay-evolution/issues/17


Superblock Payment shows matured but requires 102 confirmations
https://github.com/biblepay/biblepay-evolution/issues/10


Runaway exception: bad lexical cast: source type value could not be interpreted as target
https://github.com/biblepay/biblepay/issues/102


One Click Miner Configuration writes tithing=1 instead of tithe=1
https://github.com/biblepay/biblepay/pull/87


exec bankroll: Signing transaction failed on locked wallet
https://github.com/biblepay/biblepay/issues/83


Invalid-tithe found from address xxx for amount of xxx
https://github.com/biblepay/biblepay/issues/81


Unable to mine... Cant sign block template with CPID - Error
https://github.com/biblepay/biblepay/issues/80


The auto-tithe feature was only tithing 90%.
https://github.com/biblepay/biblepay/issues/78


viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)
https://github.com/biblepay/biblepay/issues/74


PoG Leaderboard - right click View makes QT wallet gets stuck
https://github.com/biblepay/biblepay/issues/73


PoG continues to auto tithe even though daily ~50k BBP donation was exceeded
https://github.com/biblepay/biblepay/issues/71


PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70


PoG Leadboard does show up in production
https://github.com/biblepay/biblepay/issues/67


1.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.
https://github.com/biblepay/biblepay/issues/44

Yes, you are right, sorry, I just read what I wrote and corrected it to say "some".

Sorry, I apologize for coming across with that impression to you.

Actually to clarify, all of your support contributions have been very welcome and helpful in detecting, diagnosing, and solving the bugs we had over the entire duration of BiblePay.

Thank you for what you have already contributed.

Hopefully we will be working together in this endeavor.

1878

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 10:19:55 AM »

nevermind, I'm out of testing. This is no way to treat your testers.

Just to clarify though Sun, you have been entering tickets in github with a lot of issues that have taken a siginficant amount of time, and some ended up turning into non issues.  MIP and I have taken a look at this and already explained that there is no "Mac" format and his external purse collateral works fine on his macs.

You should be more respectful of our time.  I only asked for a regimented test because we have spent a considerable amount of time on these things in total.

1879

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 09:55:11 AM »

biblepay.conf is in Mac format according to Notepad++. This is on my Windows 10 64-bit Home edition.


I can send you the file after I do exec createpurse.


the line ending is 0d0d0a instead of 0d0a . I think I mentioned this in the github. I didn't mention it because it didn't seem relevant, but if wallet is not reading biblepay.conf that creates all sorts of Issues I noticed in the past.

I already posted my reply about this. 

Lets not spend more time on this or make assumptions.

Do the following:

Start a new wallet
Type 'exec createpurse'
Type 'exec boinc1' and paste the output.


Your current wallet is already successful.  Try with a new one - and do not manually edit the biblepay.conf file this time.

Do not paste third party representations of the data for the test.

1880

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 09:51:48 AM »

Sorry, I had trouble with the re-syncing of two of those sancs following the recent upgrade. I had to delete the whole biblepay-evolution folder suggesting that there was some issue with the compilation which allowed me to start the wallet but somehow failed to sync after days... I have now just used the pre-compiled binaries and it is working fine as all of my testnet servers are at the top of the chain and can confirm your hash.

>cli getblockhash 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

Since one of those wallets that would not sync was my controlling wallet, I could not perform an update_service to the POSE_BANNED sancs which I have now done and as far as I can see all 7 sancs on testnet are ENABLED.

>list status
{
  "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": "ENABLED",
  "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": "ENABLED",
  "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": "ENABLED",
  "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": "ENABLED",
  "7c30c4cf73a81ce8ebb90b3cd6bcda3c279d86fb044605b3f95f75a1657cd19e-1": "ENABLED",
  "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": "ENABLED",
  "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "ENABLED"
}

Finally, the Gridcoin RAC has been accumulating similarly to Biblepay RAC since the start of testnet PODCv2. I just noticed the higher coinage requirement and lower points on the leaderboard with the recent spork to add a higher requirement to gridcoin team members.

Ok, good overall I suppose.  Thats great that GRC's points are showing in the leaderboard; just please let us know if it follows through with a payment too.  I assume it will.

On this sanctuary compile debacle, I have a hypothesis on that, because I have a similar problem compiling on my low end boxes.  I have a couple low-end for testnet and they are so low end they sometimes cant even finish the compile.  I can say this with certainty:  If cc1plus gets killed in the middle of a compile due to lack of ram, many times, the binary will already have the higher protocol version and the lower code (which is absolutely bad when you run it).  The way I personally had to solve this is make a compile script with 'cpulimit -l 45' (or something to that effect, if you want it I can post it) and it causes the compile to finish without getting killed.  Try that next time with a make clean first.  After that Ive had much better luck running it and leaving and then it starts back up successfully.

EDIT:  Just to clarify though, when I post a release the code is the latest; so it sounds like it *was* a compile issue.  (MIP then builds the linux binaries after the release is posted here).

EDIT2:  Starting with the last version, you can use -erasechain=1 again (we now delete all the files including instantsend.dat).  But, you shouldnt have to, unless we have a fork, and thats what we are trying to certify we dont have any more.  For example after this last release I did not erase my chain I just restarted the client.

1881

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 09:14:40 AM »

And just so everyone knows that progress is not stalling in testnet, the only two or three changes for the next version are cosmetic helpful hints-  so we are in no hurry to make another release (until we either find a bug or merge something else in).  In testing my unbanked CPID, it does have a minor bug - but that can also wait until the next release.

However one very, very important endeavor I wanted to mention that we need to schedule very soon is testing this 0.14 TestNet branch against prod.  I realize we did mine against prod a long time ago, and that worked until we found we forked after a GSC block.  On that endeavor, heres what we need to do:  Since this branch will only communicate with deterministic and higher version sancs, we need to actually release a patch for MainNet, and one of our guinea pigs (IE : ME), will upgrade 10 sancs to that version.  Then we will circle back and test TestNet against prod and verify we mine again and do not fork through the GSC block.  We'll do that very very soon, but please wait until I give the OK that the code is released in mainnet, etc.

1882

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 09:03:59 AM »

sorry I sent the post prematurely. The CORRECT ratios are as follows:

TEAM           RAC       COINAGE REQD     RATIO
GRIDCOIN   6,023     1,116,115               185.3x
BIBLEPAY    9,569         149,679                15.6x

Very impressive!

Yes this looks like it matches what we would expect too!

Could you please keep us informed to tell us how well the Gridcoin CPID works out?  IE that its RAC gets reduced today but you still enter the leaderboard and then if you ultimately get paid?

Thanks!

EDIT:  Also, when you reboot your sancs on the new version, could you please tell me if they sync right up to the top block?

Let me post a hash:

getblockhash 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

1883

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 08:52:23 AM »

It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.

In PODC 2.0, it is the users responsibility to maintain sufficient staking collateral inside the "Christian-Public-Key" address. 

So here is the easiest way to check that:

- Check and see if you are in the leaderboard 5 blocks after you send a WCG GSC
- If not, check your CPK balance.  It should have about 10 bills in it (to ensure small breakable bills exist for Cameroon one and Kairos), and it should have sufficient balance of coin-age (shown in exec rac).

I will now add more warnings to 'exec rac' to make this a little more apparent.

1) You can see your balance in Coin Control (associated with Christian Public Key), and you can see the external purse balance in 'exec rac'
2) You can make banknotes with 'exec bankroll'.  These now get paid back to the CPK, so these are PODC 2.0 friendly.
3) You can see if you are in the leaderboard a few blocks after a GSC is sent.  If not, something is wrong.

In the next version, as I stated earlier, the 'sendgscc wcg' does throw a warning if the user didnt have enough coin-age.

1884

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 30, 2019, 08:20:57 AM »

My biblepay.conf kept saving as Mac format after the externalprivatekey got inserted by the biblepay code. saving it back as windows (crlf) seems to triggered a gsc tramission for cameroon-one, kairos, and wcg as soon as I opened the wallet again.

I don't think there is a Mac format; we have linux and windows file formats; To my knowledge MAC has migrated to the linux format; MIP has confirmed this is working.

Please work with MIP on this.  He's staking collateral successfully.

Edit:  Obviously the purse must be working because you sent out collateral before.  Can you please paste the output of 'exec boinc1'?  This tests the purse.  I think you are reading too much into the purse, and making an assumption.  Don't spend any time on the assumption, just paste exec boinc1 and we will go from there.  Macs file writing format works fine.

Btw, we no longer trigger sendgsc when the wallet opens.  Its only sent at the height shown in 'exec rac'.

1885

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 29, 2019, 08:57:45 PM »

I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.

So it looks like you only staked 65 total coin age two days ago (not enough to meet the minimums), then 6 coin age today.

The problem appears to be in your total external purse balance.
(The exec rac for example, shows a 0 total coin age - that is part of the issue).

But more specifically, in this version of BBP, you must load your external purse with funds in order to have enough coin-age built up to send PODC transmissions.

Check your 'CPK' address, and see what total bbp you have in there?

EDIT:  Btw, in the next upcoming version we did add a warning message- when a user manually sends a GSC for WCG, and the wallet detects not enough coin-age, it does throw a WARNING:  Explaining that the rewards were reduced for PODC.

1886

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 29, 2019, 08:38:42 PM »

I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.

Obviously PODC 2.0 is supposed to be easier to set up than PODC, so I'm not sure how you can come to that conclusion. 

But a non-working PODC transmission does not equal hard-to-use software. 

1887

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 29, 2019, 07:11:10 PM »

i'm giving up. I can't get my cpid registered. tried several times now.


exec rac works but haven't gotten a podc payments for days now.

I will need the full exec associate command you typed so I can reproduce.  Unless you are saying your 'exec associate' was successful days ago, then I only need your CPK and CPID.

And also your CPK and CPID would be helpful.

EDIT:  And also if you successfully performed exec join wcg and also if you successfully performed exec associate, and also your block # and blockhash currently.

Also, what is the last txid of your WCG GSC transmission?

1888

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 29, 2019, 10:28:39 AM »

OK, sent a GSC transmission. Required coin-age was 324.976, and I had 200.833. Let's see how it rolls out.

Yeah, I saw yesterday you did have reduced RAC.  1 point in the leaderboard equals 1 rac currently.

1889

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 29, 2019, 10:28:04 AM »

couldn't the wallet version be enough to ban sanctuaries not on that version as well?

No, actually, in dashcore, we know both the governance protocol version and the wallet version.
So, no that wont work either.

But I believe the last release did fix it.

1890

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 28, 2019, 10:52:42 AM »

Thanks for the funds, Rob ! Otherwise I would have to mine for a couple of days while testing the minimum coinage requirements for a reward 

Do I have to send a manual PODCupdate to show up in the leaderboard?

Sure, and I will reply asap to the message btw.

On appearing in the leaderboard, the researcher will appear about 5 blocks after a PODC transmission is made; but now the way it works is, if you type exec rac, note how it says 18757 is the next wcg transmission (Fixed), add 205 to that, thats when the wallet sends out the PODC transmission automatically.  But, you will have to see if exec rac shows that you have the coin*age. 

So same issue, if you manually type 'sendgscc wcg' now, the coin age will not be sufficient (until you let it grow a little more).  You know we should also tell the user that (duh) upon manually completing that command.  EDIT:  Ok, the next version will actually give you a reply if you don't have enough coin-age, with a warning, explaining that the RAC may be reduced resulting in a lower reward. 

EDIT: But btw, when a user stakes insufficient collateral, we do reverse engineer it down to the amount staked, and lower the leaderboard RAC, so if you want to try now, you can then look at the leaderboard and see a reduced RAC.