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

Oh yeah... I see my wcg rac shows me 0 too :-)

All-

Someone just made me aware the Pool superblock report is chopped off, and their internal WCG RAC is 0 but they do have UTXO level of 100%.

I started to take a look at this - and it appears there is a problem with the WCG export file.

I will make this a top priority and get an answer for everyone now.

Please hold off on using the Pools superblock view report for now - it is not accurate.

Please remove the swear words.

i'm only loosing 30.000 BBP daily !!!

Delayed proof of work:  In this scheme, 64 trusted nodes become notaries (think 64 of our sanctuaries).  These are trusted to log and vote historical bitcoin blockhash consensus entries (IE known concrete historical non-forked blocks).  These notaries then become witnesses to the current hashing algorithm modified by the historical bitcoin hashes (for gamecredits for example) giving you supposedly more secure sum of POW.  So - its as trustful as your belief in centralizing trust to those 64 sancs. 

Its OK, but it could be argued that that ecosystem is less decentralized, less trustworthy (putting faith in the rich 64 nodes who everyone trusts) than a flat out POW system with a security addition (like our signed CPIDs).

I'm far more excited to make a custom mining algorithm out of IPFS.  I was thinking this morning, if we had IPFS "miners" - those with open API ports communicating in a trusted swarm, we could potentially charge BBP for outbound bytes, and make miners Pay BBP for inbound bytes, and modify the IPFS to be a new mining algorithm that helps enable the sharing of the biblepay hosted files.  (To replace proof-of-work).  So far its just a concept and thats what Im looking into next. 

Let me check into it.

You are closer!  You now have 1000 bbp - you only need 350 to be in the 30% bracket.  Now you need to send a UTXO.

Try:

exec podcupdate true

If successful wait 6 confirms.  Then do 'exec utxoreport cpid' and see if your utxo shows up.

I want to take a second to let everyone know that we care about their anonymity.  First of all, we do not store any personal info in the chain (we store the contact records in IPFS), and for GDPR compliance we allow a user to delete the contact record (we update the fields with empty strings and save the new value with a deleted flag=1).  Second, even with BOINC, we only store your public key and your CPID in the chain, we do not track or store any personal info.  You may use a nickname in your boinc account if you wish.  In that vein, Id want to veer away from any more features that makes biblepay look like we are trying to track people.

However, from the perspective of Mobile Devices, and public churches, yes, I like your idea.  I was going to say, we could make a general purpose field like 'usertext1' and allow them to store anything they want (or a phone #), but yes, it would be nice to send BBP from the actual mobile phone # that MIP grabs from the android device to another mobile user - goes hand in hand with the unbanked features.  As far as the mobile android actually retrieving the IPFS record: its possible.  So, yes, we could do it.

Let's take a baby step first and see if MIP is willing to add a tithe button to the mobile app.  That will exercise his ability to retrieve an IPFS record on the mobile and send Biblepay as a tithe to a recipient.  Then you can add a github request to our mobile branch.  If you want go ahead and add one for Tithing and send via phone number.

All credit to Yeshua Hamashiach.  God, please let us integrate for You.

If your UTXO stake is 0%, the WCG rac = 0 in this wallet version.
Could you run an 'exec utxoreport CPID' and verify you have UTXOs out there?  Then your WCG RAC should display properly if you are above the 10% threshhold.

Nice! Very curious about this plan.

I still have some of my BBP on Mintnodes. I see that people pulled their BBP from there, because a Masternode was first started and Mintnodes tore it down again. I would indeed never advice anyone to put more BBP in there than they're willing to lose (not your keys, not your BBP), but it seems like an easy system and you get some 'interest', so it could be worth the risk.

Also, I will vote 'yes' on Togo's proposal on this.

LOL, wait til the chart updates with last nights commit in c#, it was a whale.

I e-mailed Jimmy Mellado, president of Compassion this morning with a new idea (proof-of-orphan-sponsorship).  I went into details about how we could integrate Compassion into BiblePay, using the Compassion API (for multiple uses, one being governance receipt reimbursement, and one being mining). 

I'm looking forward to conference calls with Compassions IT team.

Since we're doing the contacts in BiblePay testnet with the ability to send payment via e-mail address. I wonder if we could also send by phone number. Then somehow add this to the Android and iOS wallet where you could send payment to someone else's phone number.

It could also be a way to airdrop to people. They sign up for the newsletter and you airdrop them 1k BBP to their "e-mail". So they have to run BBP and add their contact detail to receive the e-mail? Not sure if you can receive BBP on the blockchain for an e-mail that isn't registered yet...


I was asking primarily about liability. If they were hacked and somehow lost funds, what would they do to make us whole. He was not able to answer. They certainly have better countermeasures in place with PCI compliance (although I didn't ask if they are Level 1, 2, or 3 compliant -- Level 3 being the most robust and arduous for big companies). Still, it is concerning there is no insurance in place to handle such an issue. Given that they charge only $1/mo worth as fees, they'd really have to scale a lot and keep a portion of their profit for this rainy day scenario.

Anyway, if you got a spare 100k BBP, please support them.

I received some replies from Mintnodes that raise the credibility somewhat, although I still want to say "INVEST AT YOUR OWN RISK - Dont send capital you cant afford to lose":

=-=-=-=-=-=-=-=

Rob,

Our system will create and teardown masternodes as needed, all of this is automated to keep costs down to maintain our $1/month/masternode fee.

Well Exchanges and Shared Masternodes are two different things, as you know we have to have coins stored somewhere in collateral amounts.  We are always honest and transparent.

I don’t want to go into too much detail of our architecture as it is proprietary information that belongs to Mintnodes LLC, but the wallet coins are stored remotely away from the masternode servers. The coin wallets are on an isolated network from the internet.  We use PCI compliance practices, as I have been the last 15 years.

Mintnodes was started by our family and only 2 people of our family have access to the coins.

I don’t know if it was you but someone from BBP was asking the same questions in our discord server.

Steve.



=-=-=-=-=-=-=


I see people have voted down Togo's proposal for this, but he did spend his personal BTC on this and did it out of the goodness of his heart.  Imo we should vote yes for reimbursement.

 

Reflecting on recent posts about "haters" ...

When my sister and I were kids we would get so mad at each other sometimes we would yell and call each other "stupid." Even though our actions made it look like we hated each other, the opposite was true. We honestly loved each other.

The same thing happens among brothers and sisters in Christ. We sometimes get mad at each other and call each other names. We accuse and misjudge motives. We've all experienced it and felt the pain it causes.

Denial is slippery and can cause us to fall even when we mean well. Learning how to see past it requires practice. Here's a simple saying I've taught my kids ... "If you did it, admit it, then quit it."

my mistake.

its sparc

SOLARIS ?

How do you configure that one? Can't find any info...
thanks!

-> edit: nevermind, it's SPARC again...