Messages

3601

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

« on: February 08, 2018, 02:29:33 PM »

I'm having a slight problem because I used a new wallet. The force command doesnt seem to be working when using my old rosetta account. it still says already in chain. ie. exec associate email pass force

Try changing force to true.  I might have not interpreted the word correctly.

In the mean time Ill check.

EDIT: Yeah, try associate email pass true

3602

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

« on: February 08, 2018, 02:25:06 PM »

Figured it out, had to start the vncserver from the same account as the biblepay daemon.

Oh awesome, good.  Would you like to test it now?

masternode status
Should return Active?

Then post 'exec testvote'

Your on the latest, 1088q correct?

3603

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

« on: February 08, 2018, 01:51:14 PM »

Rob,

When I try to run -qt through the vnc session i get Invalid MIT-MAGIC-COOKIE-1 keyQXcbConnection: Could not connect to display :1.0.

Do you know how to fix this?

Thanks.

-tmike

Hi Mike,

I didnt have that, but I see someone else did here :

https://bbs.archlinux.org/viewtopic.php?id=230828

Rob

3604

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

« on: February 08, 2018, 11:48:51 AM »

Rob,

This is interesting because now for the people that were running Rosetta already, they just need to install the wallet and link their CPID. They can now turn their number crunching into money if so desired. In fact, it is so easy to install the wallet that it's a no brainer. If half of the computational power signs up for Biblepay, what do you estimate the payout to be for one normal computer? Like an i5 or i7 processor. I'm thinking the payout will be very small then.

I have one suggestion, since you have contacts with the people behind BOINC. Can you e-mail then to have some of them install the wallet? That would probably get you many CPIDs on the testnet fast adn it doesn't really cost them anything.

I have a few other suggestions too that could propel us to the top and silence a lot of naysayers, but I cant do it all myself, so some of these I will hold til we hire the devs:

- Recompiling our own custom version of boinc with our custom biblepay-cancer graphics
- Integrating boinc code into biblepay-qt
- One click set up with no questions for the user
- Making the rosetta cancer-miner part of biblepay pobh algorithm inside the wallet , IE one program
- Adding a POL script into each rosetta workunit, thereby making rewards based slightly on POL + cancer research
(Might help us in the sense that we can filter out future cancer botnet)
- Reconciling a researcher embedded UTXO in a cancer workunit back to daily Magnitude reports
(This would prove each researchers indivdual wallet has some coin*age in it, would be really great for integrity)

This stuff would be massive....

3605

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

« on: February 08, 2018, 11:36:43 AM »

Rob,

This is interesting because now for the people that were running Rosetta already, they just need to install the wallet and link their CPID. They can now turn their number crunching into money if so desired. In fact, it is so easy to install the wallet that it's a no brainer. If half of the computational power signs up for Biblepay, what do you estimate the payout to be for one normal computer? Like an i5 or i7 processor. I'm thinking the payout will be very small then.

I have one suggestion, since you have contacts with the people behind BOINC. Can you e-mail then to have some of them install the wallet? That would probably get you many CPIDs on the testnet fast adn it doesn't really cost them anything.

Yeah, I know, thats why Im so frustrated.  We dont enforce the team, and we would have a huge legion of 50,000+ researchers who would gladly make BBP for crunching, and it would grow the coin for good.  Its such a huge no brainer.

3606

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

« on: February 08, 2018, 09:06:27 AM »

I can try, it's on a VPS so I need to install x on it or something. I'll let you know.

Yeah, I installed graphics on all my VMS, that would make this easier.  Thanks!

3607

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

« on: February 08, 2018, 08:50:33 AM »

Still no file. Ubuntu 16.04.3 LTS, kernel version 4.13.0-1008-gcp.

Hmm, I just remembered something, there is a very complex command in the DCC Filter, something that is done in QT (otherwise we need a new lib in headless, and the exchanges dont like unecessary libs on their native machines) so I did it in QT.. Im thinking, we may need to have you run your hot sanc in -qt mode.  Do you have graphics on that ubuntu box, and can you launch the hot sanc like this:
./biblepay-qt -testnet

?

Need to rule that out.

3608

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

« on: February 08, 2018, 08:43:35 AM »

Hmm, it says:
error code: -1
error message:
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"

Which flavor OS is your hot sanc?  Also, do you now have a user file in /SAN?

3609

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

« on: February 08, 2018, 08:42:50 AM »

Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

Oh btw, the exec testvote, and all DCC file hash testing must be done on the hot sanc.

3610

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

« on: February 08, 2018, 08:38:22 AM »

Sure, just let me know when. The only problem right now is I only have enough tBBP for one more. You have my e-mail, it's a headache trying to keep up with the forum. How many cpids are running right now?

Looks like 4 cpids.

Well I mean we could do it in 5 mins and make it a learning experience for everyone to understand the high security in place.

3611

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

« on: February 08, 2018, 08:33:25 AM »

Great! Thanks.

Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

3612

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

« on: February 08, 2018, 08:31:11 AM »

Alright, I'm not going to try it. I literally spend all day setting up the testnet masternode yesterday. How many masternodes do we need? I can potentially host 10 of them by cloning but I don't want to do that until it's needed.

LOL, yeah the first couple I set up were tricky now for some reason they seem easy. 
Uhh, I would just be happy if you did a couple, because I think we only need 10 total sancs in testnet to prove the quorum side features are all working correctly, lets talk about that soon.
But in the mean time, I would definitely like to get 50 boinc cpids out here, because not only do I want to get a feel and give everyone a taste of what we would be doing, but also to test the superblock frequency and verify the payments per mangitude and all the security.

I have 2 running, so if you did 2 + Togos, we would be halfway there.

Ill start getting the commands to show what rules the sancs go through in the morning.

3613

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

« on: February 08, 2018, 08:27:38 AM »

Hmm, trying to reproduce now by killing my setup...

Aha!  Ok the st13 last_writetime_error is fixed for the next testnet version later today.

In the mean time, anyone who has either run into the problem , or never experienced the problem type:
exec dcc

You should see "1".
This fixes the problem temporarily until the next release.

3614

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

« on: February 08, 2018, 08:21:07 AM »

The error stopped by the way, haven't seen one today although there is still no file in SAN.

Hmm, trying to reproduce now by killing my setup...

3615

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

« on: February 08, 2018, 08:19:54 AM »

Can I monitor the hot Sanctuary from my windows wallet? Do I just need to fill in biblepay.conf or masternode.conf or both? Thanks.

On the hot sanc, all you really have to do is send the collateral to yourself (the 500,000 even), then add:
masternode=1
masternodeprivkey=yyyyy

In the biblepay.conf, and leave the masternode.conf alone.  (On the testnet sanctuary itself).

You could monitor it in windows, but since testnet is so small I would just click on Sanctuaries on the windows wallet and look by IP.

I dont know if the hot sanc vout will be possible to add to your Win pc, but if you wanted to try : you would copy the 'masternode output' (from the sanctuary itself) TXID & VOUT n to your notepad, then construct the masternode.conf file on the windows PC to include it.  Probably not worth it as it might hose your prod file, etc.  I would just look for the sanc in the list.