TestNet - PODC 2.0 (Proof of Distributed Computing)

Could you confirm what platform version this is, is this a linux qt build?  Or windows?

Self compiled or a binary?

Linux command line
cli -version
BiblePay Core RPC client version 1.4.6.7

binaries from
https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz

Linux command line
cli -version
BiblePay Core RPC client version 1.4.6.7

binaries from
https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz

Ok, I make the assumption you are also affected by the problem I pasted for Togo, so if you want to work quickly please self-compile and then retry your sanctuary revive or spend;  or alternatively please wait for 1.4.6.8.


I will work on this now for new release.

Just for sanity sake Im trying to get the root of the problem ,  I just deleted banlist on both DNS servers; can you please try your test again?

coool, now i have 5 connection and i'm on block 14807
seems we found rootcase

yWurZhEW51tyVGqgxMtYLmBFNHvAPcyeRu
this is my address, pls send me some coins

coool, now i have 5 connection and i'm on block 14807
seems we found rootcase

Oh wow, so basically let me try to guess:

You connected early on in the game with the wallet defaults, and the wallet started mining at the genesis block.
It added 10 blocks or so very easily.
Then when you got a connection to the dns nodes, they banned you because you were trying to pass on invalid headers (this is a dash rule that gives you a very huge penalty for doing that).

So you probably then switched back to gen=0 but it was too late.
We will have to remember this for the future, as in testnet its easy to solve blocks because of that not-requiring-peers rule.

That reminds me, in prod, btw, you are not allowed to mine without peers, so this all makes sense now!

Ok, I make the assumption you are also affected by the problem I pasted for Togo, so if you want to work quickly please self-compile and then retry your sanctuary revive or spend;  or alternatively please wait for 1.4.6.8.


I will work on this now for new release.

I’ll wait as compiling failed....

In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9965: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[1]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[1]: Leaving directory '/home/bbp/biblepay-evolution/src'
Makefile:11637: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Oh wow, so basically let me try to guess:

You connected early on in the game with the wallet defaults, and the wallet started mining at the genesis block.
It added 10 blocks or so very easily.
Then when you got a connection to the dns nodes, they banned you because you were trying to pass on invalid headers (this is a dash rule that gives you a very huge penalty for doing that).

So you probably then switched back to gen=0 but it was too late.
We will have to remember this for the future, as in testnet its easy to solve blocks because of that not-requiring-peers rule.

That reminds me, in prod, btw, you are not allowed to mine without peers, so this all makes sense now!

yes, it was this way

yWurZhEW51tyVGqgxMtYLmBFNHvAPcyeRu
this is my address, pls send me some coins

Sent!

I’ll wait as compiling failed....

In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9965: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[1]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[1]: Leaving directory '/home/bbp/biblepay-evolution/src'
Makefile:11637: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

To get by that, you have to follow the compile instructions in the area that says "cd biblepay-evolution/depends", "make...":
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

03:14:11

exec associate capulo nnn


03:14:12

Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)


but i'm in biblepay team.. so?

Hey All-

I see we have a very squirrely issue, its almost as if Im the only wallet that is miraculously working.

Ive been moving the wallet file to different servers and seeing a different result, so Ive come to the conclusion that we need a bug fixed.

Please stop testing until I can trace this root problem.

Thanks!

BiblePay
1.4.6.9 - Mandatory Upgrade for TestNet

- Fix key signing issue

03:14:11

exec associate capulo nnn


03:14:12

Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)


but i'm in biblepay team.. so?

I don't actually see your 'exec associate' in the chain; I assume it was the issue we had (where the wallet was not signing the tx).  Please try the exec associate again with the force true at the end?

No wonder you are having so many issues Orbis, you are on the wrong chain, please resync with "-erasechain=1" then verify this hash:

getblockhash 14700
92c8c16680413fb1f36bd8c9b389c5ad87cbf14f377a7936509656e714c11ea0

Then, start over with the 'exec cpk your_nickname' then the 'exec associate wcg_username wcg_verification_code' command, and see if that is successful?

I will not be able to track the 5K you refer to until you are on the same chain as me.  If it happens again please re-paste.

Sorry, but I was few days away. Now It looks that I'm on right chain and associate was successful.

Code: [Select]

  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"My associate TX was again with 5k tBBP. here is: 0fcb5b796acc141badc30954ac5fafa3d4d1fd458398b24cbde31ea2da0642a7
I sent all of my tBBP (75k) to external purse so I'll be waiting if it goes good. Thanks

Glad you were able to pinpoint the issue Rob! yay!

I downloaded v1.4.6.9, and I was able to successfully send coins!

How many coins are needed for a sanctuary?
I have 2,020,209.26 tBBP right now

Here is another receiving address:
ygkRiAMGaZaZM2ctREJ7mWRsFyG3emTtzt