Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 599. (Read 243376 times)

full member
Activity: 364
Merit: 102
Tmike said on the other forum that less than 1000 RAC shouldn't require staking, and I would agree with that. Good idea.  

I'm thinking if the RAC is below 1000 you don't need to stake and limit it to Windows and Android machines and no Xeon processors.
I disagree with that due to the possibility of people circumventing stake with multiple accounts

Edit: note that unbanked will need no stake on mobile if I understand correctly
full member
Activity: 364
Merit: 102
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"

Honestly I think either will work, RAC or magnitude. I just like magnitude because it scales with the network size. But either or will do for me.

The simplest way I look at is, Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.  Always, even when supply is 3 Billion.  For RAC our current RAC is 1.3M So if we do 20 BBP per RAC that is 26 million lockup.  If we have a 10 million RAC with x larger supply that is a 200 million lockup.  Woo-hoo! We just engineered ourselves higher prices at a fraction of the cost of a masternode, important especially when masternodes become unaffordable.  It is important to consistently seek some way to keep mopping up supply.  This coin has a lot of supply on the front end.  It will take time for the supply to consolidate.  If bitcoin goes way up, we will still have a high effusion rate, people won't be able to afford to buy as much biblepay.  If we keep growing the stake amount with the RAC of the network, we do something to give buyers confidence that the coin won't collapse.  Buyers are the ones who truly support the orphans, not miners and crunchers.

Even when the exchanges are out of maintenance, take some time to read the tape when the prices suddenly go up.  Prices go up by surprise because liquidity dried up and people are willing to pay higher and higher prices.  They take out those standing limit offers.  Then the miners start to come in when they realize prices just got higher.  At first, they put out limits on the offer.  When those stop getting hit, they start to get desperate and start hitting the bid, soaking up liquidity the other way.  Then prices come back down.  It would help to have a consistent way to soak up supply and we would engineer higher prices much in the way companies buy back their own stock.  Miners are part of the company.  Miners accumulating bbp as the network grows helps prices to appreciate.

For reference the current masternode lockup has 262 million bpp.  And since the start of masternodes we are consistently 20 or more satoshi higher.  So more lockup should mean higher prices, and more orphans supported.  A win for everybody.


Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.

I don't think this is true. Now, but more as as our group RAC grows, many miners/boincers will have less than 1magnitude. They still need to stake the equivalent of 1 magnitude, let's say 50k. Therefore, the total can be significantly more than 50 million

If that is the case, then staking based on RAC is much more equitable between users.  Having to stake 50,000 bbp for a fraction of a magnitude for a PC that does say 500 RAC, that same user would only have to stake 10,000, which is more equitable for the reward received for smaller users.

Staking based on RAC also makes bbp worth 1/20 of a RAC and biblepay is the compensation you get for doing crunching and using electricity, computers and time.  1/20 of a RAC is actual intrinsic value.  That is something that would actually back biblepay.  And why would you choose to stake bbp instead of crunching boinc on your own?  Because you get compensated in bbp for crunching.

We'll I hope I've made it clear that I think both will work, as long as we require someone  who is trying  to or control 50% of our rewards to stake a very significant number of BBP.

Personally in your vote I voted for magnitude, but I see both sides, and I'm glad you are thinking this through deeply and presenting counter arguments in an intelligent and respectful way
newbie
Activity: 180
Merit: 0
Tmike said on the other forum that less than 1000 RAC shouldn't require staking, and I would agree with that. Good idea. 

I'm thinking if the RAC is below 1000 you don't need to stake and limit it to Windows and Android machines and no Xeon processors.
newbie
Activity: 180
Merit: 0
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"

Honestly I think either will work, RAC or magnitude. I just like magnitude because it scales with the network size. But either or will do for me.

The simplest way I look at is, Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.  Always, even when supply is 3 Billion.  For RAC our current RAC is 1.3M So if we do 20 BBP per RAC that is 26 million lockup.  If we have a 10 million RAC with x larger supply that is a 200 million lockup.  Woo-hoo! We just engineered ourselves higher prices at a fraction of the cost of a masternode, important especially when masternodes become unaffordable.  It is important to consistently seek some way to keep mopping up supply.  This coin has a lot of supply on the front end.  It will take time for the supply to consolidate.  If bitcoin goes way up, we will still have a high effusion rate, people won't be able to afford to buy as much biblepay.  If we keep growing the stake amount with the RAC of the network, we do something to give buyers confidence that the coin won't collapse.  Buyers are the ones who truly support the orphans, not miners and crunchers.

Even when the exchanges are out of maintenance, take some time to read the tape when the prices suddenly go up.  Prices go up by surprise because liquidity dried up and people are willing to pay higher and higher prices.  They take out those standing limit offers.  Then the miners start to come in when they realize prices just got higher.  At first, they put out limits on the offer.  When those stop getting hit, they start to get desperate and start hitting the bid, soaking up liquidity the other way.  Then prices come back down.  It would help to have a consistent way to soak up supply and we would engineer higher prices much in the way companies buy back their own stock.  Miners are part of the company.  Miners accumulating bbp as the network grows helps prices to appreciate.

For reference the current masternode lockup has 262 million bpp.  And since the start of masternodes we are consistently 20 or more satoshi higher.  So more lockup should mean higher prices, and more orphans supported.  A win for everybody.


Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.

I don't think this is true. Now, but more as as our group RAC grows, many miners/boincers will have less than 1magnitude. They still need to stake the equivalent of 1 magnitude, let's say 50k. Therefore, the total can be significantly more than 50 million

If that is the case, then staking based on RAC is much more equitable between users.  Having to stake 50,000 bbp for a fraction of a magnitude for a PC that does say 500 RAC, that same user would only have to stake 10,000, which is more equitable for the reward received for smaller users.

Staking based on RAC also makes bbp worth 1/20 of a RAC and biblepay is the compensation you get for doing crunching and using electricity, computers and time.  1/20 of a RAC is actual intrinsic value.  That is something that would actually back biblepay.  And why would you choose to stake bbp instead of crunching boinc on your own?  Because you get compensated in bbp for crunching.
full member
Activity: 364
Merit: 102
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"

Honestly I think either will work, RAC or magnitude. I just like magnitude because it scales with the network size. But either or will do for me.

The simplest way I look at is, Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.  Always, even when supply is 3 Billion.  For RAC our current RAC is 1.3M So if we do 20 BBP per RAC that is 26 million lockup.  If we have a 10 million RAC with x larger supply that is a 200 million lockup.  Woo-hoo! We just engineered ourselves higher prices at a fraction of the cost of a masternode, important especially when masternodes become unaffordable.  It is important to consistently seek some way to keep mopping up supply.  This coin has a lot of supply on the front end.  It will take time for the supply to consolidate.  If bitcoin goes way up, we will still have a high effusion rate, people won't be able to afford to buy as much biblepay.  If we keep growing the stake amount with the RAC of the network, we do something to give buyers confidence that the coin won't collapse.  Buyers are the ones who truly support the orphans, not miners and crunchers.

Even when the exchanges are out of maintenance, take some time to read the tape when the prices suddenly go up.  Prices go up by surprise because liquidity dried up and people are willing to pay higher and higher prices.  They take out those standing limit offers.  Then the miners start to come in when they realize prices just got higher.  At first, they put out limits on the offer.  When those stop getting hit, they start to get desperate and start hitting the bid, soaking up liquidity the other way.  Then prices come back down.  It would help to have a consistent way to soak up supply and we would engineer higher prices much in the way companies buy back their own stock.  Miners are part of the company.  Miners accumulating bbp as the network grows helps prices to appreciate.

For reference the current masternode lockup has 262 million bpp.  And since the start of masternodes we are consistently 20 or more satoshi higher.  So more lockup should mean higher prices, and more orphans supported.  A win for everybody.


"Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million."

I don't think this is true. Now, but more as as our group RAC grows, many miners/boincers will have less than 1magnitude. They still need to stake the equivalent of 1 magnitude, let's say 50k. Therefore, the total can be significantly more than 50 million
full member
Activity: 364
Merit: 102
I liked the idea of 20 per RAC but I'm flexible.  I would be fine with it coming down over time based on the effusion rate, too.  The details can be worked out if it gets voted in.
I think 20/RAC would be a minimum for me.



Can you explain what your talking about? I don't understand.
If we staked with RAC I'd want a Min of 20 bbp per RAC
member
Activity: 157
Merit: 10
I liked the idea of 20 per RAC but I'm flexible.  I would be fine with it coming down over time based on the effusion rate, too.  The details can be worked out if it gets voted in.
I think 20/RAC would be a minimum for me.



Can you explain what your talking about? I don't understand.
newbie
Activity: 180
Merit: 0
Okay, here is the Poll: Staking based on MAG versus Staking based on RAC up for 1 week.

http://forum.biblepay.org/index.php?topic=131.0



Thanks, Tmike!
full member
Activity: 364
Merit: 102
I liked the idea of 20 per RAC but I'm flexible.  I would be fine with it coming down over time based on the effusion rate, too.  The details can be worked out if it gets voted in.
I think 20/RAC would be a minimum for me.

newbie
Activity: 180
Merit: 0
I liked the idea of 20 per RAC but I'm flexible.  I would be fine with it coming down over time based on the effusion rate, too.  The details can be worked out if it gets voted in.
member
Activity: 157
Merit: 10
Thanks, Dave.  I'd like to have a vote to choose between stake based on MAG versus stake based on RAC.

Just start one on the forum! How many BBP are you suggesting per RAC?
newbie
Activity: 180
Merit: 0
Thanks, Dave.  I'd like to have a vote to choose between stake based on MAG versus stake based on RAC.
jr. member
Activity: 405
Merit: 3
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"

Honestly I think either will work, RAC or magnitude. I just like magnitude because it scales with the network size. But either or will do for me.

The simplest way I look at is, Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.  Always, even when supply is 3 Billion.  For RAC our current RAC is 1.3M So if we do 20 BBP per RAC that is 26 million lockup.  If we have a 10 million RAC with x larger supply that is a 200 million lockup.  Woo-hoo! We just engineered ourselves higher prices at a fraction of the cost of a masternode, important especially when masternodes become unaffordable.  It is important to consistently seek some way to keep mopping up supply.  This coin has a lot of supply on the front end.  It will take time for the supply to consolidate.  If bitcoin goes way up, we will still have a high effusion rate, people won't be able to afford to buy as much biblepay.  If we keep growing the stake amount with the RAC of the network, we do something to give buyers confidence that the coin won't collapse.  Buyers are the ones who truly support the orphans, not miners and crunchers.

Even when the exchanges are out of maintenance, take some time to read the tape when the prices suddenly go up.  Prices go up by surprise because liquidity dried up and people are willing to pay higher and higher prices.  They take out those standing limit offers.  Then the miners start to come in when they realize prices just got higher.  At first, they put out limits on the offer.  When those stop getting hit, they start to get desperate and start hitting the bid, soaking up liquidity the other way.  Then prices come back down.  It would help to have a consistent way to soak up supply and we would engineer higher prices much in the way companies buy back their own stock.  Miners are part of the company.  Miners accumulating bbp as the network grows helps prices to appreciate.

For reference the current masternode lockup has 262 million bpp.  And since the start of masternodes we are consistently 20 or more satoshi higher.  So more lockup should mean higher prices, and more orphans supported.  A win for everybody.

Finally someone analyzing this from the economic/trading side. I think you make a very valid and excellent point. On the long run this coin will have to gain value and thus market cap to be taken seriously. This will never happen without generating incentives for people to buy it. The sancs were a very good start to that, as you already explained. Now the goal should definitely be to get miners "hooked" and convince them to hold instead of filling up the ask on every exchange.
Requiring staked amounts proportional to the individual's wealth AND the general supply should guarantee this.



Edit: Apparently we have a new visitor from china: https://boinc.bakerlab.org/rosetta/show_user.php?userid=1988192. However, he has his computers hidden (he's currently on RAC 19k). As I recall it, there was some kind of rule stating that you have to have your machines visible in order to get paid, is this rule still intact?
newbie
Activity: 180
Merit: 0
THE biggest risk in this coin is that BTC shoots up, we are still at our high effusion rate and the miners swamp the coin with supply to get a hold of bitcoin.  Mining BBP then becomes a back door way to mine BTC.  Staking to RAC also helps to take care of that risk.
newbie
Activity: 180
Merit: 0
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"

Honestly I think either will work, RAC or magnitude. I just like magnitude because it scales with the network size. But either or will do for me.

The simplest way I look at is, Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million.  Always, even when supply is 3 Billion.  For RAC our current RAC is 1.3M So if we do 20 BBP per RAC that is 26 million lockup.  If we have a 10 million RAC with x larger supply that is a 200 million lockup.  Woo-hoo! We just engineered ourselves higher prices at a fraction of the cost of a masternode, important especially when masternodes become unaffordable.  It is important to consistently seek some way to keep mopping up supply.  This coin has a lot of supply on the front end.  It will take time for the supply to consolidate.  If bitcoin goes way up, we will still have a high effusion rate, people won't be able to afford to buy as much biblepay.  If we keep growing the stake amount with the RAC of the network, we do something to give buyers confidence that the coin won't collapse.  Buyers are the ones who truly support the orphans, not miners and crunchers.

Even when the exchanges are out of maintenance, take some time to read the tape when the prices suddenly go up.  Prices go up by surprise because liquidity dried up and people are willing to pay higher and higher prices.  They take out those standing limit offers.  Then the miners start to come in when they realize prices just got higher.  At first, they put out limits on the offer.  When those stop getting hit, they start to get desperate and start hitting the bid, soaking up liquidity the other way.  Then prices come back down.  It would help to have a consistent way to soak up supply and we would engineer higher prices much in the way companies buy back their own stock.  Miners are part of the company.  Miners accumulating bbp as the network grows helps prices to appreciate.

For reference the current masternode lockup has 262 million bpp.  And since the start of masternodes we are consistently 20 or more satoshi higher.  So more lockup should mean higher prices, and more orphans supported.  A win for everybody.
full member
Activity: 364
Merit: 102
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"

Honestly I think either will work, RAC or magnitude. I just like magnitude because it scales with the network size. But either or will do for me.
member
Activity: 157
Merit: 10
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110


Hi- wondering if you can help. I've been using Biblepay with its GUI program through Linux Ubuntu, and mining through an account at pool2.biblepay.org. All has been going seamlessly, until today. I upgraded my Biblepay version because last time I logged into my pool2 account it said we have to upgrade to version 1.1.0.1+ in order to keep mining. But now after the upgrade, it no longer syncs, says "no block source available". It also keeps asking me for my wallet password when I load it for "PODC updates" which I have no clue what this means.

Can you please help me resolve this, or point me to a tutorial of sorts?

Thankyou

You can cancel the password prompt, its just for PODC (Cancer mining). 
See this for cancer mining:
http://wiki.biblepay.org/Distributed_Computing_2

So, first please ensure your system time and timezone is correct.  A lot of people cant sync if the time is off by more than 2 minutes....

Then resync.



Yes, validated the system timezone and time is correct. Not resyncing or showing progress. Did I have to change something in my wallet configuration file to go along with the update? Currently it looks like:

addnode=dnsseed.biblepay-explorer.org
addnode=dnsseed.biblepay-explorer.org
gen=1
genproclimit=2
poolport=80
pool=https://pool2.biblepay.org
workerid=****(hidden)

Can you delete the chain and re-sync.

And try these instead:
addnode=node.biblepay.org
addnode=biblepay.inspect.network

Delete the chain?? Do I have to rebuild the entire chain now just because of an upgrade, or is it because of the node change you suggested? Or is it to maintain integrity because of the node change? I'm not sure how to delete the chain, I suppose I just dive into my Biblepay folder and find it there?

Thanks again.

I'm just saying if your in a hurry, it only takes 5 minutes. IF you don't want to try the nodes I posted.
jr. member
Activity: 36
Merit: 10
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110


Hi- wondering if you can help. I've been using Biblepay with its GUI program through Linux Ubuntu, and mining through an account at pool2.biblepay.org. All has been going seamlessly, until today. I upgraded my Biblepay version because last time I logged into my pool2 account it said we have to upgrade to version 1.1.0.1+ in order to keep mining. But now after the upgrade, it no longer syncs, says "no block source available". It also keeps asking me for my wallet password when I load it for "PODC updates" which I have no clue what this means.

Can you please help me resolve this, or point me to a tutorial of sorts?

Thankyou

You can cancel the password prompt, its just for PODC (Cancer mining).  
See this for cancer mining:
http://wiki.biblepay.org/Distributed_Computing_2

So, first please ensure your system time and timezone is correct.  A lot of people cant sync if the time is off by more than 2 minutes....

Then resync.



Yes, validated the system timezone and time is correct. Not resyncing or showing progress. Did I have to change something in my wallet configuration file to go along with the update? Currently it looks like:

addnode=dnsseed.biblepay-explorer.org
addnode=dnsseed.biblepay-explorer.org
gen=1
genproclimit=2
poolport=80
pool=https://pool2.biblepay.org
workerid=****(hidden)

Can you delete the chain and re-sync.

And try these instead:
addnode=node.biblepay.org
addnode=biblepay.inspect.network

Delete the chain?? Do I have to rebuild the entire chain now just because of an upgrade, or is it because of the node change you suggested? Or is it to maintain integrity because of the node change? I'm not sure how to delete the chain, I suppose I just dive into my Biblepay folder and find it there?

Thanks again- just want to make sure I'm following this correctly before I go deleting stuff!
newbie
Activity: 180
Merit: 0
Let's look at this a different way.  Let's say I go to Prestonwood Baptist church, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  They might ask,"Are you buying it?" I'd have to say, "No, I'm just mining the pea-wodding out of it.  It has a limited supply, but so do the other 1550 and increasing other coins available."  They would feel like suckers being taken advantage of.

But! If we have stake based on RAC, and I say to people, "Hey why don't ya'll buy some biblepay that I'm mining.  It will help support orphans."  And they ask,"Are you buying it?"  I have to say, "Yes! For every computer I add that does crunching, I have to either hold or buy biblepay."  (With magnitude based staking, the amount I have to stake should decrease as the network grows: MAGSHARE=MAG/USERBASE as user base expands, my share of the MAG becomes smaller.)  Then they might say, "Oh, it sounds like a good idea if you are buying and holding right alongside me, even though I'm not that interested in crunching."  And I could say, "Yep, go for it!"
member
Activity: 157
Merit: 10
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110


Hi- wondering if you can help. I've been using Biblepay with its GUI program through Linux Ubuntu, and mining through an account at pool2.biblepay.org. All has been going seamlessly, until today. I upgraded my Biblepay version because last time I logged into my pool2 account it said we have to upgrade to version 1.1.0.1+ in order to keep mining. But now after the upgrade, it no longer syncs, says "no block source available". It also keeps asking me for my wallet password when I load it for "PODC updates" which I have no clue what this means.

Can you please help me resolve this, or point me to a tutorial of sorts?

Thankyou

You can cancel the password prompt, its just for PODC (Cancer mining).  
See this for cancer mining:
http://wiki.biblepay.org/Distributed_Computing_2

So, first please ensure your system time and timezone is correct.  A lot of people cant sync if the time is off by more than 2 minutes....

Then resync.



Yes, validated the system timezone and time is correct. Not resyncing or showing progress. Did I have to change something in my wallet configuration file to go along with the update? Currently it looks like:

addnode=dnsseed.biblepay-explorer.org
addnode=dnsseed.biblepay-explorer.org
gen=1
genproclimit=2
poolport=80
pool=https://pool2.biblepay.org
workerid=****(hidden)

Can you delete the chain and re-sync.

And try these instead:
addnode=node.biblepay.org
addnode=biblepay.inspect.network
Jump to: