Everything in the pool stays the same, but a Pre-Sanctuary block was 18,000 BBP, and a Post sanctuary block is 9,000 or so.
So you will see in block distribution, a lower payment realized based on Blocks Solved by the Pool that are Lower in total subsidy.
Okay sorry I do not understand with all that jargon in the way. Lets say I am making 100 shares total in 'my leaderboard' Then in Reports > Transaction History I see a payment of 50 . It will then still report these numbers? Or 40% off that. Very confusing. Forget that shares terminology, that stays the same. Click on Reports | Block distribution, and look at one of your payments. Realize that in the future, that total block subsidy is going to be about half. |
|
|
|
Fresh linux install gets error loading block database. Do you want to rebuild the block detabasenow? Y/n doesnt do anything
You could do yes, or just : rm blocks -R rm chainstate -R Restart Thanks for supporting us  |
|
|
|
Rob,
does it mean "masternode winners" command shows wining nodes ahead of the actual payouts ?
If node is "pre enabled" does it take part in voting and has a chance to win?
Is it statistically fair in the long run and gives all nodes equal payouts in the long run ?
thanks JC , I'm completely new to this .
so "pre enabled" nodes are out of the game , aren't they?
So in addition to what JC said, we need 10+ votes for a payment "quorum", so once those numbers hit over 10 we should see payments start. As far as "luck" of winning the spot, we are using an algorithm where the nodes rank is determined by how close its vin is to the blockhash its voting on, so its really luck. Yes, pre-enabled means no chance of winning the vote, as the sanctuary is not trusted yet. I just sent alex an instantsend in about 10 seconds, it was very very sweet. How will these new payments to masternodes affect non masternode people? Will we get less shares as a result? Yes- they take 40% of every block. So shares reported in 'My Leaderboard' is before or after that? The mining credit is that the real share given or 40% of that? Everything in the pool stays the same, but a Pre-Sanctuary block was 18,000 BBP, and a Post sanctuary block is 9,000 or so. So you will see in block distribution, a lower payment realized based on Blocks Solved by the Pool that are Lower in total subsidy. |
|
|
|
Rob,
does it mean "masternode winners" command shows wining nodes ahead of the actual payouts ?
If node is "pre enabled" does it take part in voting and has a chance to win?
Is it statistically fair in the long run and gives all nodes equal payouts in the long run ?
thanks JC , I'm completely new to this .
so "pre enabled" nodes are out of the game , aren't they?
So in addition to what JC said, we need 10+ votes for a payment "quorum", so once those numbers hit over 10 we should see payments start. As far as "luck" of winning the spot, we are using an algorithm where the nodes rank is determined by how close its vin is to the blockhash its voting on, so its really luck. Yes, pre-enabled means no chance of winning the vote, as the sanctuary is not trusted yet. I just sent alex an instantsend in about 10 seconds, it was very very sweet. How will these new payments to masternodes affect non masternode people? Will we get less shares as a result? Yes- they take 40% of every block. |
|
|
|
Rob,
does it mean "masternode winners" command shows wining nodes ahead of the actual payouts ?
If node is "pre enabled" does it take part in voting and has a chance to win?
Is it statistically fair in the long run and gives all nodes equal payouts in the long run ?
thanks JC , I'm completely new to this .
so "pre enabled" nodes are out of the game , aren't they?
So in addition to what JC said, we need 10+ votes for a payment "quorum", so once those numbers hit over 10 we should see payments start. As far as "luck" of winning the spot, we are using an algorithm where the nodes rank is determined by how close its vin is to the blockhash its voting on, so its really luck. Yes, pre-enabled means no chance of winning the vote, as the sanctuary is not trusted yet. I just sent alex an instantsend in about 10 seconds, it was very very sweet. |
|
|
|
Please ensure your sanctuaries are started. We have payments coming up in only 25 blocks.
That is our next huge milestone.
Rob, I can't set up my sanctuary until I get access to the BBP in my c-cex account. Is it possible to have them allow/schedule a withdrawal time frame before they leave for the month vacation? I'd love to get the sanctuary up and running right away. Thanks! Hmmm, not sure if he will have time, I just skyped him this morning and he said he is going to be shutting down all wallets for the entire trip. We do have to ensure all of our features work before we can ask, so lets ensure our sanctuary payments are actually flowing properly, we have to ensure this mandatory is safe for exchange consumption. Please PM me with how much you are short. |
|
|
|
looks like still no masternode reward
We are analyzing in slack, everything looks OK. The way it works is each ENABLED Sanctuary has a right to vote for itself. So far 282 votes have been cast and there has to be a quorum of 10 sanctuaries to approve a payment. So this could take a while. We just read a message that the Sancs cleared out 35 blocks of prior voting, so I believe everything is moving smoothly toward payments. I audited blocks 21600-21605 and so far, no payments have been attempted. |
|
|
|
If I clear the biblepay.conf is works fine but can't mine.
Could you see if the data is stored in %appdata%\biblepaycore Just see if that folder has complete admin rights? Is biblepay-qt unblocked, and has rights to run as admin? Try renaming wallet.dat to wallet.old and see if it runs with a config? Maybe try installing this on another PC, just for kicks and get it mining, it might be revealing, somehow. EDIT: One more thing, ensure in windows you create the file with notepad. In windows you need a CRLF between each line (not a CR). Ive backed up my wallet, renamed wallet.dat to wallet.old. Issue no longer persisted. All those funds, how do I get them to the new wallet? Running with the old wallet and without a config file, go to Receiving Addresses and copy them all to notepad. Then from the RPC type: dumpprivkey each_pubkey For each public key. Copy the private key(s) to notepad. From the new wallet, type importprivkey privkey. For each private key. Then rescan your wallet by restarting with -rescan. Good luck buddy. EDIT: Btw, check your backups folder for an old wallet. If you can boot from one that was not corrupted yet, you are probably back in business without a new wallet. EDIT2: Another option is booting with -salvagewallet. It supposedly rebuilds the wallet. |
|
|
|
If I clear the biblepay.conf is works fine but can't mine.
Could you see if the data is stored in %appdata%\biblepaycore Just see if that folder has complete admin rights? Is biblepay-qt unblocked, and has rights to run as admin? Try renaming wallet.dat to wallet.old and see if it runs with a config? Maybe try installing this on another PC, just for kicks and get it mining, it might be revealing, somehow. EDIT: One more thing, ensure in windows you create the file with notepad. In windows you need a CRLF between each line (not a CR). |
|
|
|
|
Great New Feature added by Luke (Znffal):
Go to the Pool
Click Help
See our new Help guides for:
Withdrawing Funds
Writing Letters to Orphans
Creating Workers
Creating Accounts
Thanks Luke, these are awesome imo!
|
|
|
|
Should not be giving runtime if its blank, but in this version, one click-mining setup works now. Could you please paste the error? But first, delete chainstate, blocks and mn*.dat from %appdata%\biblepaycore. Then restart. ---------- Runtime Error! Program C:\Program Files\BiblepayCore\biblepay-qt.exe This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ---------- 2017-12-18 00:56:20 init message: Memorizing Prayers... 2017-12-18 00:56:20 mapBlockIndex.size() = 1 2017-12-18 00:56:20 chainActive.Height() = 0 2017-12-18 00:56:20 setKeyPool.size() = 997 2017-12-18 00:56:20 mapWallet.size() = 46 2017-12-18 00:56:20 mapAddressBook.size() = 6 2017-12-18 00:56:20 init message: Loading addresses... 2017-12-18 00:56:20 torcontrol thread start 2017-12-18 00:56:20 ERROR: Read: Deserialize or I/O error - CAutoFile::read: end of file 2017-12-18 00:56:20 Invalid or missing banlist.dat; recreating 2017-12-18 00:56:20 Loaded 12979 addresses from peers.dat 56ms 2017-12-18 00:56:20 AddLocal([2605:a601:4240:79:99ce:3401:607b:9ef4]:40000,1) 2017-12-18 00:56:20 Discover: TATOOINE - 2605:a601:4240:79:99ce:3401:607b:9ef4 2017-12-18 00:56:20 AddLocal([2605:a601:4240:79:c0a8:7ec0:93fe:3ba7]:40000,1) 2017-12-18 00:56:20 Discover: TATOOINE - 2605:a601:4240:79:c0a8:7ec0:93fe:3ba7 2017-12-18 00:56:20 dnsseed thread start 2017-12-18 00:56:20 net thread start 2017-12-18 00:56:20 addcon thread start 2017-12-18 00:56:20 opencon thread start 2017-12-18 00:56:20 mnbcon thread start 2017-12-18 00:56:20 msghand thread start 2017-12-18 00:56:20 Starting Thread #0.000000 with Bible #0.000000 BibleMiner -- started thread 0.000000 2017-12-18 00:56:20 Starting Thread #1.000000 with Bible #0.000000 BibleMiner -- started thread 1.000000 2017-12-18 00:56:20 Starting Thread #2.000000 with Bible #0.000000 BibleMiner -- started thread 2.000000 2017-12-18 00:56:21 Starting Thread #3.000000 with Bible #0.000000 BibleMiner -- started thread 3.000000 2017-12-18 00:56:21 ** Started 4.000000 BibleMiner threads. ** 2017-12-18 00:56:21 init message: Done loading ---------------- the issue may be the banlist.dat - I created an empty file but I don't think that works lol ----------------- Reminder, this issue only happens when I put info in the biblepay.conf either by the one click mining option or by manually inputting using the guide in reddit. Thats not normal, could you try adding : debug=true debugmaster=true and also, try the 32bit version of the code just for kicks? I cant think of a reason a populated conf would cause a crash. Maybe you have a corrupted EXE, because I did have a bad deploy today. Maybe try redownloading, then reinstall both 32 & 64 bit, and try the 32 for kicks? |
|
|
|
From my google searching of keywords, I would DEFINITLEY advise masternode.pro, they are the top google result for the various "masternode" keyword variations, but I dont know their fees yet
If anyone could submit another form to them, that would be awesome!,
I just contacted them again in Discord, but I think they are asleep
Good news, we will be listed on masternode.pro tonight! Jason from masternode.pro contacted me back in the Discord! "mnp_jason - Today at 10:23 AM @Togoshige i will get it listed tonight" I will post more details as I find out more [/quote] Great work Togo! THANKS! This is awesome...
https://masternodes.online/ |
|
|
|
Should not be giving runtime if its blank, but in this version, one click-mining setup works now. Could you please paste the error? But first, delete chainstate, blocks and mn*.dat from %appdata%\biblepaycore. Then restart. |
|
|
|
BiblePay - 1.0.6.8c
Miners Of Men
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section This worked for me and now my Windows Wallet is up to date and on block 21579 Yes, thanks this worked. So nsummy will have to update the minersofmen pool, too for continued mining and withdrawals? Yes. His about page is frozen so maybe he is doing it now. Or maybe his biblepayd is crashed. |
|
|
|
|
Alright, some good news: Our tithe blocks have officially ended. 21580 went to the pool.
The pool is now paying for tithe blocks also.
|
|
|
|
BiblePay - 1.0.6.8c
Mandatory Upgrade
- Disable tithe blocks at #21565
- Ensure Sanctuary payments can go live at #21600
- Increment mandatory protocol version to 70911
- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551
** This is the windows release. Please upgrade to 1068 if you have not. Linux upgraded 4 hours ago **
http://biblepay.org/ ---> Downloads section Windows Cleanup: - File Explorer: %appdata%/BiblePayCore - Delete blocks and chainstate folders, delete banlist, fee_estimates, governance, mncache, netfulfiled and peers - Add this line to biblepay.conf: addnode=node.biblepay-explorer.org - In Wallet do Tools >> Wallet Repair >> Rebuild index This worked for me and now my Windows Wallet is up to date and on block 21579 Once again: thank you for your help Togo (and of course also Rob, Alex and everyone else)! My windows wallet seems in sync and the masternodelist seems to be populating again. Let's hope everything goes well this time Yes and thank you for all your help also. Lets hope we fly past 21600 without a problem as I would love to tackle more IT problems in one day in production, it would be great to pull a triple (long hour workday) today in IT, it excites me, and Alex said he stayed up all night last night, he likes it also, so we have a great team forming. The good news is we should know within 2 hrs, making this an exciting day for IT. That is our last big hurdle, as budgets and superblocks were tested in a way that will not be a threat to forking the chain (as masternode payments will be). Of course we do need to check these masternode payments after block 21600! Lets get ready to do that also. I remember 616 was mentioning this morning the payments were doubled and tripled, but looking at that issue mid-day, those were not actually masternode payments. To see those, grab the block, grab the transaction in the coinbase and type 'getrawtransaction coinbasetxid 1', then analyze the vout[1] (vout[0] is the miner who mined the block, vout[1] is the sanctuary payment). Ensure the sanc payment is correct amount, (it should be nBlockAmount - nBlockDistribution Deductions, * .40 ). Then ensure the payee is in the payee vector in order ( we can look at the masternode list ). |
|
|
|
I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution?
I'm in the same boat with a transaction cashing out from the pool.... Any help would be appreciated. I credited it, please withdraw again. |
|
|
|
 I have a transaction that sent at early version which is stucked at unconfirmed status. Any solution? I saw there are 2 buttons at Wallet repair - "Recover transactions 1" and "Recover transactions 2", is it the solution? If yes, which button should I use? Thanks! You can try "resendwallettransactions" from the RPC, but I did that earlier today and it failed. If that does not work, restart with -zapwallettxes and it will clear it. |
|
|
|
|
I'm attempting to rebroadcast the last 6 withdrawals from the pool, they are all unconfirmed. This way we will be able to trace the txids.
EDIT:
I credited the withdraws that failed to go out. Please withdraw again.
|
|
|
|
|
Show Posts
