Messages

3616

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

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

list -l
total 0

Mine says enabled.

Thanks!  When you did the 'exec dcc' did it say 1?  Also could you please try again while tailing the log and see if there is a bug in there (an error)?

Thanks!

3617

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

« on: February 08, 2018, 08:01:40 AM »

By the way, I installed the new Windows wallet but I'm getting a smartscreen error saying the file is potentially dangerous.

Its possible that it massively changed enough for google to remove it from the safe cache list.  (I remember we needed 500 downloads originally to get in the list).

Its also possible the new image files triggered it - but they are only pngs. 

Whats interesting is all the new code has nothing to do with mining, so thats kind of strange, because proof-of-dc is all business logic.

All I can say is I just installed it and Im running it - and to possibly scan it, on a 3rd party site first, and let me know how the result is?

My build environment is *very* secure.  Nothing comes into it but the existing opensource builds, and no dependencies have changed.

3618

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

« on: February 08, 2018, 07:58:41 AM »

Thanks for the Hot Sanctuary guide Togo - so just to confirm - the Hot sanctuary is all you need in testnet.  We dont need to deal with starting and stopping those from the controller wallet or protecting the funds.

(Its a funny analogy that I envision the Controller wallet to be the only one running the POW-pobh algo in the next revision, but that is for prod.  The controller wallet would be your wallet to send/receive funds, run POBH on one thread, and start-stop sancs).

Alex asked a question yesterday about the rewards.
In Testnet, the Heat miners (if you solve a block with POBh) only receive about 550 BBP.  The Sanc reward is about 5500 BBP. 
The DC Reward is 1.2 MILLION per day divided by the researchers Share (This is equal to TotalDailyEmission minus 20% standard budget minus sanctuary rewards minus heat rewards).   All figures above assume that our normal 20% budget has been held back from every block (for the monthly budget).

3619

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

« on: February 08, 2018, 07:48:06 AM »

Im also getting this message randomly in my console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::last_write_time: No such file or directory: "/home/ubuntu/.biblepaycore/SAN/magnitude"
biblepay in ProcessMessages()

cd ~/.biblepaycore
ls SAN

Looks like SAN directory exists, but its empty, so I guess it cant write the magnitude file?

Before I break this, anyone who is having this issue, Id like to ask one test first.

Could you please go to the console and type 'exec dcc'
Then wait about 15 seconds and see what is in :
~/.biblepaycore/SAN

Please post the ls -l from that directory?

Also, please tell me if you are a sanc and if your 'masternode status' is enabled?  This procedure is only supposed to run on the "chosen sancs".  Those are the ones with a rank less than 10:1.

3620

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

« on: February 08, 2018, 07:42:05 AM »

Finally, windows is ready.  Turned out that "cancer" image caused all kinds of problems in the build. 

Summary of what has changed:

1.0.8.8p - Windows & Linux - Leisure for Testnet

- Since protocol version has been increased, you will need 1088p (Windows) to start/stop a 1088 sanctuary
- Added more features to the rpc command : exec getboincinfo.  It now loops through all your cpids, and shows the RAC of each cpid and the total magnitude.  It also finds the last superblock you were in and prints some info about that (like total payments).
- Added the ability to Re-Associate a CPID with a new wallet.  This is Only if you lose your wallet or want to move your CPID to a brand new wallet.  Most of the time if you keep your wallet.dat you will never want to do this.  But if lets say you throw away your old PC and move, and buy a new PC, yet your existing CPID has say 100,000 credits, and you just want to associate that old CPID with a brand new wallet, Biblepay would say "Already_In_Chain".  To perform this action type : exec associate rosetta_email rosetta_pass force.  This will forcefully kill the old burn transaction and reassociate you. 
- Note the windows wallet has a GUI for DC association.
- Fixed the issue 616w mentioned where we show the POL weight info in prod (removed in prod), and Also verified that DC is not visible in Prod

** I have not looked at the SAN/Magnitude ST13 error yet, I will be looking at that next **

** I apologize to everyone I offended.  I want to take a breather and start over, but I want you all to keep an open mind and give DC a chance before disregarding it.  Lets test it, Ill add a vote for it, and if it fails the litmus test and the vote Ill go back to supporting POL/POBH fully.  But until then I feel we have created a feature that is #1 in crypto, especially when you take into consideration the security issue that has been solved in Biblepay (Sanctuary Quorum) **

3621

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

« on: February 07, 2018, 11:43:02 PM »

Just got an error while sitting in console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()       

It keeps coming up over and over again.

Hmm, do you have any special permissions set up or is biblepay running as root?

Try creating /home/biblepay/.biblepaycore/SAN and see if it goes away?

Ill check this issue out also...

3622

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

« on: February 07, 2018, 07:41:03 PM »

Well, my oddball ARM64 machine won't support BOINC or at least not the rosetta project.

That said, one point that has been brought up on Slack is why do we not have separate Development and Production branches of Biblepay?  The heartache of the PoL payments showing up in main net would not occur, and rapid fire upgrades in Development aren't going to look bad on us like they do in Production.

Ok, cool,  I guess try a different device then.

To answer your question plainly:  We would not have POL at all, or DC at all if we had more than one branch.  Because I wouldnt be doing all this work.  It takes a lot of hours to maintain each branch. 

I guess we wouldnt have a pool either.

Hopefully you would rather have biblepay in its current form that not have biblepay.

3623

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

« on: February 07, 2018, 07:26:24 PM »

"
If you decide to continue I ask you to announce a reasonable amount in advance as to give anyone wanting to fork off time to prepare, I might very well consider joining such an effort as it would line up better with my beliefs.

I hope the maintainers of the masternodes won't vote in favour of this proposal for reasons I have stated and we would be able to find a better way to help scientific research and or pursue other charitable actions.
"

Sorry to see you go, I take your input very seriously for POL.  For DC, your view is too constrained and biased to be taken seriously.

I think you have a certain belief system pegged with DC, and can't really envision it working the way I can.

For example, I think you believe Rosetta is a single "corporate" entity with 500 servers and an IT admin that might jack up his credits in BOINC.
However, its really 1 million global hosts who are taking turns turning in complex folding solutions through BOINC, and BOINC is so huge, as 616W just pointed out, that little tiny fish like us are not going to influence the SQL database.  Granted there is an SQL database where credits get updated, but there are over 1 million hosts in it along with us.

What I want to see is the complaint being escalated to me, such as :  How are we going to mitigate this particular centralization risk, and then we develop the IT solution that goes in biblepay to combat such issue.  To me, the issue is : analyzing the rolled up RAC, Total Credit Delta, Daily dump files, CPIDs, and at worst: putting some type of max CPU count cap on each CPID (so as to prevent one single CPID from hogging more than a 100 machine share), etc.   

But to argue that the current status quo with bitcoin is actually better than this is hilarious.  In my eyes, this system is so far superior to heat generating mining we should be a clear winner in the mainstream, and as I said on the other thread, pulling this off gives us intrinsic value.  And that is important, because if we securely check DC work units, from a black-box point of view, the community is far more valuable than bitcoin.

I can design a system that places a smart contract inside the researchers boinc account once per superblock, I can broadcast a payment from boinc back to biblepay once per day to prove that I am a cancer researcher with a certain UTXO  (for example placing a script with UTXOs inside the days
 boinc work), I dont really care what it takes, this is a creative effort.

As far as lead time:  Im shooting for going live with cancer-mining on March 31st, in Prod.  Ill enter the vote for this system before this Saturday.

So you have 50 days notice.

3624

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

« on: February 07, 2018, 04:21:17 PM »

Togo: the two articles you posted with gridcoin hacks actually contain a pointer to the same hack.  That whole thing is inflated.
Its a replay attack.  All that actually was broken in gridcoin was the advertisement beacon relied on the blockhash for its nonce, and that allowed a hacker to send in a beacon as a "replay attack".  In practice, its not that easy, costs money, and is very apparent to the researcher that you stole from (as their rewards stop).  They fixed it within 1 day of lead dev being notified.

The main problem as I mentioned in the wiki that gridcoin has is their neural network has trouble emitting the daily magnitudes so I see forking and stuff, but from what I understand its pretty much under control now, but all of these issues they had are not flaws or vulnerabilities in either boinc or the boinc projects.  They are just growth pains in a very complicated crypto project, with new business logic.

3625

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

« on: February 07, 2018, 04:08:12 PM »

The DC side doesn't really affect the blockchain though. If the DC side goes down, the blockchain is still running because the POW is what keeps it going. If there are safeguards in place to insure the magnitudes are truthful I don't see a problem. Plus, perhaps the software can auto switch to 100% POW if certain criteria are met.

I'm not really an expert so please correct me if I'm wrong.

Thats exactly right.

Were going from using 12,000 computers that generate random numbers and have others check the number is actually lower than the target, to executing a cancer program, that was written by more devs than ever worked on bitcoin combined, and checking the results by a decentralized team with over 1 million host participants.  To me, that is more decentralized than our fledgling little PC base.

And yes, on the disaster recover, we fall back to pure POW if DC is down.

Like I said, we could get hacked once a month and have a higher accuracy ratio than we do with POW being distributed to 7% of our non-greed based network.

I'm going to be drawing the line with the bashing.  If you dont like the design of PODC you are going to need to find another community.

Its very obvious that Swongel is biased, as every answer to Togo was based on a one-sided view.  Christians are about compromising and giving and making it happen and working hard.  If I say that I will develop a NEW algorithm, then so be it.  If you are not with me on changing the rules and going against the grain then please, dont stick around and drag all the rest of us down. 

FIND A SOLUTION IF YOU THINK ITS TOO CENTRALIZED.  I DONT.  CANCER MINING IS A NET POSITIVE FOR BIBLEPAY.  THIS IS GOING TO SHOW WHEN WE VOTE ON IT, AND IT WILL BE A SANCTUARY VOTE.

3626

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

« on: February 07, 2018, 03:53:58 PM »

How many tBBP should i send the the sanctuary wallet? I'm going to try doing a hot wallet sanctuary. Is the windows wallet ready yet? Thanks.

Its 500,000 in testnet.  Windows: No.

3627

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

« on: February 07, 2018, 03:53:30 PM »

I haven't looked into how PDC is being implemented but I would agree with Swongel on the principle. It is not advisable for a decentralised trust system to be relying/trusting a single external system. Biblepay would then become quite centralised.

Its quite centralized now with a botnet, and quite decentralized with PODC mining.

Sorry to disagree, but obviously you dont understand what you are talking about.

3628

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

« on: February 07, 2018, 09:08:39 AM »

The resource to print new Bible Pay, in this proposal partially delegated to BOINC is one of the resources which should be protected by the block chain, in this proposal this is not true therefor it breaks the tenants of Satoshi's white paper.

Further more this wouldn't stop bot nets since they could just as easily switch to the new BOINC alogrithm as well still keeping their current computing resources relative to the rest of the network.

Again trusting a third party for anything in the block chain it being the ability to print money, verify transactions or communications is against the fundamentals of the decentralised nature of block chain technology.

 

It is fine if botnets want to participate in cancer research.  And by giving the botnet a CPID and allowing us to see how many CPUs and CPUtypes and clockcycles and revisions are running it gives us valuable insight into the botnet, therefore, it is entirely different than we have now, and with that activity, I argue that it is beneficial, and no longer a nuisance, therefore I would not call it a botnet at that point. 

I jokingly say botnet because we have no control over their upgrades, however with Rosetta, they are at the mercy of using Rosetta, making my terminonly no longer refer to them as "nefarious" at that point.

Novel rewards through a daily superblock is not the same as minting.  Therefore this system is within the covenants of our design - and is an extension to what satoshi originally envisioned in the protocol.

Im sorry that you feel threatened by this idea for some reason, but I strongly believe the good in this outweighs the risk by a magnitude.

3629

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

« on: February 07, 2018, 08:46:38 AM »

"If there is an actual hacking target vector, please do the exact research on it and lets try to hack it.  There is not a high risk target hack vector here."

We cannot trust this because we cannot verify this.
Trusting a single system is against the fundamentals of Crypto Currency:

I quote from Satoshi Nakamoto's Bitcoin white paper:

Trusting a single third-party is a violation of these fundamentals, I urge you to reconsider the ramifications this will have.

I argue that coinbase transactions (novel mining rewards) are a different animal than peer to peer transactions in the wallet.

Besides, we still have pobh for the core consensus for block security, however the lions share of the mining are airdropped in a superblock for PODC, to encourage cancer mining instead of scaling up the heat mining side.

I believe the tenants of Satoshis paper are still being upheld.

3630

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

« on: February 07, 2018, 07:58:32 AM »

It looks like Gridcoin is now #1 in the world (by RAC):

https://boincstats.com/en/stats/-1/team/detail/118094994/charts

With over 60,000 servers connected to BOINC.

What do you say if we give them a little healthy competition with Cancer Research boys?

#1 in the world:
https://boincstats.com/en/stats/-1/team/detail/118094994/overview


I think we can overtake the US Navy if we try.