BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[eternalenvoy]

Thanks,  you just need enough ABN weight for one thread, and all the other mining threads will share it.

But if one finds a block, all will spend that ABN and stop (unless you have enough extra to continue mining).

That's mean whatever have how many weight amount at that moment, once founds a block, it will zero the weight and recalculate when hit successful?

Because in reality, I have stored about 5 million weight and begin start mining for test ABN, but after founds three block, the remaining is only about 1 million of weight.

[1714828722]

1714828722

[1714828722]

1714828722

[1714828722]

1714828722

[jsheets1970]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

[sunk818]

No problem (there's definitely some advantages to joining testnet testing)

=

Im interested to help clean up, but Id like to get paid for my time, I havent been paid for my time since November 2018 LOL

I believe Rob is still a few months behind on dev pay as well

Ill write a proposal for my past work

You wrote a proposal but the link is for the productions proposal forum. It is not clear what you've "done" for BBP in the last 8 month. Weren't you away for many months dealing with personal life? What's the 1M proposal for?

[jsheets1970]

Does anyone have a step by step current guide for compiling the unix version? Would like to see if compiling for a specific machine provides any increased hashing power. Please let me know or if you could send to me that would be awesome. jonathan.sheets@yahoo.com. Thanks in advance all.

[bible_pay]

Thanks,  you just need enough ABN weight for one thread, and all the other mining threads will share it.

But if one finds a block, all will spend that ABN and stop (unless you have enough extra to continue mining).

That's mean whatever have how many weight amount at that moment, once founds a block, it will zero the weight and recalculate when hit successful?

Because in reality, I have stored about 5 million weight and begin start mining for test ABN, but after founds three block, the remaining is only about 1 million of weight.

Not exactly, ABN is more graceful than that, and I think people dont see all the benefits of it yet.  One reason I think we should hang in there and be patient is right now the ROI on an ABN miner is very high (due to so much limited mining).  Meaning that more miners will come on board soon and fill the void.  That will actually make it very comfortable for most small miners as when diff rises to 10K again, small miners wont solve as many blocks and one ABN will last much longer.  (Just one day of coin age is enough to replenish an ABN and keep it going).  

But anyway to answer your question, we dont really pull the ABN and specifically set it to zero and track it - the ABN is simply what coin_age is left on your unspent outputs - so the nuance is - once you spend an abn - you have a new set of coin unspent outputs - that begin aging again - but you also have your older coins that were not spent that could be combined to make a new abn (for seamless mining).

[bible_pay]

Does anyone have a step by step current guide for compiling the unix version? Would like to see if compiling for a specific machine provides any increased hashing power. Please let me know or if you could send to me that would be awesome. jonathan.sheets@yahoo.com. Thanks in advance all.

This might not be what you want but please see this:

https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Also if you have a specific error, can you please paste it as we can probably help you get by it.

[bible_pay]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

[MIP]

Does anyone have a step by step current guide for compiling the unix version? Would like to see if compiling for a specific machine provides any increased hashing power. Please let me know or if you could send to me that would be awesome. jonathan.sheets@yahoo.com. Thanks in advance all.

I used this guide for my Evolution Linux compiles:

https://github.com/biblepay/biblepay-evolution/blob/master/doc/build-unix.md
https://github.com/biblepay/biblepay-evolution/blob/master/doc/build-generic.md

Not a step-by-step guide bit was enough for me.

If you want to cross-compile:
https://github.com/biblepay/biblepay-evolution/blob/master/doc/build-cross.md

Also you can PM me at discord if you want.

[bible_pay]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

So I took a look at your 'exec createabn 256000' transaction a little closer (as I dont see a problem with the exec getabnweight call), and here is the issue:

Code:

"Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}

Hone in on the "age_data" and look at the numbers in parentheses; specifically each spent BBP of 10000.0010 has a weight of 10135.65 in parentheses.

Technically, all the #s in parentheses should add up to the "GotWeight=" amount, but they dont.  You have 259K in weight in parentheses yet the GotWeight = 239.299K, why?

Looking at the code, there is no bug in the CreateAbn, or the CreateTransaction, making me wonder then how can it be off?

The main thing I suspect is we have a third place in BBP where we assess your weight (When we look at the VIN coin age).

The only way to find out why 2 of your coin-ages are missing, is if we put a feature in BBP that lets you dump the VIN coin age to the log, then you can compare the Found weight values with the Got Weight values and probably see 2 of the inputs in the ABN are either missing or have 0 coin age (for a reason we don't know of yet).

So, I will go ahead and put that feature in and tell you how to run it.

[jsheets1970]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

So I took a look at your 'exec createabn 256000' transaction a little closer (as I dont see a problem with the exec getabnweight call), and here is the issue:

Code:

"Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}

Hone in on the "age_data" and look at the numbers in parentheses; specifically each spent BBP of 10000.0010 has a weight of 10135.65 in parentheses.

Technically, all the #s in parentheses should add up to the "GotWeight=" amount, but they dont.  You have 259K in weight in parentheses yet the GotWeight = 239.299K, why?

Looking at the code, there is no bug in the CreateAbn, or the CreateTransaction, making me wonder then how can it be off?

The main thing I suspect is we have a third place in BBP where we assess your weight (When we look at the VIN coin age).

The only way to find out why 2 of your coin-ages are missing, is if we put a feature in BBP that lets you dump the VIN coin age to the log, then you can compare the Found weight values with the Got Weight values and probably see 2 of the inputs in the ABN are either missing or have 0 coin age (for a reason we don't know of yet).

So, I will go ahead and put that feature in and tell you how to run it.

Sounds good.. Did not want to come off as crazy at all or as a pain, was really just wondering how the numbers would be different. Obviously there are several factors which go into the calculation and I do not know them all so really was just trying to help ensure calculations were correct and to better understand which meant the most in terms of mining. So the more information the better to ensure calcs are indeed correct and working as you would expect.

[bible_pay]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

So I took a look at your 'exec createabn 256000' transaction a little closer (as I dont see a problem with the exec getabnweight call), and here is the issue:

Code:

"Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}

Hone in on the "age_data" and look at the numbers in parentheses; specifically each spent BBP of 10000.0010 has a weight of 10135.65 in parentheses.

Technically, all the #s in parentheses should add up to the "GotWeight=" amount, but they dont.  You have 259K in weight in parentheses yet the GotWeight = 239.299K, why?

Looking at the code, there is no bug in the CreateAbn, or the CreateTransaction, making me wonder then how can it be off?

The main thing I suspect is we have a third place in BBP where we assess your weight (When we look at the VIN coin age).

The only way to find out why 2 of your coin-ages are missing, is if we put a feature in BBP that lets you dump the VIN coin age to the log, then you can compare the Found weight values with the Got Weight values and probably see 2 of the inputs in the ABN are either missing or have 0 coin age (for a reason we don't know of yet).

So, I will go ahead and put that feature in and tell you how to run it.

Sounds good.. Did not want to come off as crazy at all or as a pain, was really just wondering how the numbers would be different. Obviously there are several factors which go into the calculation and I do not know them all so really was just trying to help ensure calculations were correct and to better understand which meant the most in terms of mining. So the more information the better to ensure calcs are indeed correct and working as you would expect.

Thanks, I appreciate all the help.

And yes once I am shown a crack exists and the numbers don't match, I am very zealous about getting it fixed, for all cases.

(If they didn't match due to being in a state of being spent, or aging that would be one thing, but when either the set doesnt match the other set, or when the age in the parentheses doesnt even add up to the age in the allocated amount then that points to a different assessment used by other nodes to see the age of your node).

I am adding a new feature now that shows a 3rd set - this is what the other node sees when looking at your age - this is also what GotWeight uses to get the weight.

[bible_pay]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

So I took a look at your 'exec createabn 256000' transaction a little closer (as I dont see a problem with the exec getabnweight call), and here is the issue:

Code:

"Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}

Hone in on the "age_data" and look at the numbers in parentheses; specifically each spent BBP of 10000.0010 has a weight of 10135.65 in parentheses.

Technically, all the #s in parentheses should add up to the "GotWeight=" amount, but they dont.  You have 259K in weight in parentheses yet the GotWeight = 239.299K, why?

Looking at the code, there is no bug in the CreateAbn, or the CreateTransaction, making me wonder then how can it be off?

The main thing I suspect is we have a third place in BBP where we assess your weight (When we look at the VIN coin age).

The only way to find out why 2 of your coin-ages are missing, is if we put a feature in BBP that lets you dump the VIN coin age to the log, then you can compare the Found weight values with the Got Weight values and probably see 2 of the inputs in the ABN are either missing or have 0 coin age (for a reason we don't know of yet).

So, I will go ahead and put that feature in and tell you how to run it.

Sounds good.. Did not want to come off as crazy at all or as a pain, was really just wondering how the numbers would be different. Obviously there are several factors which go into the calculation and I do not know them all so really was just trying to help ensure calculations were correct and to better understand which meant the most in terms of mining. So the more information the better to ensure calcs are indeed correct and working as you would expect.

Is this a windows wallet with the above debug info btw?

[jsheets1970]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

So I took a look at your 'exec createabn 256000' transaction a little closer (as I dont see a problem with the exec getabnweight call), and here is the issue:

Code:

"Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}

Hone in on the "age_data" and look at the numbers in parentheses; specifically each spent BBP of 10000.0010 has a weight of 10135.65 in parentheses.

Technically, all the #s in parentheses should add up to the "GotWeight=" amount, but they dont.  You have 259K in weight in parentheses yet the GotWeight = 239.299K, why?

Looking at the code, there is no bug in the CreateAbn, or the CreateTransaction, making me wonder then how can it be off?

The main thing I suspect is we have a third place in BBP where we assess your weight (When we look at the VIN coin age).

The only way to find out why 2 of your coin-ages are missing, is if we put a feature in BBP that lets you dump the VIN coin age to the log, then you can compare the Found weight values with the Got Weight values and probably see 2 of the inputs in the ABN are either missing or have 0 coin age (for a reason we don't know of yet).

So, I will go ahead and put that feature in and tell you how to run it.

Sounds good.. Did not want to come off as crazy at all or as a pain, was really just wondering how the numbers would be different. Obviously there are several factors which go into the calculation and I do not know them all so really was just trying to help ensure calculations were correct and to better understand which meant the most in terms of mining. So the more information the better to ensure calcs are indeed correct and working as you would expect.

Is this a windows wallet with the above debug info btw?

Windows

[bible_pay]

I think there might be some confusion being generated due to different numbers being calculated by different calls. Just to make it clear I am including the time of running for both.


23:12:42

exec getabnweight 256000 1


23:12:42

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 262754.2036458333,
  "total_required": 259210,
  "coin_age_data_pre_select": "6000.8578(1.01)=[6081.39] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n10000.0010(1.01)=[10135.65] depth=213,          \n</EOF>",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}


Obviously either exec getabnweight is too high (by almost 20K) or createabn call is too low.

If you want, you can compare and match the coins in parentheses across the two outputs, and see if you can find the two coins that are missing - and let me know that you think 2 coins are missing from one of the two commands.

Rob,

So doing the math neither of the calculations looks 100% right. In the getabnweight call it is missing the coin that was mined the previous day : 3209.3113. Excluding that then the calculation would be (25 * 10135.65) + 6081.39 which totals to the 259472 value. So that calculation is right minus not including the mined coin which perhaps was not old enough for this calculation.

The createabn call does have the previously mined coin in it and that has a weight of 3281.61. So in theory this calculation should be 3281.61 higher than getabnweight as it has all other coins but instead it is 20172.9925925926 lower. This is almost the value of 2 of the 10K coins and their weight.. Any chance you are using an array in createabn to store the coins and their ages and have it defined with only 25 members and as such my 27 coins has 2 too many and are not being counted in createabn?

Edit:  Wait a sec; I'm seeing your 10K * 25 = 250,000 in both the first set AND the second set - so you are not missing a 10K transaction.

Regarding the 3209.3113 missing in CreateABN, it does have to be 102 confirmations old, so just verify that it is still immature.

Lets look into this otherwise.

So I took a look at your 'exec createabn 256000' transaction a little closer (as I dont see a problem with the exec getabnweight call), and here is the issue:

Code:

"Command": "createabn",
  "xml": "<MT>ABN</MT><abnmsg>2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46</abnmsg><abnsig>H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=</abnsig><abncpk>BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS</abncpk><abnwgt>256000</abnwgt>",
  "err": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60",
  "age_data": "6000.8578(6081.39),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),10000.0010(10135.65),3209.3113(3281.61),",
  "tx_create_error": "CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=259473, UsingBBP=256000.00, I=25, NeededWeight=256000, GotWeight=239299.60"
}

Hone in on the "age_data" and look at the numbers in parentheses; specifically each spent BBP of 10000.0010 has a weight of 10135.65 in parentheses.

Technically, all the #s in parentheses should add up to the "GotWeight=" amount, but they dont.  You have 259K in weight in parentheses yet the GotWeight = 239.299K, why?

Looking at the code, there is no bug in the CreateAbn, or the CreateTransaction, making me wonder then how can it be off?

The main thing I suspect is we have a third place in BBP where we assess your weight (When we look at the VIN coin age).

The only way to find out why 2 of your coin-ages are missing, is if we put a feature in BBP that lets you dump the VIN coin age to the log, then you can compare the Found weight values with the Got Weight values and probably see 2 of the inputs in the ABN are either missing or have 0 coin age (for a reason we don't know of yet).

So, I will go ahead and put that feature in and tell you how to run it.

Sounds good.. Did not want to come off as crazy at all or as a pain, was really just wondering how the numbers would be different. Obviously there are several factors which go into the calculation and I do not know them all so really was just trying to help ensure calculations were correct and to better understand which meant the most in terms of mining. So the more information the better to ensure calcs are indeed correct and working as you would expect.

Is this a windows wallet with the above debug info btw?

Windows

Ok, it will be out in 30 mins for windows.

I expect this to move us one baby step further; but then we can re-assess the issue more clearly.

[fenton91]

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?

I copied my first save wallet.dat from 2018 to Biblepaycore, ereasing the actual wallet.bat, then realised i needed to copie it on biblepayEvolution and this is it. So from now, my wallet on bbpevo is my old save and not the version i used right before i made the core update .

[bible_pay]

23:12:42

exec getabnweight 256000 1

Ok, 1.4.3.9c is out there.  Now please upgrade, then type:
exec createabn 256000

And note the individual outputs of each part of the vin.  Add up the "Weight:" value for each VIN, and see where the discrepency is when comparing the vin outputs to the coin_age_data_preselect.  See if the grand total of the Weight does not match the pre_select weight in parentheses.

[bible_pay]

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?

I copied my first save wallet.dat from 2018 to Biblepaycore, ereasing the actual wallet.bat, then realised i needed to copie it on biblepayEvolution and this is it. So from now, my wallet on bbpevo is my old save and not the version i used right before i made the core update .

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.

[tiras]

it's happening right now at the pool :

[bible_pay]

it's happening right now at the pool :

Whats happening?  Should we all sell?

[tiras]

it's happening right now at the pool :

Whats happening?  Should we all sell?

probably