I like the communication and the expression of potential unique features such as a "Master Sanctuary" which is essentially an amplified masternode. I will however state that I don't think its a good idea at the current stage of the project. I think development should be constrained to Sanctuaries even in the medium term. Once Sanctuaries are live and deployable by the layman this project will take off. There is no need to incentivize whales beyond multiple masternodes. If a whale wants to participate with 15million biblepay stake, then let them run 15 or 30 masternodes, which ever is the cost. It would reinforce the network in a much more solid manner than to have a tiered caste system of masternodes.
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.
unbelievable, irresponsible 
