yes all ppl when saw this tutorials told "its crap" ... some gridcoin users too .... 4 owners/CEO of exchanges too
are you new in crypto,cos you looks so ... when im started mine doge when rlsed,and next coins all tutorials was totally easy
Here is the actual wiki page and its correct (and its linked to the OP post): http://wiki.biblepay.org/EconomicsIf you see an error, post the actual link we need to update here. Your edit privileges were revoked when you defaced the wiki. |
|
|
|
And we haven't brought out our most important person yet: God. Remember God is the true answer to lifes problems and he wants us to put our burdens on him.
I think we should organize a fast for this problem (when two or more are gathered in his name - miracles happen).
A BiblePay fast for a recovery of our stability for the continuance of our orphan base.
I say we do the fast, and wait on the proposal until after. Show God we have faith he will make happen what he wants to, and make sure we're not reacting to the pressures of this world. I will also join the fast  This is a very important crossroads, and we should really contemplate the possible outcomes of our decision. Don't worry, this is not some quickie proposal with a quick outcome. I planned on leaving the proposal up for a couple weeks to get a solid feel of the outcome. What I do hope to achieve however is a solid feel for the outcome in 10 more days, so I can take that to programming and we can test it and have a resolution for our Sept 30th mandatory upgrade path. As I feel the changes will be very positive for our next mandatory. So that should work pretty well with our fast schedule also. Thanks for joining the fast! We need it! |
|
|
|
Do we have any cryptocurrency Or SEC Or FINRA attorneys in our group? Please e-mail me: rob@biblepay.org for potential new work. |
|
|
|
This is primarily aimed at Every other team out there: US Navy, Oracle, Overclock Forums, etc, everyone.
Good point. Don't you see this as low hanging fruit, but eventually you will run out of people to recruit? Sure, some will hold/stake because of the RAC requirement. The other side is daily use to increase transaction counts. Supporting "orphans" is a beautiful cause, but I feel this is not a utility of the coin since it comes from the monthly superblock and only involvement by the people is yes/no vote. How do we commit sponsorship to the individual wallet holders? This is good long term for BBP and good long term for the sponsored children. No, I think with 50,000 active CPIDs out there, we would have a lot more growth on the PODC side. But yes, obviously we should create a real PR campaign in parallel and work on IPFS and DAHF for VAR growth. |
|
|
|
To confirm, you would blacklist GridCoin and grcpool? So, then, who else besides GridCoin would want to join BBP and stay on their current team? Hard[OCP]? I'm not saying specifically, I'm saying users should report to us conditions where they could double dip, and we can consider adding that team number to a blacklist. My job is to make the wallet capable of honoring the blacklist spork values. As far as who else would join, LOL, no, 99% of the boinc world would join! Come on, every single person in Rosetta and WCG will end up sending a forum message saying Biblepay is paying for volunteer computing! This is primarily aimed at Every other team out there: US Navy, Oracle, Overclock Forums, etc, everyone. |
|
|
|
A BiblePay fast for a recovery of our stability for the continuance of our orphan base.
Is that your desire, or is it God's desire for us? He works in mystery ways and his will may or may not be aligned with what we want in this specific situation. Having said that, a fast is a great idea and let's be hungry for Jesus. Whenever you have hunger pains, let it be what inspires you to hunger more for Jesus. There are 4 distinct issues here: Praying for something unholy, Organizing a fast for really good reasons, asking our spiritual father for help, and then Gods sovereign will to bless this project. Imho, I feel the Holy Spirit will come down on me hard if I asked anyone to pray for something unholy; I definitely do not wish to pray for price appreciation or personal gain for our personal sake; I pray for Sustainability of the project. Actually when we were hovering around 30 for a while I was pretty happy and I think that led to some complacency; we should be more proactive. But moving on I think God would really want us to promote fasts in his name! This is a great cause, and on a side note I feel its really time for a fast anyway for some other reasons (part of what I noted with Trump, although those may be my own personal beliefs, thats why I said your own Presidents). Ill be praying for extended Grace to America as we close in on 9-11 for multiple reasons. I believe his sovereign will to bless this project is distinct from a push for a fast. |
|
|
|
In light of a lot of resistance in removing the UTXO requirement, the proposal has been changed to only remove the team requirement for now: https://forum.biblepay.org/index.php?topic=246.15And now we will leave in the UTXO requirement. Please modify your NO votes in accordance with the change. |
|
|
|
** BIBLEPAY SUSTAINABILITY FAST - COMING SOON **
Target Date: September 5th - September 11th 2018 Duration: 7 Days Type: Daniel Fast Reasons: Peace and safety for our global orphans, extended Grace to America (and your local country), continuance of President Trump (and your Countries President) so as Gods will is exercised, Sustainability of Biblepay, a call of Repentance to the lukewarm, and an invitation by God to non-believers. And more by Your requests. If you have more Fast suggestions (to include in our agenda and prayer lists) please e-mail me : rob@biblepay.org and I will add them to our agenda. I hope many of you will participate. If we can get 10 people together, I think God will hear us.
|
|
|
|
I agree that - sadly - sponsoring 300+ children probably just isn't sustainable in our current condition.
If our buffer runs out and we decrease then we decrease, but I dont think we should go down without trying, for the sake of the kids. And we haven't brought out our most important person yet: God. Remember God is the true answer to lifes problems and he wants us to put our burdens on him. I think we should organize a fast for this problem (when two or more are gathered in his name - miracles happen). A BiblePay fast for a recovery of our stability for the continuance of our orphan base. Regarding the proposal, I am not convinced yet that more miners would not help us grow. Broad adoption is obviously better, and broad adoption for free is obviously better than an airdrop. We are paying 1 million BBP right now through Jaap for almost the same effect we might have every day for free with the broad user base. The only thing so far I dont like about the proposal is what West mentioned about 'double dipping'. I never did like that possibility. We could offer the ability to create a spork that contains a string of blacklisted team numbers (and I mean in no way any disrespect to the teams, this is precisely to prevent double dipping). Any team that is alerted on the forum of paying in another crypto for the same work could be added to the key (IE blacklisted) and that would prevent double dipping, except where other coins like BiblePay do not require a team. Another words: users who are part of a blacklisted team are not compensated in bbp. |
|
|
|
Is anyone here a DASH user?
I'm considering that we tighten down requirements for sanctuaries running watchman on the wall.
Could you please run this spork in DASH prod and let us know what the value is for this:
From the rpc type:
spork show:
Paste value of : SPORK_14_REQUIRE_SENTINEL_FLAG
I have a DASH wallet spork show
{
"SPORK_2_INSTANTSEND_ENABLED": 0,
"SPORK_3_INSTANTSEND_BLOCK_FILTERING": 0,
"SPORK_5_INSTANTSEND_MAX_VALUE": 2000,
"SPORK_6_NEW_SIGS": 4000000000,
"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT": 0,
"SPORK_9_SUPERBLOCKS_ENABLED": 0,
"SPORK_10_MASTERNODE_PAY_UPDATED_NODES": 4000000000,
"SPORK_12_RECONSIDER_BLOCKS": 0,
"SPORK_14_REQUIRE_SENTINEL_FLAG": 4000000000
}
Github: https://github.com/dashpay/dash/blob/master/src/spork.cpp#L28Thanks. I enabled the Requirement of running watchman on the wall. Technically, within 24 hours, all the masternodes in WATCHDOG_EXPIRED state should fail to be paid (as the sancs vote for each other). |
|
|
|
rac 15k is way too high, you will see, if no staking req will means that wallet could be offline, then it will be one time setup per 1 powerfull pc and once per month you will start wallet, move coins away and viola... Prices of 100 satoshi and high efficiency wallets sounds good to me... Rather than dropping prices and a choked stagnant growth cycle. |
|
|
|
|
Is anyone here a DASH user?
I'm considering that we tighten down requirements for sanctuaries running watchman on the wall.
Could you please run this spork in DASH prod and let us know what the value is for this:
From the rpc type:
spork show:
Paste value of : SPORK_14_REQUIRE_SENTINEL_FLAG
|
|
|
|
i'm in, we can try it i just not agree for removing stake for magnitudes below 1. magnitude 1= about 10k rac now, this is far above 'some home pc'. dual x5650 (24 core) can do 13k rac. so this can end with splitting accounts into small ones and putting one powerfull pc to 1 account without staking. and over time, more users = lower magnitude with same rac, so more powerfull pc can be included to account below 1mag. who can afford powrfull pc, can also buy bbp... in my opinion, it should be rac, not mag. about 5000 rac is enough (some older 4c/8t i7 pc, running 24/7). this will also prevent creating many accounts with 1 pc as better PCs will needs more accounts and it will be harder to maintain (but still possible ) I like your reasoning. I'll modify the proposal to be for a RAC threshhold instead. We can make a network spork for 'racthreshhold'. If the proposal passes we set it to 15000 RAC. The main reason I like RAC better from an IT perspective is the magnitude assessment algorithm has a better idea about RAC than magnitude in the creation phase so this is a more superior solution. If RAC < 15000, no UTXO required for our users. |
|
|
|
|
Guys/Girls,
I have to ask everyone to entertain this idea; I know the last time I mentioned this I encountered a little resistance (I think from a small group of miners who might be set in their ways because they have a high amount staked in PODC currently), but regardless of the political situation here at Biblepay I have to do what I think is best for our orphans. We have 329 orphans sitting at risk currently with a questionable future. I not only want to avoid attrition, I want to see growth!
So heres an idea. I really think we need to consider removing all the roadblocks inside Biblepay (IE Opening the Floodgates) for cancer mining. We can consider doing this by: Removing the Boinc team requirement (being the first cryptocurrency to not require a team for boinc), and making it easier to heat-mine. (IE doing away with the last 4 block rule). (We can leave in the signed by CPID rule as a lateral move preserving heat-mining security).
I feel with this change, we can test the theory that more miners = more adoption = higher price = more monthly orphan sponsorships.
To make this fair, what we could do is adopt this strategy for 6 months, and if it fails miserably, we can vote to come back to a Biblepay team structure.
Also, as Noxpost suggested, I dont see why we cant write our own boincstats report (as we will still have records of our Biblepay participating CPIDs, RAC, TotalRAC etc). So we really only lose the "BiblePay BOINC Team" statistics in boincstats, but instead we have our own stats page. Maybe that internal stats website is something T-Mike would like to take on for us?
So, as you can see I'm pretty zealous for success here, and want us to make a comeback. Therefore I believe its in our best interests to vote on this change.
In light of this, I will create a Sanctuary vote proposal for this idea.
If it passes, we would shoot for the changes being in our next mandatory around the end of September. However we would shoot for testing these changes in testnet in 14 days.
(On a side note, if this is passing we will take the opportunity to do some extra refactoring of the heat-mining-block-acceptor to help prevent future forks).
|
|
|
|
I have a few questions about the masternode guide "Create Sanctuary 2" at http://wiki.biblepay.org/Create_Sanctuary_2 1) Steps 2b and 2c (in PART E below) seem redundant. Are both steps required? 2) From where does the control wallet get the masternode outputs info in step 4.a and what could cause it NOT to generate a TRANSACTIONHASH & INDEX string? 3) Following the steps in PART E below, at what point is the 1550001 BBP locked? 4) I try to start a new masternode in MISSING status from the Win control wallet but get this Error: Could not allocate txin (TRANSACTION HASH & INDEX string) for masternode (IP:40000). Also the remote linux/vps command ./biblepay-cli masternode status returns the following: "vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )", "service": "51.15.224.106:40000", "status": "Not capable masternode: Masternode not in masternode list" -------------------------------------------------------------------- PART E - Financing your Sanctuary (Masternode) 1. Generate private key on Sanctuary remote Linux machine ./biblepay-cli masternode genkey (Store this as your SANCTUARY_PRIVATE_KEY) 2. Local Windows Controller Wallet - Show Proof of Coins Create a unique name (SANCTUARY_NAME) for the address you will be storing your coins in and send the required 1,550,001 coins to that address 2a. Create Masternode Coin Address with Label Tools >> Debug Console getaccountaddress SANCTUARY_NAME this creates your SANCTUARY_ADDRESS getaccountaddress: https://chainquery.com/bitcoin-api/getaccountaddress2b. Combine All Your Coins into One Address
File >> Receiving Addresses >> Right click Copy Address (this is your RECEIVING_ADDRESS)
Send all of your wallet coins to this one address
Tools >> Debug Console
sendtoaddress RECEIVING_ADDRESS 1550001 "" ""
sendtoaddress: https://chainquery.com/bitcoin-api/sendtoaddress
2c. Send Required Coins to Newly Created SANCTUARY_ADDRESS from step 2a
Enable Coin Control: Settings >> Options >> Wallet >> Click "Enable coin control features" checkbox >> Ok
Send >> Inputs >> Click Checkboxes of which Address(es) to Send Coins From
Send exactly 1550001 coinsNOTE: Fees are OK as long as you dont click the checkbox to Subtract fees. Fees are stored in a different vector NOTE: Important thing is to make the amount exactly 1550001 and dont click instant send or any other options NOTE: Coin Control will allow you to send coins from a specific address and not move coins you already set aside in other addresses https://www.dash.org/forum/threads/how-to-send-1000-dash-from-a-specific-address-in-the-wallet.15926/2d. Record Transaction Hash Open the Explorer: https://biblepay-explorer.org/Enter in your SANCTUARY_ADDRESS Record Latest Hash for your 1,550,001 deposit (TRANSACTIONHASH) 3. Wait for 7-8 or so confirmations (at 7 minute block rate, that will be around 1 hour) 4.a Controller Windows Wallet - Get TRANSACTIONHASH and INDEX from running this command:
Tools >> Debug Console
masternode outputs
You will get a string that looks like this:
{
"06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb" : "0",
}
The long string is your TRANSACTIONHASH, and the last number is the INDEX. This one is pretty easy if your more of IT geek: http://wiki.biblepay.org/Create_SanctuaryLet us know what specific issue you have while going through this one. I think one of the pitfalls in the easy to use guide is people are confused what computer they are on. |
|
|
|
On Google Chrome, biblepaycore.exe download was unsuccessful. I tried again, it didn't get the message. Strange. Says Failed - Virus scan failed. https://support.google.com/chrome/answer/2898334?hl=en&rd=2#virusStrangely enough, biblepaycore32.exe downloaded okay (1.1.4.7) When I ran it, I got this message: Windows protected your PC
Windows Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.
More info
App: biblepaycore32.exe
Publisher: Unknown publisher
Can "Publisher" information become known to Microsoft somehow to help mitigate these warnings? Trying windows 64 on chrome, it does Not say "Virus scan failed". |
|
|
|
post was too long to have both logs in the same post. valgrind output:
==14110== Memcheck, a memory error detector
==14110== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==14110== Using Valgrup, boost::optional<int> >, boost::signals2::slot1<bool, CNode*, boost::function<bool(CNode*)> >, boost::signals2::mutex> > > (result_type_wrapper.hpp:53)
==14111== by 0x335180: operator() (signal_template.hpp:246)
==14111== by 0x335180: operator() (signal_template.hpp:718)
==14111== by 0x335180: ThreadMessageHandler() (net.cpp:1790)
Thanks for the logs! Unfortunately valgrind has to be run on the actual source file (./biblepay-qt) with the cpp files present on the drive in order for us to see the line # in the report. The log above (debug.log) didnt have the very last shutdown section in it. But please try 1.1.4.7 and see if it solves the problem. We removed the condition that happened this morning for two users. |
|
|
|
Windows 1.1.4.7 is ready now for testnet. |
|
|
|
Maybe we could change the title of the thread while we're at it? This was a good suggestion: 🕇 BiblePay | Masternode Governance | CPU only | Help cure diseases | 10% to charity 🕇 Jaap when you get a chance, can you send me the biblepay web site export files for a static site? Ill take a stab at creating an IPFS version. I'll update the OP btw today, but never got a PM or email from anyone as to what they want added - I assume someone wanted something added about the airdrop. |
|
|
|
|
Show Posts
