Topic: BiblePay - New Coin Launch - Official Thread - page 17. (Read 119845 times)

Hi all, a question about backups...

1) I can backup my wallet by exporting a wallet.dat file. Do I have to do this everytime I receive more BBP? Or just whenever I add a new key?
2) How do I add new keys?
3) Can I generate and see the private key so that I can write it down/print it and store it somewhere safe?

Many thanks

am i understanding this correctly. $770 to run a sanctuary and $7700 to run a masternode?

is that money paid to the charity fund?

what are the benefits to an investor to do this?

Thanks for the advice, yes I agree 100% that we have to throttle resources appropriately.  I have a very strong sense of IT resource management grounded in reality as over the years Ive been burned on hard on IT deadlines and have adjusted it down to reality over the years.  

I agree on the comment of GodNode being slightly irreverent. Thank you.  When you have that 'feeling' in your stomach, its usually right.  Ill write down the top 7 we have so far and maybe we will make it into a vote later.

So JC I want to say - the Master Sanctuary (TBD) is not really driven by either greed or a quick to market solution-and I did not mean to imply the master sanctuary would be running the advanced solution at Christmas.  There are a couple processes that we really need in BiblePay that I feel will propel us into the top 50 if we can pull them off.  One has to do with a storefront API being embedded in the wallet.  To the user, I would really like to give them the ability to go to the RPC, and using a command similar to 'sendmoney address', we can allow them to purchase a NKJV bible with biblepays through a Master sanctuary.  If for example they typed in their address, city, state, zip into the config file.  Then maybe 'list products' and 'buy product 10000 11000'.  What Im thinking is the chosen hourly Sanctuary would run the accountability.biblepay.org, and also be a broker for bible purchases that become dropped shipped from the command line.  There is also another major feature I have to discuss.

So from a high level, Im very cognizant about the actual deliverables, but stepping down into reality, I think it would appear more like this for our end users in this case:

At Christmas, a sanctuary can be either lets say 1.1 million bbp for the standard one, or 11 million BBP for the master.  The second flavor of course requires the equivalent of running a pool and costs the user $60 a month extra.  During the first few months, the larger master sanctuary would only do one extra thing: run a web site.  Im saying, I think over Q1-Q2 2018, we can then have a solid base to merge in the advanced features we want to write - into our master sanctuaries.  

This is a pattern that needs to be established to give us a large IT footprint to make us really strong and decentralized as well, but on cutting edge, with new blockchain value added services for the end user.  

The early parameters on the financial side gives us the ability to start merging the code into the right codebases, so people know what is expected from their investment.

I don't know if there is a formula.
Right now I guess that is about 100 - 200 coins a day or so. Total approximation, I might add

This number will change over time so it is more useful to say what HPS we are getting. I have a $5 box to test it out and it was getting around 15K HPS

Hi zthomasz,

are you deploying this on a physical computer/server at home, or on a cloud server?

Most cloud servers won't let you use the graphical display so you can't use the gui.

You can still control from the commandline though.

Try
cd/biblepay/src
./biblepay-cli getmininginfo


for example

I can run a small campaign at bitcointalk, which would pay a 10 people to retweet my pinned tweet at twitter to coinexchange.io

something like this:

@CoinExchangeio #coinexchangeio Please add biblecoin BBP for trading at coinexchange.io
#Exchange #Retweet TY

I have not tweeted that yet, but I could do that, and pin it to my profile for people to retweet
Or you could tweet that at your twitter account, and participants have to follow your twitter account and retweet that tweet and perhaps more?

I am thinking I would be ok with 5000 BBP for myself to complete this campaign,
and anywhere from 1000 to 5000 more BBP to be paid to the tweeters(100 to 500 per retweet and follow, the more you pay the easier
it will be to find people to participate in this campaign),
but only 10 tweeters for now and they must have at least 200 followers and not bot follower but real people following them,
and it must be an account that is crypto related and perhaps something to do with Jesus Christ or the Holy Bible to fit
with the theme of biblepay coin.

The conditions would be up to bible_pay though

(I did not send you this in a personal message, because I do not want to get banned for sending unwanted personal messages,
but let me know if it is ok with you for me to send you personal messages, so that in the future I could contact you in private
about this kind of thing.)

I was thinking of ways to make us a team player in the great tribulation, after reading that reddit post where someone asked us if we were the mark of the beast.

I was thinking, how can we create an outline of features that would provide value during the great tribulation, instead of rolling over and dying.

So far here is what came to mind:

- Reverse implosion database, full of phone numbers, addresses, contacts and background info on Christian members
- Biblepay Emergency mode, where each step of the ledger is either manually committed, or synced via an alternative network other than cat5/wifi
- Silver coins, survival food for sale for biblepay, from the pool (and hopefully in wallet eventually)
- Some groundbreaking feature that gives intrinsic value to a coin when the blockchain stops (this is if the internet completely goes down including wifi), or, an alternative idea that keeps the chain rolling
- A simpler protocol, one that can be executed by hand (probably not realistic)

A long time ago, while working for a blood delivery company, we had an emergency mode that we entered if the power and LAN went out.  We would take orders from hospitals, write them down manually, and if possibly print all the blood drivers routes out manually, and continue operations by moving papers around like it was in the 60s.  I was thinking, if we are fortunate enough in the great trib to move anything around, we could use this as one idea.

In the most basic sense, it would be valuable to have maps of where the Christians are (IE US), and band together and share our food and water, and help each other.  So of course with the block chain being private by default, most everyone will not want to share all this personal info by default.  But one option is maybe we build in an implosion database.  We could make it encrypt 'contact records' entered into the UI with a key on the client side that corresponds to an unlock key that is broadcast back to unlock all the data but only if the chain does not advance for 7 days straight.  Then, each users copy is fully readable (ie the whole record database).