Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 290. (Read 243437 times)
November 18, 2018, 08:42:31 AM
What is the status with next Exchange listing?
November 18, 2018, 08:37:41 AM
Thanks Slovakia
Added to Reddit sidebar
I noticed the coin supply is 533 million?
MIP,SNAT excellent work on PPAs thanks
PPA is all MIP's doing
November 18, 2018, 08:03:28 AM
Thanks Slovakia
Added to Reddit sidebar
I noticed the coin supply is 533 million?
MIP,SNAT excellent work on PPAs thanks
November 18, 2018, 06:00:00 AM
Awesome work with the new repo. I would really appreciate if you could add ARM branches there too. Those are the ones that are most important (at least to me), since compilation of BBP on these machines takes forever. 
I added them but it seems Launchpad does not build new archs on an existing version. Unless I am missing something, I would need to upload the same 1.1.6.1 packages with a new debian internal version to force rebuilding. I'll give it a try but it will take some hours to compile everything again.
November 17, 2018, 07:43:16 PM
Biblepay 1.1.6.1-Leisure
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Available for MacOS and Linux at this moment
Due to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic)
If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts.
Then add the new repository
and install as usual
Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages).
From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch.
This will facilitate us managing the whole product cycle more efficiently.
Thank you!
mark new ppa repository * RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Available for MacOS and Linux at this moment
Due to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic)
If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts.
Code:
# stop biblepay
sudo apt-get remove biblepayd biblepay-qt
sudo add-apt-repository ppa:biblepay/stable --remove
Then add the new repository
Code:
sudo add-apt-repository ppa:biblepay-official/mainnet
sudo apt-get update
and install as usual
Code:
sudo apt-get install biblepayd # daemon and cli
sudo apt-get install biblepay-qt # for QT GUI
Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages).
From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch.
This will facilitate us managing the whole product cycle more efficiently.
Thank you!
November 17, 2018, 06:00:28 PM
Biblepay 1.1.6.1-Leisure
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Thanks MIP!
Also, sanctuaries it's an important update... Not mandatory, but preferred!
Other items:
* Resuming standard World Community Grid unbanked payments (new host verification method) no more limit to 100rac for WCG
November 17, 2018, 05:38:45 PM
Biblepay 1.1.6.1-Leisure
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Available for MacOS and Linux at this moment
Due to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic)
If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts.
Then add the new repository
and install as usual
Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages).
From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch.
This will facilitate us managing the whole product cycle more efficiently.
Thank you!
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Available for MacOS and Linux at this moment
Due to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic)
If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts.
Code:
# stop biblepay
sudo apt-get remove biblepayd biblepay-qt
sudo add-apt-repository ppa:biblepay/stable --remove
Then add the new repository
Code:
sudo add-apt-repository ppa:biblepay-official/mainnet
sudo apt-get update
and install as usual
Code:
sudo apt-get install biblepayd # daemon and cli
sudo apt-get install biblepay-qt # for QT GUI
Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages).
From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch.
This will facilitate us managing the whole product cycle more efficiently.
Thank you!
Awesome work with the new repo. I would really appreciate if you could add ARM branches there too. Those are the ones that are most important (at least to me), since compilation of BBP on these machines takes forever.
I really love seeing this community going forward productively and not wasting valuable time and effort in argueing. Let's hope the current bear market won't have too much more downside effect on our beautiful coin.
November 17, 2018, 04:11:53 PM
Thanks Slovakia
Added to Reddit sidebar
I noticed the coin supply is 533 million?
November 17, 2018, 03:09:41 PM
Being able to see proposals for a particular super block month would be nice. Have it be based on the blockading data and not a third party that can hide proposals with identical names
November 17, 2018, 02:41:57 PM
Biblepay 1.1.6.1-Leisure
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Available for MacOS and Linux at this moment
Due to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic)
If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts.
Then add the new repository
and install as usual
Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages).
From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch.
This will facilitate us managing the whole product cycle more efficiently.
Thank you!
* RPC command 'spork show' improved (thesnat21).
* typos and text corrections (sunk818)
* changes to support new launchpad PPAs (MIP)
Available for MacOS and Linux at this moment
Due to unresponsiveness of Licht who maintained the previous Ubuntu PPA packages, we created a new PPA with support for Ubuntu 16.04 (xenial) and 18.04 (bionic)
If you want to use this new PPA, and you used previously Licht's package on a machine, please remove it before installing the new packages, to avoid conflicts.
Code:
# stop biblepay
sudo apt-get remove biblepayd biblepay-qt
sudo add-apt-repository ppa:biblepay/stable --remove
Then add the new repository
Code:
sudo add-apt-repository ppa:biblepay-official/mainnet
sudo apt-get update
and install as usual
Code:
sudo apt-get install biblepayd # daemon and cli
sudo apt-get install biblepay-qt # for QT GUI
Later on we will create separate packages for testnet versions for that purpose, which will build from "develop" branch of our repo (as "master" branch is used to create mainnet packages).
From now on, when submitting pull requests, please select "biblepay:develop" branch as destination, instead "biblepay:master", to allow us to compile and test before moving the code to the "stable" master branch.
This will facilitate us managing the whole product cycle more efficiently.
Thank you!
November 17, 2018, 12:37:32 PM
why can we see again voting for next proposal when exists other? 
https://forum.biblepay.org/index.php?topic=286.new#new
https://forum.biblepay.org/index.php?topic=286.new#new
I believe these are the old/original proposals from October, they are still showing in the wallet.
They should not be considered in the next superblock.
November 17, 2018, 11:54:32 AM
why can we see again voting for next proposal when exists other?
https://forum.biblepay.org/index.php?topic=286.new#new
https://forum.biblepay.org/index.php?topic=286.new#new
November 17, 2018, 03:04:04 AM
hmm so wallet is out of sync, resyncing from 0, but what is interesting is that 'system' is showing 80MB/s disk activity nonstop... (when wallet is syncing) - of course it is extremely slow, few blocks per minute
November 17, 2018, 02:08:48 AM
we are probably stucked on payment block
edit: maybe only my wallet is stucked hmmmmm
edit: maybe only my wallet is stucked hmmmmm
November 16, 2018, 07:23:33 PM
November 16, 2018, 03:12:24 PM
If it isn't the pending work, then it is possible that the large amounts of people focusing on the WCG Birthday Challenge may be a case where the credits are adjusting based on other hardware being brought online. WCG uses a form of the Credit New credit system with a few modification the last I knew. Which means over time the points will adjust based on everyone else.
Interesting, are you saying the overall rewards could go down based on the earnings of the "crowd"?
That is what I'm implying yes.
Quote
How are points calculated?
Points are calculated in a two-step process which attempts to give a consistent number of points for similar amounts of research computation. First, the computational power/speed of the computer is determined by periodically running a benchmark calculation. Then, based on the central processing unit (CPU) time spent computing the research result for a work unit, the benchmark result is used to convert the time spent on a work unit into points. This adjusts the point value so that a slow computer or a fast computer would produce about the same number of points for calculating the research result for the same work unit. This value is the number of point credits "claimed" by the client. More information about that formula is available here.
Second, research results returned to the servers are validated in a manner which depends on the research project. Then the claimed points for valid results are examined for anomalous (excessively high or low compared to other machines computing the same or equivalent work unit) values and adjusted accordingly. The servers assign the resulting adjusted point values to the member (and team) for each of the returned work units. This process eliminates the ability for malicious users to tamper with results and artificially claim higher points for their work.
Points are calculated in a two-step process which attempts to give a consistent number of points for similar amounts of research computation. First, the computational power/speed of the computer is determined by periodically running a benchmark calculation. Then, based on the central processing unit (CPU) time spent computing the research result for a work unit, the benchmark result is used to convert the time spent on a work unit into points. This adjusts the point value so that a slow computer or a fast computer would produce about the same number of points for calculating the research result for the same work unit. This value is the number of point credits "claimed" by the client. More information about that formula is available here.
Second, research results returned to the servers are validated in a manner which depends on the research project. Then the claimed points for valid results are examined for anomalous (excessively high or low compared to other machines computing the same or equivalent work unit) values and adjusted accordingly. The servers assign the resulting adjusted point values to the member (and team) for each of the returned work units. This process eliminates the ability for malicious users to tamper with results and artificially claim higher points for their work.
The system tries to average things out on its own but it isn't quick. People have dabbled with the system and have had varying results. I do not have the posts linked. However, new hosts added will sometimes score better than long term hosts. But over time it levels out. This may be what people are seeing. It may be something else. A lot of details are unknown.
November 16, 2018, 02:34:52 PM
ah sooo...
pending validation - 12 pages (15tasks /page)
pending verification - 1 page
this is amount of 1 average machine... , this could not be root cause of lower points
pending validation - 12 pages (15tasks /page)
pending verification - 1 page
this is amount of 1 average machine... , this could not be root cause of lower points
November 16, 2018, 02:12:08 PM
If it isn't the pending work, then it is possible that the large amounts of people focusing on the WCG Birthday Challenge may be a case where the credits are adjusting based on other hardware being brought online. WCG uses a form of the Credit New credit system with a few modification the last I knew. Which means over time the points will adjust based on everyone else.
Interesting, are you saying the overall rewards could go down based on the earnings of the "crowd"?
November 16, 2018, 01:49:18 PM
Are/have you been running MCM exclusively? And have you seen a slow down in the validation of work units? MCM require what is referred to as a wingman to validate the work units. Leading up to challenges, you will see numerous people deploying a tactic called bunkering where they load up their machines with a ton of work and then sit on the finished results waiting for the event to start so that they can dump all of the extra results during the challenge time frame. So, it is very possible a lot of your work was getting validated at a later time. Another possibility is that the points for work shifts slightly over time as part of the credit system used. You will find that for one person one type of work unit may pay better than for another person. The next day another work unit type may pay slightly better. In the end they kind of evens out.
not exclisively, there are few other tasks like:
11791 boinc 39 19 77004 36764 2372 R 106.2 0.0 14:28.92 wcgrid_mcm1_map
12779 boinc 39 19 77004 36676 2312 R 106.2 0.0 3:29.29 wcgrid_mcm1_map
415 boinc 39 19 77136 36916 2320 R 100.0 0.0 139:33.93 wcgrid_mcm1_map
1283 boinc 39 19 77136 36956 2380 R 100.0 0.0 130:30.20 wcgrid_mcm1_map
1514 boinc 39 19 77136 36880 2320 R 100.0 0.0 128:17.18 wcgrid_mcm1_map
1522 boinc 39 19 77136 36952 2380 R 100.0 0.0 128:08.43 wcgrid_mcm1_map
3015 boinc 39 19 77136 36856 2320 R 100.0 0.0 111:57.51 wcgrid_mcm1_map
3701 boinc 39 19 77136 36924 2380 R 100.0 0.0 104:22.62 wcgrid_mcm1_map
4085 boinc 39 19 77140 36908 2380 R 100.0 0.0 100:06.13 wcgrid_mcm1_map
4822 boinc 39 19 77140 36904 2380 R 100.0 0.0 91:31.32 wcgrid_mcm1_map
5533 boinc 39 19 77136 36892 2380 R 100.0 0.0 83:47.70 wcgrid_mcm1_map
6267 boinc 39 19 77136 36880 2380 R 100.0 0.0 75:32.74 wcgrid_mcm1_map
10016 boinc 39 19 77004 36744 2320 R 100.0 0.0 34:08.22 wcgrid_mcm1_map
11130 boinc 39 19 77004 36764 2320 R 100.0 0.0 21:42.24 wcgrid_mcm1_map
12005 boinc 39 19 77004 36700 2312 R 100.0 0.0 12:06.78 wcgrid_mcm1_map
23870 boinc 39 19 337244 272312 48300 R 100.0 0.2 238:54.78 wcgrid_mip1_ros
23879 boinc 39 19 437288 362752 54036 R 100.0 0.3 238:55.29 wcgrid_mip1_ros
25413 boinc 39 19 407968 333420 53936 R 100.0 0.3 222:01.77 wcgrid_mip1_ros
25990 boinc 39 19 77268 37024 2380 R 100.0 0.0 215:37.21 wcgrid_mcm1_map
26771 boinc 39 19 77268 37016 2380 R 100.0 0.0 206:55.13 wcgrid_mcm1_map
26909 boinc 39 19 77272 37032 2380 R 100.0 0.0 205:26.09 wcgrid_mcm1_map
27058 boinc 39 19 77268 36968 2320 R 100.0 0.0 203:46.33 wcgrid_mcm1_map
28532 boinc 39 19 77136 37008 2380 R 100.0 0.0 187:26.61 wcgrid_mcm1_map
28944 boinc 39 19 77136 36992 2380 R 100.0 0.0 182:51.89 wcgrid_mcm1_map
30477 boinc 39 19 77140 36992 2380 R 100.0 0.0 165:53.40 wcgrid_mcm1_map
31516 boinc 39 19 77136 36972 2380 R 100.0 0.0 154:22.63 wcgrid_mcm1_map
31525 boinc 39 19 77136 36972 2380 R 100.0 0.0 154:17.46 wcgrid_mcm1_map
31554 boinc 39 19 77136 36976 2380 R 100.0 0.0 154:01.24 wcgrid_mcm1_map
31640 boinc 39 19 77136 36968 2380 R 100.0 0.0 153:03.18 wcgrid_mcm1_map
32117 boinc 39 19 77136 36968 2380 R 100.0 0.0 147:42.83 wcgrid_mcm1_map
1043 boinc 39 19 77136 36880 2320 R 93.8 0.0 133:00.77 wcgrid_mcm1_map
2198 boinc 39 19 77136 36928 2380 R 93.8 0.0 120:52.40 wcgrid_mcm1_map
but i was not using bunkering and i have big tasks queue, about 1000 tasks/machine so i'm not suffering from not having tasks
we will see during next days
Just to be clear, I'm not implying that you are having trouble getting tasks. I'm saying the MCM tasks that you complete require a second person to also complete that work unit to verify it. No points are awarded until the work unit is returned AND verified. So, if someone else is bunkering, they may not return their work until their 10 day deadline approaches. Thus you may not have credit for your completed work units until they return theirs. IF they didn't complete on time, then someone else will be sent work units (typically a 4 day deadline) and then you have to wait for them to complete it and return it. So, in some instances you may have to wait up to 2 weeks or more to get the credit. When someone bunkers thousands of work units all at once, there is a possibility that several of your work units are not verified until they turn theirs in. That is why I was asking. If you look at each work unit on the WCG website, you can sort your work units by what is pending verification and pending validation (different scenarios). If your pendings have grown, it is probably from bunkering this large challenge.
If it isn't the pending work, then it is possible that the large amounts of people focusing on the WCG Birthday Challenge may be a case where the credits are adjusting based on other hardware being brought online. WCG uses a form of the Credit New credit system with a few modification the last I knew. Which means over time the points will adjust based on everyone else.
November 16, 2018, 11:38:00 AM
Curious what the cause is... Thanks for doing investigating guys!
Is there a new project on WCG that is harder than the others?
I'd be curious to see what % is dedicated to each project
Is there a new project on WCG that is harder than the others?
I'd be curious to see what % is dedicated to each project
Jump to: