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

Please let me clarify the difference between leaving coins on an exchange and leaving on mintnodes:

An exchange moves stored balances to cold wallets, and has better experience in preventing web site hacks.  (At least, the top 50 exchanges supposedly do).
Mintnodes appears to be a new domain run by one individual, and does not appear to have cold wallets in place.  So from a hacking perspective I give them a risk level of 10, and bittrex a risk level of 4 for example.

No centralized service is perfectly safe.

*** HUGE CHANGES IN BIBLEPAY TO IMPROVE OUR COMMUNITY AND HELP OUR CREDIBILITY AND CREATE STRENGTH ***



So this all started when one of our fast participants, Andy from LA offered to help with a few things.  Things that resonated with me because we both pray for BiblePay and receive confirmations about issues.  

I admit not all of my ideas are going to stick forever - as some are rooted in prior IT experience and not in God's will.  So when I hear that God wants to change something about BiblePay, I listen.

There were 3 areas that Andy brought to my attention that resonated:  Ease-of-use for investors and users, Key-man risk (dev+governmental), Sanctuary simplicity.  You are already seeing some of the changes (with these providers for masternodes like GIN we reached out to in response to the Sanc issue).  

For the Ease-of-use part, our complaint was that when an investor arrives on our landing page- they are way too confused.  And the page is dark and not full of love.  In light of that, Jaap is working on our landing page changes:  Show key information to potential investors (Quickly download the wallet, how to trade biblepay, what we do, boilerplate) and he is also adding a brighter background theme and images of children.   He is also making it easier for new users to understand how to get started in relation to the next wallet version (which will have a couple more GUI buttons to get started with one click).

Key Man Risk:  This started with a conversation from one of Andys clients, wanting to get into BiblePay as a whale, but he was afraid that I was the single point of failure.  After showing him the DAO page, many, many changes were put into play.  One being that we are working on an internal plan to remove key-man risk in Phase 1 (that is at the end of this month).  More info will be given on this today.  This will eliminate key-man risk.

Sanctuary Simplicity:  The whale would not join unless they find a way for a one-click masternode.  In this case, MIP is now creating a script for one-click sanctuaries.  We also reached out to GIN who came through for us for decentralized sancs.

This exercise brought up many sub-exercises and new projects for us, which I think in the long run make us stronger and more credible.

The key-man exercise brought up some of the weak points that exist in having a BiblePay foundation.

The problems with the BiblePay foundation are that we were becoming centralized, and "ruled" by only 6 individuals, with governmental systemic risk.  This gave the rest of the community the feeling that their masternode investment voting rights were not being used appropriately by biblepay, the biblepay directors were "better" than everyone else (IE could make legal decisions and trample on the rights of the community).  Arguably, one of the most important issues raised was the governmental risk involved with a centralized foundation.  This was the risk of being a lightning rod for a government to shut down biblepay or force biblepay to add wallet rules that remove anonymity.

In light of all these points, and with the desire to decentralize I feel we should dissolve the biblepay foundation.

The primary reason we started the foundation was to enable conversion of biblepay to Fiat for Compassion.com payments.  However, I feel we have other options for this now.  All of our other vendors, Kairos, Cameroon One, BLOOM accept BiblePay or Bitcoin.  I've reached out to compassion over the weekend to ask if they will set up a dedicated receiving address and accept our payments in Bitcoin.  If not, I will provide a homework assignment for the community to find a way to set up a program where we can convert biblepay to fiat for slices of payments to compassion.  Another option is to phase out compassion and ramp up sponsoring with orgs who do accept BTC (although Im not recommending this as compassion is $38 per month per child).


As far as Newbie Experience:  As you know we recently saw the no-team requirement poll pass, and the reward level to non-biblepay teams set to 100%.  In the next version of biblepay, we are trying to make it so a brand new user can mine with very little resistance.  This means downloading the wallet, buying the UTXO amount on the exchange, downloading boinc, and clicking "Add me to Rosetta", and then click "Associate".  The next version will also show how many tasks are running on the GUI - giving the user the understanding that the wallet is working (without going through RPC commands).

kissmarx are you read www.biblepay.org? i can you help if you wanna

goldart we filled more the forms, few good exchanges want to list us, but for BTC  hotbit,bitbay,cryptonex=3BTC for pair, like said Rob , now we need to focus to marketing,PR... no need exchanges now: but, bittrex,poloniex can be good

don't see any problem right now, I believe this is a good coin to have in existence.
any price predictions during the next 2 months on biblepay? any new exchanges coming?

So I supposed I started mining with my wallet as I followed the instructions here https://www.biblepay-central.org/en/documentations/mining-how-to/mine-desktop/ . It tells about Rosetta, so I registered there. I don't quite get this. But is increasing the RAC also mining? Am I mining both in the wallet and Rosetta?

In other threads I read about mining BBP. It is connected with Rosetta. There's also WCG. Then byteball is connected. Things are very confusing I think I have to allocate more time understanding these things and research more.

616westwarmoth when ill to jump to BB,i have to setup new mining?i hope that not.....only change team and thats all, right?

i dont trust https://www.mintnodes.com better/secure choice is build masternode with users from here  
why
1.masternode was very long preenabled with expired
2.when somebody left from MN,whats next?
3.site can be hack
4.owner can left

very untrustable


im finding somebody for build new MN:  write me PM with how much BBP you have: only future tenants please,thanks
for 2% i can to build it for you...im using my machines in my datacenter
online spreedsheet+NODE checker will be too for owners of MN

example of spreadscheet our 240 days old masternode= 9 ppl

I just sent an e-mail to mintnodes asking questions.


By default I would assume all money put into mintnodes is 100% at risk and may dissapear overnight. 

If you do these things I think you will be OK:

Remove utxooverride from config
Add:
genproclimit=1

On Boincing, start crunching RAH again, until you get your full reward, then throttle RAH back to 1% if you want WCG at 99%

The UTXO override is not needed.
The genproclimit=1 is needed so that the internal miner knows to send a PODC update once every 4 hours.

Good luck.

Rob
PS You can remove genproclimit, as the default = 1 .  You can't use zero.


PS 2:  Technically people do not need to pool mine or heat mine to receive PODC rewards.

Good observation.

In light of this I'm going to make an announcement today with some recommended changes.

Hi Rob, you mean if i put the config file proc=zero then i must type PODC update cmd once a day ? Because the last time i put zero for proc that have no reward also for 2 days. Could you please clear this ?

indeed ... better choice is make MN between ppl like frenchise ... we had MN ... dave,rastiks,etc

We don't need any more exchanges until a top 10 exchange approves us.

Besides, we got a verified offer from Cryptopia for 1.5 BTC but our new exchange fund is empty, so we need to start saving up slowly, might take us a year with our lower budget, but hey next Christmas might be really bright for us if we are listed on Crytopia for Christmas of 2019!

Maybe they are leaving to test out A & B.

As far as a release date, I believe we should be done in testnet within 7 more days.  I think we can shoot for Oct 15th or so roughly.

We have a couple things to talk about in testnet:  Clicking on a GUI for Rosetta diagnostics and a different button for Setting up Rosetta, and a question about the initial baby-step of an IPFS rollout.  

I would delay it further, but I'm also prodded to release it in October because we have one business rule in Prod I want to replace that prevents forks (although we have been running very smoothly in prod lately).

I cross compile under the gitian builder, and release those for windows releases.

*** WARNING - MINTNODES ***


I was just taking a look at this site this morning, where we have been listed with Clusternodes:

https://www.mintnodes.com/faq

Mintnodes.com


I have to warn everyone, I don't think this is a very safe operation.  They are concentrating all the deposits into one place, hold all the keys to the crypto, and from what I can see, I don't have any reason to believe they are even creating real masternodes.

At the very least it looks like a way that someone can allow $1 mil to pile up and then they can run away with all of it.

Additionally Im not sure if its legal, because selling slices of nodes may be viewed as selling securities (and that could cause a shutdown for an sec violation).

Imo, we should pull support for this, unless the owner comes forward and proves the funds are stored in a cold wallet and posts the code that creates the masternodes.

You do not need to POW (Heat Mine) to receive PODC rewards.  You only need to ensure your wallet is sending 1 PODC update per day (which is supposed to happen automatically if you leave the controller wallet running).

You cannot receive WCG rewards without having RAH attached and running currently.  That is most likely your problem.

Just attach RAH and start at least one task, limit it if you want, and then things should come back for WCG.

After the next mandatory, the sancs should technically allow WCG only boincing.

WSL was my next question. I'll give it a try.
Thank you both.

Follow MIP's docs, I never had luck compiling under windows,  I could cross-compile via linux however (and even windows subsystem for linux)

Odd.. maybe because of the no team requirement change?

Rob: when is this going into effect?

There is this
https://github.com/biblepay/biblepay/blob/master/doc/build-windows.md

But I don't think it would work. I mean, I compiled exes following this but they don't seem to run.

There is a second way which is following gitian build instructions (and in fact the way Rob is doing it)
https://github.com/biblepay/biblepay/tree/master/doc/gitian-building
https://github.com/biblepay/biblepay/blob/master/doc/gitian-building.md

I didn't try it myself but this method would probably cost you 2 days to set everything up.

What I do is creating a Linux VM (Xubuntu 16.04 is great) hosted by my Windows, and do the process with Linux and X GUI.
Bear in mind that you won't find any Win32-specific code there, as everything is abstracted via QT libraries so there is no real difference as a developer between both versions.