TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)

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?

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.

I can recommend HostBRZ - $12/yr: 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.

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

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.

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
}


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?

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...

Okay, got the AWS Sanc up an running. Same issue with the IPFS

Copy-past of firewall, IPFS and telnet attempt:

Code: [Select]

[email protected]:~$ 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)

[email protected]:~$ 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
[email protected]:~$ 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.

 

Okay, got the AWS Sanc up an running. Same issue with the IPFS

Copy-past of firewall, IPFS and telnet attempt:

Code: [Select]

[email protected]:~$ 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)

[email protected]:~$ 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
[email protected]:~$ 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.

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!  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.

I works!  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.

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
}


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.

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....