Author

Topic: BiblePay - New Coin Launch - Official Thread - page 104. (Read 119850 times)

member
Activity: 83
Merit: 11
Dev is so active that I can't keep up with the new versions, as soon as I installed 1.0.2.6 on 10+ computers, 1.0.2.7 showed up. Grin

Edit: I can't connect on 1.0.2.7, debug.log at the end:

Code:
2017-08-31 20:39:27 Loaded 70 addresses from peers.dat  1ms
2017-08-31 20:39:27 dnsseed thread start
2017-08-31 20:39:27 net thread start
2017-08-31 20:39:27 mnbcon thread start
2017-08-31 20:39:27 addcon thread start
2017-08-31 20:39:27 opencon thread start
2017-08-31 20:39:27 msghand thread start
2017-08-31 20:39:27 BibleMiner -- started thread 0.000000
2017-08-31 20:39:27 BibleMiner -- started thread 1.000000
2017-08-31 20:39:27 BibleMiner -- started thread 2.000000
2017-08-31 20:39:28 BibleMiner -- started thread 3.000000
2017-08-31 20:39:28 BibleMiner -- started thread 4.000000
2017-08-31 20:39:28  ** Started 4.000000 BibleMiner threads. ** ^M
2017-08-31 20:39:28 init message: Done loading
2017-08-31 20:39:31 socket recv error Connection reset by peer (104)
2017-08-31 20:39:36 Loading addresses from DNS seeds (could take a while)
2017-08-31 20:39:37 42 addresses found from DNS seeds
2017-08-31 20:39:37 dnsseed thread exit
2017-08-31 20:41:37 socket recv error Connection reset by peer (104)

I just download it for windows 64 and it is still the 1.0.2.6
full member
Activity: 406
Merit: 101
How to safely upgrade wallet? Is it just a case of installing new download?

For a windows box, just download and install, it overwrites what it needs to but keeps most your settings intact.
full member
Activity: 462
Merit: 103
Dev is so active that I can't keep up with the new versions, as soon as I installed 1.0.2.6 on 10+ computers, 1.0.2.7 showed up. Grin

Edit: I can't connect on 1.0.2.7, debug.log at the end:

Code:
2017-08-31 20:39:27 Loaded 70 addresses from peers.dat  1ms
2017-08-31 20:39:27 dnsseed thread start
2017-08-31 20:39:27 net thread start
2017-08-31 20:39:27 mnbcon thread start
2017-08-31 20:39:27 addcon thread start
2017-08-31 20:39:27 opencon thread start
2017-08-31 20:39:27 msghand thread start
2017-08-31 20:39:27 BibleMiner -- started thread 0.000000
2017-08-31 20:39:27 BibleMiner -- started thread 1.000000
2017-08-31 20:39:27 BibleMiner -- started thread 2.000000
2017-08-31 20:39:28 BibleMiner -- started thread 3.000000
2017-08-31 20:39:28 BibleMiner -- started thread 4.000000
2017-08-31 20:39:28  ** Started 4.000000 BibleMiner threads. ** ^M
2017-08-31 20:39:28 init message: Done loading
2017-08-31 20:39:31 socket recv error Connection reset by peer (104)
2017-08-31 20:39:36 Loading addresses from DNS seeds (could take a while)
2017-08-31 20:39:37 42 addresses found from DNS seeds
2017-08-31 20:39:37 dnsseed thread exit
2017-08-31 20:41:37 socket recv error Connection reset by peer (104)

Edit 2: This seems to be unrelated to the version upgrade, something else broke at my local setup. It's like I'm banned, because I can reach the main node by pinging.

Edit 3: Solved it by running this command:

Code:
addnode "97.99.69.33:40000" "onetry"

In the conf file I had addnode=node.biblepay.org, so now I don't know if the above command would have also worked with the DNS or just with the IP.
newbie
Activity: 9
Merit: 0
BiblePay Non-Mandatory Upgrade Available
Version 1.0.2.6:


- Combine communications from all threads to one packet
- Fix inconsistent switching between Pool health down, and solo mining (into 5 minute blocks)
- Fix inconsistent POOL_DOWN messages in miner


Pool Miners: Please upgrade to alleviate load on the pool.



How to safely upgrade wallet? Is it just a case of installing new download?
full member
Activity: 159
Merit: 100

- Fix inconsistent switching between Pool health down, and solo mining (into 5 minute blocks)

Finally, thank you ! All we need now is a stable pool  Grin
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
BiblePay Non-Mandatory Upgrade Available
Version 1.0.2.6:


- Combine communications from all threads to one packet
- Fix inconsistent switching between Pool health down, and solo mining (into 5 minute blocks)
- Fix inconsistent POOL_DOWN messages in miner


Pool Miners: Please upgrade to alleviate load on the pool.

full member
Activity: 406
Merit: 101
Quote
Future Feature:
Pay to Preach, in wallet interactive prayer rooms.
Does it mean people are offered to pay to be the preacher? It would be nice to know more your plans about this feature, sounds interesting but also hard to imagine demand for such feature. My first though was confession rooms, which may benefit more from anonymity.

I think there could be a lot of versatility in several of the future features.  Pay to Preach I took as for a set fee in BBP, you'd be given "x" time to preach.  How that would work precisely (text, audio, video) I doubt is fully defined, nor where the fee would go.  However, it could be as you read it, where an interested party would be allowed to preach and then paid a reward.  Although I'm dubious how that would work but it's basically where Musiccoin is going with their new roadmap.
member
Activity: 61
Merit: 10
Quote
Future Feature:
Pay to Preach, in wallet interactive prayer rooms.
Does it mean people are offered to pay to be the preacher? It would be nice to know more your plans about this feature, sounds interesting but also hard to imagine demand for such feature. My first though was confession rooms, which may benefit more from anonymity.
full member
Activity: 406
Merit: 101
As far as block 7000, Ive been working with a couple members on their ideas of us 'raising the bar' and current 'risks'.  The primary risk being mitigated in f7000 is preventing the ability to farm out x11 hashes to GPUs.  The other feature in f7000, raising the bar, is requiring the bible hash to emit either a txid, biblepay address, or blockhash at the end of the biblehash chained verses.  We believe this raises the bar so high, no one would make an attempt to copy the bible, the logic, and the full node core into an ASIC or GPU, and in addition, requires the full node to arrive at the solution. 

This means that at block 7000, the only people that should be able to mine this coin are full nodes who must be online to arrive at each block solution.  The hashing itself will be slower, because each hash will actually be composed of two biblehashes plus the tx lookup.

More can be found here in the testing thread:
https://bitcointalk.org/index.php?topic=2070177.40


As far as block 7000 goes, I would suggest another improvement.  Would it be any significant overhead to change the Orphan Fund reward to 10% of each block found (and likewise, when Sanctuaries hit, do the same for them) as opposed to an entire block 1 in 10.  This would reduce the need for the system to scale the difficulty for the "special" blocks which I would think was a programming inconvenience.  Then all blocks are equal.  They all maintain a similar difficulty, and they all grant the same reward.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords


Thanks for your efforts on the pool  Cheesy  I have seen you mentioned block 7000 twice. Maybe I over look the discussion, and I also did not find any clue from OP, may I know what will happen on block 7000?


As far as block 7000, Ive been working with a couple members on their ideas of us 'raising the bar' and current 'risks'.  The primary risk being mitigated in f7000 is preventing the ability to farm out x11 hashes to GPUs.  The other feature in f7000, raising the bar, is requiring the bible hash to emit either a txid, biblepay address, or blockhash at the end of the biblehash chained verses.  We believe this raises the bar so high, no one would make an attempt to copy the bible, the logic, and the full node core into an ASIC or GPU, and in addition, requires the full node to arrive at the solution. 

This means that at block 7000, the only people that should be able to mine this coin are full nodes who must be online to arrive at each block solution.  The hashing itself will be slower, because each hash will actually be composed of two biblehashes plus the tx lookup.

More can be found here in the testing thread:
https://bitcointalk.org/index.php?topic=2070177.40



So, that's mean there is no way to mine biblepay with miner like cpuminer (I was actually waiting for someone to add PoB algorithm into cpuminer) in future. Full node is required in order to mine this coin, like what we do it currently by using biblepay wallet to mine. Am I right?

Correct- If someone were to make it work with cpuminer, it would go against what the vision is- because then you could have a botnet of blackboxes, generating heat, and not doing anything useful.  The vision is to only allow the useful nodes to partake in the subsidies.

hero member
Activity: 714
Merit: 500


Thanks for your efforts on the pool  Cheesy  I have seen you mentioned block 7000 twice. Maybe I over look the discussion, and I also did not find any clue from OP, may I know what will happen on block 7000?


As far as block 7000, Ive been working with a couple members on their ideas of us 'raising the bar' and current 'risks'.  The primary risk being mitigated in f7000 is preventing the ability to farm out x11 hashes to GPUs.  The other feature in f7000, raising the bar, is requiring the bible hash to emit either a txid, biblepay address, or blockhash at the end of the biblehash chained verses.  We believe this raises the bar so high, no one would make an attempt to copy the bible, the logic, and the full node core into an ASIC or GPU, and in addition, requires the full node to arrive at the solution. 

This means that at block 7000, the only people that should be able to mine this coin are full nodes who must be online to arrive at each block solution.  The hashing itself will be slower, because each hash will actually be composed of two biblehashes plus the tx lookup.

More can be found here in the testing thread:
https://bitcointalk.org/index.php?topic=2070177.40



So, that's mean there is no way to mine biblepay with miner like cpuminer (I was actually waiting for someone to add PoB algorithm into cpuminer) in future. Full node is required in order to mine this coin, like what we do it currently by using biblepay wallet to mine. Am I right?
full member
Activity: 126
Merit: 100
I dont care of solo miners. I mine on pool. Pool get coins and all my my work is wasted cuz i wasnt minin i this stupid 20 mins when block was found.
That only i think its unfair and stupid?
And today a get many crashes(yesterday 0) of wallet so mining is totaly waste of time and energy..

It's standard practice for pools to only reward miners for blocks found by the pool. After all, if the pool doesn't find the block then there's no reward to be shared in the first place.

The alternative you seem to be asking for is a direct pay-per-share system, which isn't used so often and generally involves lower payouts over time to offset the risk of the pool going bankrupt due to a bad streak of not finding blocks. That wouldn't even work on a new coin like BBP where a single high output miner dropping out of the pool or starting up solo mining could significantly disrupt the probability of the pool mining a block. You'd also need a very accurate method of determining the pool and network hashrates so you can calculate the share value, and I think there's still an issue with getting an accurate network hashrate right now unless it's been solved in a recent release.
But pool pay when you mine good block, you dont get any reward to "help" pool to ge to this block and ofc reward should be from first found block.
I think its importatnt when pool find block no so often...
member
Activity: 70
Merit: 10
I dont care of solo miners. I mine on pool. Pool get coins and all my my work is wasted cuz i wasnt minin i this stupid 20 mins when block was found.
That only i think its unfair and stupid?
And today a get many crashes(yesterday 0) of wallet so mining is totaly waste of time and energy..

It's standard practice for pools to only reward miners for blocks found by the pool. After all, if the pool doesn't find the block then there's no reward to be shared in the first place.

The alternative you seem to be asking for is a direct pay-per-share system, which isn't used so often and generally involves lower payouts over time to offset the risk of the pool going bankrupt due to a bad streak of not finding blocks. That wouldn't even work on a new coin like BBP where a single high output miner dropping out of the pool or starting up solo mining could significantly disrupt the probability of the pool mining a block. You'd also need a very accurate method of determining the pool and network hashrates so you can calculate the share value, and I think there's still an issue with getting an accurate network hashrate right now unless it's been solved in a recent release.
full member
Activity: 126
Merit: 100
I think oliwer21 was referring to the tithe blocks which don't bring rewards? Either way, it's not just you, nobody got anything in the last X hours because of the pool difficulties, otherwise that would not be the case, of course you get paid per share contributed, but the pool didn't find any blocks for a long time. Don't worry, it will be resolved soon, we have a great dev.
Youre rigt. I dont expect ill get reward for block 5455 cuz i wast minning on blocks betwen 5444 and 5455. But i was mining betwen 5388 and 5444 with shares 15-17...
But im not even on block distribution list of 5444 block.
Oliwer, there are a lot of dynamics here.

One, we have over 750 solo miners out there (I base that on yesterdays high of 750 connections to my external node).  Only about 200 pool users hit the pool simultaneously (although granted, we have over 1000 connections, since multiple threads connect per worker), but anyway let me move on.
The pool is only receiving 20% of the traffic.  It is very possible sometimes the pool will only solve a few blocks in a half a day due to random difficulty and luck.

On the tithe blocks, to make this system fair for everyone, the difficulty is lowered to a miniscule amount on tithe blocks. So those blocks do fly by without much work from the miners.

I think in our case, there are solo miners out there that are looking at the forward value of this coin.  We will find out a lot more when we hit block 7000, as they will all be forced to upgrade at the same time and hopefully we will know more about who these miners are.

I do have an idea on the performance of the pool but this is getting redicules (IE being attacked already, being such a new pool).  I'm thinking we enhance the protocol to handle an unlimited amount of threads per connection, and make the threads wait and speak back to the pool as a single unit.  More on that later.  That will have to be next as Im already deep into the next feature, but seems like something valuable we can do.





I dont care of solo miners. I mine on pool. Pool get coins and all my my work is wasted cuz i wasnt minin i this stupid 20 mins when block was found.
That only i think its unfair and stupid?

If you dont have the anointing of patience this coin isnt for you.  Were not about greed here.
I'm not greedy, but i think it's importatnt rule, that you get reward only when you mine good block on pool. So better dont mine laderboard have few minner because chance to fond block is smaller. Especialy when pool have often problems.
And i think that this rule should be written on main site of pool?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords


Thanks for your efforts on the pool  Cheesy  I have seen you mentioned block 7000 twice. Maybe I over look the discussion, and I also did not find any clue from OP, may I know what will happen on block 7000?


As far as block 7000, Ive been working with a couple members on their ideas of us 'raising the bar' and current 'risks'.  The primary risk being mitigated in f7000 is preventing the ability to farm out x11 hashes to GPUs.  The other feature in f7000, raising the bar, is requiring the bible hash to emit either a txid, biblepay address, or blockhash at the end of the biblehash chained verses.  We believe this raises the bar so high, no one would make an attempt to copy the bible, the logic, and the full node core into an ASIC or GPU, and in addition, requires the full node to arrive at the solution. 

This means that at block 7000, the only people that should be able to mine this coin are full nodes who must be online to arrive at each block solution.  The hashing itself will be slower, because each hash will actually be composed of two biblehashes plus the tx lookup.

More can be found here in the testing thread:
https://bitcointalk.org/index.php?topic=2070177.40

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I think oliwer21 was referring to the tithe blocks which don't bring rewards? Either way, it's not just you, nobody got anything in the last X hours because of the pool difficulties, otherwise that would not be the case, of course you get paid per share contributed, but the pool didn't find any blocks for a long time. Don't worry, it will be resolved soon, we have a great dev.
Youre rigt. I dont expect ill get reward for block 5455 cuz i wast minning on blocks betwen 5444 and 5455. But i was mining betwen 5388 and 5444 with shares 15-17...
But im not even on block distribution list of 5444 block.
Oliwer, there are a lot of dynamics here.

One, we have over 750 solo miners out there (I base that on yesterdays high of 750 connections to my external node).  Only about 200 pool users hit the pool simultaneously (although granted, we have over 1000 connections, since multiple threads connect per worker), but anyway let me move on.
The pool is only receiving 20% of the traffic.  It is very possible sometimes the pool will only solve a few blocks in a half a day due to random difficulty and luck.

On the tithe blocks, to make this system fair for everyone, the difficulty is lowered to a miniscule amount on tithe blocks. So those blocks do fly by without much work from the miners.

I think in our case, there are solo miners out there that are looking at the forward value of this coin.  We will find out a lot more when we hit block 7000, as they will all be forced to upgrade at the same time and hopefully we will know more about who these miners are.

I do have an idea on the performance of the pool but this is getting redicules (IE being attacked already, being such a new pool).  I'm thinking we enhance the protocol to handle an unlimited amount of threads per connection, and make the threads wait and speak back to the pool as a single unit.  More on that later.  That will have to be next as Im already deep into the next feature, but seems like something valuable we can do.





I dont care of solo miners. I mine on pool. Pool get coins and all my my work is wasted cuz i wasnt minin i this stupid 20 mins when block was found.
That only i think its unfair and stupid?

If you dont have the anointing of patience this coin isnt for you.  Were not about greed here.
full member
Activity: 126
Merit: 100
I think oliwer21 was referring to the tithe blocks which don't bring rewards? Either way, it's not just you, nobody got anything in the last X hours because of the pool difficulties, otherwise that would not be the case, of course you get paid per share contributed, but the pool didn't find any blocks for a long time. Don't worry, it will be resolved soon, we have a great dev.
Youre rigt. I dont expect ill get reward for block 5455 cuz i wast minning on blocks betwen 5444 and 5455. But i was mining betwen 5388 and 5444 with shares 15-17...
But im not even on block distribution list of 5444 block.
Oliwer, there are a lot of dynamics here.

One, we have over 750 solo miners out there (I base that on yesterdays high of 750 connections to my external node).  Only about 200 pool users hit the pool simultaneously (although granted, we have over 1000 connections, since multiple threads connect per worker), but anyway let me move on.
The pool is only receiving 20% of the traffic.  It is very possible sometimes the pool will only solve a few blocks in a half a day due to random difficulty and luck.

On the tithe blocks, to make this system fair for everyone, the difficulty is lowered to a miniscule amount on tithe blocks. So those blocks do fly by without much work from the miners.

I think in our case, there are solo miners out there that are looking at the forward value of this coin.  We will find out a lot more when we hit block 7000, as they will all be forced to upgrade at the same time and hopefully we will know more about who these miners are.

I do have an idea on the performance of the pool but this is getting redicules (IE being attacked already, being such a new pool).  I'm thinking we enhance the protocol to handle an unlimited amount of threads per connection, and make the threads wait and speak back to the pool as a single unit.  More on that later.  That will have to be next as Im already deep into the next feature, but seems like something valuable we can do.





I dont care of solo miners. I mine on pool. Pool get coins and all my my work is wasted cuz i wasnt minin i this stupid 20 mins when block was found.
That only i think its unfair and stupid?
And today a get many crashes(yesterday 0) of wallet so mining is totaly waste of time and energy..
hero member
Activity: 714
Merit: 500
I think oliwer21 was referring to the tithe blocks which don't bring rewards? Either way, it's not just you, nobody got anything in the last X hours because of the pool difficulties, otherwise that would not be the case, of course you get paid per share contributed, but the pool didn't find any blocks for a long time. Don't worry, it will be resolved soon, we have a great dev.
Youre rigt. I dont expect ill get reward for block 5455 cuz i wast minning on blocks betwen 5444 and 5455. But i was mining betwen 5388 and 5444 with shares 15-17...
But im not even on block distribution list of 5444 block.
Oliwer, there are a lot of dynamics here.

One, we have over 750 solo miners out there (I base that on yesterdays high of 750 connections to my external node).  Only about 200 pool users hit the pool simultaneously (although granted, we have over 1000 connections, since multiple threads connect per worker), but anyway let me move on.
The pool is only receiving 20% of the traffic.  It is very possible sometimes the pool will only solve a few blocks in a half a day due to random difficulty and luck.

On the tithe blocks, to make this system fair for everyone, the difficulty is lowered to a miniscule amount on tithe blocks. So those blocks do fly by without much work from the miners.

I think in our case, there are solo miners out there that are looking at the forward value of this coin.  We will find out a lot more when we hit block 7000, as they will all be forced to upgrade at the same time and hopefully we will know more about who these miners are.

I do have an idea on the performance of the pool but this is getting redicules (IE being attacked already, being such a new pool).  I'm thinking we enhance the protocol to handle an unlimited amount of threads per connection, and make the threads wait and speak back to the pool as a single unit.  More on that later.  That will have to be next as Im already deep into the next feature, but seems like something valuable we can do.






Thanks for your efforts on the pool  Cheesy  I have seen you mentioned block 7000 twice. Maybe I over look the discussion, and I also did not find any clue from OP, may I know what will happen on block 7000?
full member
Activity: 462
Merit: 103
Hmm, this was discussed before but I can't remember if the pool will only count you if you're on the leaderboard at the time of a block find. Even though that's not so logical, it seems to be your case. But that would allow for pool hopping etc.

You do have to be on the leaderboard to be paid in the block distribution when a block is solved.
But, to combat pool hopping there are rounds, and in each round the system decays your HPS2 based on the shares submitted.
Thats why if you unplug your cable for a while in the current round, your HPS2 starts diminishing slowly.

Thanks for clarifying. So, does that mean if a miner stops pool mining now and the pool finds a block 5 minutes later, they would still be credited, only a bit less? And if the pool finds the next block after some longer time X, then they will not be credited anymore. Also, what if the pool finds two blocks in 5 minutes after the miner stopped, will they still get credited for both blocks?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Hmm, this was discussed before but I can't remember if the pool will only count you if you're on the leaderboard at the time of a block find. Even though that's not so logical, it seems to be your case. But that would allow for pool hopping etc.

You do have to be on the leaderboard to be paid in the block distribution when a block is solved.
But, to combat pool hopping there are rounds, and in each round the system decays your HPS2 based on the shares submitted.
Thats why if you unplug your cable for a while in the current round, your HPS2 starts diminishing slowly.

Jump to: