Author

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

member
Activity: 98
Merit: 11
You should offer Bounties for that work. I could find people to do it though, you can also use Craigslist since BBP is actually worth money, and that would help it spread also.
Like 500 BBP for X, or 100,000 BBP for X.

Sure, but with a bounty Id be setting the price when I dont know how much the work is worth,
so ideally Id like someone to quote me how many hours of work and their pay rate, and if paying up front Id like to see proof of previous work, real name, etc,
otherwise Id pay half up front and half after its finished, or pay after the fact, any way works,
but in general I'm against setting the price myself, since I dont know the value of the work.

BiblePay has a 2.5% PR and 2.5% P2P budget, so there are a lot of coins that can go towards marketing/advertising,
and I would most definitely create a proposal for this work, but Im willing to take on the risk myself of my own coins to get the ball rolling.
http://wiki.biblepay.org/Create_Sanctuary_2#SUBMIT_PROPOSAL

I am going to hook you up with a Professional Print Shop in Texas. They can make shirts and everything, can you PM me your email? They have done stuff from Leased Retail Space Churches, to every Best Buy store in the Country (Including Hawaii and Alaska, lol) at one time.
full member
Activity: 442
Merit: 100
Is there some issue at ccex , can I buy some coins there?
I see the wallet in maintanace, so is it ok to buy coins from there?
jr. member
Activity: 405
Merit: 3


Hi Dave,

Its just not true that we only care about precious masternodes.

Here is the way I view the priorities right now just so you know:  I want to ensure we are ready for block 24600, so we can pay our orphans. 

Next, I want to maintain production support levels.  That includes any critical errors with 1075.  And finally, I place a very low priority level personally on any "hash speed discussions".  So maybe thats the point of contention.  We only have enough resources to talk about the prod support and the critical errors and not about peoples mining speed, unless its an inconsistency in the pool that affects everyone.

Of course we have time to talk about how competetive mining works.

But first:
So, Im not aware of a critical bug in 1075, and have not received a log.  Can someone please give us a log so we can see what stopped the node in 1075??

There is no way to even look at a problem without a log.



Thank you for your explanations (also in your other posts about the competitive mining. Indeed that makes sense. I have copied the last lines from the debug.log, where the error occurs (wasn't really sure where to start...):
Code:
2018-01-04 13:15:15 Resetting mining tithe 259.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:28 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:39 Resetting mining tithe 260.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:15:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:16:41 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:17:37 Resetting mining tithe 261.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:18 Resetting mining tithe 262.000000CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:18:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063277955.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:48 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:51 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:19:56 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:12 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:27 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:20:57 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:17 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:21:45 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:38 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:22:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:23:46 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:24:42 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:08 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:25:11 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:05 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:33 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:26:52 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:27:34 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:28:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:06 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:29:36 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:24 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:30:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:31:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:10 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:29 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:32:50 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:33:55 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:22 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:37 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:34:53 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:35:49 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:16 ERROR: Write: Failed to open file /home/david/.biblepaycore/peers.dat.add3
2018-01-04 13:36:18 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:36:23 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:37:47 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:25 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:38:32 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:00 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:26 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:39:58 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:09 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:41:44 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 ERROR: WriteBlockToDisk: OpenBlockFile failed
2018-01-04 13:42:14 *** Failed to write block
2018-01-04 13:42:14 Error: Error: A fatal internal error occurred, see debug.log for details
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/blk00000.dat
2018-01-04 13:42:14 Unable to open file /home/david/.biblepaycore/blocks/rev00000.dat
2018-01-04 13:42:14 tor: Thread interrupt
2018-01-04 13:42:14 torcontrol thread exit
2018-01-04 13:42:14 opencon thread interrupt
2018-01-04 13:42:14 addcon thread interrupt
2018-01-04 13:42:14 mnbcon thread interrupt
2018-01-04 13:42:14 scheduler thread interrupt
2018-01-04 13:42:14 net thread interrupt
2018-01-04 13:42:16 ProcessNewBlock : ACCEPTED
2018-01-04 13:42:16 msghand thread interrupt
2018-01-04 13:42:16 PrepareShutdown: In progress...
2018-01-04 13:42:16 StopNode()
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Verifying mncache.dat format...
2018-01-04 13:42:16 Loaded info from mncache.dat  6ms
2018-01-04 13:42:16      Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2149
2018-01-04 13:42:16 Writting info to mncache.dat...
2018-01-04 13:42:16 Written info to mncache.dat  6ms
2018-01-04 13:42:16      Masternodes: 84, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 84, nDsqCount: 2856
2018-01-04 13:42:16 mncache.dat dump finished  12ms
2018-01-04 13:42:16 Verifying mnpayments.dat format...
2018-01-04 13:42:16 Loaded info from mnpayments.dat  135ms
2018-01-04 13:42:16      Votes: 24615, Blocks: 2564
2018-01-04 13:42:16 Writting info to mnpayments.dat...
2018-01-04 13:42:16 CMasternodePayments::FillBlockPayee -- Masternode payment 660063284675.000000 to BGW1hEmxB48ydQpmJk5cpPoMrdCxWocbBs
2018-01-04 13:42:16 Written info to mnpayments.dat  121ms
2018-01-04 13:42:16      Votes: 25214, Blocks: 2624
2018-01-04 13:42:16 mnpayments.dat dump finished  259ms
2018-01-04 13:42:16 Verifying governance.dat format...
2018-01-04 13:42:16 Loaded info from governance.dat  16ms
2018-01-04 13:42:16      Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 24), Votes: 0
2018-01-04 13:42:16 Writting info to governance.dat...
2018-01-04 13:42:16 Written info to governance.dat  5ms
2018-01-04 13:42:16      Governance Objects: 22 (Proposals: 19, Triggers: 2, Watchdogs: 1/1, Other: 0; Seen: 26), Votes: 847
2018-01-04 13:42:16 governance.dat dump finished  21ms
2018-01-04 13:42:16 Verifying netfulfilled.dat format...
2018-01-04 13:42:16 Loaded info from netfulfilled.dat  0ms
2018-01-04 13:42:16      Nodes with fulfilled requests: 10
2018-01-04 13:42:16 Writting info to netfulfilled.dat...
2018-01-04 13:42:16 Written info to netfulfilled.dat  0ms
2018-01-04 13:42:16      Nodes with fulfilled requests: 9
2018-01-04 13:42:16 netfulfilled.dat dump finished  0ms
2018-01-04 13:42:16
BiblepayMiner -- terminated
2018-01-04 13:42:16 Shutdown: done

Hope this helps. Wink
full member
Activity: 1260
Merit: 115
You should offer Bounties for that work. I could find people to do it though, you can also use Craigslist since BBP is actually worth money, and that would help it spread also.
Like 500 BBP for X, or 100,000 BBP for X.

Sure, but with a bounty Id be setting the price when I dont know how much the work is worth,
so ideally Id like someone to quote me how many hours of work and their pay rate, and if paying up front Id like to see proof of previous work, real name, etc,
otherwise Id pay half up front and half after its finished, or pay after the fact, any way works,
but in general I'm against setting the price myself, since I dont know the value of the work.

BiblePay has a 2.5% PR and 2.5% P2P budget, so there are a lot of coins that can go towards marketing/advertising,
and I would most definitely create a proposal for this work, but Im willing to take on the risk myself of my own coins to get the ball rolling.
http://wiki.biblepay.org/Create_Sanctuary_2#SUBMIT_PROPOSAL
full member
Activity: 1260
Merit: 115
member
Activity: 98
Merit: 11
You should offer Bounties for that work. I could find people to do it though, you can also use Craigslist since BBP is actually worth money, and that would help it spread also.

Like 500 BBP for X, or 100,000 BBP for X.
member
Activity: 98
Merit: 11
Is there a BiblePay YouTube video yet? I would share it.
full member
Activity: 1260
Merit: 115
Looking for GRAPHIC DESIGN & HTML/CSS Skills for BiblePay Bitcointalk Ad Banner, Will reward work in BBP coins!

Ad Info: https://bitcointalksearch.org/topic/advertise-on-this-forum-round-232-2664093
Ad Examples: https://bitcointalk.org/adrotate.php?adinfo
Ad Test Page: https://bitcointalk.org/ad_test.html
BiblePay Logo Design files: https://www.reddit.com/r/BiblePay/comments/7asnaa/new_coin_logo_zip_of_images/
BiblePay Colors: Red (Maroon) #971b20, Yellow (Gold) #e2ae24, White #ffffff
Reddit Thread: https://www.reddit.com/r/BiblePay/comments/7ndg5g/bitcointalk_banner_ad_need_htmlcss_skills/

Anyone have feedback on what should be on the banner? What text should say?
Obviously we would want the logo on there and the BiblePay name.
What should the banner link to? the main website? Should we have multiple links?

Would it be better to use a freelance site to find someone for this?

(Note: Ill be looking for potential help with Reddit ad banner in the near future as well)
member
Activity: 98
Merit: 11
You will see the price of Bible Pay go up this week.
member
Activity: 104
Merit: 10
Christians will like knowing this, but when Christians say "the Flood Myth is in every Culture", it isn't in every Culture, but it is in a lot of Cultures, and it was in Native American (Not just Native US Native Americans) Mythology. There is an Incan God called Viracocha and a Colombian God called Bochica. These were people who were said to have come and taught the Native Americans various different Crafts, and Stone Working, and other arts. It is most likely that this was a Person who came on a Boat. I believe the Legend says he came from the water on a Snake or a Feathered Snake, and then taught everyone, and then left by Walking away on the Water; he is also pictured with Tears to represent the Rain and Lightning Bolts in his Hands. This is likely a story about someone who came from Asia or Africa; maybe even a whole Tribe that just became part of America and a story was passed down. Thor Hyderdhal proved that you do not need a Hull on a Boat to get across the Ocean.
https://en.wikipedia.org/wiki/Thor_Heyerdahl

And also similarly to the Christian God, there is a Mountain God, called Apu (Lord), and the storm God called Huracan (Heart of the Sky) the source for the word Hurricane. Looking at these Gods gives you a better Perspective on the Mountain, Desert, Sea God of the Middle East. And they have a Flood Myth, and in their Flood Myth God created the Earth 3 times. Once, he created people from Stones, Giants, and they displeased him so he Flooded the Earth, then he made Humans and they displeased him, so he Flooded the Earth, and now we are in the 3rd phase supposedly after whatever the Native American name for Noah is. So the Flood Myth exists in very different Places, and the same Religion exists in very different iterations. Because really everything mentioned here is Jewish, except for Viracocha who is like their Jesus.

And this is kind of strange, but Corn supposedly comes from America, but there are examples where Jewish people used Corn Motifs on their Spears. But supposedly they didn't know about Corn.


This is what happens when you veer away from the Lord, Jesus Christ:

http://www.dailymail.co.uk/femail/article-5228857/A-10-year-old-drag-queen-founded-drag-club-kids.html

I've seen too many NDEs where Jesus gave an Indian or Muslim a second chance by showing him Hell, and it becomes clear these principalities exist where some of the "gods" you refer to are actually running a principality in hell.  If you hang around these spirits long enough, you will eventually find they backstab you.  The same ones you think Love you are going to turn on you some day, because they dont care about your soul.  They want their daddy to get it so they will have an easier night with less torture for themselves.

John Ramirez talks about this, hes done it all:

https://www.youtube.com/watch?v=VEmE-cQEX3Y




I don't believe there is such thing as a Hell. We burn our Dead, to send them as a message to the Gods, and they are returned.

Similar to when you say to a kid "You look so much like your grandma" or "You look so much like your Dad". Or when Corn uses Dead Fish to Grow. Or how all the Water we are drinking has been through Dinosaur Urinary tracts, and Animal Urinary tracts over and over. We are brought back as well, maybe not the same form, but our energy is reused.
Looks like the author intends to make a big, friends on board, please sit tight, hold your coin
member
Activity: 98
Merit: 11
And btw, I am not against you guys. I am going to get more people to start mining Bible Pay and I will get the price up for you guys. And I will share it with the Religious Debate Community soon. I know a lot of people in the "Debate Circuit" as they call it. And more than just Christians who use the Bible.
member
Activity: 98
Merit: 11
Christians will like knowing this, but when Christians say "the Flood Myth is in every Culture", it isn't in every Culture, but it is in a lot of Cultures, and it was in Native American (Not just Native US Native Americans) Mythology. There is an Incan God called Viracocha and a Colombian God called Bochica. These were people who were said to have come and taught the Native Americans various different Crafts, and Stone Working, and other arts. It is most likely that this was a Person who came on a Boat. I believe the Legend says he came from the water on a Snake or a Feathered Snake, and then taught everyone, and then left by Walking away on the Water; he is also pictured with Tears to represent the Rain and Lightning Bolts in his Hands. This is likely a story about someone who came from Asia or Africa; maybe even a whole Tribe that just became part of America and a story was passed down. Thor Hyderdhal proved that you do not need a Hull on a Boat to get across the Ocean.
https://en.wikipedia.org/wiki/Thor_Heyerdahl

And also similarly to the Christian God, there is a Mountain God, called Apu (Lord), and the storm God called Huracan (Heart of the Sky) the source for the word Hurricane. Looking at these Gods gives you a better Perspective on the Mountain, Desert, Sea God of the Middle East. And they have a Flood Myth, and in their Flood Myth God created the Earth 3 times. Once, he created people from Stones, Giants, and they displeased him so he Flooded the Earth, then he made Humans and they displeased him, so he Flooded the Earth, and now we are in the 3rd phase supposedly after whatever the Native American name for Noah is. So the Flood Myth exists in very different Places, and the same Religion exists in very different iterations. Because really everything mentioned here is Jewish, except for Viracocha who is like their Jesus.

And this is kind of strange, but Corn supposedly comes from America, but there are examples where Jewish people used Corn Motifs on their Spears. But supposedly they didn't know about Corn.


This is what happens when you veer away from the Lord, Jesus Christ:

http://www.dailymail.co.uk/femail/article-5228857/A-10-year-old-drag-queen-founded-drag-club-kids.html

I've seen too many NDEs where Jesus gave an Indian or Muslim a second chance by showing him Hell, and it becomes clear these principalities exist where some of the "gods" you refer to are actually running a principality in hell.  If you hang around these spirits long enough, you will eventually find they backstab you.  The same ones you think Love you are going to turn on you some day, because they dont care about your soul.  They want their daddy to get it so they will have an easier night with less torture for themselves.

John Ramirez talks about this, hes done it all:

https://www.youtube.com/watch?v=VEmE-cQEX3Y




I don't believe there is such thing as a Hell. We burn our Dead, to send them as a message to the Gods, and they are returned.

Similar to when you say to a kid "You look so much like your grandma" or "You look so much like your Dad". Or when Corn uses Dead Fish to Grow. Or how all the Water we are drinking has been through Dinosaur Urinary tracts, and Animal Urinary tracts over and over. We are brought back as well, maybe not the same form, but our energy is reused.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
so what these numbers means?
  "hashcounter": 23921555,
  "competetive_mining": true,
  "competetivemining_hash_counter": 22418835,
  "global_competetive_mining_tithe": 89,
  "competetive_mining_ratio": 0,
  "pooledtx": 0,

at least hashcounter vs competetivemining hash counter?
It means since started, you hashed 23.9MM hashes, but only 22.4MM were good, therefore competetive mining kicked in and tithed 89 satoshis (total over the period) to fill in the difference.  Its a small effect, but could be big on a very fast processor.  The more threads you run the smaller the effect.

If you ran this on a fast processor with only 2 threads, the satoshis would increase quickly.

The (competetive tithe amount) does reset to 0 after the block switches.
(The global_competetive value does not, it just stays to show you something happened).


EDIT: competetive_mining_ratio is the amount of edge you achieved running the competetive feature as a %, but since its smaller than .01% it appears as zero.
newbie
Activity: 491
Merit: 0
so what these numbers means?
  "hashcounter": 23921555,
  "competetive_mining": true,
  "competetivemining_hash_counter": 22418835,
  "global_competetive_mining_tithe": 89,
  "competetive_mining_ratio": 0,
  "pooledtx": 0,

at least hashcounter vs competetivemining hash counter?
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I created a new dedicated forum for mining issues, more specifically for HashPs discussions, troubleshooting, General Mining, etc.


Would someone like to volunteer to moderate this forum?  You could moderate and help solve technical issues with hashps.


And finally, Alex suggested an awesome idea, that we maintain a spreadsheet with a reference to OS, processor type and hashps.
Whoever the mod is, could you please create a global sheet also?

http://forum.biblepay.org/index.php?board=6.0

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
The competetive mining feature, 1075, and 1075 in general should not be lowering hash PS, as the entire algo is still the same, and the feature is a small enhancement to the miner.

What the feature does is starts adding a tithe, destined to the foundation, of 1 satoshi when you run out of mining nonces.

This usually only happens on fast processors.

Biblepay requires a low nonce to prevent us from being ported to an asic or gpu.

To give you an example of the current maximum nonce in the current block, type exec pinfo from the RPC.
The 'pinfo' output is the max nonce biblepay allows for the next block to be solved.

If your machine was so fast, say running 20 threads that its nonces were greater than the exec pinfo level, competetive mining would kick in and add a foundation tithe of 1,2,3,4++ satoshi (once every 30 seconds or so) to keep you hashing at full speed.

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
1.0.7.5 version seem have problem.

It is the second times occurred , I am re-indexing again.
I worry it will happen again....



Hello all!
I have been following this thread and this project for several weeks now and I am really excited to see the hard work and dedication going into developing all of this. However the last couple of days it seems to me that the only concern you have regarding troubleshooting is with the MN owners, not the miners.
Several people reported the above mentioned error and I also experience it regularly since updating to 1.0.7.5 on different machines, different networks, even different cities across Germany. So the error is definitely not on my side, because also the configurations on these machines differ from each other and each and every one gets this error after a few hours of mining.
However, no one has offered any permanent solution or even explained where this is coming from. I think the only reason so few people have this problem is because judging by the connected peers on my systems most people are still on the working version 1.0.7.1.

So when will this annoying problem be fixed? Another question you never answered was how this new "competitive mining" feature really works. Right now it seems to me that all the update did was giving an even bigger malus to the faster CPUs and DualCPU-systems and more and more degrading mining output. For example my 10 year old Core2 laptop with proclimit 1 is sometimes producing almost as many shares as my Dual-hexacore-Xeon server on proclimit 12, which is absolutely ridiculous.

I understand that your main priority right now are your precious masternodes, but please don't forget about us small-time miners and remember that without the miners your blockchain wouldn't really work either. Comparing the output from before Christmas or even from last week I'm currently at approx. 10%, which barely - if at all - covers my electricity bill.

Thanks for your time and effort and God bless this project!


Edit: For clarification: up to now it seems that the error only occurs with the linux client (Ubuntu 16.04 LTS in my case), the windows wallet doesn't seem to be affected.

Hi Dave,

Its just not true that we only care about precious masternodes.

Here is the way I view the priorities right now just so you know:  I want to ensure we are ready for block 24600, so we can pay our orphans. 

Next, I want to maintain production support levels.  That includes any critical errors with 1075.  And finally, I place a very low priority level personally on any "hash speed discussions".  So maybe thats the point of contention.  We only have enough resources to talk about the prod support and the critical errors and not about peoples mining speed, unless its an inconsistency in the pool that affects everyone.

Of course we have time to talk about how competetive mining works.

But first:
So, Im not aware of a critical bug in 1075, and have not received a log.  Can someone please give us a log so we can see what stopped the node in 1075??

There is no way to even look at a problem without a log.

member
Activity: 131
Merit: 10
BiblePay - 1.0.7.5
Leisure Upgrade


- Competetive mining feature:
  The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
  this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
  IF you run out of mining nonces, and only increments to 2 satoshi again if you run out.  However, when the block changes,
  the amount is reset to 0 again.  Alex and I have tested this and it appears to give a 5% mining edge.  Therefore I wanted
  to release this as quickly as possible for general consumption.  Since it gives a mining edge, I made the feature ON by default.
  To turn it off add the key: competetivemining=false to your biblepay.conf file.

- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).



Is it have a problem?I found some upgraded PC can't running bbp process , but old version still running normal....
I tried to reboot or change dns, and changed back to port80 but it seem not work..

quote:
# Error: Error: A fatal internal error occurred, see debug.log for details
Error: Failed to connect best block





I just got the same error. I am reindexing now...

EDIT: Re-indexing seemed to work

1.0.7.5 version seem have problem.

It is the second times occurred , I am re-indexing again.
I worry it will happen again....



Hello all!
I have been following this thread and this project for several weeks now and I am really excited to see the hard work and dedication going into developing all of this. However the last couple of days it seems to me that the only concern you have regarding troubleshooting is with the MN owners, not the miners.
Several people reported the above mentioned error and I also experience it regularly since updating to 1.0.7.5 on different machines, different networks, even different cities across Germany. So the error is definitely not on my side, because also the configurations on these machines differ from each other and each and every one gets this error after a few hours of mining.
However, no one has offered any permanent solution or even explained where this is coming from. I think the only reason so few people have this problem is because judging by the connected peers on my systems most people are still on the working version 1.0.7.1.

So when will this annoying problem be fixed? Another question you never answered was how this new "competitive mining" feature really works. Right now it seems to me that all the update did was giving an even bigger malus to the faster CPUs and DualCPU-systems and more and more degrading mining output. For example my 10 year old Core2 laptop with proclimit 1 is sometimes producing almost as many shares as my Dual-hexacore-Xeon server on proclimit 12, which is absolutely ridiculous.

I understand that your main priority right now are your precious masternodes, but please don't forget about us small-time miners and remember that without the miners your blockchain wouldn't really work either. Comparing the output from before Christmas or even from last week I'm currently at approx. 10%, which barely - if at all - covers my electricity bill.

Thanks for your time and effort and God bless this project!



Hey Dave,
Looks like your comment just answered the question that I posted on reddit.  I have an older i3 that is far out performing the i5 that I have.  Below are the settings that I am using, and the results that I am getting.  The crazy part is that I have a laptop that is outright killing my two desktops on hash rates.  Also, I agree that the output of coins received now is lower than what it was before the update, and that makes my chance of getting a master node almost zero.  See below:

"I need some assistance please. I just setup two new computers to mine Biblepay tonight, and I am pretty confused by the results.

I have looked up benchmarks for both processors and in every way the i5 should be smoking the i3, but it is exactly the opposite. The i5 should have twice the performance, but it is coming in at under half.

Anyways, here is a breakdown of what I have:

I3 - 2120, no gpu, 8gb ram, win 7, and overall just a slug of a Dell machine

i5 - 4590, msi gpu, 12 gb ram, win 7, and is very fast overall

On the i3 I have the genproclimit=3 and it is using ~ 75% of the CPU. I am getting approximately 950 hashps.

On the i5 I have tried several settings and had to rest a genproclimit = 2 due and 60%. 3, 4, and 5 would peg 100% on the cpu. I am getting 300 hashps at 2, 400 at 3, and 500 at 4.

To top this all off, I have a laptop getting 2500 hashps at 4.

Any help would be greatly appreciated."


I am not seeing the error issue that you are so I can't give you any assistance on that front.  Best of luck.
jr. member
Activity: 405
Merit: 3
BiblePay - 1.0.7.5
Leisure Upgrade


- Competetive mining feature:
  The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
  this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
  IF you run out of mining nonces, and only increments to 2 satoshi again if you run out.  However, when the block changes,
  the amount is reset to 0 again.  Alex and I have tested this and it appears to give a 5% mining edge.  Therefore I wanted
  to release this as quickly as possible for general consumption.  Since it gives a mining edge, I made the feature ON by default.
  To turn it off add the key: competetivemining=false to your biblepay.conf file.

- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).



Is it have a problem?I found some upgraded PC can't running bbp process , but old version still running normal....
I tried to reboot or change dns, and changed back to port80 but it seem not work..

quote:
# Error: Error: A fatal internal error occurred, see debug.log for details
Error: Failed to connect best block





I just got the same error. I am reindexing now...

EDIT: Re-indexing seemed to work

1.0.7.5 version seem have problem.

It is the second times occurred , I am re-indexing again.
I worry it will happen again....



Hello all!
I have been following this thread and this project for several weeks now and I am really excited to see the hard work and dedication going into developing all of this. However the last couple of days it seems to me that the only concern you have regarding troubleshooting is with the MN owners, not the miners.
Several people reported the above mentioned error and I also experience it regularly since updating to 1.0.7.5 on different machines, different networks, even different cities across Germany. So the error is definitely not on my side, because also the configurations on these machines differ from each other and each and every one gets this error after a few hours of mining.
However, no one has offered any permanent solution or even explained where this is coming from. I think the only reason so few people have this problem is because judging by the connected peers on my systems most people are still on the working version 1.0.7.1.

So when will this annoying problem be fixed? Another question you never answered was how this new "competitive mining" feature really works. Right now it seems to me that all the update did was giving an even bigger malus to the faster CPUs and DualCPU-systems and more and more degrading mining output. For example my 10 year old Core2 laptop with proclimit 1 is sometimes producing almost as many shares as my Dual-hexacore-Xeon server on proclimit 12, which is absolutely ridiculous.

I understand that your main priority right now are your precious masternodes, but please don't forget about us small-time miners and remember that without the miners your blockchain wouldn't really work either. Comparing the output from before Christmas or even from last week I'm currently at approx. 10%, which barely - if at all - covers my electricity bill.

Thanks for your time and effort and God bless this project!


Edit: For clarification: up to now it seems that the error only occurs with the linux client (Ubuntu 16.04 LTS in my case), the windows wallet doesn't seem to be affected.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I can't remember who requested the pop-up bible verse when a transaction is received by the wallet, but it will be in the next release.


Great idea!
Thanks:

Jump to: