Testnet - Test Proof of Giving

[Rob Andrews]

I get this

getblockhash 96825
cd92bf4727388a839ef25c8dfc33879cebd034a7863fcfd32a5a09222a9d96c6


getblockhash 98560
f85fb3b1f158ded99a47faa82e8173ad2a3ba0d1ceb73f35ee6c1a9e82ad24f8

I match yours, and it looks like we are all together in one chain.

Log is "fairly" clean for POG, except one issue on tier 13 over and over - will investigate this.

[Rob Andrews]

1175 crash in both (testnet and prod), but without black flashing windows
I installed back 1172b it work good in both. My hash for block 98560 is the same like yours
But in 1172b autounlock after starts doesn't work for me in testnet. I still need to unlock it manually.
WIN 10 64bit.

I believe the autounlock prompt was fixed in 1175, (as it was pretty heinously clear at that time it had a bug) so could you please test again once we rerelease this new version that "hopefully" allows you to avoid the crash... Thanks.

[Rob Andrews]

1.1.7.6 is out there, anyone who crashed on Win10-home will you please test to see if the problem was the initializing boinc windows?

Please add this to the config file:

boincmetrics=-1

(-1 means dont try at all, 0 is the default, and 1 means try the legacy way (IE visible command prompt windows)).

[MIP]

ok so how do you recommend me to proceed to start testing? Any specific cases?

[Rob Andrews]

ok so how do you recommend me to proceed to start testing? Any specific cases?

I think at this stage we just wait for someone who has been crashing on windows to set 'boincmetrics=-1' and confirm it doesnt crash.

Then once we know it was that API call, you can make the decision if we want to fix the Win API call or wait until Evolution rebase is released.

I remember reading that the BOOST (later version boost that is with the MAC include you found for us) does support the WIN "hide" switch, so imo that would be the easiest (just let everyone live with the flashing screens for a while) and then we leverage that arg.

[Rob Andrews]

ok so how do you recommend me to proceed to start testing? Any specific cases?

Oh sorry, you are referring to POG in general?

Yeah, let me see if we have some uncovered test cases.  Do you need some testnet money?

Have you already tithed and set it to autotithe every N mins yet btw?  That helps to allow us to max out the POG diff.

[Rob Andrews]

Oh sorry, you are referring to POG in general?

Yeah, let me see if we have some uncovered test cases.  Do you need some testnet money?

Have you already tithed and set it to autotithe every N mins yet btw?  That helps to allow us to max out the POG diff.

If you set your nickname (nickname=yourname) in the config we can test:
1) Private chat call and answer
2) You can help us test the ROI on a brand new POG node; IE be sure to write down exactly what you started with before POG started, then tally your total expenditures (IE donations to the foundation over the duration) and tally the "POG rewards", and paste the ROI level here.  You should receive about a 50% profit on what you spend over a certain period.

[Ichthus220]

Just downloaded 1.1.7.6 and running a testnet flag and nickname=ichthus220. What do I do next?

[MIP]

I think at this stage we just wait for someone who has been crashing on windows to set 'boincmetrics=-1' and confirm it doesnt crash.

Then once we know it was that API call, you can make the decision if we want to fix the Win API call or wait until Evolution rebase is released.

I remember reading that the BOOST (later version boost that is with the MAC include you found for us) does support the WIN "hide" switch, so imo that would be the easiest (just let everyone live with the flashing screens for a while) and then we leverage that arg.

I haven't found anything yet that shows the flag CREATE_NO_WINDOW can create crashes (unless you launch a full Win GUI app which is not the case). I was thinking on a buffer overflow but I am leaning towards the case when the user can't launch boinccmd for a number of reasons. This way we enter

Code Select Expand

// If an error occurs, exit the application.
    if ( ! bSuccess ) {
        exit(1);
    }

and this would explain the apparent "crash". I can change this with a better error handling instead exiting. I'm pretty sure this would fix the problem (but user could not interact with boinccmd). I'll tell you when it's ready.

[MIP]

If you set your nickname (nickname=yourname) in the config we can test:
1) Private chat call and answer
2) You can help us test the ROI on a brand new POG node; IE be sure to write down exactly what you started with before POG started, then tally your total expenditures (IE donations to the foundation over the duration) and tally the "POG rewards", and paste the ROI level here.  You should receive about a 50% profit on what you spend over a certain period.

I registered by nick on conf file but it does not seem to get it. This is my conf in %appdata%\biblepaycore\testnet3\biblepay.conf folder

Code Select Expand

testnet=1
shrinkdebuglog=1
debug=true
debugmaster=true
tithe=3
nickname=MIP
genproclimit=1
gen=1

Regarding PoG, I have like 350.000 tBBP, but very recent coins. I have tithe=3 in conf but I don't know if that's enough or I have to do some manual command (I don't even know if it's getting it because of the conf problem I mentioned above).

Sorry to be so noob on PoG but I really didn't have the time to follow these days 

[klondike]

chain is broken, more chains exists...what is correct?

[Rob Andrews]

I registered by nick on conf file but it does not seem to get it. This is my conf in %appdata%\biblepaycore\testnet3\biblepay.conf folder

Code Select Expand

testnet=1
shrinkdebuglog=1
debug=true
debugmaster=true
tithe=3
nickname=MIP
genproclimit=1
gen=1

Regarding PoG, I have like 350.000 tBBP, but very recent coins. I have tithe=3 in conf but I don't know if that's enough or I have to do some manual command (I don't even know if it's getting it because of the conf problem I mentioned above).

Sorry to be so noob on PoG but I really didn't have the time to follow these days 

Yeah, this version of dash never did quite get the testnet3 conf (but it does for the masternode file) but I think the easiest way for us to get going past this, is please try this (your conf contents are good) -
cp ~/.biblepaycore/testnet3/biblepay.conf ~/.biblepaycore/biblepaytest.conf
Start the client with :
./biblepay-qt -conf=biblepaytest.conf

Then it will read the entire file (this problem wasnt related to the nickname it was related to the way the paths work in testnet)

Sure Ill send you a few mil, please paste the address - even though it might take a while, diff could drop.

No problem at all, I know its impossible to keep up with all these nuances and the method in which we post here since we have scarce documentation at this point.

Afa tithing, for now just try to send one manually to see that you dont have any aged coins, you can type 'exec titheinfo' to see the reqs, also on the first page, try the 'exec getdimensionalbalance x y' command to see that nothing shows up for this particular diff level.  You can get the diff level from titheinfo.  Let me know if you have an understanding of the difficulty requirements (IE the 3 params) - if not I will go into deeper explanation on those.

[Rob Andrews]

chain is broken, more chains exists...what is correct?

Working on my 3 nodes and I have 13 good connections.  What seems to be the problem?

EDIT:  All 13 connections connected to me are on block 99828.  Chain appears good.

[Rob Andrews]

Just downloaded 1.1.7.6 and running a testnet flag and nickname=ichthus220. What do I do next?

Do you need any testnet coins?

Please test out the chat feature, lets see if we can see each other in the chat room.

[orbis]

Rob,

Bingo
I've downloaded 1176 and after start it crashed in prod and testnet too.
After adding "boincmetrics=-1" to config all works like a charm

I'm now on block 99830 with hash 58c842b0aa157e2059479d9ab2a1ffd4ae3f17da99f91965429c191421e658d6.
I hope I'm on good chain

Now I'm waiting if thithes will work in auto mode after startup unlock.