|
|
thesnat21
Jr. Member
 Offline
Activity: 490
Merit: 4
|
 |
October 16, 2018, 10:25:22 AM |
|
Unbanked payment missing again.
How is daily superblock time doing? Still hanging in there around 24 hours per day? Noticed its been drifting past closer to 25 hours between daily superblock to superblock.
Same on unbanked, worked for 3 days then missed yesterdays again. |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 02:06:45 PM |
|
Unbanked payment missing again.
How is daily superblock time doing? Still hanging in there around 24 hours per day? Noticed its been drifting past closer to 25 hours between daily superblock to superblock.
Same on unbanked, worked for 3 days then missed yesterdays again. Ok interestng. Well so far the strange thing I see is only 54% of our network upgraded (exec versionreport), meaning that its possible our old chain is not forked yet (since the rules aren't exactly 'breaking' rules). I think we will need to somehow know which sanc version created the contract. We do know which version mined it, but not which sanc version created it. But I'm leaning toward the high possibility that since we have barely a supermajority upgraded, its possible an old sanc created the contract under the old rules. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 02:10:34 PM |
|
It could be your nameserver on your sanc. Ensure a nameserver record like "nameserver 8.8.8.8" exists in /etc/resolv.conf. Could you paste the URL that your sanc cant access and I will try it on my sanc? There is a huge amount of information I'm trying to gather together, I am thinking of creating a wiki just to post this weeks update. |
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
October 16, 2018, 02:27:19 PM |
|
Unbanked payment missing again.
How is daily superblock time doing? Still hanging in there around 24 hours per day? Noticed its been drifting past closer to 25 hours between daily superblock to superblock.
Same on unbanked, worked for 3 days then missed yesterdays again. Ok interestng. Well so far the strange thing I see is only 54% of our network upgraded (exec versionreport), meaning that its possible our old chain is not forked yet (since the rules aren't exactly 'breaking' rules). I think we will need to somehow know which sanc version created the contract. We do know which version mined it, but not which sanc version created it. But I'm leaning toward the high possibility that since we have barely a supermajority upgraded, its possible an old sanc created the contract under the old rules. This is confusing... { "Version": "Popularity,Percent %", "1.1.3.8": "12; 5.85%", "1.1.4.6": "1; 0.49%", "1.1.4.7": "1; 0.49%", "1.1.4.8": "1; 0.49%", "1.1.5.4": "1; 0.49%", "1.1.5.6": "53; 25.85%", "1.1.5.7": "18; 8.78%", "1.1.5.8": "5; 2.44%", "1.1.5.9": "113; 55.12%" } As of 77000 we should have minimum of 1.1.5.7, Are we not enforcing that on the network? I'm curious how clients on 1.1.5.6 or older are still mining blocks. |
|
|
|
|
|
|
|
sunk818
|
|
October 16, 2018, 02:57:47 PM |
|
It looks like USDT is really falling apart with big liquidity issues. I can't imagine who'd want to accumulate it. Did you see how BTC reacted?
Why would anyone want to hold tether when you have audited stablecoins like Gemini Dollar or True USD? Tether's time is ending because they can't get an audit together which means they are hiding something. |
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
October 16, 2018, 04:02:48 PM |
|
It looks like USDT is really falling apart with big liquidity issues. I can't imagine who'd want to accumulate it. Did you see how BTC reacted?
Why would anyone want to hold tether when you have audited stablecoins like Gemini Dollar or True USD? Tether's time is ending because they can't get an audit together which means they are hiding something. At the moment because neither of those are on many exchanges, or have volume to support their use. This could change obviously with this event.. |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 04:07:48 PM |
|
It looks like USDT is really falling apart with big liquidity issues. I can't imagine who'd want to accumulate it. Did you see how BTC reacted?
Why would anyone want to hold tether when you have audited stablecoins like Gemini Dollar or True USD? Tether's time is ending because they can't get an audit together which means they are hiding something. Well, imho, maybe a group has discovered the effect of the arb in dumping tether. I think if (this is pure speculation), if a group has 100MM of tether accumulated at a cost of $1 per tether, lets say they want to enter the alt coin market. They buy 50M in bitcoin, they dump tether, they sell bitcoin on the highest exchanges and/or buy altcoins with the BTC simultaneously. It could be that they are taking advantage of the tether derivatives desk another words to leg into another currency. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 04:09:52 PM
Last edit: October 16, 2018, 04:22:27 PM by bible_pay |
|
It could be your nameserver on your sanc. Ensure a nameserver record like "nameserver 8.8.8.8" exists in /etc/resolv.conf. Could you paste the URL that your sanc cant access and I will try it on my sanc? There is a huge amount of information I'm trying to gather together, I am thinking of creating a wiki just to post this weeks update. It works from my sanc #1. Could you please provide a specific error? PS: When you start the ipfs daemon, it should say if its listening on the 'gateway' port. That IP should be your public sanc IP. It might have thrown an error. If you have a firewall running, you must open port 8080 also. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 04:12:33 PM
Last edit: October 16, 2018, 04:26:53 PM by bible_pay |
|
Unbanked payment missing again.
How is daily superblock time doing? Still hanging in there around 24 hours per day? Noticed its been drifting past closer to 25 hours between daily superblock to superblock.
Same on unbanked, worked for 3 days then missed yesterdays again. Ok interestng. Well so far the strange thing I see is only 54% of our network upgraded (exec versionreport), meaning that its possible our old chain is not forked yet (since the rules aren't exactly 'breaking' rules). I think we will need to somehow know which sanc version created the contract. We do know which version mined it, but not which sanc version created it. But I'm leaning toward the high possibility that since we have barely a supermajority upgraded, its possible an old sanc created the contract under the old rules. This is confusing... { "Version": "Popularity,Percent %", "1.1.3.8": "12; 5.85%", "1.1.4.6": "1; 0.49%", "1.1.4.7": "1; 0.49%", "1.1.4.8": "1; 0.49%", "1.1.5.4": "1; 0.49%", "1.1.5.6": "53; 25.85%", "1.1.5.7": "18; 8.78%", "1.1.5.8": "5; 2.44%", "1.1.5.9": "113; 55.12%" } As of 77000 we should have minimum of 1.1.5.7, Are we not enforcing that on the network? I'm curious how clients on 1.1.5.6 or older are still mining blocks. We had a mandatory - due to the block check rules changing, so that technically is enough to cause a fork and require a mandatory - but getting more specific, in this particular case, the rules that changed are not "breaking". They dont change hashes in POW, and they are subtle. For one we removed the check that enforces that a heat miner must be in the prior superblock. Once we have a little more supermajority on 1159 where that rule is "broken", these other guys will have to upgrade as they will be on a fork. Edit: To put it more simply, we are waiting for one of the legacy miners to break a mining rule, and have enough on 1159 with "more work" to cause a fork, that will lead to a breaking change. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 04:20:49 PM |
|
Now that the PODC BiblePay Team Requirement is removed, What are the steps BOINC crunchers will need to take to get rewarded BBP coins? Pretend you are a new BiblePay User, and a Total Newbie to Crypto, but you know BOINC ========= Steps: 0. World Community Grid crunchers, make sure your My Profile has "Display my data" enabled, Click Save https://www.worldcommunitygrid.org/ms/viewMyProfile.do=== 1. Download BiblePay Wallet https://www.biblepay.org/wallet/=== 2. Get 1,000 Free BiblePay coins from the Pool Faucet http://pool.biblepay.org/ >> Register Account >> "Faucet" menu >> "Faucet" Enter BiblePay address and CPID (Cross Project Identifier), Click Send USER: How to get Biblepay address? USER: How to get CPID? QUESTION: Do you still have to be a member of Team BiblePay to receive the faucet reward? === 3. Link your BOINC account inside the Biblepay Wallet "Distributed Computing" tab >> Enter Account >> Click "Associate" === 4. Buy and Stake coins to receive full crunching rewards To get 100% of your RAC rewarded, you need 20 BBP coins per each 1 RAC stored in your wallet. This is called UTXO weight. QUESTION: To get any rewards at all you need at least 2 BBP per each 1 RAC? Basically you have to buy and hold at least a little bit of BiblePay coins in order to receive rewards (NOTE: this was added as an anti-botnet feature to protect the blockchain) This command shows how much BBP you will need for staking: Wallet >> Tools >> Debug Console >> Type Command: exec totalrac USER: How to buy Biblepay? You need Bitcoin USER: How to Buy Bitcoin? USER: How to Transfer Bitcoin? USER: How to Use an Exchange? Buy BiblePay coins from SouthXchange with Bitcoin, Buy Bitcoin from Coinbase or a local exchange! Links: https://www.reddit.com/r/BiblePay/comments/7nevdg/how_to_get_biblepay_bbp_coins/=== 5. Once Staked, Keep BiblePay Wallet running 24/7 to send daily staking updates and now you'll get paid BiblePay coins every day! === References: https://www.biblepay.org/freebbp/#faucetshttps://www.biblepay-central.org/en/documentations/mining-how-to/https://www.biblepay.org/mining/https://www.biblepay.org/airdrop/https://www.reddit.com/r/BiblePay/comments/97cx4f/world_community_grid_wcg_mining_guide/https://www.biblepay-central.org/en/documentations/getting-biblepay-coins/========= Theres a lot of steps O_O, if we can make this smooth and as easy and user friendly as possible we can increase the number of potential conversions, Anything missing? Anything wrong? Any improvements? This is quick first draft Excellent start. So on the faucet, I think the faucet would go bankrupt if we turn off the team requirement and leave it at 1000 bbp. I think we will either need to keep as-is and let them change the team, pull the faucet reward, and if they want change the team back they may do so. If we remove the team, I believe we need to lower the reward to 50 bbp. So for now, let's leave it as-is, and require team biblepay for the faucet reward. For the UTXO requirement: Yes, they will need 2 BBP per RAC to receive the PODC minimum rewards. |
|
|
|
|
togoshigekata
|
|
October 16, 2018, 06:39:10 PM |
|
It could be your nameserver on your sanc. Ensure a nameserver record like "nameserver 8.8.8.8" exists in /etc/resolv.conf. Could you paste the URL that your sanc cant access and I will try it on my sanc? There is a huge amount of information I'm trying to gather together, I am thinking of creating a wiki just to post this weeks update. It works from my sanc #1. Could you please provide a specific error? PS: When you start the ipfs daemon, it should say if its listening on the 'gateway' port. That IP should be your public sanc IP. It might have thrown an error. If you have a firewall running, you must open port 8080 also. 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/45.76.236.38/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmPzJZs5NhAaLHU6Uquk8F1s1VAjoenVCDNueX9H3d9NrT
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/45.76.236.38/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/45.76.236.38/tcp/8080
Daemon is ready sudo ufw status
Status: active
To Action From
-- ------ ----
22/tcp LIMIT Anywhere
40000/tcp ALLOW Anywhere
9998/tcp ALLOW Anywhere
8080/tcp ALLOW Anywhere
22/tcp (v6) LIMIT Anywhere (v6)
40000/tcp (v6) ALLOW Anywhere (v6)
9998/tcp (v6) ALLOW Anywhere (v6)
8080/tcp (v6) ALLOW Anywhere (v6) Seems to just spin, hmmm, Do you need to have BiblePay GUI running for IPFS to work? Thats one difference I can see from my testnet testing |
|
|
|
morka
Newbie
Offline
Activity: 11
Merit: 0
|
|
October 16, 2018, 07:42:33 PM |
|
Hi All
We are behind Block 77000 and my Problem remains the same.
Rosetta PODC works.
Still my wcg Rac does not Appear in my Biblepay Wallet. (1.1.5.9)
E-Mail in wcg is the same as for Rosetta.
CPID in wcg is not the same as in Rosetta
At the Pool, in the Superblock view my WCG Rac is 0.
What can I do too make my wcg "points" count in biblepay?
|
|
|
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 07:47:16 PM |
|
Hi All
We are behind Block 77000 and my Problem remains the same.
Rosetta PODC works.
Still my wcg Rac does not Appear in my Biblepay Wallet. (1.1.5.9)
E-Mail in wcg is the same as for Rosetta.
CPID in wcg is not the same as in Rosetta
At the Pool, in the Superblock view my WCG Rac is 0.
What can I do too make my wcg "points" count in biblepay?
I believe your problem is entirely that your WCG CPID is not matching RAHs, so lets try to get that working for now. Please install BOINC gui on one of your machines crunching Rosetta. From that machine, detach WCG. Ensure RAH is crunching tasks actively. Then re-attach WCG. Then click Update on WCG. Usually after this, within 24 hours, WCG will honor and update its CPID to match your RAH cpid. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 08:12:16 PM |
|
It could be your nameserver on your sanc. Ensure a nameserver record like "nameserver 8.8.8.8" exists in /etc/resolv.conf. Could you paste the URL that your sanc cant access and I will try it on my sanc? There is a huge amount of information I'm trying to gather together, I am thinking of creating a wiki just to post this weeks update. It works from my sanc #1. Could you please provide a specific error? PS: When you start the ipfs daemon, it should say if its listening on the 'gateway' port. That IP should be your public sanc IP. It might have thrown an error. If you have a firewall running, you must open port 8080 also. 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/45.76.236.38/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit/ipfs/QmPzJZs5NhAaLHU6Uquk8F1s1VAjoenVCDNueX9H3d9NrT
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/45.76.236.38/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/45.76.236.38/tcp/8080
Daemon is ready sudo ufw status
Status: active
To Action From
-- ------ ----
22/tcp LIMIT Anywhere
40000/tcp ALLOW Anywhere
9998/tcp ALLOW Anywhere
8080/tcp ALLOW Anywhere
22/tcp (v6) LIMIT Anywhere (v6)
40000/tcp (v6) ALLOW Anywhere (v6)
9998/tcp (v6) ALLOW Anywhere (v6)
8080/tcp (v6) ALLOW Anywhere (v6) Seems to just spin, hmmm, Do you need to have BiblePay GUI running for IPFS to work? Thats one difference I can see from my testnet testing Very interesting Togo, thanks. Yes, I concur, I'm having the same problem on my IPFS public linux node. (I was actually just working on a similar issue for biblepay-core, to change the bootstrap node list dynamically to include our Christian camp nodes). Anyway, I see the problem. We just have the default ipfs.io bootstrap nodes in the config file. Please modify your ipfs config file with the following change: https://github.com/biblepay/biblepay/blob/master/InstallingIPFS_Ubuntu64.mdPlease see the section called "Add Bootstrap node". Can you add that line and remove the existing bootstrap nodes, then restart ipfs, then lets see if the cake resolves? |
|
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 09:05:40 PM |
|
Thank you Rob, it works now!
What is a good way to run the ipfs daemon on its own?
(If if I run it over SSH it consumes the window)
I think we will need to put it in a machine startup script - like /etc/init.d/servicename, but for now since we are just in volunteer mode you can run: ipfs daemon & Until we figure out if the mining program will start it automatically. If you want you can write a machine startup script for ubuntu, and give it to us and Ill add it to the ipfs document. We really just need the machine to run "ipfs daemon" on reboot. EDIT: It looks like the daemon does exit if its already running, so I suppose we could do it through crontab once an hour if we want to pipe output to devnull. Similar to our watchman entry but maybe once an hour. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 16, 2018, 09:15:18 PM |
|
C-CEX has put us in maintenance! Yes!
|
|
|
|
|
