Bible Pay

TestNet => TestNet Discussion Archive => Topic started by: Rob Andrews on August 27, 2018, 06:52:39 pm

Title: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 27, 2018, 06:52:39 pm
Welcome to the BiblePay Testnet thread for IPFS!

To install the latest version for testnet:
Please upgrade to v1.1.4.7+




How to install IPFS on a Sanctuary (Ubuntu 64 instructions):
https://raw.githubusercontent.com/biblepay/biblepay/master/InstallingIPFS_Ubuntu64.md

How to launch biblepay-qt in testnet:
./biblepay-qt -testnet -listen=0 -masternode=0

(The listen and masternode flags are only required if you want to run Testnet side-by-side your Prod sanctuary)

Synced Verification Info:

getblockhash 53930
45aa03a87251d06b867e4fbb5e24d87970e18176d1739e609366156423a847fb


To help us isolate and assess any instability I started a gateway server (similar to ipfs.io except http:// and running on 8080):
http://ipfs.biblepay.org:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt
We may want to change the biblepay links to go through this gateway to remove instability.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 09:43:58 am
Going forward does the QT wallet also run a IPFS daemon? Or is this specifically tied to masternode holders? Or participation is a separate configuration? Can't wait to try out the new build! :)

Curious your thoughts on content control/censorship. Say someone uploads copyright material, x-rated videos, etc. Can we vote down, or do we work with IPFS directly to censor this material?

So, Ive been thinking about the topology, and I think it will be a nightmare if we build IPFS code into the regular user build (IE the non sanc build), one because of the code volatility, two most users will not set the IPFS firewall up correctly, it makes our normal user process much more complicated, the files will probably be over-stored on every user machine.  So I wanted to start by looking at this from the Sanc perspective.  If we require Sancs to run IPFS, that would give us approx. 250~ nodes of storage for biblepay, and those guys are usually running in the cloud where the firewall config is easy, and they would be the ones paid for proof-of-storage.  (We can talk about Mining for proof-of-storage later), Im considering this topology for :  Jumpstarting biblepay with IPFS, integration with DAHF, and proof-of-document-storage.

As far as durability, Im thinking each Sanctuary that runs IPFS will scan the active transactionids with attachments, and verify the amount was Paid for storage.  If paid, it will verify it has the file in the local repo (by doing an ipfs get if its not there). 
As far as proof-of-document-storage, we need a way to enforce that the sanc itself is doing its job.  Sort of a system where one sanc picks a random active document and checks to see if its actually available on 10 sancs.  Any sanc that has the document missing is somehow flagged as a bad actor.
Maybe we withhold payments to sancs who are bad actors (IE they lose their position in the sanc queue for sanc payments).
In this way we could just split the document fees among all the sancs (or give the document fee to the next sanc in line for payment, for efficiency reasons), but hit the sanctuary with a hard penalty if they stop running ipfs.

As far as X-Rated content, Im big into ensure they dont store that!  I am so big against this and viruses, that maybe the answer is we do not store unencrypted documents on our system!  Maybe we need to enforce encryption, so only the sender and receiver can actually do anything with the file.  Of course that hoses up our vision of storing our wiki and web site in our own file system.

We have to also consider what ipfs says about restricted content (lets say its an unreleased movie).  Someone uploads an unreleased movie into the ipfs biblepay storage.  Their stance is its not a copyright violation because its stored as a merkle-dag, I believe.  But that isnt good enough for us, as I dont want any x-rated files in our chain, or a copy of a virus.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 09:54:40 am
A couple more important notes about IPFS:

Unreliability:
Since https://ipfs.io/ipfs is a free public service gateway, I've noticed that its up and down.  This morning during testing I couldnt download any files (it hangs).  Other times, it works great.  So obviously we will need to create our own.  In this first version for biblepay the gateway is hardcoded in as "ipfs.io" so expect the hiccups to occur.  We can offer a separate download link directly from IPFS (IE going around the web resolution) to see if its specifically the gateway web server or not.

MIMEs:
In this first version, we take the IPFS hash of the file, and provide url's that end with the IPFS hash of the file.  This works for most things as the browser detects the mime type.  In the future it is possible for us to create a directory shell for the file and provide the file name and extension and still be IPFS compliant.  This will allow the link to be opened with a file extension like this:
ipfs.io/ipfs/directory_hash/file_name.file_extension  (This may be helpful for us when we are writing a web site or wiki etc).

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 10:11:48 am
One thing we might be able to do to be DMCA compliant (I'm creating a term here for the sake of the discussion, called DMCA compliant which means: we refuse to store x-rated or illegal files, we refuse to store copyrighted works), and calling it DMCA compliance. 
Maybe we refuse uploads into our repository that are not encrypted with a key found in the biblepay.conf file (IE documentkey), and it must not be blank. 
Then if an organization uses us for storage they can give that key to their customer (for decryption), but to us, we are just storing merkle-dag blocks of encrypted data.
For the biblepay-foundation web site and DAHF:  we can share those two keys with everyone, then people can click on the website and the DAHF links and it will find the key to decrypt those without doing additional user work.  I suppose we will need a 'keyring'.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 12:04:40 pm
Please test this gateway with a file uploaded outside of biblepay into IPFS:

http://ipfs.biblepay.org:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 12:06:44 pm
I see there is a version of IPFS available on .NET:
https://github.com/richardschneider/net-ipfs-api

Not sure how good it is, but thats exciting to know.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: T-Mike on August 28, 2018, 12:16:15 pm
Installing now. What do you want me to test? I'm using headless by the way.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 12:21:45 pm
Installing now. What do you want me to test? I'm using headless by the way.

Everything in the OP post.  The tests are primarily for QT.

On headless you can only test one command: exec ipfsadd documentname.

This version is a proof-of-concept to show that a user can attach a document to a transaction and the receiver (or anyone in this case can open that from IPFS).
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: T-Mike on August 28, 2018, 12:47:35 pm
Everything in the OP post.  The tests are primarily for QT.

On headless you can only test one command: exec ipfsadd documentname.

This version is a proof-of-concept to show that a user can attach a document to a transaction and the receiver (or anyone in this case can open that from IPFS).

Ah yes, sorry. I actually read it then forgot.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 02:46:36 pm
Windows 1.1.4.7 is out there now!

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 03:31:47 pm
I forgot to mention guys:  To add an attachment,  from QT, click the Send Tab, populate the address (or click donate to foundation), and click the "Attach File" button (which  happens to be transparent, which is a bug - will be fixed soon).  Pick a file from the picker then it will add it to the transaction.

Once its actually Sent, it will be added to IPFS; if it fails to go to IPFS you will see "transaction create failed" and your money will not be deducted or burned and the tx will be cancelled.

Then after you sent it successfully, go to the QT transaction list and double click the Transaction.  You can either click Open Attachment, or you can scrape the link out of the description and check for the document in IPFS.  You should be able to modify the link with the biblepay IPFS gateway and see the same doc from our gateway.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on August 28, 2018, 04:25:04 pm

MacOS testnet version is available in
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 04:59:09 pm
So here is one idea we could potentially compete in the proof-of-document storage business:

1) All docs uploaded into the biblepay network must be encrypted; most likely we enforce an encryption mechanism based on a keypair before we store the file in IPFS.  Our stance would be only the uploader or (shared key recipient) can actually decrypt and use the file.  This should pass DMCA compliance.

2) To enforce Sanctuary compliance and document Quality-of-service, we modify the Sanctuary voting process to do the following:  Currently sanctuaries vote for each other (for proof-of-service) to be paid when they prove another node is online (thats how masternode winners gets populated, the vote count next to the sanc shows the winners for that block).  We modify this process to pull actual document hashes from the chain (from leased docs), and we verify N (maybe 10) documents actually exist on the target sanc (by checking the merkle-dag tree on the foreign sanc using IPFS) and then we vote for payment.  Any sanc that fails even one merkle-dag check means we do not vote for that sanc for payment - meaning it should fall off the payment list if its either not running IPFS or not maintaing a directory.

It would be interesting to evaluate how much benefit this would provide biblepay.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on August 28, 2018, 06:04:16 pm
Ive updated, cleaned and reindexed my testnet server, v1.1.4.7

Code: [Select]
getblockhash 53960
fe0857f5************c1b13f8

Old notes on setting up Testnet Masternode:
https://forum.biblepay.org/index.php?topic=190.msg3701#msg3701

Ive installed ipfs in /home and have the daemon running

Masternode says PRE-ENABLED state, but I just started it again anyways,
"masternode list" shows all other masternodes as NEW_START_REQUIRED?

UPDATE: Masternode ENABLED now

Do we need multiple masternodes enabled to test?

===

Please test this gateway with a file uploaded outside of biblepay into IPFS:
http://ipfs.biblepay.org:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

Code: [Select]
This site canít be reached
ipfs.biblepay.org took too long to respond.
Search Google for ipfs biblepay org 8080
ERR_CONNECTION_TIMED_OUT
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on August 28, 2018, 06:31:02 pm

So, if sender & recipient can view attachment only... is this like an extension of signed messages? Does that mean public content will be hosted via IPFS but not required to be peers by BiblePay sanctuaries? M
aking attachments only visible to sender & recipient is very low utility and limited use case don't you think?

IPFS handles illegal content by blocking the hash (https://discuss.ipfs.io/t/avoid-hosting-of-illegal-material/48). I think people will use attachment feature more if content has option to be public. Maybe a checkbox to opt-in making attachment private & encrypted, so only sender & recipient can view. I think if we have issues with illegal content due to higher adoption, this is a good issue to have and can be dealt with if we ever cross that bridge. For now, getting people to join BBP due to innovative feature is important for BBP's survival...

I can't reach the site either, but I was able to see your hi.txt containing hello by using ipfs directly.

Quote
C:\>ipfs ls /ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/
QmSkYzY65dGXo8q6kjrsj1erH4bLZmyQoHDd8wwoAKpG8V 15 hi.txt

C:\>ipfs cat /ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt
hello
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on August 28, 2018, 10:23:36 pm

Wow, it actually works pretty good. :-*
Windows 10 64-bit.

> Test attaching a document to a new QT Send Transaction

Looks like c:\ is prefixed to the URL.

For example, if I want to upload a file located in --
C:\temp\GatewayArchNP_EN-US13744808809_1366x768.jpg , QT actually looks for
c:\c:\temp/GatewayArchNP_EN-US13744808809_1366x768.jpg

When I attach file, the URL is file:///C:/temp/GatewayArchNP_EN-US13744808809_1366x768.jpg

QT wallet responds with IPFS Attachment Failed. IPFS File not found.

If I remove c:/ then the send button works: file:///temp/GatewayArchNP_EN-US13744808809_1366x768.jpg

I don't know code, but found the error message in src/rpcblockchain.cpp , around line 6400 , something about sPath...

Also, if we if attach file from non C: drive, what will happen. Will need to test again (e.g. attachment is from e: drive)


~~~

I uploaded a 21MB video. BiblePay took the file, but there was no progress indicator.

> Test double clicking the transaction list and viewing the attached IPFS file hash

Works with no checkboxes ticked on.

Is there a file size limit or file type restriction? I tried uploading 21MB video. It uploaded okay it seems, but doesn't show up in Transaction Details.

If after ipfs.exe uploads the file, what happens to the file if I decide to not send the transaction. Is the file deleted on the server? Worried about DDoS type of issue where files are uploaded, but no transaction sent.

> Test Opening the IPFS document link

IPFS Document: Navigate to document QmanVaVYE1phtQeQqp23SZk6FM5nWBRu2KD9d6eaGZHV1P 
Transaction ID: ce930cf4b4794964ca69129c7ef51ba99601ba588f055b717036645c34cf2869-000

IPFS Document: Navigate to document QmcUr2WpiEg6ZWwTdHRDfxNVZzwpns7pdoYSQyt46wMHyX 
Transaction ID: 45d826b3e6f24da2dd6379fedf10413dc9dab9132b0b1c390110fe6a7667861e-000

* Make blue link clickable as well under Transaction Details?
* Make a newline so Transaction ID is in its own line after IPFS document
* Maybe instead of blue checkmark icon on left column (for confirmed), have a clickable paper clip icon to indicate there is attachment with transaction?

> Test the fee charged for BiblePay storage

What fee?
> Assess exact root cause of IPFS instability; IPFS.io links are down right now, but ipfs.biblepay.org worked. Are you going to make ipfs.biblepay.org HTTPS?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 28, 2018, 11:22:07 pm
Ok, there was a firewall rule needed for the ipfs gateway 8080 - fixed.

Ill check out the other stuff in the AM.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 07:06:25 am
Ive updated, cleaned and reindexed my testnet server, v1.1.4.7

Code: [Select]
getblockhash 53960
fe0857f5************c1b13f8

Old notes on setting up Testnet Masternode:
https://forum.biblepay.org/index.php?topic=190.msg3701#msg3701

Ive installed ipfs in /home and have the daemon running

Masternode says PRE-ENABLED state, but I just started it again anyways,
"masternode list" shows all other masternodes as NEW_START_REQUIRED?

UPDATE: Masternode ENABLED now

Do we need multiple masternodes enabled to test?

===

Code: [Select]
This site canít be reached
ipfs.biblepay.org took too long to respond.
Search Google for ipfs biblepay org 8080
ERR_CONNECTION_TIMED_OUT

The ipfs.biblepay.org ipfs gateway should be up now, can you please try again?

As far as masternodes, the code doesnt enforce anything right now, so as long as we have a few IPFS nodes running we are good.  We can run a command once we have a few successful attachments to ensure these are available on multiple nodes.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 07:39:00 am
Wow, it actually works pretty good. :-*
Windows 10 64-bit.
> Test attaching a document to a new QT Send Transaction
Looks like c:\ is prefixed to the URL.
For example, if I want to upload a file located in --
C:\temp\GatewayArchNP_EN-US13744808809_1366x768.jpg , QT actually looks for
c:\c:\temp/GatewayArchNP_EN-US13744808809_1366x768.jpg
When I attach file, the URL is file:///C:/temp/GatewayArchNP_EN-US13744808809_1366x768.jpg

QT wallet responds with IPFS Attachment Failed. IPFS File not found.
If I remove c:/ then the send button works: file:///temp/GatewayArchNP_EN-US13744808809_1366x768.jpg
I don't know code, but found the error message in src/rpcblockchain.cpp , around line 6400 , something about sPath...
Also, if we if attach file from non C: drive, what will happen. Will need to test again (e.g. attachment is from e: drive)

~~~

I uploaded a 21MB video. BiblePay took the file, but there was no progress indicator.
> Test double clicking the transaction list and viewing the attached IPFS file hash
Works with no checkboxes ticked on.

Is there a file size limit or file type restriction? I tried uploading 21MB video. It uploaded okay it seems, but doesn't show up in Transaction Details.

If after ipfs.exe uploads the file, what happens to the file if I decide to not send the transaction. Is the file deleted on the server? Worried about DDoS type of issue where files are uploaded, but no transaction sent.

> Test Opening the IPFS document link

IPFS Document: Navigate to document QmanVaVYE1phtQeQqp23SZk6FM5nWBRu2KD9d6eaGZHV1P 
Transaction ID: ce930cf4b4794964ca69129c7ef51ba99601ba588f055b717036645c34cf2869-000

IPFS Document: Navigate to document QmcUr2WpiEg6ZWwTdHRDfxNVZzwpns7pdoYSQyt46wMHyX 
Transaction ID: 45d826b3e6f24da2dd6379fedf10413dc9dab9132b0b1c390110fe6a7667861e-000

* Make blue link clickable as well under Transaction Details?
* Make a newline so Transaction ID is in its own line after IPFS document
* Maybe instead of blue checkmark icon on left column (for confirmed), have a clickable paper clip icon to indicate there is attachment with transaction?

> Test the fee charged for BiblePay storage

What fee?
> Assess exact root cause of IPFS instability; IPFS.io links are down right now, but ipfs.biblepay.org worked. Are you going to make ipfs.biblepay.org HTTPS?


Good morning all... :)

"Looks like c:\ is prefixed to the URL."
So on this issue, during programming I was testing against linux and hadn't got into the quirks on windows yet.  So it looks like QT changes backslash to forward slash and prepends with the "file:\\\".  The C, D, E drive prefix is not a problem (thats there because the file picker does support picking from various hard drives).  Really the whole problem can be eliminted in this version if you do this:  After picking the file, remove the "file:\\\" (note the three slashes here).  Thats all the code needs to do on win & linux to get it to work.   YAY!

Wow, a 21 meg file, thats cool, lets see if it plays from our gateway link, can you paste the link?

As far a limit I have it set to 90 Megs right now.  Its not a limit in IPFS.  So we can go higher.
As far as doing whats called 'garbage collection', this is the activity of deleting files that users didnt pay for, I did think of that, and I think we can handle that in this way:  The sancs maintain a directory of files that are paid for.  The rest get garbage collected.

As far as clicking on the link to navigate to the doc from inside the view window:  I originally planned this to work-but due to a limitation in QT the textedit wont let you click external links  (Great) meaning in order to get it to work we have to upgrade the viewport to be like our prayer view page (I think its a rich edit box) and I dont feel like breaking anything yet, so thats why I added the Open Attachment button, :).    So yes this needs to be on our enhancement list. (You can copy the link btw and manually open it).

Newline after txid: OK will do

Paperclip idea to show attachment is preset:  Good idea

So Ill make a new release today with the fix to the file picker, but guys, now that you know the workaround this should not be a showstopper.













Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 07:51:03 am

So, if sender & recipient can view attachment only... is this like an extension of signed messages? Does that mean public content will be hosted via IPFS but not required to be peers by BiblePay sanctuaries? M
aking attachments only visible to sender & recipient is very low utility and limited use case don't you think?

IPFS handles illegal content by blocking the hash (https://discuss.ipfs.io/t/avoid-hosting-of-illegal-material/48). I think people will use attachment feature more if content has option to be public. Maybe a checkbox to opt-in making attachment private & encrypted, so only sender & recipient can view. I think if we have issues with illegal content due to higher adoption, this is a good issue to have and can be dealt with if we ever cross that bridge. For now, getting people to join BBP due to innovative feature is important for BBP's survival...

I can't reach the site either, but I was able to see your hi.txt containing hello by using ipfs directly.

I do think you make very good points, although before I delve into the nuances of this, I checked out your link for 'blocking the hash' at ipfs and came to a different conclusion.  I believe IPFS' position on this is not that they will create a blacklist, nor a whilelist, nor a blocked hash blacklist, but instead that IPFS is a protocol and not a store.  Their position is that it is the users responsibility who owns the hardware to determine if they should host a hash.  Meaning that if Im joe six pack, I should be smart enough to not navigate to an x-rated link, but if I do, its up to me to delete that file quickly from my store as I dont want it hosted.

The IPFS architecture is set in a way that if you pull a file from (the IPFS decentralized host network) and do not delete it from your IPFS local store, you are now hosting it-as its now in your repo.  If you dont want copyrighted moves hosted you should not "get" them in the first place.

So my argument here is biblepay is not capable of policing what we store.

Before delving into this, my position by default is that we should not provide a service where one can upload a virus (imagine Not-Petya), or Porn, or an unreleased Movie, into biblepays store (of sancs) unencrypted, in a way where the world at large can download these three things from an association from one of our blocks transactions.  It is simply unresponsible for us to take the position that "oh maybe it wont happen", I feel like we have to be vigilant and set a precedent of quality here so the world knows we are Christian (IE our light is shining).

I do understand your view that what use or utility are you if every file is encrypted?  You want me to pay 5000 bbp to host my web site files with you for 6 months, but you dont even let me view them without a decryption key?  LOL.  On the other end of the spectrum we have a real estate lease, where they want to put the PDF in and its just one document for a business transaction, that person may not mind transmitting the key via email to the customer.  But I do realize, the revenue cut would be dramatic.

So, my initial design idea to tackle this would be to require encryption, but support an on-the-fly decryption if the consumer has the key.  For example if the gateway supported this feature
ipfs.io/ipfs/hash/myfile.pdf?key=blah

Then the file is decrypted and served using the key blah.  I realize it looks pretty lame and weak, but it technically takes the responsibility off of biblepay (as to what we are hosting) and allows the file to be useful in a website etc.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on August 29, 2018, 07:56:26 am
win 1147- testnet ... peerlist is empty and i cant synching
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 08:12:45 am
win 1147- testnet ... peerlist is empty and i cant synching

I see the problem; node.biblepay.org is not resolving.  I made a couple DNS changes.
It should resolve itself in an hour.

In the mean time try from the RPC:
addnode dns2.biblepay.org
addnode testnet.biblepay.org

And see if it comes up.

This should not require a config change for new users in one hour.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on August 29, 2018, 09:02:08 am
ok,thanks....it looks that im connected to 2 peers

super
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on August 29, 2018, 09:37:30 am
Please test this gateway with a file uploaded outside of biblepay into IPFS:
http://ipfs.biblepay.org:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

Tested again, I see "hello"!
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 09:45:51 am
Tested again, I see "hello"!

Ok good, and Sun was asking if this gateway link could be https, Yes, I already bought a certificate but for a long drawn out technical reason, the IPFS is not working in HTTPS mode yet (I think those guys have it in a tunnel over there) so eventually Yes, we will crack this if this gets to prod.  Its not one of those easy things to turn on.

So do we have any other docs to click on yet?

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 09:52:19 am
Ok good, and Sun was asking if this gateway link could be https, Yes, I already bought a certificate but for a long drawn out technical reason, the IPFS is not working in HTTPS mode yet (I think those guys have it in a tunnel over there) so eventually Yes, we will crack this if this gets to prod.  Its not one of those easy things to turn on.

So do we have any other docs to click on yet?

Heres one I sent to myself this morning:

http://ipfs.biblepay.org:8080/ipfs/QmdZUzpryL6adzUBvzgA8Mzgfy8aPNqN6iXFQnv8wGsMjc


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on August 29, 2018, 10:30:20 am
I had to upgrade my server, was freezing up, 100% disk usage, couldnt pinpoint the issue, didnt see anything big in ~/.biblepaycore hmmm

===

I clicked the Add Recipient button in the Send tab,
It opened a 2nd set of duplicate inputs with an extra Attached File field
I had already filled out the first set of inputs, and filled 2nd with same info,
I clicked send and it said I couldnt have the same address in both,
I got confused b/c I wasnt sure why I needed 2 different addresses, put in a diff one and sent

I think this is the correct link format? (address file attached to and filename):
http://ipfs.biblepay.org:8080/ipfs/yLoLPque5vWgYJLmZjYJzicYPDphUP2HdT/BiblePay_Logo_Transparent_3000x1000.png

Code: [Select]
invalid ipfs path: selected encoding not supported
Transaction only has 1 confirmation so far
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 11:04:19 am
I had to upgrade my server, was freezing up, 100% disk usage, couldnt pinpoint the issue, didnt see anything big in ~/.biblepaycore hmmm

===

I clicked the Add Recipient button in the Send tab,
It opened a 2nd set of duplicate inputs with an extra Attached File field
I had already filled out the first set of inputs, and filled 2nd with same info,
I clicked send and it said I couldnt have the same address in both,
I got confused b/c I wasnt sure why I needed 2 different addresses, put in a diff one and sent

I think this is the correct link format? (address file attached to and filename):
http://ipfs.biblepay.org:8080/ipfs/yLoLPque5vWgYJLmZjYJzicYPDphUP2HdT/BiblePay_Logo_Transparent_3000x1000.png

Code: [Select]
invalid ipfs path: selected encoding not supported
Transaction only has 1 confirmation so far
So no you dont have to click Add recipient to the send transaction.  You can just click Send, and click Add File (not add recipient).

Yeah the UI wont let you send two transactions to the same person; you would have to send one to the foundation, one to yourself for example (but , you only need to send one transaction, not two so thats moot point).

The link you pasted seems like something you made up, could you paste the one from the double click of the transaction?  It should end in a hash.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on August 29, 2018, 11:04:41 am
is any restriction on testnet?

addnode=dns2.biblepay.org
addnode=testnet.biblepay.org
testnet=1
genproclimit=15


mining only with 1core .....

attach file is for what? isnt this IPFS like offering space..... how much space i offer,so many BBP getting?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on August 29, 2018, 12:08:16 pm
Im unable to duplicate it, but I believe the confusion stemmed from the Attached File field being missing the first time I was using the Send tab after upgrading, and then it showed up on the Add Recipient. It shows up every time now.

I also had no idea there was a multiple recipient feature LOL

=

When I click "Open Attachment", no action occurs,
Im using Lubuntu with just Firefox installed

I composed the link above as a guess

Transaction ID: 51bf312343f303c1ca9234f2515b8947738a0303fd8742b4b7d4aa377620cbf0-000

XML:
{PACK} {MT}MESSAGE{/MT} {MK}OUT_TX{/MK} {MV}  {/MV} {/PACK} {PACK} {MT}ATTACHMENT{/MT} {MK}OUT_TX{/MK}{MK}{/MV}{ipfshash}{/ipfsash}{/PACK} ...

Im unable to copy paste from Vultr Console / Lubuntu (nor know how to change resolution)
(What Linux GUIs do you guys use in Testnet?)
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 12:19:31 pm
Im unable to duplicate it, but I believe the confusion stemmed from the Attached File field being missing the first time I was using the Send tab after upgrading, and then it showed up on the Add Recipient. It shows up every time now.

I also had no idea there was a multiple recipient feature LOL

=

When I click "Open Attachment", no action occurs,
Im using Lubuntu with just Firefox installed

I composed the link above as a guess

Transaction ID: 51bf312343f303c1ca9234f2515b8947738a0303fd8742b4b7d4aa377620cbf0-000

XML:
{PACK} {MT}MESSAGE{/MT} {MK}OUT_TX{/MK} {MV}  {/MV} {/PACK} {PACK} {MT}ATTACHMENT{/MT} {MK}OUT_TX{/MK}{MK}{/MV}{ipfshash}{/ipfsash}{/PACK} ...

Im unable to copy paste from Vultr Console / Lubuntu (nor know how to change resolution)
(What Linux GUIs do you guys use in Testnet?)
Oh I think I see whats going on; OK so on the copy-paste.  Im using debian 7-64 on my dev machine and it has copy-paste, but my vultr nodes do not, but you can get around this by doing a 'showblock blocknumber' then 'getrawtransaction txid' after you send it from your VM (if you want to scrape it from your windows box).  Yeah I dont know of a way to get copy-paste working in vultr. 

So that tx you pasted above looks like nothing worked on it; thats OK, I think we need to start over.
(I can see because the ipfshash is empty above in the XML).

So just try attaching a file from the beginning, and ensure the attachment textbox is populated and no error results after sending.
Then double click the transaction  from the transaction list and see if the Link in it is populated (in blue).  If its not, that explains why the Open Attachment button does not work.

Then once that opens for you, then from another machine try to get the txid then we will pull the data out of it and Ill try it from the gateway address to see if its replicating.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on August 29, 2018, 12:53:44 pm
ok just sent another transaction,
in transaction details I see green "IPFS Document:" hyperlink "Navigate to document Q*"
Open Attachment button works now, it opened up the image in Firefox

https://ipfs.io/ipfs/QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r (https://ipfs.io/ipfs/QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r)

1 confirmation so far

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on August 29, 2018, 01:50:37 pm
need i BBP for testing this?

yfhc5FdNSyAYyB4Fx4aJ2x4KoXiGuXxhyH

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 02:11:43 pm
need i BBP for testing this?

yfhc5FdNSyAYyB4Fx4aJ2x4KoXiGuXxhyH

A little bit yes, so you can send some tx to yourself.

The purpose of attaching an IPFS document to a transaction is to make biblepay useful without bloating the blockchain (with the bytes of the document).

Sent 200K (as I only have 1 mil on my dev machine right now).
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 02:13:32 pm
ok just sent another transaction,
in transaction details I see green "IPFS Document:" hyperlink "Navigate to document Q*"
Open Attachment button works now, it opened up the image in Firefox

https://ipfs.io/ipfs/QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r (https://ipfs.io/ipfs/QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r)

1 confirmation so far

Its working I see it!

http://ipfs.biblepay.org:8080/ipfs/QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r

So our gateway is working also, good.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on August 29, 2018, 08:09:45 pm
> Wow, a 21 meg file, thats cool, lets see if it plays from our gateway link, can you paste the link?

File uploaded I think (maybe it is in your hash list), but it doesn't show up in transaction details. Also tried 10 meg jpeg and doesn't show up.

I think ipfs has js wrapper to play videos, but not sure if they play outright. Maybe it is browser dependent.

I tried the following and I seem to be peered with you now: :)

ipfs pin add QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 29, 2018, 09:44:35 pm
> Wow, a 21 meg file, thats cool, lets see if it plays from our gateway link, can you paste the link?

File uploaded I think (maybe it is in your hash list), but it doesn't show up in transaction details. Also tried 10 meg jpeg and doesn't show up.

I think ipfs has js wrapper to play videos, but not sure if they play outright. Maybe it is browser dependent.

I tried the following and I seem to be peered with you now: :)

ipfs pin add QmcbKYZRFGYsmBiEhqjQ4J7uoGY5DSHqs5uQg7fqsW7J1r

That doesnt make sense; the code either accepts it or rejects it.  I do not think you tested it properly; can you Upload the file into the transaction and double click it, and then paste it, and that means the Single test was performed?  (In contrast to uploading it and forgetting to check on the transaction list message). 

If something fails, you can just post the entire error message here, since this is an atomic test.

So far, I see no flaws in the system except user error and the ipfs gateway going up-down at random times.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on August 29, 2018, 10:01:26 pm
yfhc5FdNSyAYyB4Fx4aJ2x4KoXiGuXxhyH

I sent you some.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on August 29, 2018, 10:18:43 pm
That doesnt make sense; the code either accepts it or rejects it.  I do not think you tested it properly; can you Upload the file into the transaction and double click it, and then paste it, and that means the Single test was performed?  (In contrast to uploading it and forgetting to check on the transaction list message). 

If something fails, you can just post the entire error message here, since this is an atomic test.

So far, I see no flaws in the system except user error and the ipfs gateway going up-down at random times.


There is a third possibility isn't there besides accepts it or rejects it... and that is... it accepts it, processes the upload, but the transaction ID doesn't include the ipfs hash in the transaction details? I wish I was smart enough to understand my 2.4MB file works, but not a 4MB file. 4mb jpeg - can you try to attach this file and see if you can replicate what I've been saying? This is the file: https://upload.wikimedia.org/wikipedia/commons/1/1e/Caerte_van_Oostlant_4MB.jpg (https://upload.wikimedia.org/wikipedia/commons/1/1e/Caerte_van_Oostlant_4MB.jpg)

So, I was able to upload a 2.4MB file:

Quote
Status: 0/unconfirmed, broadcast through 2 nodes
Date: 8/29/2018 20:15
To: klondike testnet yfhc5FdNSyAYyB4Fx4aJ2x4KoXiGuXxhyH
Debit: -106.00000000 tBiblepay
Net amount: -106.00000000 tBiblepay

IPFS Document: Navigate to document QmceXVXDjork9aT2MoVnroYRc3RxLXdJY8UA9872y8o9FV  Transaction ID: e32028e1f1576521540a450b137947c1b690bca598e7660b7bea6e62710d8f43-000



Debug information

Debit: -119 989.49989340 tBiblepay
Credit: 119 883.49989340 tBiblepay

Transaction:
CTransaction(hash=e32028e1f1, ver=1, vin.size=1, vout.size=2, nLockTime=54059)
    CTxIn(COutPoint(77527314927f560414ba52f571fab48f701b34385b22cad00f7db7984b4a635c, 2), scriptSig=483045022100d68ecb44edde, nSequence=4294967294)
    CTxOut(nValue=106.00000000, scriptPubKey=76a914d49b3ddf917fb85e7e39b440)
    CTxOut(nValue=119883.49989340, scriptPubKey=76a914fa9ea914a5d2e9b1e1541102)

Inputs:
yga9M5wSn9zUp8oTi4Yzqom7F7D1rWRApc Amount=119 989.49989340 tBiblepay IsMine=true IsWatchOnly=false


XML:
{PACK}{MT}ATTACHMENT{/MT}{MK}OUT_TX{/MK}{MV}QmceXVXDjork9aT2MoVnroYRc3RxLXdJY8UA9872y8o9FV{/MV}{ipfshash}QmceXVXDjork9aT2MoVnroYRc3RxLXdJY8UA9872y8o9FV{/ipfshash}{/PACK}{PACK}{MT}MESSAGE{/MT}{MK}OUT_TX{/MK}{MV}test 6 big truck video {/MV}{/PACK}{change}1{/change}

but this one 4mb jpeg doesn't show the ipfs hash in transaction details.

Quote
Status: 0/unconfirmed, broadcast through 2 nodes
Date: 8/29/2018 20:15
To: klondike testnet yfhc5FdNSyAYyB4Fx4aJ2x4KoXiGuXxhyH
Debit: -107.00000000 tBiblepay
Net amount: -107.00000000 tBiblepay
Transaction ID: 87126350a8ba79a679e66807e0e17b22b1dfdf3d3db64775fd3565ecad9eb2e7-000



Debug information

Debit: -443 465.02000000 tBiblepay
Credit: 443 358.02000000 tBiblepay

Transaction:
CTransaction(hash=87126350a8, ver=1, vin.size=1, vout.size=2, nLockTime=54059)
    CTxIn(COutPoint(45d826b3e6f24da2dd6379fedf10413dc9dab9132b0b1c390110fe6a7667861e, 1), scriptSig=483045022100f73941971aeb, nSequence=4294967294)
    CTxOut(nValue=107.00000000, scriptPubKey=76a914d49b3ddf917fb85e7e39b440)
    CTxOut(nValue=443358.02000000, scriptPubKey=76a914a7c5ca8893336e79620b426b)

Inputs:
yM4cUY5evJmSKJEjbTsgxh6RQbpqk53kYe Amount=443 465.02000000 tBiblepay IsMine=true IsWatchOnly=false


XML:
{PACK}{MT}ATTACHMENT{/MT}{MK}OUT_TX{/MK}{MV}{/MV}{ipfshash}{/ipfshash}{/PACK}{PACK}{MT}MESSAGE{/MT}{MK}OUT_TX{/MK}{MV}test 7 4mb jpg {/MV}{/PACK}{change}1{/change}
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 30, 2018, 07:16:43 am

There is a third possibility isn't there besides accepts it or rejects it... and that is... it accepts it, processes the upload, but the transaction ID doesn't include the ipfs hash in the transaction details? I wish I was smart enough to understand my 2.4MB file works, but not a 4MB file. 4mb jpeg - can you try to attach this file and see if you can replicate what I've been saying? This is the file: https://upload.wikimedia.org/wikipedia/commons/1/1e/Caerte_van_Oostlant_4MB.jpg (https://upload.wikimedia.org/wikipedia/commons/1/1e/Caerte_van_Oostlant_4MB.jpg)

So, I was able to upload a 2.4MB file:

but this one 4mb jpeg doesn't show the ipfs hash in transaction details.


Ok, Sorry I was getting 'code defensive' there, its a new day!  Hang on.

First on the 2meg video you uploaded:
https://ipfs.io/ipfs/QmceXVXDjork9aT2MoVnroYRc3RxLXdJY8UA9872y8o9FV

Its working, so thats nice and exciting.  Thanks.


On the 4mb jpeg, great news, I reproduced:  Your right- I dont see the ipfs hash and it is a 3rd condition! Thanks.    Checking....

Ok the 4mb jpeg issue is resolved.  It had to do with the base64 conversion setting, its fixed, now you can upload it, and now you should see any errors appear in biblepay that have to do with attaching problems bubble on the screen.

Here is the link to the one I just uploaded:
http://ipfs.biblepay.org:8080/ipfs/QmawtK1eHmjUcF4z87bEg7819hk6FE9cPTsG7HKcLCBZ5x


Please try again...



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 30, 2018, 11:13:01 am
Ok, so in the next version you should be able to see the attachment icon (right now its two pieces of paper but we can have Marcus take a look at possibly changing to a paperclip later),  fixed the filepicker to fix the disk path on windows and unix, added the newline between the rows,
and a biggie in testnet:  Something was filling up the drives with spam - I found the root cause and modified the miner to require the signed cpid in order to mine and that fixed the spam.

Im still working on some other issues so I wont release this version yet.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on August 30, 2018, 02:27:48 pm
Something was filling up the drives with spam - I found the root cause and modified the miner to require the signed cpid in order to mine and that fixed the spam.

Do you know where the file spam is Rob?
My testnet machine is at 99% disk usage again haha, I closed biblepay for now until next update,

I appreciate all your hard work Rob! and thank you to everyone helping test

UPDATE: Thanks sunk818, it was the debug.log in ~/.biblepaycore/testnet3
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on August 30, 2018, 06:06:54 pm
Do you know where the file spam is Rob?
My testnet machine is at 99% disk usage again haha, I closed biblepay for now until next update,

I appreciate all your hard work Rob! and thank you to everyone helping test

I think he means the debug.log file -- it gives me block rejected message... the block only mines every 15 minutes, so you end up with log spam.

shrinkdebuglog=1 in your biblepay.conf will trim the debug.log file upon restart of the QT wallet

Quote
2018-08-30 23:09:21
ProcessBlockFound::Generated 531.66870093
2018-08-30 23:09:21 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-08-30 23:09:21 ERROR: ProcessBlockFound -- ProcessNewBlock() failed, block not accepted
2018-08-30 23:09:21 CBlock(hash=0115fdd5b3d2a857c4ac2bbea3a11e77968d14028e126b4af8ec8cd94ef33eaf, ver=536870912, hashPrevBlock=63fc662f64b9e4568a2cb639d55c737bce9f0838e8acf8d7b0c658a33e446936, hashMerkleRoot=dec75898b0af80571ea24833187edfd4ecaf0920d2256a87e049f5e2d8f217c5, nTime=1535670561, nBits=1f0300d6, nNonce=26, vtx=1)
  CTransaction(hash=dec75898b0, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 037cd3000101)
    CTxOut(nValue=531.66870093, scriptPubKey=2103c55c0fc363e85b294f7c610314)
    CTxOut(nValue=4785.01830833, scriptPubKey=76a9149ee0a2740dbc649db0f13245)


blocks need to be mined right, so transactions go through in testnet? Or no?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 31, 2018, 09:06:11 am
Open attachment button in transaction details is visible whether an attachment exists or not.

Do you think Open Attachment button should be hidden when there is no attachment?

Yes, I meant to do that, and forgot about that!  Doing now....

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on August 31, 2018, 09:13:17 am
Do you know where the file spam is Rob?
My testnet machine is at 99% disk usage again haha, I closed biblepay for now until next update,

I appreciate all your hard work Rob! and thank you to everyone helping test

UPDATE: Thanks sunk818, it was the debug.log in ~/.biblepaycore/testnet3

Thanks Togo!

Yeah, for now if you could delete testnet3\debug.log after its running. 

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 01, 2018, 09:45:50 am
macOS wallet worked fine. Uploaded an image without having to make any adjusts to the file name in the form field.


Good article on using IPFS to share documents where it is only available to the recipient (encrypted with their public key) as one use case:
https://medium.com/@mycoralhealth/learn-to-securely-share-files-on-the-blockchain-with-ipfs-219ee47df54c


Hey all, with our recent drop in price I believe we need a huge end of September release.

Please keep eyes peeled for the next testnet version.
Im working on merging in a spork to give us the ability to test PODC with NO TEAM requirement, and we really need a few cpids to verify this works properly.
We also need to test the blacklist spork, to ensure if a team is changed to a blacklisted team, the payment stops in the superblock.

I'm adding in IPFS integration now, to provide proof-of-document-storage (I suppose we can call this PODS).  Ill explain the spork settings later today.  But in PODS, the next version will provide Durability for the data (meaning for the life of the lease, you can download the file from the gateway).  It will also enforce sanctuary payment by requiring Sancs to host the files that are paid for in the chain (otherwise the sanc loses the sanctuary payment).

Regarding the encryption method, yes, I like that idea for one-to-one transfers, and Im on the fence as to if we should Require that when we go live with PODS, or allow the docs to be downloaded as we have them now (through the gateway).  I understand both sides of the argument- usability for future decentralized websites vs privacy.  The IPFS system is storing the files as blocks, so currently the data is not encrypted.  But we should consider encrypting everything before we go to prod with the feature.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 01, 2018, 12:30:42 pm
Hi guys,

Bit late to the party, but didn't have physical access to my computers, so I couldn't start my dedicated testnet-rig. Fired up two testnet wallets now. One on Win 10 and one on Xubuntu 16.04.

The Win 10 one is synced and I successfully sent a file to the ipfs:

http://ipfs.biblepay.org:8080/ipfs/QmfCcpUP5oM6L96NPeeQ54SUzXyA7E2wWC2scy5LNL4wV1 (http://ipfs.biblepay.org:8080/ipfs/QmfCcpUP5oM6L96NPeeQ54SUzXyA7E2wWC2scy5LNL4wV1)

The Xubuntu-one has some trouble connecting to peers (already did the 'addnodes') and also seems to have a lot of tBBP although it's a brand new Xubuntu installation and the wallet says it's only synched about 400 blocks thus far.

I haven't started a Sanctuary yet (still waiting for the Xubuntu-wallet to sync), but I did install the IPFS without errors (it seems).

I also started a teamless boinc-account that is building up RAC as we speak :)

One question: my Sanctuaries are hosted on a low-budget VPS, with I think 20GB HDD-space. Can it be possible that Sanctuaries become 'corrupt' (don't know the right phrasing here) when people start sending very large files?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 07:54:28 am
Just to update everyone waiting for the release:  It should be ready within a couple hours.  It's running a little late due to some of the debugging required for ipfs.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 08:18:50 am
There seems to be an indication that there's a max storage you can configure:
https://github.com/ipfs/go-ipfs/pull/4388/commits/0d2cc04fa7691f04b899e0a6dede77db96356e68 (https://github.com/ipfs/go-ipfs/pull/4388/commits/0d2cc04fa7691f04b899e0a6dede77db96356e68)


For BBP & IPFS, you'd have to guarantee at least 6 months which is the whole point of attaching files within BBP right? If BBP checks that all documents are available to peer on each sanctuary, then these documents need to be "pinned" (https://discuss.ipfs.io/t/trying-to-better-understand-the-pinning-concept/754) since garbage collection jeopardize document availability on a specific sanctuary.

Since we don't know the total storage required, some sanctuaries will likely perform the heavy lifting if they have the storage required. Other sanctuaries would likely make a best effort and let garbage collection remove the less accessed documents. I don't know what Rob is thinking about Proof of Document Storage (PoDS), but I could what percentage of the documents you can store on your sanctuary affecting how you are paid.

Since my sanctuary with 50GB storage can only store 50% of the required documents, I'm only eligible for 50% of the PoDS reward. But my other sanctuary with 100GB storage can host 100% of the required documents, is eligible for 100% PoDS reward. PoDS reward could be 10% (e.g. 3.85% of the monthly payouts) of the 38.5% Sanctuary. Initially, every sanctuary would get 100% PoDS reward, but if PoDS takes off, those with more storage can receive the full 100% payment over time.

Note that some of these things can be made into network adjustable sporks, so we can adapt to them.
On the comfortable hosting size per node, I personally think allocating 10-20 gig of storage should be enough, and Jaap, you can set a limit in the config file of ipfs so it does not overrun your drive.  I was thinking, BBP should be relatively cheap per K of storage, but we can probably charge quite a bit for a bigger file.  If its going to be hosted on 270 nodes, and available to the world, that file might be $5 per month.  We can discuss pricing later.  We also have to discuss how the sancs receive compensation for the attachment (currently I have it set as *penalization* if they dont participate in doc storage) but if there is a 1000 bbp fee on a transaction, right now it would go to the orphanage foundation.  This has to be well thought out and implemented for prod.

As far as Sanc penalization, heres how it is set currently:  We do have a spork that turns the PODS system on or off (podsmode=0 means its off in prod).  When it is on, we have a health check feature.  When a sanctuary is assessing proof-of-service, this is the activity of a current sanctuary looping through all known biblepay sancs, and checking if they are online (end-to-end verification), when the sanc assesses the state of another node to be healthy it stores a value of either "ENABLED" or "WATCHDOG_EXPIRED", enabled means the other sanc is online.  So with PODS, we add in an extra similar health check for IPFS.  If the foreign sanctuarys gateway port (8080) cannot serve the healthcheck.dat file properly, the sanc gets marked as "DOWN".  This would actually cause my sanc to not vote on the down sanc for regular sanc payment.    Meaning masternode winners votes would shrink - specifically with the downed sancs not being voted for payment.

However if the sanc is UP, if we have PODS in STRICT mode, it will then try to pull down a file that is paid for and leased in biblepay.  If that file is pulled successfully by hash (we check the actual downloaded files bytes length and the web servers stated byte length also) then we add that file to our own repo if it was missing, and we mark it as downloaded (this is so we dont keep asking for the same failed file), but if that sanc is not able to deliver that particular file, we mark that sanc as "DOWN".

So in this way all sancs who are up and host all the files are fully paid, sancs who are up and only host half the files should technically receive about 50% of the winning blocks still, because they will still receive some UP votes from other sancs who happen to be checking the files that *are* present.  So another words, I think we might want to KISS, and allow payment to be :
SANC REWARD * PERCENT OF FILES SHARED = SANC REWARD * PERCENT OF VOTES = THEORETICAL EQUAL PAYMENT
In practice, if this does not work, we will need to add an affinity of file hashes to votes, but I really would rather resist adding complexity if possible.
(This is how it is programmed now - sancs vote for you if you have the file the sanc is checking for at the time it is ready to vote and you are up).  Sancs do keep a list of what files were checked in memory and loop through different files automatically.

In this next version each sanc has to run ipfs, and in the ipfs config file (see ipfs stats for the location of config) you must edit the config and change the "127.0.0.1:8080" binding to "your_sanc_ip:8080" - this is so you can host a public file gateway.  Note that by default your IPFS does not run a gateway, so this has to be manually changed by everyone.  I have not investigated automating ipfs installs yet etc.

Please try to edit your ipfs configs and restart the daemon, and see if you all can pull a file from:

http://yor_sanc_ip:8080/ipfs/testhash

Once you get that working your sanc is ready to be ipfs enabled.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 09:19:59 am
Steps to edit IPFS config in order to expose your IPFS for Biblepay integration:

cd ~/.ipfs
nano config
scroll down to line 47 (the line reads:  "Gateway:" /ip4/127.0.0.1/tcp/8080)

Edit the line to be:
"Gateway": "/ip4/your_sanc_public_ip/tcp/8080"

Stop the daemon and restart the daemon.

Once ipfs is running again, verify you can pull a file from your sanc publically:

http://yor_sanc_ip:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 10:38:11 am
I just pushed 1.1.4.8, I'll explain some more after church.

Building Windows now.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 02, 2018, 01:15:30 pm
cd ~/.ipfs

Hmm... This is strange...

The IPFS seems to be installed without error, and also running, but this directory doesn't seem to exist.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 05:51:10 pm
Hmm... This is strange...

The IPFS seems to be installed without error, and also running, but this directory doesn't seem to exist.
Hi Jaap, please try
ipfs stats repo

The Repo path should be in there.
Then cd to it and nano config.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 05:58:04 pm
Windows should be out there now.  1.1.4.8.

Ill set up a sanc and then attempt to edit the OP with additional tests, etc.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 06:33:14 pm
Should I blacklist Gridcoin for the blacklist test?  (Rosetta - team 12575), the way this works is we add 12575 to the team blacklist.  (We support multiple teams, so we can also blacklist 30513 (Gridcoin World Community Grid)?

EDIT:  Ok, in testnet I blacklisted WCG Gridcoin and Rosetta Gridcoin.
And I just removed the team requirement for WCG and Rosetta.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 02, 2018, 10:59:53 pm
So far so good, at this point all please upgrade to 1.1.4.8, set up a sanc, verify we are synced, and lets regroup when the sancs say "ENABLED" (we must have some enabled to test ipfs).

I just brought two up, one is enabled now and one is enabling.

The sporks are ready so for now we can use Togo's account as our non biblepay team guinea pig, my CPID as a biblepay guinea pig and we still need a volunteer to set the team as Gridcoin to test the blacklist.

Please set up your IPFS gateway and test with a file from the public IP (as shown in the example above) and then we will regroup.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 03, 2018, 01:08:35 am
Hi Jaap, please try
ipfs stats repo

The Repo path should be in there.
Then cd to it and nano config.

Thanks! I looked into it and the path is correct now. I adjusted the config and tried to start the daemon. Got this error message:

Code: [Select]
Error: serveHTTPGateway: manet.Listen(/ip4/MYIP/tcp/8080) failed: listen tcp4 MYIP:8080: bind: cannot assign requested address
Also, I have joined team Gridcoin (teamid=12575) and have connected my wallet to Rosetta@home :)


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 03, 2018, 02:00:40 am
Trying to figure out how to set up masternode for the first time. Getting close I hope.

Anyway, uploaded 21MB video. Plays right away on Chrome on ipfs.biblepay.org ... ipfs.io was initially spinning but retried after 4 min and the video played finally.

Is the default for Open Attachment ipfs.io or ipfs.biblepay.org ? I'm getting better results with ipfs.biblepay.org on the immediate request.

http://ipfs.biblepay.org:8080/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4 (http://ipfs.biblepay.org:8080/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4)

Quote
Status: 0/unconfirmed, broadcast through 3 nodes
Date: 9/2/2018 23:58
Source:IPFS-AttachmentTo: Donate to Orphans yadZnJ3hD3FRC8CiLZEVNqejvQFgNtu5ci
Debit: -10 000.00000000 tBiblepay
Transaction fee: -0.00100000 tBiblepay
Net amount: -10 000.00100000 tBiblepay

IPFS Document: https://ipfs.io/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4 (https://ipfs.io/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4) 
IPFS Alternate Link: http://ipfs.biblepay.org:8080/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4 (http://ipfs.biblepay.org:8080/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4) 

Transaction ID: a9f2bbf8855aa9aa71e6de5cc7397311fc82f880900a2c49ec74bd1793d9366d-000

Debug information

Debit: -5316.68724846 tBiblepay
Debit: -5316.68700926 tBiblepay
Credit: 633.37325772 tBiblepay

Transaction:
CTransaction(hash=a9f2bbf885, ver=1, vin.size=2, vout.size=2, nLockTime=54656)
    CTxIn(COutPoint(aaa458f8c797caff2c1496523284a76a3b7221abbfdca63aa6359c699dd3b025, 0), scriptSig=47304402200da7c97435fa16, nSequence=4294967294)
    CTxIn(COutPoint(9e369d963e90c5391f85c57a36422b4e910a084e473f12d6d3722b41c99ee95a, 0), scriptSig=4730440220774651f9309807, nSequence=4294967294)
    CTxOut(nValue=633.37325772, scriptPubKey=76a914b578b1aceae2ee88995f786f)
    CTxOut(nValue=10000.00000000, scriptPubKey=76a9149cff090c148949e19f4ed915)

Inputs:
yYk8sAG6VrArnyuy5fi6rBjQfEaamd69kq Amount=5316.68724846 tBiblepay IsMine=true IsWatchOnly=false
testnet ycQa1b7LZUUbNunvgtWhvxPyT5YhEcJr5D Amount=5316.68700926 tBiblepay IsMine=true IsWatchOnly=false

XML:
{change}1{/change}{PACK}{MT}ATTACHMENT{/MT}{MK}OUT_TX{/MK}{MV}QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4{/MV}{ipfshash}QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4{/ipfshash}{/PACK}{PACK}{MT}MESSAGE{/MT}{MK}OUT_TX{/MK}{MV} {/MV}{/PACK}
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 03, 2018, 02:09:27 am
Trying to figure out how to set up masternode for the first time. Getting close I hope.


I found this guide to be good for testnet:
https://forum.biblepay.org/index.php?topic=108.msg1444#msg1444

I just run the testnet-sactuary hot on my home linux rig.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 07:21:34 am
Thanks! I looked into it and the path is correct now. I adjusted the config and tried to start the daemon. Got this error message:

Code: [Select]
Error: serveHTTPGateway: manet.Listen(/ip4/MYIP/tcp/8080) failed: listen tcp4 MYIP:8080: bind: cannot assign requested address
Also, I have joined team Gridcoin (teamid=12575) and have connected my wallet to Rosetta@home :)
Jaap, sounds like you are close.
This is a guess, but could you double check the IP and format you typed into the config?  I would first go to your host, and check your public IP address, and make sure it matches.  Also you can type 'ipfs daemon' (after stopping the daemon) and check to see the lines it prints out that it is binding your IP address to other ports; write down the IP that is the public one- see that it matches your host (is your host vultr?) if it does you may just have an error on your gateway entry; it may be case sensitive also, compare the original entry from another node before changing it to the new entry?

One other thing to see: maybe you are already running a service on 8080.  Try to stop the ipfs daemon first, then type 'telnet localhost 8080', see if it replies.  If it does you are running something else on the box, maybe another type of web server.  You would have to stop that other thing first, then start the 'ipfs daemon'.


EDIT:  I just saw your post above that you run the linux rig hot at home; thats probably the issue; if running from the house, you would need to open up the firewall port 8080 and forward it to the linux rig, then it should bind the port.  One side issue with running at home:  check to see if your sanc says ENABLED in our list - the new PODS enforcer requires a sanc to be ENABLED to check its PODS quality.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 07:30:10 am
Trying to figure out how to set up masternode for the first time. Getting close I hope.

Anyway, uploaded 21MB video. Plays right away on Chrome on ipfs.biblepay.org ... ipfs.io was initially spinning but retried after 4 min and the video played finally.

Is the default for Open Attachment ipfs.io or ipfs.biblepay.org ? I'm getting better results with ipfs.biblepay.org on the immediate request.

http://ipfs.biblepay.org:8080/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4 (http://ipfs.biblepay.org:8080/ipfs/QmdMBtPQvuqPyCJgnczh5RcVeS5mi5UJydLzeVvcGcccd4)

Thats great!  Yeah, maybe we should make the default open behavior biblepay.org, sounds good.
I had that pausing issue with ipfs.io also - I can imagine they are probably being pounded by tons of 'free' traffic from every direction.

So today Im going to look into adding a fee to the attachment.  For now its just basically a fee per K being attached, and I think we should start by enforcing that it goes to the orphan foundation otherwise the transaction commit fails.  I will also add a process that pins docs that are legitimate and
 have paid PODS fees. 




Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 03, 2018, 09:32:34 am
Jaap, sounds like you are close.
This is a guess, but could you double check the IP and format you typed into the config?  I would first go to your host, and check your public IP address, and make sure it matches.  Also you can type 'ipfs daemon' (after stopping the daemon) and check to see the lines it prints out that it is binding your IP address to other ports; write down the IP that is the public one- see that it matches your host (is your host vultr?) if it does you may just have an error on your gateway entry; it may be case sensitive also, compare the original entry from another node before changing it to the new entry?

One other thing to see: maybe you are already running a service on 8080.  Try to stop the ipfs daemon first, then type 'telnet localhost 8080', see if it replies.  If it does you are running something else on the box, maybe another type of web server.  You would have to stop that other thing first, then start the 'ipfs daemon'.


EDIT:  I just saw your post above that you run the linux rig hot at home; thats probably the issue; if running from the house, you would need to open up the firewall port 8080 and forward it to the linux rig, then it should bind the port.  One side issue with running at home:  check to see if your sanc says ENABLED in our list - the new PODS enforcer requires a sanc to be ENABLED to check its PODS quality.

Hmmm...

This is strange.... I'll just post the entire startup proces here (and delete it later).
The firewall on that rig is disabled and the port was already forwarded to that rig in my router.

When I telnet it (making sure the daemon is off) it says 'telnet: Unable to connect to remote host: Connection refused' so I guess there is nothing else running on that port.


Code: [Select]
jaap@jaap-HP-Pavilion-dm1-Notebook-PC:~/.ipfs$ ipfs daemon
Initializing daemon...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/192.168.1.149/tcp/4001
Swarm listening on /ip4/192.168.1.183/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:1703:2523:7b47:8758/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:3868:73f5:7c0f:da76/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:4366:95b0:9e9c:d91d/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:8c52:a032:7b4a:f626/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560::25e/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560::595/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmeUCRZ8edAvqojUZgWBsQ69XaSdWozhwHK39UMrskfYky
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/192.168.1.149/tcp/4001
Swarm announcing /ip4/192.168.1.183/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:1703:2523:7b47:8758/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:3868:73f5:7c0f:da76/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:4366:95b0:9e9c:d91d/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:8c52:a032:7b4a:f626/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560::25e/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560::595/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
Error: serveHTTPGateway: manet.Listen(/ip4/84.29.208.33/tcp/8080) failed: listen tcp4 84.29.208.33:8080: bind: cannot assign requested address
Received interrupt signal, shutting down...

The adjusted line in my config is:
Code: [Select]
"Gateway": "/ip4/84.29.208.33/tcp/8080"
The rule on my router is:
Code: [Select]
8080 test
IPv4-TCP, UDP
From any host in wan
Via any router IP at port 8080
IP 192.168.1.149, port 8080 in lan

I triple-checked the external-ip.

Btw, I don't think I had problems running Sanctuaries in testnet this way before. The necessary ports are open, and the external IP almost never changes (only sometimes after a reset of the providers modem). My Sanctuary is:
Code: [Select]
71c44d1cc7e3f29aac6b0c8e9ade3c43cc79da3d0c22f183439d8e440c6a7d3e
I will try and restart the rig. See if that helps.
EDIT: restarting didn't help :(
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 12:05:13 pm
Hmmm...

This is strange.... I'll just post the entire startup proces here (and delete it later).
The firewall on that rig is disabled and the port was already forwarded to that rig in my router.

When I telnet it (making sure the daemon is off) it says 'telnet: Unable to connect to remote host: Connection refused' so I guess there is nothing else running on that port.


Code: [Select]
jaap@jaap-HP-Pavilion-dm1-Notebook-PC:~/.ipfs$ ipfs daemon
Initializing daemon...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/192.168.1.149/tcp/4001
Swarm listening on /ip4/192.168.1.183/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:1703:2523:7b47:8758/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:3868:73f5:7c0f:da76/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:4366:95b0:9e9c:d91d/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560:0:8c52:a032:7b4a:f626/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560::25e/tcp/4001
Swarm listening on /ip6/fdbe:33bf:560::595/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmeUCRZ8edAvqojUZgWBsQ69XaSdWozhwHK39UMrskfYky
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/192.168.1.149/tcp/4001
Swarm announcing /ip4/192.168.1.183/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:1703:2523:7b47:8758/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:3868:73f5:7c0f:da76/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:4366:95b0:9e9c:d91d/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560:0:8c52:a032:7b4a:f626/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560::25e/tcp/4001
Swarm announcing /ip6/fdbe:33bf:560::595/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
Error: serveHTTPGateway: manet.Listen(/ip4/84.29.208.33/tcp/8080) failed: listen tcp4 84.29.208.33:8080: bind: cannot assign requested address
Received interrupt signal, shutting down...

The adjusted line in my config is:
Code: [Select]
"Gateway": "/ip4/84.29.208.33/tcp/8080"
The rule on my router is:
Code: [Select]
8080 test
IPv4-TCP, UDP
From any host in wan
Via any router IP at port 8080
IP 192.168.1.149, port 8080 in lan

I triple-checked the external-ip.

Btw, I don't think I had problems running Sanctuaries in testnet this way before. The necessary ports are open, and the external IP almost never changes (only sometimes after a reset of the providers modem). My Sanctuary is:
Code: [Select]
71c44d1cc7e3f29aac6b0c8e9ade3c43cc79da3d0c22f183439d8e440c6a7d3e
I will try and restart the rig. See if that helps.
EDIT: restarting didn't help :(

Hi Jaap,

Looking at my vultr node when I bring up ipfs daemon, I see in my case, the line that says "swarm listening on" with the port of 4001:  Mine is listening on the External IP, looks like you have two adapters, and it binds one to one internal ip and another to another internal IP on yours.  Could you try binding 4001 to your external IP (I think you have to edit the config to change that), and also point the 4001 port to that machine in the firewall then restart the daemon and see if it changes the behavior of 8080.

Btw, on your Sanc, does it actually flip over to ENABLED eventually?  Edit:  Your sanc address should start with a "y", I cant see your status on my node.

EDIT 2:  Btw Jaap its really easy to run a sanc side-by-side your running prod sanc - do you have one on vultr?  If you have a lot of problems, it might be easier to do that.




Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 03, 2018, 12:15:57 pm
Hi Jaap,

Looking at my vultr node when I bring up ipfs daemon, I see in my case, the line that says "swarm listening on" with the port of 4001:  Mine is listening on the External IP, looks like you have two adapters, and it binds one to one internal ip and another to another internal IP on yours.  Could you try binding 4001 to your external IP (I think you have to edit the config to change that), and also point the 4001 port to that machine in the firewall then restart the daemon and see if it changes the behavior of 8080.

Btw, on your Sanc, does it actually flip over to ENABLED eventually?  Edit:  Your sanc address should start with a "y", I cant see your status on my node.

Thanks for the help Rob!

Yes, I already though it was strange that it was listening to two internal IP's. The other internal IP is my second testnet rig (Win 10 with just a mining wallet), and I actually already tried closing programs on that other rig.

Hmm... Going to look into this a bit later.

About the Sanctuary:
It's actually 'ENABLED' in my own list, but I'm the only enabled sanctuary in my list, two others seem online but they have a 'WATCHDOG EXPIRED' label.

Well... If both the IPFS and the Sanctuary don't work like they're supposed to, then I'll just have to fire up another VPS.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 03, 2018, 01:46:17 pm
Hmmm... Can't get it to work.

When I use the localhost ip the deamon starts, when I use the external Ip it doesn't...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 02:07:44 pm
Hmmm... Can't get it to work.

When I use the localhost ip the deamon starts, when I use the external Ip it doesn't...

So whats your IP Jaap, Id like to see if your sanc is enabled on my node?

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 03, 2018, 02:26:11 pm
So today Im going to look into adding a fee to the attachment.  For now its just basically a fee per K being attached, and I think we should start by enforcing that it goes to the orphan foundation otherwise the transaction commit fails.  I will also add a process that pins docs that are legitimate and  have paid PODS fees. 

I hope you're not realistically thinking $5/mo is appropriate fee because Google Drive is $1.99/mo for 100GB of storage. It is a commodity service so realistically, you should expect pennies to store attachments or not even charge at all. $5/mo is a pipe dream is extremely unrealistic.

Whatever fee you collect and have it go to orphan fund is a good idea. Every little bit helps and hopefully the service will scale over time.

Still having some issues with bigger attachments. Tried a 45MB video but I don't see it in the transaction.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 03, 2018, 02:47:42 pm
So whats your IP Jaap, Id like to see if your sanc is enabled on my node?

84.29.208.33
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 03:54:22 pm
I hope you're not realistically thinking $5/mo is appropriate fee because Google Drive is $1.99/mo for 100GB of storage. It is a commodity service so realistically, you should expect pennies to store attachments or not even charge at all. $5/mo is a pipe dream is extremely unrealistic.

Whatever fee you collect and have it go to orphan fund is a good idea. Every little bit helps and hopefully the service will scale over time.

Still having some issues with bigger attachments. Tried a 45MB video but I don't see it in the transaction.

Its not smart to compare apples to oranges; we're renting files on a blockchain, not space on a centralized server.  Not sure why you would consider a decentralized chain less valuable than a centralized company who can delete your account at any time, or decide what news is important for us. 

Nah, it shouldnt necessarily be pennies.  It takes what, 20% of a sanctuary to run ipfs?  With that logic why run ipfs at all.  (I wouldnt participate if I was only getting $1 total per month for hosting ipfs).

Anyway we are storing 250 copies of a file while the cloud servers are using RAID or storing across 20 machines for durability, so we are also doing 10* the work per file.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 04:21:16 pm
84.29.208.33

You show as UP on my nodes.  Let me see why I dont show as UP on your node.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 04:40:53 pm
You show as UP on my nodes.  Let me see why I dont show as UP on your node.

Im *.*.88.12, and the problem was I was running watchman in PROD mode, update to testnet mode - now I see myself as ENABLED, Jaap do you see me as enabled now?

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 03, 2018, 05:15:31 pm
Its not smart to compare apples to oranges; we're renting files on a blockchain, not space on a centralized server.  Not sure why you would consider a decentralized chain less valuable than a centralized company who can delete your account at any time, or decide what news is important for us.

I was speaking from an average consumer that'd not looking to host files that may be deleted or censored. That seems like an edge case unlikely to happen to 99% of common users. For all intents and purposes, I'm not concerned as consumer how a file is distributed (centralized or decentralized). I just care that the URL works when I need access to it.

Is the marketing plan to encourage uploads that is likely to be censored elsewhere? That seems very risky and controversial. If you're expecting $5/mo premium, then I suppose that has to be the group of people we target? If files are on the ipfs.biblepay.org:8080, does that make files censorship proof? Or biblepay would be ultimate authority on what lives and dies on IPFS?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 03, 2018, 05:25:17 pm
I was speaking from an average consumer that'd not looking to host files that may be deleted or censored. That seems like an edge case unlikely to happen to 99% of common users. For all intents and purposes, I'm not concerned as consumer how a file is distributed (centralized or decentralized). I just care that the URL works when I need access to it.

Is the marketing plan to encourage uploads that is likely to be censored elsewhere? That seems very risky and controversial. If you're expecting $5/mo premium, then I suppose that has to be the group of people we target? If files are on the ipfs.biblepay.org:8080, does that make files censorship proof? Or biblepay would be ultimate authority on what lives and dies on IPFS?

Why even discuss it if we dont agree on "Im not concerned as a consumer how a file is distributed (centralized or not)".  Because in this case, if you aren't concerned that we are working on blockchain technology, then why discuss it.  As that is a night and day difference.

I feel we are making a mistake to not encrypt the files.  No, they will not be censored or deleted if they are encrypted.  If they are not encrypted, they could be censored, deleted, taken down by government request, etc.

The fee is currently set at .0002 bbp per K of filesize uploaded.  We can potentially lower it after we know the system works properly, but it would be doubtful that it should be lowered so low that it fills up 10 gigs of each of our sanc drives.  But I would lower it incrementally so that we receive some moderate usage by the network.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 03, 2018, 06:08:11 pm
Why even discuss it if we dont agree on "Im not concerned as a consumer how a file is distributed (centralized or not)".  Because in this case, if you aren't concerned that we are working on blockchain technology, then why discuss it.  As that is a night and day difference.

I feel we are making a mistake to not encrypt the files.  No, they will not be censored or deleted if they are encrypted.  If they are not encrypted, they could be censored, deleted, taken down by government request, etc.

The fee is currently set at .0002 bbp per K of filesize uploaded.  We can potentially lower it after we know the system works properly, but it would be doubtful that it should be lowered so low that it fills up 10 gigs of each of our sanc drives.  But I would lower it incrementally so that we receive some moderate usage by the network.

I feel the point of any feature is to help secure funding orphans long-term. This means daily usage by BBP users which leads to higher BBP prices. You don't get to increasing daily users without targeting more of the user segment. Some will care about the technology, but more will care about the UI and how usable the product is.

We've talked about this before, but if files are not public by default, it removes the usefulness of the feature. Can encryption be optinal?

Can "smart fee" (dynamic pricing) be applied to PoDS as well? If storage capacity is close to full, charge more... if not, charge less. It'd be like charging for parking in a small lot. Cheaper when there's fewer cars, but more expensive as there's limited space. I suppose we could extend it and have long-term parking vs short-term as well...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 03, 2018, 11:53:06 pm
Im back, upgraded $10/month Ubuntu 16.04 Vultr server to v1.1.4.8b of BiblePay

Steps to edit IPFS config in order to expose your IPFS for Biblepay integration:

cd ~/.ipfs
nano config
scroll down to line 47 (the line reads:  "Gateway:" /ip4/127.0.0.1/tcp/8080)

Edit the line to be:
"Gateway": "/ip4/your_sanc_public_ip/tcp/8080"

Stop the daemon and restart the daemon.

Once ipfs is running again, verify you can pull a file from your sanc publically:

http://yor_sanc_ip:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

Updated ipfs config with my IP Address

Link works!
http://144.202.69.224:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

I had to open up port 8080

Code: [Select]
sudo ufw allow 8080/tcp
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 04, 2018, 01:20:51 am
Im *.*.88.12, and the problem was I was running watchman in PROD mode, update to testnet mode - now I see myself as ENABLED, Jaap do you see me as enabled now?

Yes :)

Still can't get IPFS to work though >:(

And about the feature in general: the original reason for it's conception is to use it for DAHF right? And the ability  for other users to store data is a - welcome - side-effect, right?

The main reason for implementing this short-term is to add value to the coin, but we really should explain to all the users how this is also one of the building blocks for DAHF. At least, I hope to use this angle for marketing.

Or am I mistaken in this?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 04, 2018, 11:53:29 am
Yes :)

Still can't get IPFS to work though >:(

And about the feature in general: the original reason for it's conception is to use it for DAHF right? And the ability  for other users to store data is a - welcome - side-effect, right?

The main reason for implementing this short-term is to add value to the coin, but we really should explain to all the users how this is also one of the building blocks for DAHF. At least, I hope to use this angle for marketing.

Or am I mistaken in this?
Hi Jaap,
It might be easier - if you already rent one node somewhere - to get testnet sanc and ipfs running there first, then circle back to the house and try googling the issue as maybe the cloud vps will be revealing.  Id try to offer assistance, but IPFS is not working for me at home either, and since our sancs require a public IP anyway with watchman, to me its more straightforward to recommend you run testnet side by side a running prod sanc with ipfs.  (unless you dont have a cloud vps).

Anyway, Yes, originally IPFS was added to solve the block-sync issue to ensure DAHF could be decentralized properly.  However, this turned into a pretty strong value-add feature for our coin.  We can potentially say:  We have side-chain document storage, with 200* redundancy.  (The ipfs merkle dag *is* a side chain of blocks and a filehash *is* related to one of our txids on-chain).  Thats a pretty strong feature.  If we can guarantee that the document is available for the life of the lease, that is a great value add for biblepay.  We rent document storage for a fee.  I added the feature last night that quotes and charges:  When you make an attachment, we quote a price and it appears in the confirm fee dialog as a separate PODS fee now.  The fee is tithed to the orphan foundation.  Sancs only poll and verify Paid for non-expired docs in the next version.

So I think from a PR perspective, we can say we are offering PODS (proof-of-document-storage) and side-chain file storage.  We should not try to claim we offer hard drive space as I feel thats too competetive.  And yes we do need to ensure we have at least 1 gig of space for DAHF, as I feel we will have the ability to sync financial blocks in the future.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 04, 2018, 01:41:26 pm
I can recommend HostBRZ - $12/yr: https://lowendbox.com/blog/hostbrz-vps-shared-reseller-hosting-from-2-year/ (https://lowendbox.com/blog/hostbrz-vps-shared-reseller-hosting-from-2-year/)

Vultr too pricey especially just for testnet.

25GB should be enough for BBP blockchain (production) and IPFS storage.


I tried port forwarding at home, but masternode status still doesn't like it... so I'll attempt a VPS as well. I've got a few I can add bbp testnet on to.

Id be wary to recommend anything other than ubuntu64 on vultr which is only $5 per month - but if you guys have actual experience with it maybe its good.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 05, 2018, 04:40:21 am
I specifically mentioned that he might already be running a sanctuary in prod.  Not recommending that he rents a host just for testnet.

Id be wary to recommend anything other than ubuntu64 on vultr which is only $5 per month - but if you guys have actual experience with it do what is best for yourselves.

I actually have an AWS instance that I can use for testnet. They have a free-tier program, and they basically give you a 1-core, 1GB RAM, 30GB SSD instance :)
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 05, 2018, 04:46:05 am
Hi Jaap,
It might be easier - if you already rent one node somewhere - to get testnet sanc and ipfs running there first, then circle back to the house and try googling the issue as maybe the cloud vps will be revealing.  Id try to offer assistance, but IPFS is not working for me at home either, and since our sancs require a public IP anyway with watchman, to me its more straightforward to recommend you run testnet side by side a running prod sanc with ipfs.  (unless you dont have a cloud vps).

Anyway, Yes, originally IPFS was added to solve the block-sync issue to ensure DAHF could be decentralized properly.  However, this turned into a pretty strong value-add feature for our coin.  We can potentially say:  We have side-chain document storage, with 200* redundancy.  (The ipfs merkle dag *is* a side chain of blocks and a filehash *is* related to one of our txids on-chain).  Thats a pretty strong feature.  If we can guarantee that the document is available for the life of the lease, that is a great value add for biblepay.  We rent document storage for a fee.  I added the feature last night that quotes and charges:  When you make an attachment, we quote a price and it appears in the confirm fee dialog as a separate PODS fee now.  The fee is tithed to the orphan foundation.  Sancs only poll and verify Paid for non-expired docs in the next version.

So I think from a PR perspective, we can say we are offering PODS (proof-of-document-storage) and side-chain file storage.  We should not try to claim we offer hard drive space as I feel thats too competetive.  And yes we do need to ensure we have at least 1 gig of space for DAHF, as I feel we will have the ability to sync financial blocks in the future.

I'm going to run the testnet IPFS on a seperate (AWS) VPS. I'm also going to leave the on at home running and I'll try to fix the issue with that one.

And thanks for the explanation about IPFS and DAHF.

Offtopic: I'm thinking maybe we could create an interview-style explanation about the DAHF-plans in the near future? I'll just ask a lot of noob-questions (acting as if I never heard of any of the terms before, and I don't have the slightest clue about what such a DAHF could be beneficial for me), and you could give me answers. I think that might be a good PR-thing to explain what we're trying to do to the general public.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 05, 2018, 05:21:58 am
This is my boincinfo. I've joined team Gridcoin and don't seem to be receiving any payments :)

Code: [Select]
12:18:30

exec getboincinfo


12:18:33

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 426706,
  "NextSuperblockHeight": 56836,
  "NextSuperblockBudget": 542174,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 100.02,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 12575,
  "c852da1a620ad630b70c8ec1ccdee366_WCGRAC": 0,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 423,
  "Total_RAC": 100.02,
  "Total Payments (One Day)": 9424,
  "Total Payments (One Week)": 28416,
  "Total Budget (One Day)": 1626522,
  "Total Budget (One Week)": 2168696,
  "Superblock Count (One Week)": 93,
  "Superblock Hit Count (One Week)": 5,
  "Superblock List": "56539,56143,56044,55747,47629",
  "Last Superblock Height": 56737,
  "Last Superblock Budget": 542174,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 5.793957905272723,
  "Magnitude (One-Week)": 13.10280463467448
}

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 05, 2018, 09:44:02 am
This is my boincinfo. I've joined team Gridcoin and don't seem to be receiving any payments :)

Code: [Select]
12:18:30

exec getboincinfo


12:18:33

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 426706,
  "NextSuperblockHeight": 56836,
  "NextSuperblockBudget": 542174,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 100.02,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 12575,
  "c852da1a620ad630b70c8ec1ccdee366_WCGRAC": 0,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 423,
  "Total_RAC": 100.02,
  "Total Payments (One Day)": 9424,
  "Total Payments (One Week)": 28416,
  "Total Budget (One Day)": 1626522,
  "Total Budget (One Week)": 2168696,
  "Superblock Count (One Week)": 93,
  "Superblock Hit Count (One Week)": 5,
  "Superblock List": "56539,56143,56044,55747,47629",
  "Last Superblock Height": 56737,
  "Last Superblock Budget": 542174,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 5.793957905272723,
  "Magnitude (One-Week)": 13.10280463467448
}

Excellent, double checking your info on my testnet sanc3, I believe it is working properly - as far as the team blacklist.  I received my boinc reward on sanc3 properly also (being in team biblepay).  Now for sanity, lets have you switch from Gridcoin to a random team please?  Lets see if payments start? 

Btw Jaap, did adding an attachment to a transaction work for you properly and you can view it on the gateway URL?


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 05, 2018, 10:05:18 am
Excellent, double checking your info on my testnet sanc3, I believe it is working properly - as far as the team blacklist.  I received my boinc reward on sanc3 properly also (being in team biblepay).  Now for sanity, lets have you switch from Gridcoin to a random team please?  Lets see if payments start? 

Btw Jaap, did adding an attachment to a transaction work for you properly and you can view it on the gateway URL?

Okay, I switched from Gridcoin to Russia Team (teamid=264).

About the attachment. Yes, I tried that, it was successful, and I can view it on the biblepay gateway. I posted it a few pages back :)

http://ipfs.biblepay.org:8080/ipfs/QmfCcpUP5oM6L96NPeeQ54SUzXyA7E2wWC2scy5LNL4wV1

Setting up my sanc on AWS now btw...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 06, 2018, 05:36:04 am
Okay, got the AWS Sanc up an running. Same issue with the IPFS :(

Copy-past of firewall, IPFS and telnet attempt:
Code: [Select]
ubuntu@ip-172-31-37-125:~$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
8080/tcp                   ALLOW       Anywhere
22/tcp                     LIMIT       Anywhere
40000/tcp                  ALLOW       Anywhere
40001/tcp                  ALLOW       Anywhere
9998/tcp                   ALLOW       Anywhere
8080/tcp (v6)              ALLOW       Anywhere (v6)
22/tcp (v6)                LIMIT       Anywhere (v6)
40000/tcp (v6)             ALLOW       Anywhere (v6)
40001/tcp (v6)             ALLOW       Anywhere (v6)
9998/tcp (v6)              ALLOW       Anywhere (v6)

ubuntu@ip-172-31-37-125:~$ ipfs daemon
Initializing daemon...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/172.31.37.125/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmS25G9JVn9SJ7HpmK5JKehQBSU4LAT8YY2Fkb8RT68UgW
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/172.31.37.125/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
Error: serveHTTPGateway: manet.Listen(/ip4/18.222.48.73/tcp/8080) failed: listen tcp4 18.222.48.73:8080: bind: cannot assign requested address
ubuntu@ip-172-31-37-125:~$ telnet localhost 8080
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

I don't understand why, when I telnet the localhost port, I get a 'connection refused' error. Nothing is running on there except the wallet.

 >:(

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 06, 2018, 11:36:11 am
Okay, got the AWS Sanc up an running. Same issue with the IPFS :(

Copy-past of firewall, IPFS and telnet attempt:
Code: [Select]
ubuntu@ip-172-31-37-125:~$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
8080/tcp                   ALLOW       Anywhere
22/tcp                     LIMIT       Anywhere
40000/tcp                  ALLOW       Anywhere
40001/tcp                  ALLOW       Anywhere
9998/tcp                   ALLOW       Anywhere
8080/tcp (v6)              ALLOW       Anywhere (v6)
22/tcp (v6)                LIMIT       Anywhere (v6)
40000/tcp (v6)             ALLOW       Anywhere (v6)
40001/tcp (v6)             ALLOW       Anywhere (v6)
9998/tcp (v6)              ALLOW       Anywhere (v6)

ubuntu@ip-172-31-37-125:~$ ipfs daemon
Initializing daemon...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/172.31.37.125/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmS25G9JVn9SJ7HpmK5JKehQBSU4LAT8YY2Fkb8RT68UgW
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/172.31.37.125/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
Error: serveHTTPGateway: manet.Listen(/ip4/18.222.48.73/tcp/8080) failed: listen tcp4 18.222.48.73:8080: bind: cannot assign requested address
ubuntu@ip-172-31-37-125:~$ telnet localhost 8080
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

I don't understand why, when I telnet the localhost port, I get a 'connection refused' error. Nothing is running on there except the wallet.

 >:(

I see the problem.  This should fix the home issue also.  In vultr, the public ip of the node is the actual bound ip of the node - so the firewall rules are simple:  just listen on the public internet IP.

On the home machine, its behind a router, and you have your port port forwarded to the machines LAN ip.  On AWS, I see this is the same; you are behind a router.  Your machine IP is 172.31.37.125 and your sanc ip is 18.222.48.73.  So what we need to do is listen on:  LAN IP : 8080 (not external ip 8080) and then forward the traffic To the machine on 8080.  So just try binding your 8080 to your LAN IP.    (IE On your AWS instance, change the binding for the gateway to :      172.31.37.125:8080 and see if it comes up)....

Ill try this on my home IPFS also later when I can reboot the machine.


NOTE TO ALL TESTERS:
Im working on a new version so we can test the Non-biblepay-team percentage feature, so we will need to all upgrade testnet.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 06, 2018, 11:46:44 am
I see the problem.  This should fix the home issue also.  In vultr, the public ip of the node is the actual bound ip of the node - so the firewall rules are simple:  just listen on the public internet IP.

On the home machine, its behind a router, and you have your port port forwarded to the machines LAN ip.  On AWS, I see this is the same; you are behind a router.  Your machine IP is 172.31.37.125 and your sanc ip is 18.222.48.73.  So what we need to do is listen on:  LAN IP : 8080 (not external ip 8080) and then forward the traffic To the machine on 8080.  So just try binding your 8080 to your LAN IP.    (IE On your AWS instance, change the binding for the gateway to :      172.31.37.125:8080 and see if it comes up)....

Ill try this on my home IPFS also later when I can reboot the machine.


NOTE TO ALL TESTERS:
Im working on a new version so we can test the Non-biblepay-team percentage feature, so we will need to all upgrade testnet.

I works!  ;D Thanks Rob.

This is my home IPFS:
http://84.29.208.33:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

And this is the AWS IPFS:
http://18.222.48.73:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

Question: I'm accessing AWS via Putty. But if I close my putty session, I think that will also terminate the IPFS, or am I mistaken in this? I tried my home IPFS, but that one terminates when I close the window.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 06, 2018, 12:15:50 pm
I works!  ;D Thanks Rob.

This is my home IPFS:
http://84.29.208.33:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

And this is the AWS IPFS:
http://18.222.48.73:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt

Question: I'm accessing AWS via Putty. But if I close my putty session, I think that will also terminate the IPFS, or am I mistaken in this? I tried my home IPFS, but that one terminates when I close the window.

There are some commands that let you fork a command to run in bash (in its own session), but the better way I think is to add the 'ipfs daemon' command to the machine startup script - I believe if you : nano /etc/rc.local and add it in there somewhere before the 'exit 0' line.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 07, 2018, 02:25:49 am
There are some commands that let you fork a command to run in bash (in its own session), but the better way I think is to add the 'ipfs daemon' command to the machine startup script - I believe if you : nano /etc/rc.local and add it in there somewhere before the 'exit 0' line.

Thanks Rob. I'll try this.

Something else: I changed my team to a non-crypto non-BiblePay team and a superblock has passed, but I didn't receive a reward (I have another testnet-wallet that is connected and has a CPID that is in team-BiblePay for cross-checking). I will wait another superblock just to be sure.

Code: [Select]
09:21:24

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 426751,
  "NextSuperblockHeight": 58816,
  "NextSuperblockBudget": 542174,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 153.57,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 264,
  "Warning": "CPID c852da1a620ad630b70c8ec1ccdee366 not in team Biblepay.  This CPID is not receiving rewards for cancer research.",
  "c852da1a620ad630b70c8ec1ccdee366_WCGRAC": 0,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 523,
  "Total_RAC": 153.57,
  "Total Payments (One Day)": 12548,
  "Total Payments (One Week)": 50387,
  "Total Budget (One Day)": 3795218,
  "Total Budget (One Week)": 7048262,
  "Superblock Count (One Week)": 113,
  "Superblock Hit Count (One Week)": 14,
  "Superblock List": "58717,58519,58420,58321,57925,57826,57727,57034,56935,56539,56143,56044,55747,47629",
  "Last Superblock Height": 58717,
  "Last Superblock Budget": 542174,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 3.306265937819646,
  "Magnitude (One-Week)": 7.148854568686579
}
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 07, 2018, 09:34:10 am
Thanks Rob. I'll try this.

Something else: I changed my team to a non-crypto non-BiblePay team and a superblock has passed, but I didn't receive a reward (I have another testnet-wallet that is connected and has a CPID that is in team-BiblePay for cross-checking). I will wait another superblock just to be sure.

Code: [Select]
09:21:24

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 426751,
  "NextSuperblockHeight": 58816,
  "NextSuperblockBudget": 542174,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "yb3AGeCR9xDge8chVwi6TuDtxuMy7w4DD7",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 153.57,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 264,
  "Warning": "CPID c852da1a620ad630b70c8ec1ccdee366 not in team Biblepay.  This CPID is not receiving rewards for cancer research.",
  "c852da1a620ad630b70c8ec1ccdee366_WCGRAC": 0,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 523,
  "Total_RAC": 153.57,
  "Total Payments (One Day)": 12548,
  "Total Payments (One Week)": 50387,
  "Total Budget (One Day)": 3795218,
  "Total Budget (One Week)": 7048262,
  "Superblock Count (One Week)": 113,
  "Superblock Hit Count (One Week)": 14,
  "Superblock List": "58717,58519,58420,58321,57925,57826,57727,57034,56935,56539,56143,56044,55747,47629",
  "Last Superblock Height": 58717,
  "Last Superblock Budget": 542174,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 3.306265937819646,
  "Magnitude (One-Week)": 7.148854568686579
}

So on the non-crypto team 100% payment, I lean towards believing the logic would have worked, but I decided to refactor the magnitude assessment process to make it a little nicer (primarily because we have been adding rules over time that has made it pretty ugly), so I had to take down my sancs. 

I 'believe' im probably the only other piece of the quorum (unless Togos is coming to ENABLED right now) so that most likely why the contracts werent created.

I should have a new version for testnet by the end of the day then we can recircle and re-test the non-crypto and the next upcoming rule (the one with the % paid to non-biblepay teams).

EDIT: I forgot to answer about DAHF a few days ago:  Yes Im open to the QA, yes, that would be great btw.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 07, 2018, 12:50:28 pm

1.1.4.9-Leisure Upgrade (Mandatory for Testnet)

- Add Foundation receiving address for IPFS so we can track IPFS
payments separate from donations
- Make wallet prayers private, and require public prayers to be signed
(prevent prayer graffiti)
- Ensure miner does not submit bad blocks (help prevent forks)
- Add spork for non-biblepay-team-payment-percentage
- Refactor Sanctuary Magnitude Assessment process
- Disclose IPFS fee to user before committing transaction.  Charge a
Foundation IPFS fee when committing an IPFS transaction.
- Add IPFS altlink to transactiondescription




Alright all, everyone, please upgrade all testnet nodes.




Windows is compiling....
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 07, 2018, 01:15:13 pm
1.1.4.9-Leisure Upgrade (Mandatory for Testnet)

- Add Foundation receiving address for IPFS so we can track IPFS
payments separate from donations
- Make wallet prayers private, and require public prayers to be signed
(prevent prayer graffiti)
- Ensure miner does not submit bad blocks (help prevent forks)
- Add spork for non-biblepay-team-payment-percentage
- Refactor Sanctuary Magnitude Assessment process
- Disclose IPFS fee to user before committing transaction.  Charge a
Foundation IPFS fee when committing an IPFS transaction.
- Add IPFS altlink to transactiondescription

Alright all, everyone, please upgrade all testnet nodes.

Windows is compiling....

Upgrading to v1.1.4.9!

UPDATE: Upgraded and Masternode ENABLED

Code: [Select]
getblockhash 59184
75d44ce0****acd993768c
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 07, 2018, 03:32:49 pm
Windows is deployed.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 08, 2018, 02:49:01 am
Windows is deployed.

Thanks!

I've got two sancs with ipfs online :)
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on September 08, 2018, 02:49:47 am
Windows is deployed.

Also available for MacOS at

https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 08, 2018, 12:50:44 pm
Thanks!

I've got two sancs with ipfs online :)
Great.  I have my 2 back up again, and I see i got my last PODCs from the last few superblocks... 
Where did we leave off...  Jaap did you receive your expected payment for the non Gridcoin non Biblepay team?  The spork is set to pay .35% to non biblepay teams....

Lets see if its 35%?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 08, 2018, 02:26:05 pm
Great.  I have my 2 back up again, and I see i got my last PODCs from the last few superblocks... 
Where did we leave off...  Jaap did you receive your expected payment for the non Gridcoin non Biblepay team?  The spork is set to pay .35% to non biblepay teams....

Lets see if its 35%?

It is  8)

In the previous version and on team BiblePay I got about 1000 BBP, now I get about 300 BBP (but the RAC has probably also risen in the mean time).
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 10, 2018, 01:46:29 pm
Great job guys.

Alright, lets be patient for a day or so and add another blockbuster feature : Business Objects in BiblePay.

The ability to store a business object off-chain that conforms to GDPR regulations (IE we respect the end-users hide/delete ability).

In our first baby step toward persisting off-chain business objects we will add the ability to store a contact in biblepay (with a signed primary key).

Later we will use this for the Great Tribulation map, BiblePay babysitters, Viewing a business object in a grid, hiding/deleting a business object, adding a church as a vendor, adding an organization-network to the object (virtual permissions), and Tithing on Mobile devices (at church).

For now my goal is to explain how to save yourself in a contact record, view the contact record, test GDPR regulations, and send BBP via e-mail to someone.

The next version should be ready within 24 hours.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 11, 2018, 11:19:58 pm
... Testing locally, please standy by until tomorrow ...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 13, 2018, 11:05:53 am
... Testing locally, please standy by until tomorrow ...

So this (next RSA) feature has sort of prevented the release, but now the new feature has finally been tested and now I can go back to preparing the next release.

We should have this ready by this afternoon....

SunK, not sure where the question went on Business objects, but yes, the object itself would be stored in IPFS to prevent chain bloat.

Ill paste a wiki later on the mechanics of business object persistence.  This is primarily to create a stable interface to understand the RWAD ability by organization.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 13, 2018, 02:14:09 pm
SunK, not sure where the question went on Business objects, but yes, the object itself would be stored in IPFS to prevent chain bloat.

Call me Sun. Yeah, maybe I thought I posted it, but maybe I deleted by mistake.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 13, 2018, 07:41:17 pm
1.1.5.0 - Leisure Upgrade (Mandatory for TestNet)

- Updated Build Instructions
- Added Contact Add/Edit/View/Delete page
- Added ability to store and retrieve a business object in IPFS
- Added ability to serialize and deserialize a business object with JSON
- Added RSA file and string encryption (for symmetric uses, such as encrypted business objects and user permissions)
- Added RPC bolist, bosearch commands, exec bolist contact, exec bosearch contact email emailaddress
- Added ability to send BBP via e-mail address (exec emailbbp e-mailaddress amount)


Alright, it's out for linux.  Building windows now.

I'll explain some of this ASAP.

Please refer to this wiki as the starting point for Business Objects:
https://wiki.biblepay.org/Business_Objects


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 13, 2018, 10:52:43 pm
Upgraded to v1.1.5.0, Masternode ENABLED, ipfs daemon running
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 14, 2018, 03:52:03 am
Lets go through some use cases for business objects.  Currently we only support non-encrypted objects in this version, so when we Add a business object, all of biblepay can see it (from a hacker standpoint) and any IPFS node can see it (if they decipher the JSON and know how to hack into the local database).  In the future, we can support encrypted business objects, which would only be viewable from someone within your organization.  In the future we would also be able to honor the RWAD permissions per user per organization.

So lets start with what we can do now.  Please go to your Contact Add page from the menu.  The primary key of a contact record is One labeled wallet public key (we automatically create a wallet public key and label it BUSINESS_OBJECTS in the address book).  So this means if you Edit an existing  Contact record, it will be Updated by physically deleting the old one, and saving a new one with the primary key - IE Your public receiving address + CONTACT.  So there won't be duplicates and we will have One contact per wallet.

Go ahead and add a contact record to the chain, but most importantly fill out a working e-mail address (as I want to demo that feature).  Save the record.  (You can add a contact by Clicking Add Contact from the top menu).

After a few confirms you can type 'exec bolist contact' to see if your contact record is publically viewable.  What we can do with this is:  make a wallet UI (ie a grid for a list), in a generic way, to allow a user to view a list of that type of business object (and search the list in the future).  We can map these users on our great tribulation map.  We can send biblepay to each other via e-mail address.  We can work with MIP to make a tithing feature now (a congregation can tithe to a registered church). 

After a while you can also test an edit.  To edit a contact, go back to contact add and change one the fields, and re-save the record.  The system will realize its an edit and save it appropriately.  For GDPR we also support physical Deletion of a record.

Next we can test the business object search feature.  You can search by type, fieldname and field value currently.  Type 'exec bosearch contact email rob@biblepay.org', and the system will locate all contacts with a field named email with a field value of my e-mail address and add them to the results list and display them. 

Next, if you want to test sending bbp via e-mail address, type:   exec emailbbp rob@biblepay.org 5, and feel free to replace the amount (5) and the recipient e-mail.  The wallet will locate the contact record and send the amount.

I also want to point out that although it appears we created a 'contact' feature, you should look at business objects from a generic perspective.  Contact is one type of business object with a UI.  If we make this as generic and abstract as possible, we could really make a powerful front-end system here, by making UI based on generic business objects - another words, we don't have to create 70 pages of UI to make a powerful system.  We can create add/edit/view abilities for business objects, that provide manipulation and UI for both form based and list based presentations, another words, it would be easy to support as the data is serialized in a common format in the back end, and presented in a common way in the front end.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 15, 2018, 03:48:22 am
I haven't come around to testing the newest features yet Rob, but is it possible that something went wrong when deploying the Windows version? Seems like it's still on 1.1.4.9.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 15, 2018, 10:16:15 am
I haven't come around to testing the newest features yet Rob, but is it possible that something went wrong when deploying the Windows version? Seems like it's still on 1.1.4.9.

Yeah, I didn't even build windows yet.  So I have a new feature for us to test today (Quantitative Tightening).
Let me go ahead and release this in a couple hours, then build windows along with the new version.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 15, 2018, 01:23:18 pm
Yeah, I didn't even build windows yet.  So I have a new feature for us to test today (Quantitative Tightening).
Let me go ahead and release this in a couple hours, then build windows along with the new version.

Alright guys, 1.1.5.2 is out there for linux.

Please, everyone must upgrade in testnet in order for us to test QT (quantitative tightening) properly (as we dont want an old sanc voting on a contract with a missing price, if that happens, the QT will succeed sometimes and fail other times, meaning we would oscillate between a QT start phase and a QT reset).  In prod as long as we make this a mandatory upgrade, we will be able to successfully launch the spork however.


So please upgrade and let me know when we have a new superblock voted in and we can look at the biblepay price and QT level.


Has anyone tested a contact add yet?  I'm getting the feeling we only have one tester and no one cares about the new features.  If we want biblepay to succeed then we have to do a better job.


EDIT:
NOTE!  We had a bug discovered in 1.1.5.1, please upgrade to 1.1.5.2. 
(Windows 1.1.5.2 is now compiling).  1.1.5.2 is required for QT to successfully mine (in the miner).



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 15, 2018, 10:15:54 pm
Upgraded to v1.1.5.2, Masternode Enabled, ipfs daemon running

=

I tested adding a Contact:

Contacts >> Contact Add

(https://i.imgur.com/saYOlvk.png) (https://i.imgur.com/saYOlvk.png)

Filled in info, Clicked Save Record, A Popup came up, but not sure what it says

(https://i.imgur.com/CYiKETY.png) (https://i.imgur.com/CYiKETY.png)

In my transactions I saw that a transaction happened with the Funding Address, -1.0001 BBP

Typing command "exec bolist contact", I see my contact object in the list!

I tested 'exec bosearch contact email rob@biblepay.org', works!
I searched for togo@biblepay.org as well, also worked

I ran  'exec emailbbp rob@biblepay.org 5' and 5 BBP was sent!

References:
https://forum.biblepay.org/index.php?topic=244.msg4313#msg4313
https://forum.biblepay.org/index.php?topic=244.msg4316#msg4316
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 16, 2018, 07:41:17 am
Finally have some time again :)

I've updated two wallets to 1.1.5.2. Unfortunately, my home rig is having issues (not BiblePay related), so I only have one Sanctuary left for the time being (the AWS one).

Creating and editing contacts seems to work like a charm. While Togo's popup seems to have some problems, mine works fine. It says "Contact record saved succesfully." when creating/editing contacts.

Really cool feature that you're able to send BBP with an email address! I sent you 456 BBP Rob.

Code: [Select]
096aaf8e0214e30159dfb63667049c52351e8f76467005d91e04be9d8d50b611


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on September 16, 2018, 02:49:45 pm
1.1.5.2c is available for MacOS at
https://www.biblepay.org/biblepaycore-testnet.dmg
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 16, 2018, 05:52:08 pm
Upgraded to v1.1.5.2, Masternode Enabled, ipfs daemon running

=

I tested adding a Contact:

Contacts >> Contact Add

(https://i.imgur.com/saYOlvk.png) (https://i.imgur.com/saYOlvk.png)

Filled in info, Clicked Save Record, A Popup came up, but not sure what it says

(https://i.imgur.com/CYiKETY.png) (https://i.imgur.com/CYiKETY.png)

In my transactions I saw that a transaction happened with the Funding Address, -1.0001 BBP

Typing command "exec bolist contact", I see my contact object in the list!

I tested 'exec bosearch contact email rob@biblepay.org', works!
I searched for togo@biblepay.org as well, also worked

I ran  'exec emailbbp rob@biblepay.org 5' and 5 BBP was sent!

References:
https://forum.biblepay.org/index.php?topic=244.msg4313#msg4313
https://forum.biblepay.org/index.php?topic=244.msg4316#msg4316


Great progress!  Thats an interesting pop-up.  Can you try again and see if its expandable  - or if it reproduces the same behavior twice?

Yes, I see you in the list, I received your BBP and sent you back something like 10.2 bbp this morning, thanks.


BTW guys, these contacts are stored in IPFS, not in the chain.  Its interesting.. Kind of wild that we are creating a front end business system here.



And Jaap, I got your bbp also, great!  I sent 10.15 or so back.  (Via e-mail address).



So I was thinking, I fear starting with a disruptive mandatory where we *require* the sancs to all run IPFS so quickly (with all these other features at the same time).  Im thinking we phase the IPFS requirement in slowly, maybe we create another type of business object, and make it optional to run IPFS (so that we have 10 or so nodes running in prod).  Then we vote on potentially requiring IPFS after the next mandatory is out, and possibly requiring it if that vote passes.  But I do want to pull off some high-end features during this next release:  Contact add/edit, Gospel links, IPFS attachments, Fork Fix, etc.

I am considering that we make a really extensible feature for the next mandatory release: a user configurable business object.  I believe we will start with Gospel Links, and make add/edit/view/list pages, and enter in all the gospel links we have in the pool.  Id like to make it so we can store the actual Christian Video content in IPFS (so if the internet is down, and Christians are in a camp together they can pull the videos off of the local IPFS laptop).  In baby step 1, we can upload the links as-is.  In baby step 2, we can make a YouTube -> IPFS converter.   (So for our Great Trib feature, User A who runs a cloud VMS would not stream to the Christian camp, but User B who runs IPFS on a laptop would have the video content in the event the net was down).

In other respects, I found a bug in 1.1.5.2 in QT.  The great news is:  QT was *starting* to work today.  The Sancs decided on the price, decided we were in phase 1, emitted a contract, the core wallets found it, honored it-but the bug prevented the block from being mined.  So we will all need to upgrade to 1.1.5.3 next- it should be out shortly.  Note that I believe the chain will roll back 100 blocks or so, as it finds some bad testnet blocks mined at the higher non-qt adjusted subsidy.  This will be normal, the chain should recover, and we should revert to qt phase 1. 


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 16, 2018, 05:53:11 pm
All, please upgrade to 1.1.5.3 so we may resume testing QT.  Bug is fixed.

EDIT: Windows has been released.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 16, 2018, 10:00:14 pm
Also please reindex your chains. 

Proper blockhash is:
getblockhash 67134
535412acfe3f3efd39830edc8f82b70c9e7cca32950e9866f10b5fbaea800069


PS We need a miner to start mining on 1153 - my only testnet cpid just solved 4 in a row so it cant continue.



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 17, 2018, 12:33:16 am
Upgraded to v1.1.5.3, Reindexed, Masternode stuck trying to sync, tail debug.log shows my CPID cant solve more blocks haha
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 17, 2018, 06:34:18 am
Also please reindex your chains. 

Proper blockhash is:
getblockhash 67134
535412acfe3f3efd39830edc8f82b70c9e7cca32950e9866f10b5fbaea800069


PS We need a miner to start mining on 1153 - my only testnet cpid just solved 4 in a row so it cant continue.

My Sanctuary is synched with the proper hash, but it's not linked to a CPID and I don't have tBBP on that wallet to link it.

The wallet I have all my tBBP on doesn't synch yet (it can't find any peers), so I can't send tBBP to my Sanctuary :,)

Can someone send tBBP to my Sanctuary:
yjZ91KimqJp7jdpPpZv6G93BNjLmUGcM83

Thanks!
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 17, 2018, 09:19:35 am
Upgraded to v1.1.5.3, Reindexed, Masternode stuck trying to sync, tail debug.log shows my CPID cant solve more blocks haha

Yeah, I see that mining issue.  I took a look at the code - and basically the state we are in testnet is each cpid can solve every other block (the lookback is 1 but in prod its 4).  So I was able to solve the block after yours, 67135, but I think maybe you just stopped mining?  Looks like were' stuck, anyone have any good cpids out there?

Let me take a look at all my other wallets and see if I can find an old cpid.  (I cant reassocate one new one if the chain isnt moving, :) )

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 17, 2018, 09:19:58 am
My Sanctuary is synched with the proper hash, but it's not linked to a CPID and I don't have tBBP on that wallet to link it.

The wallet I have all my tBBP on doesn't synch yet (it can't find any peers), so I can't send tBBP to my Sanctuary :,)

Can someone send tBBP to my Sanctuary:
yjZ91KimqJp7jdpPpZv6G93BNjLmUGcM83

Thanks!

I sent 1 mil a block back, but we are stuck til we find another cpid :).

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on September 17, 2018, 10:27:16 am
All, please upgrade to 1.1.5.3 so we may resume testing QT.  Bug is fixed.

EDIT: Windows has been released.

MacOS version is also ready for testnet.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 17, 2018, 03:37:14 pm
I sent 1 mil a block back, but we are stuck til we find another cpid :).

I was trying to get my home testnet rig running again, but I see that my other wallet has synced and is now mining.

Code: [Select]
22:36:59

getblockhash 67200


22:36:59

099a38caaa724a66bfa4cbac026cbc0dbfabd714c0926116ba298640de02fcfd

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 17, 2018, 05:39:25 pm
Hmmm, getmininginfo shows my hashps as 0.494 (networkhashps 1.317),
tail debug.log shows my CPID cant solve blocks

Code: [Select]
ERROR: ContextualCheckBlock: CPID c9a2065f***2f1e8d has solved prior blocks.
Mining on 1 thread is turned on / enabled by default with QT wallet open?

I have same hashes:

Code: [Select]
getblockhash 67134
535412acfe3f3efd39830edc8f82b70c9e7cca32950e9866f10b5fbaea800069

getblockhash 67200
099a38caaa724a66bfa4cbac026cbc0dbfabd714c0926116ba298640de02fcfd

Im currently on block 67259

Code: [Select]
getblockhash 67259
a2d44e*****31dd4ad
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 17, 2018, 06:49:51 pm
I reported this back in 1.1.4.8 - never addressed or regression due to kB fees? The address I send payment to doesn't show up in my transaction list.


Seems to only happen if I send to an address I own. Even if I pay a fee, it doesn't show up as a transaction.


If I donate to foundation, I see two transactions.


Only the payment to yiqFGdxM2vzKCk74GrjevEGNTC2rLqKFeg (the PoDS Foundation address?) only appears in my transaction list. I only tried to upload 9MB file.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 18, 2018, 07:29:23 am
It seems I cheered too early  :(

I got my home testnet rig up an running again though. I hope it has a different CPID associated, but I'm not sure because I tried some re-associations in the past days.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 18, 2018, 10:04:48 am
So on the positive side we broke through the chain, and we are rolling.

But the thing Togo mentioned in his log he has solved prior blocks; so I set up two distinct CPIDs in testned and they are both synced to the top.
Whats very, very strange is they both also say they solved prior blocks (like Togo).

In addition, I took a look at the code, and it looks fine, and we havent changed anything related to mining with this QT feature, so Im confused how we introduced a failure in this respect.  Im also mining at .80 hps.

So, let me add some special logging for this and Ill get to the root of the problem.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 18, 2018, 01:49:52 pm
All - I decided to remove QT (quant tightening) due to lack of popularity.

Please get 1.1.5.4, and resync the chain.

Windows is compiling...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 18, 2018, 03:19:53 pm
All - I decided to remove QT (quant tightening) due to lack of popularity.

Please get 1.1.5.4, and resync the chain.

Windows is compiling...

Upgrading...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 18, 2018, 09:16:38 pm
My CPID for testnet may have not solved any work in over a month, not sure if thats part of the issue
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 18, 2018, 09:55:22 pm
All - I decided to remove QT (quant tightening) due to lack of popularity.

Please get 1.1.5.4, and resync the chain.

Windows is compiling...

Oops, after I removed QT, I just realized one of the chain parameters in testnet was adjusted to look back 30 days for the QT 'governanceinfo' prior total (this was for future qt).... Sorry...

Please all, upgrade to 1.1.5.4b....

Building windows now.


We can talk about the cpids solving ability tomorrow after we resync again.

Thanks.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 19, 2018, 07:38:37 am
Oops, after I removed QT, I just realized one of the chain parameters in testnet was adjusted to look back 30 days for the QT 'governanceinfo' prior total (this was for future qt).... Sorry...

Please all, upgrade to 1.1.5.4b....

Building windows now.


We can talk about the cpids solving ability tomorrow after we resync again.

Thanks.

When you guys re-sync today, please delete your mnc*.* and mnp*.* files and the banlist.dat also first.

I have found that we may be caching a superblock (in the govobj system) with a bad payment - and I believe that will fix our sync issue in testnet.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on September 19, 2018, 09:02:56 am
Oops, after I removed QT, I just realized one of the chain parameters in testnet was adjusted to look back 30 days for the QT 'governanceinfo' prior total (this was for future qt).... Sorry...

Please all, upgrade to 1.1.5.4b....

Building windows now.


MacOS version for testnet also available.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 19, 2018, 09:36:48 am
When you guys re-sync today, please delete your mnc*.* and mnp*.* files and the banlist.dat also first.

I have found that we may be caching a superblock (in the govobj system) with a bad payment - and I believe that will fix our sync issue in testnet.

Alright, I've updated all my wallets and deleted the .dat's you suggested. Resynching now...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 19, 2018, 11:56:57 am
Alright, I've updated all my wallets and deleted the .dat's you suggested. Resynching now...

Thanks all - Ive relaunched 4 nodes and 2 are mining.  Although each block I solve is having trouble being added to the other nodes.
But, I believe we are back in the same state we were in prior to the QT fiasco, so Im thinking we just need another miner online now.

Lets be patient and see if another miner allows us to sync.  Im on block :
getblockhash 67726
35fa0d84e64d0fb0b4ec6a05588d8b38b42967e5acbebaa5384e780d10f55728
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 19, 2018, 01:09:10 pm
Thanks all - Ive relaunched 4 nodes and 2 are mining.  Although each block I solve is having trouble being added to the other nodes.
But, I believe we are back in the same state we were in prior to the QT fiasco, so Im thinking we just need another miner online now.

Lets be patient and see if another miner allows us to sync.  Im on block :
getblockhash 67726
35fa0d84e64d0fb0b4ec6a05588d8b38b42967e5acbebaa5384e780d10f55728

I have three wallets. Only one was syncing to the tip (and had the same blockhash as you have), but that one didn't have a CPID associated with it. I just associated a CPID with that one, so let's wait and see if that's going to work.

The other two I'll try to resync...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 19, 2018, 02:30:58 pm
I have three wallets. Only one was syncing to the tip (and had the same blockhash as you have), but that one didn't have a CPID associated with it. I just associated a CPID with that one, so let's wait and see if that's going to work.

The other two I'll try to resync...

Something is starting to happen now... I think.


Yes- all the wallets are clicking up now in tandem.  We had some type of problem based on where we sputtered out (right at the block before the last boinc superblock) and since our masternodes were all dead, the wallet couldnt come to consensus on that superblock.  Now we are past it and we have 6 or so testers online.  We just need to bring up our sancs now.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 19, 2018, 02:46:49 pm
Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexed
Code: [Select]
Segmentation fault (core dumped)
tail debug.log
Code: [Select]
ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767

Im going to clean and reindex again
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 19, 2018, 02:59:04 pm
Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexed
Code: [Select]
Segmentation fault (core dumped)
tail debug.log
Code: [Select]
ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767

Im going to clean and reindex again

84.29 is running 1154.  I know that area of code, we crashed a couple times there in the past - there is even some code in there to try to prevent the crash.  Its really elusive because every time I hear this and try to valgrind it, there is no way to reproduce the exact situation again - I know it has something to do with having a lot of forks in your getchaintips.  I think one of the forks best block hashes is NULL to the wallet.  But we dont save NULL blocks in the map.  I did check Dash to see if they changed that but not yet.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 19, 2018, 03:46:46 pm
mnsync status
shows that Im synced now AssetID 999

getblockhash 67777
bd687ccb***0788387b2

Masternode is PRE_ENABLED

hashps: 0.135,
networkhashps: 178.888
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 19, 2018, 03:58:58 pm
84.29 is running 1154.  I know that area of code, we crashed a couple times there in the past - there is even some code in there to try to prevent the crash.  Its really elusive because every time I hear this and try to valgrind it, there is no way to reproduce the exact situation again - I know it has something to do with having a lot of forks in your getchaintips.  I think one of the forks best block hashes is NULL to the wallet.  But we dont save NULL blocks in the map.  I did check Dash to see if they changed that but not yet.

That's one of my wallets :o

What is strange, is that that wallet is on the right block/chain, but it says it's not synced. I also have a Sanctuary on there, and I can't start it because it says it's not synched...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 19, 2018, 04:20:37 pm
Hmmm, my wallet crashed, v1.1.5.4b, I had upgraded, cleaned and reindexed
Code: [Select]
Segmentation fault (core dumped)
tail debug.log
Code: [Select]
ERROR: Block has no ancestor
Misbehaving: 84.29.208.33:62767
ERROR: invalid header received bd9004da***6d0fea
ERROR: Found block with no ancestor
ERROR: Block has no ancestor.
ERROR: ProcessNewBlock: AcceptBlock FAILED
Misbehaving: 84.29.208.33:62767

Im going to clean and reindex again

After restarting the 85.29 node I got the same 'Segmentation fault' error that Togo got:

Code: [Select]
ERROR: Found block with no ancestor
2018-09-19 21:17:36 ERROR: Block has no ancestor.

2018-09-19 21:17:36 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-09-19 21:17:36 Misbehaving: 47.189.72.5:58842 (0 -> 3)
2018-09-19 21:17:36 ProcessNewBlock : ACCEPTED
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 19, 2018, 05:18:14 pm
After restarting the 85.29 node I got the same 'Segmentation fault' error that Togo got:

Code: [Select]
ERROR: Found block with no ancestor
2018-09-19 21:17:36 ERROR: Block has no ancestor.

2018-09-19 21:17:36 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-09-19 21:17:36 Misbehaving: 47.189.72.5:58842 (0 -> 3)
2018-09-19 21:17:36 ProcessNewBlock : ACCEPTED


Thats kind of cool; if you still have that node in that state, could you sudo apt-get install valgrind,  valgrind ./biblepay and see what line it breaks on?

If not we'll eventually figure it out, but you will probably have to reindex to get past it.

I seem to be back to normal on all nodes now.

I'll do my best to find that bug.  I know we fixed the major fork issue in this version, now we need a couple more minor things... checking.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 20, 2018, 01:19:14 am

Thats kind of cool; if you still have that node in that state, could you sudo apt-get install valgrind,  valgrind ./biblepay and see what line it breaks on?

If not we'll eventually figure it out, but you will probably have to reindex to get past it.

I seem to be back to normal on all nodes now.

I'll do my best to find that bug.  I know we fixed the major fork issue in this version, now we need a couple more minor things... checking.

Sorry, I already -reindexed it :(

But I've installed valgrind in case it ever happens again. Can't seem to get it working in all my noobness though... Could you tell me what specific command I should use?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 20, 2018, 09:41:58 am
Sorry, I already -reindexed it :(

But I've installed valgrind in case it ever happens again. Can't seem to get it working in all my noobness though... Could you tell me what specific command I should use?
Sure, it should be easy as the defaults usually work.  Once you have valgrind installed, depending on how you launch biblepay (IE either "./biblepay-qt" or "./biblepayd") replace that string with this:

cd ~/biblepay
valgrind ./biblepay-qt

For example would start the QT wallet with valgrind running.  You can put all your normal parameters after the ./biblepay-qt also.  It might be easier to pipe the output to a log file since the log would be long (like  >vallog.txt) etc.  If you dont pipe to a log you can scroll back through the end of the trace and see functions and line numbers.  We usually need the last stack trace (the whole section to see how it was called).  Since some functions call other functions etc.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 20, 2018, 10:15:41 am
Sure, it should be easy as the defaults usually work.  Once you have valgrind installed, depending on how you launch biblepay (IE either "./biblepay-qt" or "./biblepayd") replace that string with this:

cd ~/biblepay
valgrind ./biblepay-qt

For example would start the QT wallet with valgrind running.  You can put all your normal parameters after the ./biblepay-qt also.  It might be easier to pipe the output to a log file since the log would be long (like  >vallog.txt) etc.  If you dont pipe to a log you can scroll back through the end of the trace and see functions and line numbers.  We usually need the last stack trace (the whole section to see how it was called).  Since some functions call other functions etc.

Very clear explanation. Thanks!
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 20, 2018, 10:43:07 am
Oh one more thing I just remembered, if anyone does receive that 'block has no ancestor' and crash, you can also make a copy of your testnet chainstate and blocks folders, and zip it and send to me, or simply keep it in order to have it to reproduce the error again in valgrind.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 20, 2018, 05:15:46 pm
So I added some more handling to the area of "ancestor not found".  I found a bug in Contact Add - fixed - will be in the next testnet version.

Im working on automating BOINC setup for brand new cancer miners. 

Let's pause for a little bit until the next version is ready, then we can test all this together.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 22, 2018, 11:24:37 am
Update:  1.1.5.5 has been checked in for TestNet, please upgrade.

Windows is compiling.

I will Blog ASAP on what was added and how we can test it.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 22, 2018, 11:35:31 am
Update:  1.1.5.5 has been checked in for TestNet, please upgrade.

Windows is compiling.

I will Blog ASAP on what was added and how we can test it.

Upgrading :)
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 22, 2018, 12:57:56 pm
Hi All,

Here are some of the new test cases:

1.  Diagnosing Rosetta:  type 'exec rosettadiagnostics'.  This command prints if Boinc is installed or not, if a rosetta account exists, and if Rosetta is attached and crunching.  Note that this does not work on windows yet, but it will within a couple days (as a couple values need entered in the code for windows).  Although this is not a GUI (yet) this was one thing we needed to provide the ability to make a GUI work.

2.  Auto attaching RAH for a brand new user:  type 'exec attachrosetta e-mail pass'.  This command won't harm your setup if you are already working so have no fear in trying it.  Its basically an end-end test that tries to fix anything it finds that is wrong.  If boinc isn't installed, it tells you to install boinc and stops.  If an account does not exist, it creates one.  If RAH is not attached, it attaches RAH.  This command also does not work on windows yet, but will within a couple days.

3.  Business objects.  Now we have the capability to create multiple types of business objects in IPFS.  We currently have 3:  object, contact and gospellink.  Note that the contents of each business object record are stored in IPFS not the chain.  To see the list of gospellink's for example, type exec bolist gospellink. 

4.  Navigating to a List (of business object records).  To keep our BO system generic, instead of promoting hundreds of UI pages at this stage, the navigation is done through programmatic jumps from object to object (not from UI bound to objects).  So let's test the display of the list of gospellinks:  From the menu, click Business Object List.  This shows the master list of business objects (we have 3).  Right click on Gospel Link, then click List.  The system will then show a list of Gospel Links.

5.  Navigating to a URL in a business object:  Right now we have Testimony URL in Contact and Video URL in GospelLink.  To view a video for example, right click on the GospelLink and click NavigateTo.  You can also do this from Contact.  The system searches for a field called "URL" and navigates to that field value (currently).

6.  Add your own gospellink:  Type 'exec addgospellink url notes' (Note that any value with a space in it must be surrounded by quotes).  In the future we will have an Add page to add a business object record to any business object.

Hopefully you can see the value in business objects, as a generic store that Biblepay may possibly charge to lease individual organization specific permissioned objects.  Realize in the future we will need to add permissions to keep an org's objects from being defaced by the public.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 22, 2018, 02:38:26 pm
Windows is deployed.

EDIT:  Ok, the two boinc diagnostics commands should work in windows now (1155c has been deployed).

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 22, 2018, 05:53:45 pm
For contacts, is specific long & lat a good idea? I'd worry someone who wants to target a group specifically could use it for evil. I wonder if long & lat should be close but not exact... like round up to zip code or census block group. So, you get a general idea of where someone is, but not exact location. The final disclosure can occur interpersonally.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 22, 2018, 06:21:01 pm
For contacts, is specific long & lat a good idea? I'd worry someone who wants to target a group specifically could use it for evil. I wonder if long & lat should be close but not exact... like round up to zip code or census block group. So, you get a general idea of where someone is, but not exact location. The final disclosure can occur interpersonally.

I guess its up to the user to do what they want, and what features we use it for.
A public church can put the exact coordinates and maybe people who want to Tithe in BBP can go to that church.

The long & lat might be useful in the great tribulation if someone has a Christian camp that accepts other Christians, when things start getting bad.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 23, 2018, 03:11:17 am
Did a bit of testing.

1. 'exec rosettadiagnostics'.

I needed to also use my rosetta email+pass? And the strange thing, is that the console doesn't actually need that, because I've used different accounts and it displays the same information. It just pulls the information from the installed BOINC so it seems, irrelevant of the account information I provide.

Code: [Select]
09:40:12

exec rosettadiagnostics


09:40:12

You must specify Rosetta e-mail and password. IE 'exec rosettadiagnostics email pass' (code -1)


09:40:30

exec rosettadiagnostics jaapgvk@gmail.com password


09:40:33

{
  "Command": "rosettadiagnostics",
  "Boinc_Installed": true,
  "Rosetta_Account": " 3e10121b68e0279c03dcc38a113a32d6",
  "Rosetta RAC": 241.68,
  "CPID": " c852da1a620ad630b70c8ec1ccdee366"
}


09:42:52

exec rosettadiagnostics jaapgvk@hotmail.com password


09:42:54

{
  "Command": "rosettadiagnostics",
  "Boinc_Installed": true,
  "Rosetta_Account": " c51f05dc2375716f27fb005da8efaa92",
  "Rosetta RAC": 241.68,
  "CPID": " c852da1a620ad630b70c8ec1ccdee366"
}


On Windows, I get more text in the Console:

Code: [Select]

09:23:31

exec rosettadiagnostics


09:23:31

You must specify Rosetta e-mail and password. IE 'exec rosettadiagnostics email pass' (code -1)


09:27:40

exec attachrosetta jaapgvk@hotmail.com password


09:27:43

{
  "Command": "attachrosetta",
  "Boinc_Installed": true,
  "Rosetta_Account": " c51f05dc2375716f27fb005da8efaa92",
  "Attaching Rosetta Project": "ALREADY_ATTACHED",
  "Rosetta RAC": 2016.64,
  "CPID": " d9b22fccfae5582d4ee7838883aaa3cf2) -----------   name: World Community Grid   master URL: http://www.worldcommunitygrid.org/   user_name: Byteball_20393052   team_name: BiblePay   resource share: 100.000000   user_total_credit: 669899.499099   user_expavg_credit: 2247.448592   host_total_credit: 27217.403270   host_expavg_credit: 1256.724297   nrpc_failures: 0   master_fetch_failures: 0   master fetch pending: no   scheduler RPC pending: no   trickle upload pending: no   attached via Account Manager: no   ended: no   suspended via GUI: no   don't request more work: no   disk usage: 0.000000   last RPC: Sun Sep 23 08:59:42 2018   project files downloaded: 0.000000GUI URL:   name: Research Overview   description: Learn about the projects hosted at World Community Grid   URL: https://www.worldcommunitygrid.org/research/viewAllProjects.doGUI URL:   name: News and Updates   description: The latest information about World Community Grid and its research projects   URL: https://www.worldcommunitygrid.org/about_us/displayNews.doGUI URL:   name: My Contribution   description: Your statistics and settings   URL: https://www.worldcommunitygrid.org/ms/viewMyMemberPage.doGUI URL:   name: Results Status   description: View the status of your assigned work   URL: https://www.worldcommunitygrid.org/ms/viewBoincResults.doGUI URL:   name: Device Profiles   description: Update your device settings   URL: https://www.worldcommunitygrid.org/ms/device/viewProfiles.doGUI URL:   name: Forums   description: Visit the World Community Grid forums   URL: https://www.worldcommunitygrid.org/forumLogin.doGUI URL:   name: Help   description: Search for help in our help system   URL: https://www.worldcommunitygrid.org/help/viewHelp.do   jobs succeeded: 307   jobs failed: 0   elapsed time: 4487911.968094   cross-project ID: "
}

2. 'exec attachrosetta e-mail pass'

This seems to be working! This also looks at the installed BOINC for information (not the wallet it seems). I tried it with a phony account, (the 'bozo' one) and it was successfully created!

But although it's a new account the output says it's the same CPID as the account I'm already using. This is of course because it's checking the installed BOINC program for that data.

Of course, this is for new users, so it's not really relevant. Just reporting my experience :)

Code: [Select]

09:26:50

exec attachrosetta jaapgvk@hotmail.com password


09:26:54

{
  "Command": "attachrosetta",
  "Boinc_Installed": true,
  "Rosetta_Account": " c51f05dc2375716f27fb005da8efaa92",
  "Attaching Rosetta Project": "ALREADY_ATTACHED",
  "Rosetta RAC": 241.68,
  "CPID": " c852da1a620ad630b70c8ec1ccdee366"
}


09:29:19

exec attachrosetta jaapgvk@gmail.com password


09:29:21

{
  "Command": "attachrosetta",
  "Boinc_Installed": true,
  "Rosetta_Account": " 3e10121b68e0279c03dcc38a113a32d6",
  "Attaching Rosetta Project": "ALREADY_ATTACHED",
  "Rosetta RAC": 241.68,
  "CPID": " c852da1a620ad630b70c8ec1ccdee366"
}


09:30:01

exec attachrosetta jaapgvk@bozo.com password


09:30:11

{
  "Command": "attachrosetta",
  "Boinc_Installed": true,
  "Rosetta Account Does Not Exist": "Creating New Account",
  "Created new Rosetta Account": " a01b665a9decc97d8903a4dfb4685e0a",
  "Rosetta_Account": " a01b665a9decc97d8903a4dfb4685e0a",
  "Attaching Rosetta Project": "ALREADY_ATTACHED",
  "Rosetta RAC": 241.68,
  "CPID": " c852da1a620ad630b70c8ec1ccdee366"
}

3. 'exec bolist gospellink'

Seems to work. Also tried 'exec bolist contact'.

Code: [Select]
09:54:18

exec bolist contact


09:54:24

{
  "YEPXEYE5DWIPVVLU4NFR9HT2FNNZRG92O5 ()": {
    "objecttype": "0"
  },
  "YFKKMNRGSMZJZX2672Y9HSBVCPXN5PQ5Q3 (QmYDGa2kPgp55ukkrxx8pAP6B8djdTS8dV861G9ZJBbjoQ)": {
    "contact_name": "Glotta",
    "company_name": "Glacier",
    "url": "",
    "longitude": "",
    "latitude": "",
    "receiving_address": "yfkKmnrGsMZjzX2672y9hSbVcPXN5pq5q3",
    "email": "glotta@glacier.org",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YHWZCBB7IARVKJHSRZHRVJ7SHTW5UDTBB5 (QmUTSuv8mQbEFctrDgc5co2GEJZQTWMq8SkJx2MRrVYuow)": {
    "contact_name": "Klondike Michelle",
    "company_name": "KM",
    "url": "",
    "longitude": "",
    "latitude": "",
    "receiving_address": "yhWzcBB7iarVkJHSrZhRVj7ShTW5udtbb5",
    "email": "km@countysalesion.com",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YMZJVHYHYFVKWWAXMEKA3QUE7MIYJYEATW (QmWxHpJLEpAAFEMFkfypnUK2DyKLqgY1Cn7AJ6zKBwtk7c)": {
    "object_name": "gospellink",
    "fields": "url,notes",
    "receiving_address": "yMzjVhyHyfvKWWaxmEkA3QuE7MiyjyeaTw",
    "objecttype": "object",
    "added": "1537565843"
  },
  "YRV7XXFKXG1LN9STPCZZW5ANG7X2UZW9WE (QmRuD7MsHbaAoc7aDgPjWgL3QxVrX5AhhXK8RwBjMcoUXe)": {
    "contact_name": "Jaap",
    "company_name": "Jaaps stuff - V2",
    "url": "",
    "longitude": "",
    "latitude": "",
    "receiving_address": "yRv7XXFkxg1LN9sTpcZzW5ang7X2uZw9we",
    "email": "jaap@biblepay.org",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YSZ6AKRATVNGZPUU48IDSXAESFMH6JH1FP (QmbXSdS9eCoX5M7vDciwYrJ4Z3nrHV52BdMaaYu8Ngimx2)": {
    "contact_name": "Togo",
    "company_name": "BiblePay",
    "url": "https://i.imgur.com/9iWuZZb.jpg",
    "longitude": "97.7431",
    "latitude": "30.2672",
    "receiving_address": "ySz6akraTvNGZPUu48iDSxAeSfMh6JH1fP",
    "email": "togo@biblepay.org",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YTXTZDGWJIJUJ5SACUFQJVHMV1L2YGXBAX (QmPm6ytp5ZTD6k1nos9cb5cqX7RTCPPVaF9a46zX7MBxde)": {
    "contact_name": "Ich",
    "company_name": "Ichibhad Icelyliner",
    "url": "",
    "longitude": "",
    "latitude": "",
    "receiving_address": "yTXTZDGWjijUJ5saCuFqJVHMv1L2YGxbAx",
    "email": "ike@googlifindli.net",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YUXQSP5QDUCBYUZGDFE7V9YHWS9KUQQ1VI (Qmej1uHbMfiwHvfoMBdRExLxoMEaRzwk6Rhcf4qwkXFbhq)": {
    "contact_name": "Boffoon",
    "company_name": "Biblica",
    "url": "",
    "longitude": "",
    "latitude": "",
    "receiving_address": "yUXQSp5qducbYUzGdFe7v9YHws9KUQQ1Vi",
    "email": "abc@abc.com",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YWR2WSVV4XKNPJDTHVIDMQYVV68WJADZIR (Qmbde9kGT2u9Xo4GfhUHbkvRP1pzLtrUB9b8wYy9dFXuZQ)": {
    "contact_name": "Rad Raijaikienleineiter",
    "company_name": "Robocop",
    "url": "",
    "longitude": "",
    "latitude": "",
    "receiving_address": "yWR2wSVV4XknPJdthvidMQyVv68WjADziR",
    "email": "rad@robocop.com",
    "contact_type": "User",
    "objecttype": "contact"
  },
  "YXKWUOVQVVBCBD5B9SY7BDDQP49T1VPBDQ (QmRg6Nouc3K5B62iyPeMzjGjL72gEV5fEkMh9gC3ytdhVJ)": {
    "contact_name": "Kitty Purilio",
    "company_name": "Purina",
    "url": "",
    "longitude": "1",
    "latitude": "4",
    "receiving_address": "yXKwUovqVvBcbD5b9sy7bDdQp49t1VpbDQ",
    "email": "kitty@purina.com",
    "contact_type": "Church",
    "objecttype": "contact"
  },
  "YZOIPWCYC8APMZ5ZGEYSEAQXKBXNYY2X2T (QmWmuz1uVLjpEWKMGkvU5k6crvZpTWBxg4dQPbGFa6QyM7)": {
    "contact_name": "Kitty Andrews",
    "company_name": "Catalina",
    "url": "",
    "longitude": "2",
    "latitude": "3",
    "receiving_address": "yZoiPWCyC8apMz5zGEysEAqXkbxNyy2X2T",
    "email": "rob@biblepay.org",
    "contact_type": "Vendor",
    "objecttype": "contact"
  }
}


09:55:01

exec bolist gospellink


09:55:03

{
  "YMZJVHYHYFVKWWAXMEKA3QUE7MIYJYEATW (QmWcK7tDoWc3XKTtmGDTfbNiDLehpZGQx7zqEuHQJgDXEY)": {
    "url": "https://www.youtube.com/watch?v=1SWW5ocbdSk",
    "notes": "Audio Bible - The Book of John - NKJV - Book 43",
    "receiving_address": "yMzjVhyHyfvKWWaxmEkA3QuE7MiyjyeaTw",
    "objecttype": "gospellink",
    "added": "1537566273"
  },
  "YMZJVHYHYFVKWWAXMEKA3QUE7MIYJYEATW1537566981 (QmSm7qdSgSWqRcRKRnBndzH6CvM5YAo4VaTaFcSMqxW1qE)": {
    "url": "http://jesus-christ.us/HellIsReal.htm",
    "notes": "Hell is Real - Web Page 1",
    "receiving_address": "yMzjVhyHyfvKWWaxmEkA3QuE7MiyjyeaTw",
    "objecttype": "gospellink",
    "secondarykey": "1537566981",
    "added": "1537566981"
  },
  "YMZJVHYHYFVKWWAXMEKA3QUE7MIYJYEATW1537566996 (QmPNrW7kemhW4sA1Y1JctpdjyYiyyLMYonGEbMTHK8QzPT)": {
    "url": "https://www.youtube.com/watch?v=L7FkyF4ux70",
    "notes": "23 Minutes In Hell Intro - CBN - Bill Wiese",
    "receiving_address": "yMzjVhyHyfvKWWaxmEkA3QuE7MiyjyeaTw",
    "objecttype": "gospellink",
    "secondarykey": "1537566996",
    "added": "1537566996"
  },
  "YMZJVHYHYFVKWWAXMEKA3QUE7MIYJYEATW1537567016 (QmacHUEyzKY9XT9dVBR2WoPxZFFnFX257reB8jmk4A1zpm)": {
    "url": "https://www.youtube.com/watch?v=-H0MDGIXZ0o",
    "notes": "15 YR OLD JEWISH BOY NATAN - TESTIMONY OF END OF DAYS",
    "receiving_address": "yMzjVhyHyfvKWWaxmEkA3QuE7MiyjyeaTw",
    "objecttype": "gospellink",
    "secondarykey": "1537567016",
    "added": "1537567016"
  },
  "YMZJVHYHYFVKWWAXMEKA3QUE7MIYJYEATW1537567034 (QmaVsBVC73N5KUJkgDy4p8AM6Xk7tjcBUYPehTxMg4EEv9)": {
    "url": "https://www.youtube.com/watch?v=agr-clNBdJc",
    "notes": "God Helped Me Escape Insane Asylum! | Gary Whetstone",
    "receiving_address": "yMzjVhyHyfvKWWaxmEkA3QuE7MiyjyeaTw",
    "objecttype": "gospellink",
    "secondarykey": "1537567034",
    "added": "1537567034"
  }
}

4.  'Navigating to a List (of business object records).'

Works!

5. 'Navigating to a URL in a business object'

Works!

6. 'exec addgospellink url notes'

Seems to work :) I can't find it in the Business Objects List yet, but maybe it takes some time.
EDIT: it's now showing!

Code: [Select]
10:06:59

exec addgospellink "https://www.youtube.com/watch?v=I9w0oV62V-w" "The Best Praise and Worship Songs - Best Christian Music - Praise The Lord"


10:07:00

{
  "Command": "addgospellink",
  "obj_txid": "9de114bf684dc995b4df77d86aa694984cd5730af0ea72623475b300e2633f9b"
}

Awesome work Rob! I think that it's wonderful to have these kinds of in-wallet functionality. Would be awesome if we can really give the user an awesome experience with proposals, sanctuaries, letter writing, business objects, doing transactions of course, and who knows what more, all inside the wallet. Could be a great user-experience IMO.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on September 23, 2018, 06:03:26 am
Windows is deployed.

EDIT:  Ok, the two boinc diagnostics commands should work in windows now (1155c has been deployed).

MacOS testnet version also available.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 23, 2018, 08:04:41 am
Jaap,

Thanks for testing.  The reason rosettadiagnostics requires the e-mail pass in the arguments is we use it to check if an account exists with rosetta or not first, and that lets us make the decision on replying with the right narrative if a Rosetta account needs to be created or not.

I was thinking the way this could be implemented from the GUI is we put two more buttons on the DC page (Rosetta Diagnostics, and Set-Up Rosetta), and we use the same info populated on the page (the user and pass) to call the function, and we show the result in a messagebox.

Then in this next baby step, we can change the directions for new users to be something like :  Install boinc, Click Set-Up Rosetta, Click Associate... etc.

On the nice UI pages etc, I was thinking we might be able to store more schema info in IPFS, and create a "Menu" object.  It might be possible for me to add menu items that point to business objects.  That would be an IPFS-driven menu system. Then the menu in the wallet is extended by what menu records exist; and we link for example "Gospel Link" to the Gospel Link List (from the Menu value for gospellink). 

Havent though about letter writing yet, but I thought of what might be a good one:  Our expenses and revenue being stored in IPFS.  If we make an object for expense and one for revenue, we could port whats in the pool accountability over to the wallet.  I think in order to do that, the permissions must be done first, otherwise hackers will deface the records (and that would  of course is not an option for the accountability records).  They have to be readable by all, but writable by the authorized signer.





Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on September 25, 2018, 01:57:54 pm
peer list = 0  :)
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 02:02:52 pm
Theres been at least 3 masternodes running, Ive been one of them I updated to v1.1.5.5 three days ago, Updating now to latest version 1.1.5.5d
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 02:08:25 pm
Theres been at least 3 masternodes running, Ive been one of them I updated to v1.1.5.5 three days ago, Updating now to latest version 1.1.5.5d

Togo- have you successfully tested the Contact list and Gospellink list, and is it good?
In the next version, the 1155d, you guys can please test the Diagnostic and Add buttons on the DC page- these do the same things as we test from the command line - except appear in the message box.
Im thinking for a brand new newbie, they will be able to install boinc, click Add Rosetta, then click Associate Rosetta.

Let me circle back around and re-test our blacklist and our team percentage and our non-biblepay PODC amount.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 02:11:33 pm
peer list = 0  :)

addnode testnet.biblepay.org

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on September 25, 2018, 02:19:48 pm
addnode=dns2.biblepay.org
addnode=testnet.biblepay.org
testnet=1
genproclimit=0


i have this
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 02:59:00 pm
Havent done any testing yet, but Ill jump on it,

Ive run into compile error twice now upgrading to v1.1.5.5d hmmm, I have 1.6GB RAM Free

rpcblockchain.cpp: In function 'std::__cxx11::string RetrieveDCCWithMaxAge(std::__cxx11::string, int64_t)':
rpcblockchain.ccp:4580:27: warning: unused variable 'consensusParams' [ XXXXXXXXXXXXX
g++: internal compiler error: Killed (program cc1plus)

Now my VM froze, restarted it and compiling again, will report back asap!

UPDATE: Compiling seems to be working well now
UPDATE 2: QT Running, Masternode ENABLED and Syncing, IPFS daemon running

getblockhash 73646
dcd7eb33******19ec72cdc
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 03:30:52 pm
addnode=dns2.biblepay.org
addnode=testnet.biblepay.org
testnet=1
genproclimit=0


i have this

Are you synced to 73635?  All 3 of my nodes are synced.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on September 25, 2018, 03:39:18 pm
i cant sync nothing
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 03:43:52 pm
i cant sync nothing
Please try this:

telnet testnet.biblepay.org 40001

On my screen it is succesful.  That means for you you should be able to sync.
What is your testnet node IP, let me see if banned?

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 03:48:00 pm
I just updated the spork for NonBiblePayTeamPercentage to 90%, lets please test a non biblepay team superblock payout.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 05:12:50 pm
1.  Diagnosing Rosetta:  type 'exec rosettadiagnostics email password',

"Results": "Boinc Installed: No\n"
"Errors": "Boinc is not installed. Please run 'sudo apt-get install boincmgr boinc'

sudo apt-get install boincmgr boinc
unable to locate package: boincmgr

sudo apt-get update & sudo apt-get upgrade

Now its installing a bunch of stuff, Im a Linux newbie am I doing this right? LOL

Is it boinc-manager vs boinc-mgr?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 05:23:49 pm
1.  Diagnosing Rosetta:  type 'exec rosettadiagnostics email password',

"Results": "Boinc Installed: No\n"
"Errors": "Boinc is not installed. Please run 'sudo apt-get install boincmgr boinc'

sudo apt-get install boincmgr boinc
unable to locate package: boincmgr

sudo apt-get update & sudo apt-get upgrade

Now its installing a bunch of stuff, Im a Linux newbie am I doing this right? LOL

Sorry, wherever I wrote 'boincmgr', it should have been 'boinc boinc-client', that installs boinc and boinc gui.

boincmgr is the name of the UI app boinc installs....


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 05:52:23 pm
No worries!

Hmm so I have boinc and boinc-client installed,
the command has message "Boinc Installed: No"
I closed and reopened QT wallet and tried again, same

Server is Ubuntu 16.04 x64 with Lubuntu GUI installed hosted on Vultr

Poking at the code:
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7313
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7254

BoincCommand()
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7238

GetSANDirectory2()
https://github.com/biblepay/biblepay/blob/87d751ea7eee9c97ded2b747b312253dc772f238/src/podc.cpp#L327

sOS
https://github.com/biblepay/biblepay/blob/8617e91c0d134c3300285bcf744e359688e49428/src/init.cpp#L1211
"LIN", "WIN" or "MAC"

Code: [Select]
std::string sPath = GetSANDirectory2() + "boinctemp";
// Boinc sends some output to stderr, some to stdout

std::string sEXEPath = sOS == "WIN" ? "\"c:\\program files\\BOINC\\boinccmd\"" : "boinccmd";

std::string sCmd = sEXEPath + " >" + sPath + " " + sCommand + " 2>&1";

Random question: if computer is Windows, boinccmd is looked for on the C: drive?

I still need to look into the GetSANDirectory2() some more and then test running the sCMD I build

Im able to run boinccmd command with no parameters, it gives help output

Code: [Select]
std::string GetSANDirectory2()
{
boost::filesystem::path pathConfigFile(GetArg("-conf", "biblepay.conf"));
     if (!pathConfigFile.is_complete()) pathConfigFile = GetDataDir(false) / pathConfigFile;
boost::filesystem::path dir = pathConfigFile.parent_path();
std::string sDir = dir.string() + "/SAN/";
boost::filesystem::path pathSAN(sDir);
if (!boost::filesystem::exists(pathSAN))
{
boost::filesystem::create_directory(pathSAN);
}
return sDir;
}

I cant find the function pathConfigFile() hmm
Is this weird C++ syntax for variable creation? lol

GetArg()
https://github.com/biblepay/biblepay/blob/082a12b0e4727c2df5363dfa14889b41b4957d3a/src/util.cpp#L473

What is is_complete()?
https://www.boost.org/doc/libs/master/libs/type_traits/doc/html/boost_typetraits/reference/is_complete.html

Where is GetDataDir() defined?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 06:35:00 pm
No worries!

Hmm so I have boinc and boinc-client installed,
the command has message "Boinc Installed: No"
I closed and reopened QT wallet and tried again, same

Server is Ubuntu 16.04 x64 with Lubuntu GUI installed hosted on Vultr

Poking at the code:
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7313
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7254

BoincCommand()
https://github.com/biblepay/biblepay/blob/f74f97ab5f04a20de770d80c40bb90eec1921aa2/src/rpcblockchain.cpp#L7238

GetSANDirectory2()
https://github.com/biblepay/biblepay/blob/87d751ea7eee9c97ded2b747b312253dc772f238/src/podc.cpp#L327

sOS
https://github.com/biblepay/biblepay/blob/8617e91c0d134c3300285bcf744e359688e49428/src/init.cpp#L1211
"LIN", "WIN" or "MAC"

Code: [Select]
std::string sPath = GetSANDirectory2() + "boinctemp";
// Boinc sends some output to stderr, some to stdout

std::string sEXEPath = sOS == "WIN" ? "\"c:\\program files\\BOINC\\boinccmd\"" : "boinccmd";

std::string sCmd = sEXEPath + " >" + sPath + " " + sCommand + " 2>&1";

Random question: if computer is Windows, boinccmd is looked for on the C: drive?

I still need to look into the GetSANDirectory2() some more and then test running the sCMD I build

Im able to run boinccmd command with no parameters, it gives help output

Code: [Select]
std::string GetSANDirectory2()
{
boost::filesystem::path pathConfigFile(GetArg("-conf", "biblepay.conf"));
     if (!pathConfigFile.is_complete()) pathConfigFile = GetDataDir(false) / pathConfigFile;
boost::filesystem::path dir = pathConfigFile.parent_path();
std::string sDir = dir.string() + "/SAN/";
boost::filesystem::path pathSAN(sDir);
if (!boost::filesystem::exists(pathSAN))
{
boost::filesystem::create_directory(pathSAN);
}
return sDir;
}

I cant find the function pathConfigFile() hmm
Is this weird C++ syntax for variable creation? lol

GetArg()
https://github.com/biblepay/biblepay/blob/082a12b0e4727c2df5363dfa14889b41b4957d3a/src/util.cpp#L473


Very good diagnosis, thanks.

So on the windows question: Yes, on windows boinc doesnt seem to be in the PATH by default, so we prefix the entire path in and use the default drive.  I realize if a user puts boinc in another drive, we fail on windows for now.  But it works on my windows machine for a good start.  On linux and mac 'boinccmd' should be in the path. 

Now that is strange your boinccmd is not working- we can diagnose this.  First lets see if biblepay created your san directory.

cd ~/.biblepaycore/SAN
ls -l

You should see a 'boinctest' file.  cat it to the screen, see if it has the boinc help output?  Its supposed to have a timestamp of right when you typed 'exec rosettadiagnostics user pass'.  See if it does get written to?  Does it contain the text 'projectattach'?  If it doesnt, let me know if you have a different version of boinc and Ill compare the output to mine.  Yes, we should get this working on your ubuntu 64, so we can work across more platforms.

The pathConfigFile just returns the full path to :  ~/.biblepaycore/, thats where the blocks directory is.  (Other parts of the code add in 'testnet3' to actually respect the blocks directory testnet is using). We add the 'SAN' suffix for Sanctuary Quorum files and other temporary stuff used by IPFS. 

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 06:41:59 pm
Cool, okay so SAN folder exists and it has files, it has the boinctemp file, I typed cat boinctemp but it said "can't connect to local host", ok so I opened it with vi and thats the text it says inside of it

and the built up command looks something like this for linux?

sCMD =  boinccmd > [GetSANDirectory2() + "boinctemp"] help 2>&1

boinc --version
7.6.31 x86_64-pc-linux-gnu

sudo apt-get install boinc boinc-client
(7.6.31+dfsg-6ubuntu1)

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 07:16:48 pm
Cool, okay so SAN folder exists and it has files, it has the boinctemp file, I typed cat boinctemp but it said "can't connect to local host", ok so I opened it with vi and thats the text it says inside of it

and the built up command looks something like this for linux?

sCMD =  boinccmd > [GetSANDirectory2() + "boinctemp"] help 2>&1

boinc --version
7.6.31 x86_64-pc-linux-gnu

sudo apt-get install boinc boinc-client
(7.6.31+dfsg-6ubuntu1)

So the text inside boinccmd is "can't connect to localhost"? 
Your linux box should have "cat" on it as that should be on all machines.
If you cd ~/.biblepaycore/SAN
then
cat boinctemp
You should see the contects of boinctemp?  Should match the vi version?
Yes, you got the sCMD, but lets try it a different way - try to reproduce being able to output the same info in the boinctemp file from bash:

cd ~/.biblepaycore/SAN
boinccmd > boinctemp help 2>&1
cat boinctemp

Does the contents say the same things as:
boinccmd help

?

If so maybe boinc actually isnt working, try to run 'boincmgr' to see if its installed?


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 07:26:35 pm
Correct, the text inside is "can't connect to local host", yeah so Im a noob, I never use the cat command, I thought it was trying to connect to a server given the output LOL

So boinccmd help command gives same text "can't connect to local host"

boinccmd by itself outputs all the flags, but adding help parameter it says the above

Should it be --help? boinccmd --help works, boinccmd help gives cant connect message

Tested boincmgr command, BOINC Manager GUI popped up
in bottom right said looking for connection, then said disconnected

===

cd ~/.biblepaycore/SAN
boinccmd > boinctemp help 2>&1
cat boinctemp

Does the contents say the same things as:
boinccmd help

Yes, they both say: can't connect to local host

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 07:58:38 pm
Correct, the text inside is "can't connect to local host", yeah so Im a noob, I never use the cat command, I thought it was trying to connect to a server given the output LOL

So boinccmd help command gives same text "can't connect to local host"

boinccmd by itself outputs all the flags, but adding help parameter it says the above

Should it be --help? boinccmd --help works, boinccmd help gives cant connect message

Tested boincmgr command, BOINC Manager GUI popped up
in bottom right said looking for connection, then said disconnected

===

cd ~/.biblepaycore/SAN
boinccmd > boinctemp help 2>&1
cat boinctemp

Does the contents say the same things as:
boinccmd help

Yes, they both say: can't connect to local host
Ok, good, then its working as expected- I believe boinc is not really running.  (On the --help instead of help, no 'help' is correct, --help is the description of the help).

So if you
cd /var/lib/boinc-client
boinc


(IE run boinc from that dir) you should see boinc start and then fail after a while - it should write the fail reason to the log.
Whatever is in that log, that explains why boinc did not install correctly on that machine.

Most likely, either the triggers didnt run when you installed it or the boinc service isnt running.  If it doesnt fail after 1 minute, try the biblepay feature again while the 1st terminal is running boinc and see if it detects boinc.  If it does, then you just have a missing service (IE a bad install of boinc).

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 08:01:29 pm
Hmmm, there is no boinc-client folder inside of /var/lib

Ran boinc command and its running, looks like I accidentally generated boinc files into the /var/lib folder haha

Some interesting output from boinc:

[---] Data directory: /var/lib
execv: No such file or directory

dir_open: Could not open directory 'slots' from '/var/lib'

rest of output just bounces from resuming or suspending computation because CPU is busy
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 08:32:34 pm
Hmmm, there is no boinc-client folder inside of /var/lib

Ran boinc command and its running, looks like I accidentally generated boinc files into the /var/lib folder haha

Some interesting output from boinc:

[---] Data directory: /var/lib
execv: No such file or directory

dir_open: Could not open directory 'slots' from '/var/lib'

rest of output just bounces from resuming or suspending computation because CPU is busy

Got it.  Ok, I would summarize this one as boinc not being installed correctly.
Please try it on a machine with boinc that works, and see if we report Boinc Installed: Yes, then with boinc uninstalled, Boinc installed: No.

Maybe the sudo apt get commands are wrong and have hosed this particular box.  But it appears boinc is not installed correctly on that box.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 08:58:07 pm
I ran

sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get dist-upgrade -y
sudo apt-get install boinc-client -y --reinstall

and I now have a /boinc-client folder in /var/lib

=

boinccmd help now ouputs "Authorization failure: -155",

Opened QT wallet, Debug Console, exec rosettadiagnostics email pass
Boinc Installed: Yes
Rosetta_Account: c1f31****8d5954
Rosetta_RAC: -1.00
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 09:16:27 pm
I ran

sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get dist-upgrade -y
sudo apt-get install boinc-client -y --reinstall

and I now have a /boinc-client folder in /var/lib

=

boinccmd help now ouputs "Authorization failure: -155",

Opened QT wallet, Debug Console, exec rosettadiagnostics email pass
Boinc Installed: Yes
Rosetta_Account: c1f31****8d5954
Rosetta_RAC: -1.00

Good deal, so far it appears to be working.  -1 RAC means it doesnt 'see' rosetta crunching yet.

So now if you want to click the "Add Rosetta" button on the GUI (from the DC page in the QT wallet) - you can simulate what a new user would go through to start crunching.

Then just click Diagnostics again and see if its accurate (IE shows your Rosetta RAC).

BTW:  In the latest version, you should see a big LCD indicator of the # of Rosetta tasks in the middle of the page that are crunching.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 09:27:27 pm
I went to "Distributed Computing" tab,
clicked "Create and Attach R&H Account",
got a pop up "Fix BOINC Configuration" "E-mail must be populated.Password must be populated."

Entered in email and password, clicked "Create and Attach R&H Account" again
"Fix BOINC Configuration"
"Boinc_Installed: Yes
Rosetta_Account: c1f31***5954
Attaching Rosetta Project: Attached Successfully
Rosetta RAC: -1
CPID:"

"R&H Diagnostics" button, have to enter in email and pass and similar output
"Boinc_Installed: Yes
Rosetta_Account: c1f31***5954
Rosetta RAC: -1.00"

My Current Tasks on DC Tab is 0

Do I have to start boinc manually?
Im watching top and only see boinc pop up for a split second every 30 seconds

ps -ef I see /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 25, 2018, 10:36:23 pm
I went to "Distributed Computing" tab,
clicked "Create and Attach R&H Account",
got a pop up "Fix BOINC Configuration" "E-mail must be populated.Password must be populated."

Entered in email and password, clicked "Create and Attach R&H Account" again
"Fix BOINC Configuration"
"Boinc_Installed: Yes
Rosetta_Account: c1f31***5954
Attaching Rosetta Project: Attached Successfully
Rosetta RAC: -1
CPID:"

"R&H Diagnostics" button, have to enter in email and pass and similar output
"Boinc_Installed: Yes
Rosetta_Account: c1f31***5954
Rosetta RAC: -1.00"

My Current Tasks on DC Tab is 0

Do I have to start boinc manually?
Im watching top and only see boinc pop up for a split second every 30 seconds

ps -ef I see /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log
Good deal, but no , you shouldnt have to manually start rosettas tasks.  When our code attaches rosetta, it launches the tasks.

I think that machine still has something wrong; (due to unclean uninstall which I think is a boinc issue)-
Let me back up a sec; I think the entire issue on that machine was that we didnt tell the user "sudo apt update" first, then the sudo apt-get install boinc boinc-client.  I think that set you into a downward spiral.

To find the problem you have to locate the boinc log file by cding to :  cd /var/lib/boinc-client
Manually running boinc
Then wait for the error, then look for where it writes the boinc log.  In there you should find something wrong.

But I think on a normal install, things should start up and the LCD indicator jump up to the task level of the machines resources.


Try going to boinc gui (boincmgr) and see if you can see any rosetta tasks running, probably not.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 25, 2018, 11:00:21 pm
Ok so I did:

sudo apt-get install boinc boinc-client -y --reinstall
(previously only reinstalled just boinc-client)

closed and reopened QT Wallet, went to DC tab after awhile, says 1 current task
I entered email and pass, clicked "R&H Diagnostics"

Boinc Installed: yes
Rosetta_Account: c1f31**5954
Rosetta_RAC: 6830.33
CPID: 93138f****15a77

===

UPDATE: Running boinc command manually, it crashes with  gstate.init() failed, Error Code: -180
https://boinc.mundayweb.com/wiki/index.php?title=Gstate.init()_failed,_error_code:_-180

Im going to turn off the server and spin up a new one
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: klondike on September 26, 2018, 01:47:10 am
Please try this:

telnet testnet.biblepay.org 40001

On my screen it is succesful.  That means for you you should be able to sync.
What is your testnet node IP, let me see if banned?
now working,didnt nothing  :o
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 26, 2018, 02:50:36 am
I saved my wallet.dat using winscp, and destroyed the server
I spun up a new Vultr server in Dallas, 2 CPU this time,
Installed BiblePay, set tesnet=1 in biblepay.conf,
I couldnt sync at first, I added addnode=testnet.biblepay.org and was able to sync
Installed lubuntu-desktop
(tried to mess with VNC but I failed, grey screen)
Connected with Vultr View Console button
Installed ipfs
Installed boinc and boinc-client
Ran through the DC tab buttons, everything worked, I have 5 rosetta tasks running

Should I set back up a masternode?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 26, 2018, 07:24:27 am
I saved my wallet.dat using winscp, and destroyed the server
I spun up a new Vultr server in Dallas, 2 CPU this time,
Installed BiblePay, set tesnet=1 in biblepay.conf,
I couldnt sync at first, I added addnode=testnet.biblepay.org and was able to sync
Installed lubuntu-desktop
(tried to mess with VNC but I failed, grey screen)
Connected with Vultr View Console button
Installed ipfs
Installed boinc and boinc-client
Ran through the DC tab buttons, everything worked, I have 5 rosetta tasks running

Should I set back up a masternode?

Sorry to see you go through all that.  I suppose its for the better though, because you effectively tested from an empty server (in contrast to uninstalling boinc).  On a side note, I tested the feature successfully on my debian VM and on windows 7.  (Ive been doing most of my testnet testing by picking 3 of my prod sancs, and running biblepay-qt in testnet mode using a biblepaytest.conf file, that basically shuts off listen=0,testnet=1 and allows it to run side-by-side a running sanc instance). 

On the masternode, yes, I think at this point you are so close you might as well set up a hot sanc so we can do a little testing on RAC rewards.

On a side note, Ive got some VNC hosts running, although you dont need to do this, when I ran into the grey screen issue, I did this and it worked for me on ubuntu 16:
https://askubuntu.com/questions/800302/vncserver-grey-screen-ubuntu-16-04-lts
The first answer with the 8 upvotes.  It seems there are no desktop components being launched by vncserver by default.

Were you able to see the contact list and the gospellink list and navigate to a gospel link btw?

If you want to add a gospellink feel free to add one, you can scrape it from the pool 'external links'.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 26, 2018, 08:27:41 am
Sanctuary set up, PRE_ENABLED

I clicked Business Objects menu and was able to click around Contacts and Gospels and was able to open Gospel link
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 26, 2018, 10:26:53 am
Wow! I was gone for two days and a lot has happened  :o

My findings:
'Current tasks' shows correctly in the wallet.

About the buttons in the 'Distributed Computing' tab:
Maybe we can change them a bit to make them more clear. Maybe something like:
-Attach existing R@H account
-Create and attach new R@H account
-Run R@H diagnostics

Maybe even put the 'Create and attach new R@H account' button first, because if we do the installation from the wallet, that's the button most new users will use.

On this computer, BOINC and the wallet were already installed and running:

Code: [Select]
Boinc Installed: Yes
Rosetta_Account: 3e10121b68e0279c03dcc38a113a32d6
Rosetta_RAC: 214.02
CPID: c852da1a620ad630b70c8ec1ccdee366

This CPID was on a non-BiblePay Team (Russian Team), and the rewards indeed seem to have droppen 10%. They used to be around 130 and they are now around 117.

I've now changed it to Team BiblePay and will see if it will pay out 100% in the future (instead of the 90% now).

Lastly, the latest Windows version currently online doesn't have the added buttons in the 'Distributed Computing' tab yet. I don't know if the windows wallet is still on 'c'?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 26, 2018, 04:56:22 pm
Wow! I was gone for two days and a lot has happened  :o

My findings:
'Current tasks' shows correctly in the wallet.

About the buttons in the 'Distributed Computing' tab:
Maybe we can change them a bit to make them more clear. Maybe something like:
-Attach existing R@H account
-Create and attach new R@H account
-Run R@H diagnostics

Maybe even put the 'Create and attach new R@H account' button first, because if we do the installation from the wallet, that's the button most new users will use.

On this computer, BOINC and the wallet were already installed and running:

Code: [Select]
Boinc Installed: Yes
Rosetta_Account: 3e10121b68e0279c03dcc38a113a32d6
Rosetta_RAC: 214.02
CPID: c852da1a620ad630b70c8ec1ccdee366

This CPID was on a non-BiblePay Team (Russian Team), and the rewards indeed seem to have droppen 10%. They used to be around 130 and they are now around 117.

I've now changed it to Team BiblePay and will see if it will pay out 100% in the future (instead of the 90% now).

Lastly, the latest Windows version currently online doesn't have the added buttons in the 'Distributed Computing' tab yet. I don't know if the windows wallet is still on 'c'?

Good, Im glad most of your tests passed!

Yeah, I think the button captions could use a little improvement.  I changed the "Add me as a researcher" to "Associate Researcher CPID with BiblePay" (thats because I didnt want people to confuse attaching a project with attaching biblepay.  I still left it first in the order- only because I feel we will have half who already have CPIDs and they just want to associate the wallet.  The newbies will have to know to do Create then Associate.  I recaptioned the Diag button to "Run R@H Diagnostics".    This will be in the next version however.

Regarding it not being there, yes, your right but since we had this emergency release today, now 1.1.5.6 is out there.  So now you can try the buttons in windows (with the old captions :)...

Great on the RAC change!



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 27, 2018, 09:32:50 am
Testing from a clean Windows 10 PC.

Push button: 'Create and Attach R@H Account'
Popup says:
Quote
Boinc is not installed. Please run 'sudo apt-get install boincmgr boinc.

Of course, you already discussed the Linux part of things with Tigo, but I'm on Windows now. So I guess the popup should also say something about installing BOINC on Windows.

Anyway, I installed BOINC but didn't run it yet, and tried the button again. The same 'Boinc not installed' popup showed. I launched BOINC and hit the button again and the wallet started a proces. It was a succes! Very awesome! Absolutely.

The wallet created the account, Boinc started downloading tasks immediately and is crunching away now.

And is my assertion correct that you don't need any BBP in your wallet to start mining this way? Of course you need it for staking (at least for now). I sent 1000 BBP to my wallet just in case, but I don't the the 1 BBP transaction you would normally see when attaching your account to the blockchain. The wallet doesn't show my CPID yet, but it hasn't been 6 blocks yet. I will check again later...
EDIT: more than six blocks have passed and the wallet still doesn't show my CPID. So I guess something went wrong? If I can do anything to troubleshoot, please let me know :)

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 27, 2018, 11:38:01 am
Testing from a clean Windows 10 PC.

Push button: 'Create and Attach R@H Account'
Popup says:
Of course, you already discussed the Linux part of things with Tigo, but I'm on Windows now. So I guess the popup should also say something about installing BOINC on Windows.

Anyway, I installed BOINC but didn't run it yet, and tried the button again. The same 'Boinc not installed' popup showed. I launched BOINC and hit the button again and the wallet started a proces. It was a succes! Very awesome! Absolutely.

The wallet created the account, Boinc started downloading tasks immediately and is crunching away now.

And is my assertion correct that you don't need any BBP in your wallet to start mining this way? Of course you need it for staking (at least for now). I sent 1000 BBP to my wallet just in case, but I don't the the 1 BBP transaction you would normally see when attaching your account to the blockchain. The wallet doesn't show my CPID yet, but it hasn't been 6 blocks yet. I will check again later...
EDIT: more than six blocks have passed and the wallet still doesn't show my CPID. So I guess something went wrong? If I can do anything to troubleshoot, please let me know :)


Hi Jaap,

Thats awesome on the Windows test for Create New Account!  Great, we are close.
Hmm, thats very interesting the 'associate researcher with biblepay' didnt work, as I didnt change that.  Yes that still requires something like .25 bbp for it to run - and its supposed to give you an error messagebox if it fails to send the DCC transaction, and yes you are supposed to see it in the txlist even during the 6 block wait....

Let me try to reproduce that button on windows.  Its possible I accidentally removed the actual Click behavior of the button in the last version.

Yes, correct, for a new user they could start crunching, but not receive any rewards until their UTXO amount exceeds the required minimum, so they would see the task count, and the RAC, but not be in any superblocks until they stake a minimum UTXO against the associated CPID.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 27, 2018, 11:52:03 am
Jaap, I tried to reproduce the "associate" button not sending the collateral, and from what I see, it does still call the same old associate code and it still works.

However I do see one potential reason it didnt work for you.  Im thinking on a brand new wallet with 0, we require the BBP to be at least 2 confirms deep before it can be spent on a collateral tx.  You should have received 'insufficient funds' in the message box, and not 'welcome to BiblePay cancer mining!'. 

See if you can remember what it said?  Anyway if you retry with a confirmed balance, it will probably work fine....

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 27, 2018, 12:47:46 pm
Jaap, I tried to reproduce the "associate" button not sending the collateral, and from what I see, it does still call the same old associate code and it still works.

However I do see one potential reason it didnt work for you.  Im thinking on a brand new wallet with 0, we require the BBP to be at least 2 confirms deep before it can be spent on a collateral tx.  You should have received 'insufficient funds' in the message box, and not 'welcome to BiblePay cancer mining!'. 

See if you can remember what it said?  Anyway if you retry with a confirmed balance, it will probably work fine....

Oh, wait! Maybe I just misunderstood. I thought that the 'create and attach R@H' button did more than it maybe actually does.

I thought that the 'create' portion was the creation of the R@H account, and I thought that the 'attach' portion was about 'attaching' your CPID to the blockchain.

But the 'attach' part is not about the CPID, but about attaching R@H to the Boinc client! I thought it was an all-in-one button that included attaching your CPID :-X

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 27, 2018, 01:32:44 pm
Oh, wait! Maybe I just misunderstood. I thought that the 'create and attach R@H' button did more than it maybe actually does.

I thought that the 'create' portion was the creation of the R@H account, and I thought that the 'attach' portion was about 'attaching' your CPID to the blockchain.

But the 'attach' part is not about the CPID, but about attaching R@H to the Boinc client! I thought it was an all-in-one button that included attaching your CPID :-X

Excellent!  That means the test didnt fail, great.  (Because the msgbox should show any error, even Insufficient funds).

Anywhoo,  heres what Im thinking:

Case 1:
A new biblepay user who is an existing researcher on boincstats with lots of rac.  All they do is click the Associate CPID button (thats the old button that was always there).


Case 2:
A new user who doesnt use boinc.  They click the 'Create Account & Attach project' button and that does everything Except associate the cpid with the wallet.  Then We tell them to click Associate after they get boinc running.


This way we can appeal to either group without causing duplicate DCC transactions to be sent.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 27, 2018, 01:50:50 pm
Excellent!  That means the test didnt fail, great.  (Because the msgbox should show any error, even Insufficient funds).

Anywhoo,  heres what Im thinking:

Case 1:
A new biblepay user who is an existing researcher on boincstats with lots of rac.  All they do is click the Associate CPID button (thats the old button that was always there).


Case 2:
A new user who doesnt use boinc.  They click the 'Create Account & Attach project' button and that does everything Except associate the cpid with the wallet.  Then We tell them to click Associate after they get boinc running.


This way we can appeal to either group without causing duplicate DCC transactions to be sent.

Yes, I think that will be great for the UX when setting up the wallet. I shall change the guide on biblepay-central to reflect these steps when this goes into prod.

One thing comes to mind: right now there is the 'get 1000 BBP from pool' step, that ensures you have enough BBP to associate your CPID (and even have something to start staking with).

Looking at the new wallet set-up from a new user perspective, you first use the 'create and attach R@H' button. If everything goes right, you now have R@H crunching with a fresh account. Since this account doesn't have any RAC, you can't use the pools faucet yet.

So, thinking about a guide. Should the steps be:
1. Download and run BOINC
2. Use the 'create and attach R@H' button
3. Solve enough tasks to have >100 RAC + wait 24 hours just to be sure
4. Use pool faucet
5. Associate your CPID
6. Buy enough BBP for staking.

Of course, you don't HAVE to follow these steps, as long as you have enough BBP to associate your CPID. You could also use http://biblepayfaucet.com/ perhaps, but it can take a long time using that faucet to get enough BBP for the CPID association.

Anyway, people will also need to stake of course, so they will probably also have to buy BBP anyway even if they get the 1000 BBP.

Just thinking out loud about UX and how to make this proces as easy as possible...
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 27, 2018, 06:56:20 pm
I tried SunK's recommended lowendbox service of $1 a month:
https://lowendbox.com/blog/hostbrz-vps-shared-reseller-hosting-from-2-year/

Its horrible, first day the nodes went down 15 hours in, 2nd day - they erased one server by accident, problems still not resolved.

Might be good for a test VMS, but not for a production node.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 27, 2018, 07:07:15 pm
Yes, I think that will be great for the UX when setting up the wallet. I shall change the guide on biblepay-central to reflect these steps when this goes into prod.

One thing comes to mind: right now there is the 'get 1000 BBP from pool' step, that ensures you have enough BBP to associate your CPID (and even have something to start staking with).

Looking at the new wallet set-up from a new user perspective, you first use the 'create and attach R@H' button. If everything goes right, you now have R@H crunching with a fresh account. Since this account doesn't have any RAC, you can't use the pools faucet yet.

So, thinking about a guide. Should the steps be:
1. Download and run BOINC
2. Use the 'create and attach R@H' button
3. Solve enough tasks to have >100 RAC + wait 24 hours just to be sure
4. Use pool faucet
5. Associate your CPID
6. Buy enough BBP for staking.

Of course, you don't HAVE to follow these steps, as long as you have enough BBP to associate your CPID. You could also use http://biblepayfaucet.com/ perhaps, but it can take a long time using that faucet to get enough BBP for the CPID association.

Anyway, people will also need to stake of course, so they will probably also have to buy BBP anyway even if they get the 1000 BBP.

Just thinking out loud about UX and how to make this proces as easy as possible...

Sounds like a winner.  That is another good reason we separated the Associate from the Attach - we don't really want the associate part to fail unless they deliberately have 0 bbp to use and there is a long potential lag for a user between starting boinc and clicking associate.

Ill start reviewing everything we changed to see if we have wrapped up what is supposed to be in the mandatory.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 28, 2018, 12:17:44 am
Unable to add test contact.

Fields I filled out: Company Name, Contact Name, Funding Receiving Address (I changed it from default to another one), E-Mail address. Drop Down Vendor

2018-09-28 05:11:39 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-09-28 05:11:39

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepaytestnet\biblepay-qt.exe in Runaway exception       

2018-09-28 05:11:59
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 28, 2018, 12:19:14 am
I tried SunK's recommended lowendbox service of $1 a month (https://lowendbox.com/blog/hostbrz-vps-shared-reseller-hosting-from-2-year/) ... Its horrible

Sorry that happened. That's not been my experience, but support can be spotty with lowend servers sometimes. If you don't need support and can manage on your own, its been for me.

Sounds like a winner.  That is another good reason we separated the Associate from the Attach - we don't really want the associate part to fail unless they deliberately have 0 bbp to use and there is a long potential lag for a user between starting boinc and clicking associate.
I think more buttons is not helpful. I'd want to keep the "Add Me As Researcher" button only and have all the action flows from it.If they don't have an R@H account, create one and track their CPID. Give Download link with instructions to add R@H project. Crunch tasks. When s/he gets enough RAC (whether is 1 hour or 1 day or 1 week), have the pool automatically pay from the faucet. Maybe have BBP wallet check every 4 hours like PoDC updates for the RAC? Whenever there is enough BBP in the wallet, ask if they want to submit their CPID to the blockchain to receive daily PoDC payouts. IMO, it should be all behind the scene and seamless. Maybe that's too complicated to do? IDK.

Side comments:
1) Maybe WCG can fit in there somewhere too... (Display My Data needs to be checked on in Settings on the web site)
2) Form tabbing is wonky. From user name it goes to Add Researcher button instead of to password
3) R@H diagnostics show WCG, but the WCG data is not parsed out. Its all a jumbled mess from web site it seems.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 28, 2018, 07:20:46 am
Unable to add test contact.

Fields I filled out: Company Name, Contact Name, Funding Receiving Address (I changed it from default to another one), E-Mail address. Drop Down Vendor

2018-09-28 05:11:39 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-09-28 05:11:39

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepaytestnet\biblepay-qt.exe in Runaway exception       

2018-09-28 05:11:59


Please re-post this with every field value and user changed value existing on the screen that can allow us to reproduce the crash including what you click.

Unable to reproduce:  Unable to fix :  At this point this feature appears to work fine to us.

Also please ensure this is the latest wallet version.  Earlier than 2 versions ago, we did have a contact save issue.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 29, 2018, 12:52:08 pm
So now let us take a step back, and think of a cryptographically hard way to homogenize these upcoming features to be useful to BiblePay and God.

If we provide the ability to Upload a Christian Video into IPFS and into a block, with resulting IPFS hash, that is considered a "Video" object.  We provide the ability to save a "Prayer" object into IPFS.  We provide the ability to add a Letter into IPFS written to a certain orphanid.

Now what we need is the ability to Vote from the wallet, as a user, not as a Sanctuary, on an objects hash, to upvote it or downvote it or abstain.  Abstain is useful if you have no opinion on a reviewed object.  I think what we need to do, not-subject to creating a new integrity system, is have Vote-Weight be determined by a given wallets UTXO weight.  As people with higher balances tend to have more integrity.  So a vote object will contain utxo weight, and its target an IPFS hash.  This will allow a USER to vote with their UTXOWeight on an IPFSHash.

Then we can take a look at a list of Videos, and corresponding vote levels.  A user like Jaap, if he had 1 mil balance would have 10* the weight on his vote than a user with 100,000 balance.

Later on we can use this idea to expand our economy - to potentially pay community members for rating BiblePay objects.  This will be useful for rewarding Letters, Viewers(Voters) and content uploaders.

Then we modify the block to share payment with the reviewers if it contains a Letter, a Video or a Prayer.  So I suppose if we had an escrow, we would need a 'review window' - a period of time - where Votes are compensatable (IE 30 days from the date of the block).  So if a letter is written on 10-1-2018, it could be voted on from 10-1 through 10-31.  On 11-1 the payment is released based on quality as a split between the reviewers and the content creator.  The Creator might get  a % based on quality from 0-100, and the reviewers split the rest based on utxoweight. 

So we have situation A, a great letter to an orphan:

20,000 block:

Rating 90% - rated by 10 people, with the 10th having 90% of the utxo weight:
Reward:  10,000 to the creator,  10000 split among the 10 reviewers multiplied by UTXO weight - with 9000 of the reward going to reviewer #10

Situation B: A terrible letter, written by a Satanist to an orphan:

20,000 block:

Rating 10% (Rated by 1 satanist and 9 good Christians):
Reward:  1,000 to the creator, 19,000 split among the 10 reviewers by utxo weight


It would be an interesting economy.  This type of situation would cause us to spread more gospel and compensate reviewers to do more work (IE Consume more gospel also).


I'll get to work on creating a vote object to allow voting by UTXO weight.






Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 29, 2018, 05:01:43 pm
On first sight, this seems like a very nice system! I like the idea of incentivizing people to vote. This is like an automatic bounty system.

And users with a high utxo weight are likely to be loyal to BiblePay (why else would they have a lot of BBP).

As you say, it would be an interesting economy. If this reaches prod, I hope that we can spread awareness for this in a way that also attracts new users.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 29, 2018, 08:21:10 pm
This is pretty cool!
- solves the Orphan Letter Writing review issue
- solves the Prayer review issue
- incentivizes more gospel viewing

Just so I understand correctly, is it possible to spam Prayers? or does the person putting up a Prayer have something to lose if they are a troll/spammer?

I could see someone spam 10 terrible prayers, they all get downvoted, everyone downvoting makes money from the blockchain, then the guy makes 1000 bad prayers and we all keep making money downvoting, and hes just trying to waste all our money and review time

So is this what you meant by the escrow? I put collateral on the line, if Im a troll, I lose my collateral and its paid to the reviewers and no new money is given out, if Im not a troll and its good quality content I posted, I get my collateral back and may even get paid from the blockchain with new money? or from a community fund?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on September 29, 2018, 11:20:36 pm
At some point, there should be a ceiling like 1.55M. Otherwise, it'll just be whomever has the most UTXO weight. At some point, your "integrity" has very little to do with how much BBP you hold. It is a matter of how much money you have or early you joined BBP. If not enough people vote, certainly fall back to this scheme, but if enough people participate in voting let there be a cap. That encourages more participation instead of resentment.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: jaapgvk on September 30, 2018, 05:52:34 am
At some point, there should be a ceiling like 1.55M. Otherwise, it'll just be whomever has the most UTXO weight. At some point, your "integrity" has very little to do with how much BBP you hold. It is a matter of how much money you have or early you joined BBP. If not enough people vote, certainly fall back to this scheme, but if enough people participate in voting let there be a cap. That encourages more participation instead of resentment.

I think this is something we should indeed talk about (the inns and outs), that's why I also highlighted 'new users'.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 30, 2018, 01:42:29 pm
Another note on rating, how can we differentiate between say reviewing a 1 line sentence vs a page vs a 10 page document? Would we want to pay each the same? or would we want to base pay and collateral on how long it takes to review an item? How many words to read, How many minutes in a video, etc

Could someone just vote randomly or all yes or all no on items and make money without having to actually review anything?

Should we penalize bad voters?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on September 30, 2018, 07:42:13 pm
Rob, is the copy paste issue a Vultr problem? or a Lubuntu problem?

Should I try Xubuntu or Ubuntu-Desktop? and VNC?

https://help.ubuntu.com/community/Installation/SystemRequirements
"Recommended Minimum System Requirements
Ubuntu Desktop Edition
2 GHz dual core processor
2 GiB RAM (system memory)
25 GB of hard-drive space"

https://xubuntu.org/requirements/
512 MB of memory
7.5 GB of free space
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 30, 2018, 08:32:37 pm
Unable to add test contact.

Fields I filled out: Company Name, Contact Name, Funding Receiving Address (I changed it from default to another one), E-Mail address. Drop Down Vendor

2018-09-28 05:11:39 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-09-28 05:11:39

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepaytestnet\biblepay-qt.exe in Runaway exception       

2018-09-28 05:11:59


Thanks for the bug report; it turns out the fix wasn't really in the wallet and I can clearly see what caused this.

Its fixed and will be checked in within a couple hours.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 30, 2018, 08:33:42 pm
On first sight, this seems like a very nice system! I like the idea of incentivizing people to vote. This is like an automatic bounty system.

And users with a high utxo weight are likely to be loyal to BiblePay (why else would they have a lot of BBP).

As you say, it would be an interesting economy. If this reaches prod, I hope that we can spread awareness for this in a way that also attracts new users.
+++
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 30, 2018, 08:41:00 pm
This is pretty cool!
- solves the Orphan Letter Writing review issue
- solves the Prayer review issue
- incentivizes more gospel viewing

Just so I understand correctly, is it possible to spam Prayers? or does the person putting up a Prayer have something to lose if they are a troll/spammer?

I could see someone spam 10 terrible prayers, they all get downvoted, everyone downvoting makes money from the blockchain, then the guy makes 1000 bad prayers and we all keep making money downvoting, and hes just trying to waste all our money and review time

So is this what you meant by the escrow? I put collateral on the line, if Im a troll, I lose my collateral and its paid to the reviewers and no new money is given out, if Im not a troll and its good quality content I posted, I get my collateral back and may even get paid from the blockchain with new money? or from a community fund?

First on the escrow:  I wasnt referring to this problem specifically, but yes, I was designing a way to keep the reward sitting in a delayed state while the community reviews it.

You make an excellent point - we dont want to incentivize spam.  The first idea that comes to mind is incetivizing a user to keep their content creator account (IE their nickname pointing to a public key) making it beneficial for them to build up a 'trust score' or 'integrity score' as a content creator.  Basically, the more submissions they make the more each one can be worth.  Maybe their integrity score multiplied * reward is the reward, plus, we can say a very low quality submission (say < .40) slows down the creators ability to add more content.  So if you are doing a great job no delay; the worse of a submission, the bigger delay before you can re-submit new work. 

Not sure on this one, open to more ideas.

Great point.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on September 30, 2018, 08:48:15 pm
Another note on rating, how can we differentiate between say reviewing a 1 line sentence vs a page vs a 10 page document? Would we want to pay each the same? or would we want to base pay and collateral on how long it takes to review an item? How many words to read, How many minutes in a video, etc

Could someone just vote randomly or all yes or all no on items and make money without having to actually review anything?

Should we penalize bad voters?

Huge point on the video time vs letter size etc.  This is another one that would be rife for abuse if we asked the user how long it took to review, or if we checked the size.  If we pay more, people will look for hard drive hog sized videos; or write overly long letters.   Another tough one.  One idea might be for us to measure the elapsed time the biblepay user spends in-review in a particular piece of content - and keep track of the average and maybe it influences payout.

I thought about the penalization of the bad voting.  For a while I thought about paying police to find chronic voting abusers.  I lean toward trusting utxo weight rather than trusting a manual policing process.  But in this case we could write a report that picks the top worst voters (voters that go against the grain consistently - more than say 66% of the time).  What we would do with them, I dont know.
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: togoshigekata on October 01, 2018, 01:56:26 am
I was able to set up Ubuntu Desktop and VNC on a $20/month Vultr server, my steps below:

Code: [Select]
sudo apt-get update
sudo apt-get upgrade -y

sudo apt-get install ubuntu-desktop -y
apt-get install gnome-panel gnome-settings-daemon metacity nautilus gnome-terminal -y
sudo apt-get install vnc4server -y

vncserver # enter password
vncserver -kill :1

cd ~/.vnc/

vi xstartup # copy paste below to file
gnome-panel &
gnome-settings-daemon &
metacity &
nautilus &
gnome-terminal &
:wq

sudo apt-get install ufw
sudo ufw allow ssh/tcp
sudo ufw limit ssh/tcp
sudo ufw allow 5901/tcp
sudo ufw logging on
sudo ufw enable
sudo ufw status

reboot

TightVNC Java Viewer
http://www.tightvnc.com/download.php

IP address + Port 5901 and asked for password

vncserver -kill :1
vncserver -geometry 1280x960

I was able to copy paste at first, but now I cant, I can copy out but not in, digging deeper into it

If I ever try it on a smaller server Ill report results

References:
https://stackoverflow.com/questions/25657596/how-to-set-up-gui-on-amazon-ec2-ubuntu-server
https://medium.com/@s.on/running-ubuntu-desktop-gui-aws-ec2-instance-on-windows-3d4d070da434
https://medium.com/@Arafat./graphical-user-interface-using-vnc-with-amazon-ec2-instances-549d9c0969c5
https://stackoverflow.com/questions/15816/changing-the-resolution-of-a-vnc-session-in-linux
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on October 01, 2018, 01:58:12 am
Using latest version. 1156c. Tried to add contact.

2018-10-01 06:55:11 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2018-10-01 06:55:24 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-10-01 06:55:24

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepay\biblepay-qt.exe in Runaway exception       


and then tried again on testnet3 and see attachment for erorr message.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 01, 2018, 05:23:54 am
Rob, is the copy paste issue a Vultr problem? or a Lubuntu problem?

Should I try Xubuntu or Ubuntu-Desktop? and VNC?

https://help.ubuntu.com/community/Installation/SystemRequirements
"Recommended Minimum System Requirements
Ubuntu Desktop Edition
2 GHz dual core processor
2 GiB RAM (system memory)
25 GB of hard-drive space"

https://xubuntu.org/requirements/
512 MB of memory
7.5 GB of free space

I don't think its vultr specifically, I think its that they use NoVnC by default.  Ive gotten around it lately by using "VNC4Server" (I think that is the default on ubuntu, called 'vncserver') and the clipboard works when I do that.  I also believe some SSL clients - the clipboard works.  So yeah, I think putting the key in the file should be more aligned with user error, but Im still going to potentially make a feature to give us an entire one click masternode setup (by encrypting the key, sending it into IPFS, and allowing you to retrieve the key via a bible command).  Maybe just for a baby step, Ill start with 'sendmessage' 'receivemessage' and let the user do what they want from the RPC.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 01, 2018, 05:36:46 am
Using latest version. 1156c. Tried to add contact.

2018-10-01 06:55:11 GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.
2018-10-01 06:55:24 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-10-01 06:55:24

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepay\biblepay-qt.exe in Runaway exception       


and then tried again on testnet3 and see attachment for erorr message.

Not seeing that problem; but since I forgot to fix the tab order, lets see if we can take care of this now.  I checked in 1.1.5.7b.  In this latest verson, the tab order is fixed in the DC page and the Contact add page, and the Title of Contact add should now say "Contact Add v1.1".  Could you please get that version and try again?  This way I will know you have the latest save code also.

Thanks.

Windows has been released also.

(I tested one on my win box in prod and it worked fine).



Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 01, 2018, 05:40:02 am
I was able to set up Ubuntu Desktop and VNC on a $20/month Vultr server, my steps below:

Code: [Select]
sudo apt-get update
sudo apt-get upgrade -y

sudo apt-get install ubuntu-desktop -y
apt-get install gnome-panel gnome-settings-daemon metacity nautilus gnome-terminal -y
sudo apt-get install vnc4server -y

vncserver # enter password
vncserver -kill :1

cd ~/.vnc/

vi xstartup # copy paste below to file
gnome-panel &
gnome-settings-daemon &
metacity &
nautilus &
gnome-terminal &
:wq

sudo apt-get install ufw
sudo ufw allow ssh/tcp
sudo ufw limit ssh/tcp
sudo ufw allow 5901/tcp
sudo ufw logging on
sudo ufw enable
sudo ufw status

reboot

TightVNC Java Viewer
http://www.tightvnc.com/download.php

IP address + Port 5901 and asked for password

vncserver -kill :1
vncserver -geometry 1280x960

I was able to copy paste at first, but now I cant, I can copy out but not in, digging deeper into it

If I ever try it on a smaller server Ill report results

References:
https://stackoverflow.com/questions/25657596/how-to-set-up-gui-on-amazon-ec2-ubuntu-server
https://medium.com/@s.on/running-ubuntu-desktop-gui-aws-ec2-instance-on-windows-3d4d070da434
https://medium.com/@Arafat./graphical-user-interface-using-vnc-with-amazon-ec2-instances-549d9c0969c5
https://stackoverflow.com/questions/15816/changing-the-resolution-of-a-vnc-session-in-linux

I think you are extremely close because your server side setup looks like mine (Vnc4Server, the crazy geometry setups etc), however one difference, on my side instead of tightvncviewer Ive been using 'real vnc' www.realvnc.com VNCViewer for windows, and my clipboard is working now, if you are on windows maybe try that?

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 01, 2018, 08:22:43 am
THANK YOU ALL FOR TESTING UP TO THIS POINT and helping us integrate IPFS into BiblePay!

Ill leave this thread open so we can continue discussing voting on objects and creating a business object economy.

Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: sunk818 on October 02, 2018, 12:41:34 am
says object not found in the description.

every time I do contact add, the number goes up from 1 to 2 to 3 to 4



was able to save bo object


not clear how you bring up your saved contact to delete.


some contacts you can view and info comes up (like togo), but others just empty comes up


i guess if you have long & lat, you somehow map this to gps or map. end of the world scenario, there's no guarantee there will be servesr to give you map layer... maybe text directions are better along with long-lat?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 02, 2018, 08:18:03 am
says object not found in the description.
every time I do contact add, the number goes up from 1 to 2 to 3 to 4
was able to save bo object
not clear how you bring up your saved contact to delete.
some contacts you can view and info comes up (like togo), but others just empty comes up
i guess if you have long & lat, you somehow map this to gps or map. end of the world scenario, there's no guarantee there will be servesr to give you map layer... maybe text directions are better along with long-lat?

"Object not found" means you entered the contact add the first time without having a contact record.
The incrementing number is just something I put in to show that page refreshed and updated the fields (I will take it out once the page is useful).
To Delete your contact, you click "Contact Add", and then "Delete".

As far as long lat during the Trib, If we had an in-wallet map of Christians near your contact, you could do the work of mapping and printing while the internet is up and having it on paper - maybe one would do this once per week once things start getting bad.  I think the important thing is that we are nimble enough to empower a user before the internet is cut.  (We dont know that it will be cut but we should prepare for that).

In the BO List of contacts, there is a difference between a blank contact and a deleted contact.  The blank ones are ones that cleared the info and saved the record, but didnt delete the record.  (Primarily because of testing).  Im sure it will happen in prod also.

This system is Far from perfect, and is just a baby.  The idea is to see how useful business objects can be to us, especially BO's store in IPFS and make it cosmetically nicer as we go (as we see it is actually being used in prod).


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: harrisvan87 on October 03, 2018, 03:06:48 am
Quote
Initializing daemon...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/10.111.43.4/tcp/4001
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmSousmHa2QXQzQPBKxteXtr3RZBX8RvDcCuCL9y56Q                                                                                        Kqg
Swarm announcing /ip4/10.111.43.4/tcp/4001
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
Error: serveHTTPGateway: manet.Listen(/ip4/115.78.130.36/tcp/8080) failed: liste                                                                                        n tcp4 115.78.130.36:8080: bind: cannot assign requested address

Hello Bible Team, i just install and run the IPFS on my Sanc but seem it issue now with port 8080. How can i  fix this ?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: MIP on October 03, 2018, 06:26:51 am
Hello Bible Team, i just install and run the IPFS on my Sanc but seem it issue now with port 8080. How can i  fix this ?

run this to check whether the port is already being used or not:

sudo netstat -plnt
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: harrisvan87 on October 03, 2018, 08:34:13 am
Quote
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State                                                                                               PID/Program name
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN                                                                                              863/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN                                                                                              810/sshd
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN                                                                                              737/cupsd
tcp        0      0 0.0.0.0:40000           0.0.0.0:*               LISTEN                                                                                              1234/biblepayd
tcp6       0      0 :::22                   :::*                    LISTEN                                                                                              810/sshd
tcp6       0      0 ::1:631                 :::*                    LISTEN                                                                                              737/cupsd
tcp6       0      0 :::40000                :::*                    LISTEN                                                                                              1234/biblepayd
tcp6       0      0 :::9998                 :::*                    LISTEN                                                                                              1234/biblepayd
Hi MIP, here the result. i see page 6 that Jaap got same error. but im not technical guys so im not sure according Rob's advise how to bind the 8080 port to local ip address
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 03, 2018, 04:45:20 pm
Hello Bible Team, i just install and run the IPFS on my Sanc but seem it issue now with port 8080. How can i  fix this ?

Hi Harris, It looks like the problem isnt that port 8080 is listening already, I believe the problem is the port should be bound to your local LAN IP (in contrast to your public IP), could you try re-editing your ipfs config file and binding the 8080 entry to:
10.111.43.4

instead, then restart the ipfs daemon?

Then to see if it actually works remotely, navigate to your http://public_ip:8080/ipfs/ipfs_hash?

Good luck dude.


Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: harrisvan87 on October 03, 2018, 10:10:45 pm
Quote
Initializing daemon...
Successfully raised file descriptor limit to 2048.
Swarm listening on /ip4/10.111.43.4/tcp/4001
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmSousmHa2QXQzQPBKxteXtr3RZBX8RvDcCuCL9y56QKqg
Swarm announcing /ip4/10.111.43.4/tcp/4001
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
Gateway (readonly) server listening on /ip4/10.111.43.4/tcp/8080
Daemon is ready
Thanks Rob, it working .
I see IPFS running on my Sanc now, but how i know and operation the status of IPFS really synced and usage of IPFS ?
Title: Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
Post by: Rob Andrews on October 07, 2018, 02:30:53 pm
Thanks Rob, it working .
I see IPFS running on my Sanc now, but how i know and operation the status of IPFS really synced and usage of IPFS ?

I'll be back on this thread shortly...

Title: Business objects in production
Post by: sunk818 on October 20, 2018, 11:49:54 pm
In production, some business objects say COMPASSION.COMn (extra n) in there.


Also, Compassion.com & Kairos right click navigate to works great.


For some reason, BLOOM right click navigate to doesn't do anything.


If I type the Bloom URL manually in Chrome 69, it displays okay. Using Windows 10 Pro, Chrome 69, BiblePay 1.1.5.9