91
Archived Proposals / Re: Aug 2018 BBP Telegram Airdrop Support
« on: September 05, 2018, 08:34:49 AM »
Thanks for helping me out Sunk!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
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
}
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 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.
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?
So whats your IP Jaap, Id like to see if your sanc is enabled on my node?
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.
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.
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...
"Gateway": "/ip4/84.29.208.33/tcp/8080"
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
71c44d1cc7e3f29aac6b0c8e9ade3c43cc79da3d0c22f183439d8e440c6a7d3e
Do I see two proposals? One is for and one is against?
Trying to figure out how to set up masternode for the first time. Getting close I hope.
Hi Jaap, please try
ipfs stats repo
The Repo path should be in there.
Then cd to it and nano config.
Error: serveHTTPGateway: manet.Listen(/ip4/MYIP/tcp/8080) failed: listen tcp4 MYIP:8080: bind: cannot assign requested address
cd ~/.ipfs