Bible Pay

Read 34226 times

  • Rob A.
  • Administrator

    • 1101


    • 18
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
"
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.




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.


  • Rob A.
  • Administrator

    • 1101


    • 18
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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.



  • strayapple
  • Newbie

    • 4


    • 0
    • September 04, 2017, 08:12:57 am
    more
just compiled 1.0.8.8 sourcecode,but can't sync blocks.
it's still not working after i added these node:
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

any other node ?


  • T-Mike
  • Sr. Member

    • 391


    • 2
    • February 06, 2018, 06:12:58 pm
    more
Figured it out, the testnet also uses the biblepay.conf in the /.biblepaycore folder, not the /.biblepaycore/testnet3 folder.
« Last Edit: February 07, 2018, 10:28:37 pm by T-Mike »


  • T-Mike
  • Sr. Member

    • 391


    • 2
    • February 06, 2018, 06:12:58 pm
    more
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.
« Last Edit: February 07, 2018, 10:16:09 pm by T-Mike »


  • Rob A.
  • Administrator

    • 1101


    • 18
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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...



  • togoshigekata
  • Sr. Member

    • 275


    • 17
    • September 01, 2017, 10:21:10 am
    • Texas, USA
    more
HOW TO SETUP HOT TESTNET LINUX SANCTUARY (MASTERNODE)

References:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
http://wiki.biblepay.org/Create_Masternode#BiblePay_Sanctuaries_Setup_-_Linux_Server
http://wiki.biblepay.org/Create_Sanctuary_2

=====================================================

A. Setup Remote Linux Server
http://wiki.biblepay.org/Create_Sanctuary_2#PART_B_-_Rent_Linux_Cloud_Machine

B. Install, Run and Stop BiblePay
http://wiki.biblepay.org/Create_Sanctuary_2#PART_C_-_Install_Sanctuary_Linux_Wallet
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

C. Set Wallet to Testnet
cd ~/.biblepaycore
vi biblepay.conf
testnet=1
:wq

cd home/biblepay/src
./biblepayd -daemon

=====================================================

1. Ask for 500,005 tBBP (test BiblePay) on the forum, post your address:
./biblepay-cli getaccountaddress ""

2. Create a new address to send escrow to:
./biblepay-cli getaccountaddress MN1

Copy the Address Output
yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo

3. Send 500,000 tBBP to escrow address:
./biblepay-cli sendtoaddress yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo 500000

Copy the TXID Output
da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772

4. Turn on mining for a few minutes to make blocks advance
./biblepay-cli setgenerate true 1
./biblepay-cli getinfo
./biblepay-cli getmininginfo
./biblepay-cli setgenerate false

5. Get the VOUT
./biblepay-cli masternode outputs

Copy the VOUT Output
1 or 0

6. Get the Private Key
./biblepay-cli masternode genkey

Copy the Private Key Output
92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

7. Stop BiblePay
./biblepay-cli stop

7. Add Sanctuary to masternode.conf
cd ~/.biblepaycore/testnet3
vi masternode.conf  (i insert, :wq to write and quit)

[SANCTUARY_ALIAS] SPACE [SANCTUARY_PUBLIC_IP:40001] SPACE [SANCTUARY_PRIVATE_KEY] SPACE [ESCROW_TXID] SPACE [ESCROW_VOUT]

MN1 34.208.206.95:40001 92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772 1

8 Add flags to biblepay.conf:
Note: I added same to both biblepay.conf files, in main folder and in testnet3

rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=34.208.206.95
masternode=1
masternodeprivkey=92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

9. Open Ports in Firewall
sudo apt-get update
sudo apt-get install ufw
sudo ufw allow ssh/tcp
sudo ufw limit ssh/tcp
sudo ufw allow 40001/tcp
sudo ufw allow 9998/tcp
sudo ufw logging on
sudo ufw enable
sudo ufw status

10. Start masternode
./biblepay-cli masternode start-alias MN1
NOTE: Weird mine was already started somehow

11. Masternode Debugging
./biblepay-cli mnsync status
./biblepay-cli masternode list
./biblepay-cli masternode status

Wait for Masternode info to sync, AssetID 999 MASTERNODE_SYNC_FINISHED:
./biblepay-cli mnsync status

12. Install Watchman
sudo apt update
sudo apt -y install git python-virtualenv virtualenv
cd ~/.biblepaycore
git clone https://github.com/biblepay/watchman.git
cd watchman
virtualenv venv
venv/bin/pip install -r requirements.txt

13. Set Watchman to Testnet
vi watchman.conf
Comment network=mainnet  (add # in front)
Uncomment network=testnet (remove # in front)
:wq

cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py

Make sure this command gives no output and then add it to crontab

crontab -e

# i insert
* * * * * cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1
# :wq

14. Wait for Masternode Status to go from PRE_ENABLED to ENABLED,
turn on mining if no one is mining
./biblepay-cli masternode list

=====================================================

Let me know if this is correct, seems to be working for me so far, but Im still in PRE_ENABLED state


  • togoshigekata
  • Sr. Member

    • 275


    • 17
    • September 01, 2017, 10:21:10 am
    • Texas, USA
    more
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()

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

cd ~/.biblepaycore
ls SAN

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


  • strayapple
  • Newbie

    • 4


    • 0
    • September 04, 2017, 08:12:57 am
    more
Who can send me 1 test bbp to my address yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh

I wan to associate my boinc account with biblepay,but it said Balance too low to advertise DCC, 1 BBP minimum is required.


  • znffal
  • Full Member

    • 132


    • 4
    • October 02, 2017, 04:01:47 pm
    more
Who can send me 1 test bbp to my address yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh

I wan to associate my boinc account with biblepay,but it said Balance too low to advertise DCC, 1 BBP minimum is required.
I sent some. Hope it worked buddy!


  • strayapple
  • Newbie

    • 4


    • 0
    • September 04, 2017, 08:12:57 am
    more
I sent some. Hope it worked buddy!
thanks very much,it worked!

"Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"


  • Rob A.
  • Administrator

    • 1101


    • 18
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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) **


  • T-Mike
  • Sr. Member

    • 391


    • 2
    • February 06, 2018, 06:12:58 pm
    more
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) **

That's great! Will test it out.

Thanks for apologizing, let's continue to work on this as a body.


  • Rob A.
  • Administrator

    • 1101


    • 18
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
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.