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

tithes are sum of tithes or count?
could you please add pogpool output from console? just as plaintext somewhere

Tool updated

https://viisastentori.fi/bbp_test/index.php

Added tithes in each block. (data is still inadequate, but will improve block by block)

Updates are triggered by founding a block

MacOS DMG ready
Ubuntu PPAs ready.

BiblePay - Mandatory Upgrade - v1.1.8.9 - before Block 103175 - (February 22nd, 2019)
For entire network (including Sanctuaries and Exchanges)


- Prevent crash in POG Leaderboard when chain not synced (MIP)
- Mandatory height @103175 : Prevent POG illegal tithes, Fix POG pool bug, make POG more exact
- Enhance exec pogaudit, and exec istithelegal
- Allow users to pay prayer_threshhold_amount to send a public prayer

Yes, when an employer has a high turnover it's a red flag (I guess that would be true when you can afford to pay the staff).  In our case we had a lot of swearing people from Slovakia in the thread who didn't volunteer.  I'm kind of insulted (as usual by most of your posts) as they are very insensitive ; I think 3-4 people that turned over in a volunteer project is not enough of a sample (especially when they were working for free in a hostile environment) -  Please post examples of how we can delegate better (I have experience in this field).

I'm glad you didn't call BiblePay a charity coin. Christian values can include charity work, but I don't think we should pigeon-hole ourselves. Innovation requires being able to pivot quickly as the environment changes without compromising core Christian values. Personally, and you're welcome to disagree, #1 and #4 seems to have been the focus thus far. #2 and #3 we need a lot of improvement. First, when an employer has high turnaround of staff that's usually red flag. BiblePay has turned away a lot of smart and talented individuals... You have to ask yourself why this is a recurring theme. Its difficult to operate smoothly and be a productive organization when there are constant stop & starts. You lose a lot of momentum and the community at large loses a lot of trust of the project as a result. I can appreciate the difficulty in managing all this... besides writing code having to be responsible and trust others to perform key functions as well.

Let's remember, and above all keep in mind, it was Togo that started all this talk of forks.   

Yes! This is a much clearer way of expressing it. It isn't code, it's coders. With innovation and passion and tenacity.  Anyone can fork a project but the skill isn't just an ability to type in code or understand blockchain (although as rob pointed out that can be hard enough). True leadership is what makes a sustainable project.

Anyone who isn't aligned on the risk/ reward matrix can fork, but they should be prepared to have the leadership and commitment necessary to sustain it and grow it. If they don't have that, then they should either work to change the vision or take one of the other 2 routes specified earlier - support or be quiet

Thanks MIP and Rob for leading this (and any others I may be leaving out).

Although I agree in general with this, yes its true you can utilize a consulting company, who are experts at a niche to produce v1 of a forked BTC clone, or, a night time hacker can produce a BTC clone (knowing enough to be dangerous), I feel we are taking away some of the credit due to real blockchain programmers.  That is, lets say there are 3 levels of expertise:  a nighttime hacker who dabbles with c++, a veteran c++ coder, and a blockchain programmer who also knows 5+ years of c++.

I still am of the opinion that #3 is more of a pink elephant.  I've been looking for blockchain devs for years and they are extremely rare and valuable.

Here's what you get when you fork a coin and you know nothing about the blockchain:  A non-recoverable dead coin, a coin heading to the graveyard, and a coin you cannot maintain properly (IE release patches).  One where the blockchain seizes up because someone made a mistake.  The night time hacker might know how to compile bitcoin but do they really know how to create a new genesis block?  Do they know how to write a new report using the transactions?  Its one of those niches you learn through trial and error.  It took me two years of nighttime sweat to finally figure out how to be a blockchain programmer.  I was already a c# programmer for 20 years before I attempted this.  (It did only take me a couple weeks to figure out how to clone litecoin, but that was back when there were no real guides and I was working on windows).

So let's still give kudos to real blockchain programmers like MIP, and hope we attract more!  All credit to Jesus for what we have achieved so far.

Thanks Nox for your generous and professional contribution in BiblePay.

Now as promised let me offer my personal opinion on what I believe the goals/priorities are for Biblepay. NOTE that these are noxpost's priorities, which may or may not align to the wider group (hence the discussion). In order, I would claim that our priorities are:


1) Spread the Gospel of Jesus Christ through service to and financial support of like-minded organizations, with accountability and transparency.
2) Support a community of believers, and provide a way for them to come together to widen their impact on the world for Christ.
3) Utilize our gifts, talents, and abilities to lead the way in developing sustainable and responsible methods of value creation in cryptocurrency, including for those with limited infrastructure.
4) Long-term return of value for participants/investors in the Biblepay ecosystem.

I don't think it qualifies as insider information if its posted publicly?

Let's play nice and not assume ill intent.

I just want to add to this. I have done a number of private blockchain applications, have a surprisingly large collection of blockchain development certifications (although I don't write much code myself at this point, as I'm a CTO for a tech company), and have worked on a number of non-crypto use cases in consulting engagements with massive organizations. That is to say ONLY that I feel qualified to speak about getting familiar with blockchain development, even if I don't have anywhere near the hands-on experience of MIP or Rob.

In the matter at hand - my teams can typically get a new member through the blockchain basics and producing code in about a week, and can have a private fork up and running in a similar timeframe. Basic ETH20 chains or even Bitcoin forks aren't real hard to make, and there are a number of tools that can even assist people who want to make a fork.

All I mean to say is that it isn't technical ability that is the barrier to entry. If it were, there wouldn't have been literally hundreds of new coins created last year. Creating something of value - thinking ahead, seeing the difficulties, responding to problems or scale, getting a differentiator that both adds value and stands out in a meaningful way....THAT's the barrier. Maybe with enough willpower somebody could fork a codebase themselves (or hey, just pay someone on Upwork to do it for you if you have to, or buy a college kid some pizza to clone a repository), but that's not at all what you need to actually have a coin and infrastructure up and running and supportable.

I'm not sure that people understand how much innovation has gone into BBP. PODC, the distributed hedge fund, POG, POBH, there are so many interesting techniques and new ways of handing the now-almost-classical proof of work vs proof of stake problem, and that innovation goes beyond technical into thinking about real-world problems like electricity use, helping others, and spreading the Gospel.

The other thing people don't understand is that when innovation rises, so does chaos. New ideas take lots of tries, lots of small adjustments. Some ideas are home runs, some are total strikeouts. Some are even great, but presented at the wrong time or wrong market conditions. If you want to play in an innovative space, you have to accept it. If you want something safe and stable, stay away from someone (or some system) attempting to push the envelope and do new things.

I don't think it's "we're a community or not" - it's "do we have the same risk/reward tolerance, and do we want to do something radical or not?" In that sense, yes, someone with a lot of history, ability, time to spend, willingness, and capital will have a VERY loud voice as to the risk/reward tolerance. Rob is always seeking input on how the community wants to go, while bringing new ideas, but you can't blame the guy for voting with his time and money. But maybe the discussion could be more positive if we focus on what success looks like for BBP, and ensure that everyone who is a part of this community has the same goals.

I'll put in another post in a minute or two of what I think that success is, just to separate the topics a little in case anyone wants to debate what I've said above

I've heard this argument before--if you don't like it, then make your own. Is that really efficient? Please don't make blockchain development out to be so difficult. With open source and copypasta, you can have a coin up and running in a few hours. BBP is unusual in its complexity. But that's not the point.

You have to make a choice. Either we're a community coin, and we all get input, or we're a monarch coin and we should just keep our criticism to ourselves.  Which do you choose?

Not giving up, just stating that BiblePay PoG needs more polish and refinement to be able to market it to new participants. We've been brainstorming and a member suggested Rasp Pi. Since PoG is eco-friendly, putting BiblePay on a Rasp Pi (perhaps a self updating OS image), can further the idea of being good stewards of God's creation. This will promote and forward Christian values.

Proverbs 27:18 ESV Whoever tends a fig tree will eat its fruit, and he who guards his master will be honored.

Genesis 1:26 ESV Then God said, “Let us make man in our image, after our likeness. And let them have dominion over the fish of the sea and over the birds of the heavens and over the livestock and over all the earth and over every creeping thing that creeps on the earth.”

POG does not rely on sanctuaries for historical information as POG does not use contracts.  If we were writing a smart contract system then POG would run on sancs, but its not necessary to do that and overcomplicate this system.  As one of the big pros with POG is it offers a hard consensus.

I would recommend studying up on bitcoins consensus mechanism and the difference between deterministic business logic and soft forks and then come back and discuss that matter.

Additionally, it's clear that POG does not benefit from a 24 hour barometer as the financials of it only have one simple dimension.

This is not unilateral, if you want you can invite all of the blockchain programmers from bitcoin over.  And we are democratic, as every dollar spent on sanc voting rights can vote.

HiveOS is not supported by BiblePay, but best I can tell HiveOS is a fork of Ubuntu (Linux).

You might try installing the BiblePay packages.
http://wiki.biblepay.org/Ubuntu_Packages

~~~

For BOINC, try the following:

sudo apt-get install boinc-client -y
sudo apt-get install boinctui -y

boinctui is a text GUI client for Linux. You can add projects using boinctui.
It may save you from having to edit global_prefs.xml or global_prefs_override.xml as well.

if you insist on command line, the cli ways to add projects. xxx_cpid is the weak key you can find in your profile on the respective boinc sites.

boinccmd --project_attach http://www.worldcommunitygrid.org xxx_cpid
boinccmd --project_attach http://boinc.bakerlab.org/rosetta/  xxx_cpid

other useful cli commands:
boinccmd --get_simple_gui_info
boinccmd --project http://boinc.bakerlab.org/rosetta/ detach
boinccmd --project http://www.worldcommunitygrid.org detach

So just to clarify as it seems you are still hanging on to some FUD here:  POG does recalculate difficulty every block (just like DGW) - not once per day, but I maintain that it should not recalculate once per day because there is a single payment event per day.  The payment event is a distinct event from difficulty recalculation and tithe acceptance.  The important thing to understand is POG has a 40 block lookback for its barometer, while DGW has 28, and both algorithms recalculate difficulty every block (as they should).  So there is nothing wrong with either algorithm - POG or DGW, and nothing wrong with using the diff algorithm in POG in prod (no flaws).  There is no benefit to changing it - and it is an IT decision based partially on performance, which I care about, not on peoples "opinions" who are not blockchain programmers.

On PODC vs POG:  I see the pros and cons, and based on some of the cons I still imho personally veer towards POG while we weigh out the new user baseline results.  I would still like to see an increase in user count (in contrast to stagnation) play out.  If it doesn't play out in environment B over 6 months then maybe my opinion will change.  We will have a democratic vote and discuss these pros & cons in great detail in that forum thread then.  I don't want to use too much of my bandwidth on this right now since we will have a thread for it within 14 days.  Til then lets see if we can deploy POG correctly and see how it behaves in the low emission environment.

** Future Mandatory Upgrade Alert (for everyone Except Exchanges) **


All, it has come to my attention that POG has not been fixed.  A bug has been discovered that affects the behavior of POG and we are working on it now.

I am extremely sorry for the inconvenience.   I know we have a lot of upgrades in this community and this is not one that I planned for.

To make it easier on our exchanges, this upgrade is being completed in a way where only the users and sancs will need to upgrade.  I am aiming for at least one quarter of stability before our next exchange mandatory upgrade.

Since it is extremely important that POG works properly in this first Phase, I am shooting for a Thursday mandatory upgrade deadline, and for the code to be ready within 24 hours.

More information will be posted as soon as the next version is ready.

Again -- sorry for the inconvenience.

Rob

Been running two mining rigs on Win10 for over a year mining coins via GPU miners and running Biblepay/BOINC on the cpus of both.

I've switched one of the rigs over to HiveOS and it just seems much easier to deal with. Unfortunately I've not found any tutorials as far as how to use Biblepay or BOINC on HiveOS.  My rig that runs Biblepay wallet is still on Win10, but BOINC on the 2nd mining rig is offline for now.

Does anyone have a nice tutorial for mining Biblepay/BOINC on HiveOS? 

Thanks! 

This is a relatively fair assessment, its not overly harsh and I can deal with this, thanks West.

On #1 - If they disagree with the developer they are called Fudders or Satanists.  I strongly disagree with this #1.  This is simply not true.  The problem here is your perception of my reply.  Look, We are in a cryptocurrency, so it is of paramount importance to get posts right, as it affects our investors perception- but for BiblePay, imho, its even more because it hurts our orphan count.  That's why I'm so sensitive about Fud.  You posted something 10 pages back about a misleading statement about pog (to hurt pogs perception rather than be a completely neutral with a biased constructive comment) you said "what is this the 3rd iteration or whatever" and some things alluding to that it had "problems" with the 40 block lookback, yet knew nothing about the effect of the DGW algorithm.  It was correct for me to say this is FUD.  The problem with the 2nd version of POG is just that the function is not returning the right value (even today) and its a technical thing, but it does not mean POG is flawed as a concept.  So, this has been rampant with people like Slovakia attacking in the first 600 pages or so.  I maintain that if a person gives me the benefit of the doubt, and is civil, and phrases what they do not know as a polite question, I cave and give the rest of the info and meet halfway.  I admit flaws, in myself, in my code, in life in general, and meet halfway.  I called people satanists who had mean spirited attitudes but remember the difference here, I apologized.  (I don't remember you apologizing for attacking in ways that hurt us however). 

On #2 - We have big problems with our docs.  I admit it.  Jaap went on retirement, Luke resigned, we don't have a web developer, etc.  Its something we need to fix.

On #3 - This is a bona-fide problem because we constantly write cutting edge code that has RPC commands and no UI support for users.  I think we are getting a leg up on this now that MIP is solving this problem as we speak. 

On #4 - I've come to the realization from the Holy Spirit that the project needs stability and that we should focus on adding Gospel features after our (POG?) is working and making it stable permanently.  I still maintain the calling to be blessed by God is a platform that makes it useful for God's Kingdom (IE a tool for Christians, and an avenue to get saved).

On #5 - This won't be like this forever - I feel that you will see transparency in my team and our bio in due time; we need to cover the status of The BiblePay Foundation first and this will be part of that endeavor.