Macko said he's forking BiblePay. Does anyone have any info on the ticker or OP post?
I saw the problem before, I wrote ...
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 136. (Read 243386 times)
June 27, 2019, 05:34:20 PM
I saw the problem before, I wrote ...
June 27, 2019, 05:00:54 PM
It’s unfortunate to hear this news, which means no need to test the new mining function of ABN....
Yes, I know. I was hoping for a community known for advanced features, but each advanced feature is very elusive in the block chain world. You have to create a feature in a decentralized way doing at least 10* the work, and debug it with 10 man years for it to pass enough tests vigorously to stay in prod.
But, Im still very very optimistic because Cameroon Ones feature is passing in the Sanc poll, and that alone will be very good to be known by - a community with 100 self sponsored orphans with pass through payments is pretty impressive. (It also gives us 501c3 donations and tax deductions, and bitcoin miner donations capabilities, and makes us a DAC).
Let's look forward to that towards the end of July.
I encourage you to stay persistent. I think ABN can work with more testing. We were ramping up the cores being able to mine. I think if you had a requirement of 1 input of 256k BBP w/ 205 confirmation and the output generates 1 x 256k BBP, this is makes it easier to communicate to other people and easier to calculate I assume. Not as fancy as the current setup, but probably easier to troubleshoot and explain to others.
Or other ideas like this that is test on another altcoin:
After executing a single SHA256 hash on the miner’s reward address, the last character found must match the last character of the block hash value submitted by the miner in the candidate block. This randomizes who can actually win the block. Even the fastest miner can’t be guaranteed to win the block or a series of blocks in succession. The chances are 1 in 16 that the miner will be able to win the block (http://cdn.getlynx.io/2019-03-17_Lynx_Whitepaper_v1.1.pdf page 16)
June 27, 2019, 02:58:09 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
Rob, could you post here the current top block hash ?
I ran my global report, and see no forks at all, so maybe I jumped the gun, but the decision is already complete, I can't go back on it. Let's stay with pure POBH for now.
So the hash is :
getblockhash 128163
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
Agreeing with our explorer:
https://chainz.cryptoid.info/bbp/block.dws?128163.htm
The pool has resynced to the same block as the explorer; so we don't actually have any forks.
does it mean my sanctuary is out of sync ?
Code:
"protocolversion": 70733,
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
Yes - please re-sync.
Please, anyone else that disagrees with the 128163 hash posted - please post. Id like to know that no one else other than Tiras' sanctuary disagrees.
Because I ran a report that showed 100% were in agreement to the 128163 hash - not one was out of sync across the world in all datacenters.
I emailed SX to check also.
resyncing controller MN
In the miners wallet though top block is matching your hash but 128158 is different from that on my sanctuary ...
it's unlikely sanctuary went on the fork , right ?
Miner:
Code:
15:43:45

getblockhash 128163
15:43:45
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
15:44:09
getblockhash 128158
15:44:09
92c5bb76c6c01fe1e2582452a223b6273a72cc0c8936c717f2b39c47fdf4161c

getblockhash 128163
15:43:45
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
15:44:09
getblockhash 128158
15:44:09
92c5bb76c6c01fe1e2582452a223b6273a72cc0c8936c717f2b39c47fdf4161c
Sanc:
Code:
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
The correct hash for 128158 was 92c5bb it looks like. I don't know why that sanc went off on a fork (unless it has a strange error in its log right before 128158 height).
But yeah looks like that 128158 sanc needs resynced.
June 27, 2019, 02:48:43 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
Rob, could you post here the current top block hash ?
I ran my global report, and see no forks at all, so maybe I jumped the gun, but the decision is already complete, I can't go back on it. Let's stay with pure POBH for now.
So the hash is :
getblockhash 128163
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
Agreeing with our explorer:
https://chainz.cryptoid.info/bbp/block.dws?128163.htm
The pool has resynced to the same block as the explorer; so we don't actually have any forks.
does it mean my sanctuary is out of sync ?
Code:
"protocolversion": 70733,
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
Yes - please re-sync.
Please, anyone else that disagrees with the 128163 hash posted - please post. Id like to know that no one else other than Tiras' sanctuary disagrees.
Because I ran a report that showed 100% were in agreement to the 128163 hash - not one was out of sync across the world in all datacenters.
I emailed SX to check also.
resyncing controller MN
In the miners wallet though top block is matching your hash but 128158 is different from that on my sanctuary ...
it's unlikely sanctuary went on the fork , right ?
Miner:
Code:
15:43:45

getblockhash 128163
15:43:45
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
15:44:09
getblockhash 128158
15:44:09
92c5bb76c6c01fe1e2582452a223b6273a72cc0c8936c717f2b39c47fdf4161c

getblockhash 128163
15:43:45
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
15:44:09
getblockhash 128158
15:44:09
92c5bb76c6c01fe1e2582452a223b6273a72cc0c8936c717f2b39c47fdf4161c
Sanc:
Code:
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
June 27, 2019, 02:41:27 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
Rob, could you post here the current top block hash ?
I ran my global report, and see no forks at all, so maybe I jumped the gun, but the decision is already complete, I can't go back on it. Let's stay with pure POBH for now.
So the hash is :
getblockhash 128163
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
Agreeing with our explorer:
https://chainz.cryptoid.info/bbp/block.dws?128163.htm
The pool has resynced to the same block as the explorer; so we don't actually have any forks.
does it mean my sanctuary is out of sync ?
Code:
"protocolversion": 70733,
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
Yes - please re-sync.
Please, anyone else that disagrees with the 128163 hash posted - please post. Id like to know that no one else other than Tiras' sanctuary disagrees.
Because I ran a report that showed 100% were in agreement to the 128163 hash - not one was out of sync across the world in all datacenters.
I emailed SX to check also.
June 27, 2019, 02:38:01 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
Rob, could you post here the current top block hash ?
I ran my global report, and see no forks at all, so maybe I jumped the gun, but the decision is already complete, I can't go back on it. Let's stay with pure POBH for now.
So the hash is :
getblockhash 128163
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
Agreeing with our explorer:
https://chainz.cryptoid.info/bbp/block.dws?128163.htm
The pool has resynced to the same block as the explorer; so we don't actually have any forks.
does it mean my sanctuary is out of sync ?
Code:
"protocolversion": 70733,
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
"balance": 0.00032649,
"blocks": 128158,
# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range
biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7
June 27, 2019, 02:37:50 PM
so whats now? 
i see that all my machines started mining now
POG is also retired?
i see that all my machines started mining now
POG is also retired?
No, just ABN is retired. I just want to make sure we have a high difficulty and we have a fork-free life.
We still have our GSCs, POG, Healing, and Cameroon One coming soon.
Next smart contract is @ 128350.
June 27, 2019, 02:35:22 PM
so whats now?
i see that all my machines started mining now
POG is also retired?
i see that all my machines started mining now
POG is also retired?
June 27, 2019, 02:26:01 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
Rob, could you post here the current top block hash ?
I ran my global report, and see no forks at all, so maybe I jumped the gun, but the decision is already complete, I can't go back on it. Let's stay with pure POBH for now.
So the hash is :
getblockhash 128163
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
Agreeing with our explorer:
https://chainz.cryptoid.info/bbp/block.dws?128163.htm
The pool has resynced to the same block as the explorer; so we don't actually have any forks.
June 27, 2019, 02:24:17 PM
It’s unfortunate to hear this news, which means no need to test the new mining function of ABN....
Yes, I know. I was hoping for a community known for advanced features, but each advanced feature is very elusive in the block chain world. You have to create a feature in a decentralized way doing at least 10* the work, and debug it with 10 man years for it to pass enough tests vigorously to stay in prod.
But, Im still very very optimistic because Cameroon Ones feature is passing in the Sanc poll, and that alone will be very good to be known by - a community with 100 self sponsored orphans with pass through payments is pretty impressive. (It also gives us 501c3 donations and tax deductions, and bitcoin miner donations capabilities, and makes us a DAC).
Let's look forward to that towards the end of July.
June 27, 2019, 02:22:53 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
Rob, could you post here the current top block hash ?
June 27, 2019, 02:20:16 PM
It’s unfortunate to hear this news, which means no need to test the new mining function of ABN....
So now is using back the old model - POBH ?
So now is using back the old model - POBH ?
June 27, 2019, 02:10:47 PM
So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
So I believe this happened because of the very low difficulty ABN affords us.
In light of that, I have decided to shut down ABN.
We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).
SECURITY IS #1 WITH BIBLEPAY
In light of this, ABN is being retired for the time being.
The ABN weight requirement will dissapear in a few more blocks.
In the mean time, Im going to run a report network wide to verify that we have one heavy chain.
The pool is resyncing.
June 27, 2019, 02:00:24 PM
it's happening right now at the pool :
Whats happening? Should we all sell?
probably
Thanks, thats what I was wondering about you.
you got me Rob , no kidding
instead of just commenting why most miners go with 99% errors .....
June 27, 2019, 02:00:05 PM
until now everything goes well, but now i'm not mining even if abn weight is over 256k
i'm again lost in numbers so here are logs
2019-06-27 18:55:50
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:51
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:52
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:53
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:55
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
biblepay-cli exec getabnweight 256000 1
{
"Command": "getabnweight",
"version": 1.2,
"weight": 391767.0227314815,
"total_required": 2814146,
"coin_age_data_pre_select": "2.0705(0.76)=[1.51] depth=161, \n6599.0000(0.34)=[2228.61] depth=74, \n3078.3803(1.63)=[5010.66] depth=353, \n19600.0000(0.74)=[14552.32] depth=158, \n3234.2297(2.31)=[7461.00] depth=497, \n23750.0000(0.34)=[7987.31] depth=73, \n50281.0000(0.34)=[16968.09] depth=74, \n3156.9454(0.69)=[2185.06] depth=150, \n3098.2479(0.73)=[2254.26] depth=158, \n589735.5310(0.07)=[40496.50] depth=17, \n1804716.0300(0.07)=[123928.01] depth=17, \n3148.0506(0.85)=[2674.82] depth=185, \n2900.2653(1.22)=[3547.26] depth=265, \n64866.0000(0.34)=[21826.96] depth=73, \n3184.4436(1.24)=[3942.30] depth=270, \n3180.2484(0.58)=[1852.35] depth=128, \n",
"weight 256000.00": 256917.0167476852,
"total_required 256000.00": 2584530
}
biblepay-cli getinfo
{
"version": 1040309,
"protocolversion": 70734,
"walletversion": 61000,
"balance": 2814146.47145174,
"privatesend_balance": 0.00000000,
"blocks": 128157,
"timeoffset": 0,
"connections": 9,
"proxy": "",
"difficulty": 815.6984772165931,
"testnet": false,
"keypoololdest": 1513986561,
"keypoolsize": 1013,
"paytxfee": 0.00000000,
"relayfee": 0.01000000,
"errors": ""
}
biblepay-cli getmininginfo
{
"blocks": 128157,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 815.6984772165931,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 50,
"networkhashps": 222376.8235935041,
"hashps": 104792.0223031746,
"minerstarttime": "06-27-2019 00:11:03",
"hashcounter": 7057560364,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; ",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 256000
}
i'm again lost in numbers so here are logs
2019-06-27 18:55:50
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:51
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:52
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:53
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
2019-06-27 18:55:55
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64 *****
biblepay-cli exec getabnweight 256000 1
{
"Command": "getabnweight",
"version": 1.2,
"weight": 391767.0227314815,
"total_required": 2814146,
"coin_age_data_pre_select": "2.0705(0.76)=[1.51] depth=161, \n6599.0000(0.34)=[2228.61] depth=74, \n3078.3803(1.63)=[5010.66] depth=353, \n19600.0000(0.74)=[14552.32] depth=158, \n3234.2297(2.31)=[7461.00] depth=497, \n23750.0000(0.34)=[7987.31] depth=73, \n50281.0000(0.34)=[16968.09] depth=74, \n3156.9454(0.69)=[2185.06] depth=150, \n3098.2479(0.73)=[2254.26] depth=158, \n589735.5310(0.07)=[40496.50] depth=17, \n1804716.0300(0.07)=[123928.01] depth=17, \n3148.0506(0.85)=[2674.82] depth=185, \n2900.2653(1.22)=[3547.26] depth=265, \n64866.0000(0.34)=[21826.96] depth=73, \n3184.4436(1.24)=[3942.30] depth=270, \n3180.2484(0.58)=[1852.35] depth=128, \n",
"weight 256000.00": 256917.0167476852,
"total_required 256000.00": 2584530
}
biblepay-cli getinfo
{
"version": 1040309,
"protocolversion": 70734,
"walletversion": 61000,
"balance": 2814146.47145174,
"privatesend_balance": 0.00000000,
"blocks": 128157,
"timeoffset": 0,
"connections": 9,
"proxy": "",
"difficulty": 815.6984772165931,
"testnet": false,
"keypoololdest": 1513986561,
"keypoolsize": 1013,
"paytxfee": 0.00000000,
"relayfee": 0.01000000,
"errors": ""
}
biblepay-cli getmininginfo
{
"blocks": 128157,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 815.6984772165931,
"errors": "",
"pooledtx": 0,
"chain": "main",
"genproclimit": 50,
"networkhashps": 222376.8235935041,
"hashps": 104792.0223031746,
"minerstarttime": "06-27-2019 00:11:03",
"hashcounter": 7057560364,
"pooledtx": 0,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=256917, UsingBBP=2584530.00, I=25, NeededWeight=256000, GotWeight=212590.64; ",
"gsc_errors": "",
"poolmining": false,
"pool_url": "",
"required_abn_weight": 256000
}
June 27, 2019, 01:54:40 PM
it's happening right now at the pool :
Whats happening? Should we all sell?
probably
Thanks - dissapointed.
June 27, 2019, 01:52:41 PM
it's happening right now at the pool :
Whats happening? Should we all sell?
probably
June 27, 2019, 01:47:08 PM
it's happening right now at the pool :
Whats happening? Should we all sell?
June 27, 2019, 01:21:05 PM
it's happening right now at the pool :
June 27, 2019, 12:46:57 PM
Since I made an core wallet update from mars version to the last one, i lost 1Million BBP. Already tried options to restaure the losted transaction but nothing is working. Someone can help ?
How did you obtained that amount? (Mining, masternodes. buying in exchange, etc)
Some users that leave older versions mining unnatended usually fork from official chain and obtain funds by mining alone in their fork. But actually those funds don't exist because they are not in the official chain.
Buying and BOINC mining with many CPU.
I know i was on fork for 100 000 BBP, but i lost almost 1 Million BBP and still cain't get them back
If the missing 1M BBP was there before the last wallet update, it should be there now.
I assume you copied the wallet.dat file from %appdata%\BiblepayCore to new %appdata%\BiblepayEvolution folder, did you?
Its each of our individual responsibilities to keep a copy of wallet.dat offsite and backed up, relatively frequently.
But I'm sorry to hear about this.
I can only think of 2 options:
1) Go back to the original machine, and look in the \backups folder, and see if you have a more recent backup of the wallet.dat file.
or
2) You can potentially try to find file undeleter software that would recover the deleted wallet.dat file from the sectors of the disk. I lost some bitcoin way back when it was $1 per btc and when I used undeleter software, I was able to get the wallet.dat but in my case it was overwritten with a windows file and I lost all the BTC.
Jump to: