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

[bible_pay]

So I am noticing something funny in the windows miner calculations on ABN. Maybe I just don't understand the calculations enough but here is what I see

When running exec getabnweight 256000 1 I get the following output
{
  "Command": "getabnweight",
  "version": 1.1,
  "weight": 334184.134375,
  "total_required": 300610,
  "coin_age_data": "173.0000(1.91)=[331.21] depth=410,          \n24844.0227(2.44)=[60651.57] depth=498,          \n658.0000(2.78)=[1832.00] depth=572,          \n5999.9000(3.40)=[20402.09] depth=693,          \n611.0000(3.48)=[2123.88] depth=712,          \n39459.7973(0.84)=[33099.43] depth=177,          \n210427.3141(0.84)=[176512.69] depth=177,          \n",
  "weight 256000.00": 294952.8723611111,
  "total_required 256000.00": 282173
}

When I look at the debug log I see the following for CreateABN
2019-06-26 13:55:15
***** CreateNewBlock::Unable to add ABN because CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=294953, UsingBBP=282173.00, I=25, NeededWeight=256000, GotWeight=230516.75 *****
2019-06-26 13:55:20 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)

Not sure why a couple of things are being displayed
1. Why does CreateABN have a different GotWeight that getabnweight : "weight 256000.00": 294952.8723611111 <> GotWeight=230516.75 *****
2. Why does CreateABN have a different UsingBBP than The total amount of BBP in the wallet when no immature blocks : "total_required": 300610 <> UsingBBP=282173.00

Anyone know what this line means?
2019-06-26 13:53:02 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: c982c3e05e4b59a9b559e26600e56bc621c8baa158439d63f7e4e5b97488125a, high-hash, proof of work failed (code 16)

Finally, once a block has been found and ABN is low, anything other than 1 or 2 threads in the miner seem to send the process into not responding state in windows as others have pointed out.

On question1, the difference between GotWeight and Weight: 
The wallet wants a target weight of 256K for ABN, but looping through its entire collection, it only "got" 230.5K.  The reason for the discrepency (334,184 weight in getabnweight) is due to something that was broken and will be fixed in this new version 1.4.3.9 (out in 1 1/2 hrs).

On Q2:  This is really the same issue as #1; it should have "used" 300,610.

On Issue of not responding, this was reproduced and will be fixed in 1.4.3.9.

[1715562868]

1715562868

[1715562868]

1715562868

[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 ?

Have you moved wallet.dat to the new:
~/.biblepayevolution
Location?

[bible_pay]

Mining for the pool doesn't seem to be working for me since the introduction of ABN.  My debug console is saying this:

"gsc_errors": "low abn weight 0",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 256000

"Command": "getabnweight",
  "version": 1.1,
  "weight": 307379.4657638889,
  "total_required": 286408


Any idea what could be wrong?  Thanks!

I think you will need the new version; please wait for 1.4.3.9. 

[bible_pay]

BiblePay
1.4.3.9-Leisure Upgrade

- Remove Log Spam
- Refactor miner's interface to acquire new ABN Tx; Add shared ABN
transaction; Update getmininginfo once every 5 seconds; Remove lag
- Enhanced 'exec createabn 256000' debug tool; this runs through a test
ABN and outputs each coin allowing the user to compare the
coin_age_data_pre_select to the coin_age_data to ensure it matches
- Added 'abninfo' to getmininginfo; This shows abn errors or abn success
info
- Fix bug in ABN selector

[capulo]

at least cpu usage looks better, 32 core is stable ~3200%, 40 core ~4000%, before i was not able to do more than ~3000% on 40 core
i'm still waiting for block

EDIT: i found block and i cant see any lags
until now everything is working fine (minersleep 0 and proclimit>40)

[tiras]

I think you will need the new version; please wait for 1.4.3.9.  

new version installed .

got  "weight": 321529.6356250001

starting mining ...   getting  "gsc_errors": "low abn weight 0",  

Code:

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 321529.6356250001,
  "total_required": 4383176
}


{
  "blocks": 128013,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 1284.675288874595,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 8,
  "networkhashps": 203697.0239518975,
  "hashps": 0,
  "minerstarttime": "06-27-2019 02:17:29",
  "hashcounter": 0,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
.............
  "abninfo": "Unable to Create ABN: CreateABN::Fail::(Create Transaction) Insufficient funds.::TargetWeight=257874, 
  UsingBBP=4258966.00, I=25, NeededWeight=256000, GotWeight=76578.03; NeededWeight=256000, GotWeight=76578.03; ",
  "gsc_errors": "low abn weight 0",
  "poolmining": true,
  "pool_url": "https://pool.biblepay.org",
  "required_abn_weight": 256000

and the problem with a different abnweight is still there :

Code:

Linux Wallet :
{
  "version": 1040309,
  "protocolversion": 70734,
  "walletversion": 61000,
  "balance":XXXXXXX.37985347,
  "privatesend_balance": 0.00000000,
  "blocks": 128015,
  "timeoffset": 0,
  "connections": 9,
  "proxy": "",
  "difficulty": 1783.151584720362,
  "testnet": false,
  "keypoololdest": 1535151048,
  "keypoolsize": 1007,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}
{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 175468.9461805555,
  "total_required": 4383360
}

Windows Wallet :
{
  "version": 1040309,
  "protocolversion": 70734,
  "walletversion": 61000,
  "balance": XXXXXXX.37985347,
  "privatesend_balance": 0.00000000,
  "blocks": 128015,
  "timeoffset": 0,
  "connections": 9,
  "proxy": "",
  "difficulty": 1783.151584720362,
  "testnet": false,
  "keypoololdest": 1535575821,
  "keypoolsize": 1016,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": ""
}


{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 354863.0961342592,
  "total_required": 4383360
}

[SEO_Account]

- Add POG rule to prevent sanctuary scalping

So is this to prevent unlocking sanc funds that have a lot of coin age to POG ?

[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.

[tiras]

why is it supposed to be so painful and frustrating ?

abn weight :  weight": 333452.4020138889

trying to mine :   "abninfo": "Unable to Create ABN: Sorry, your coin-age is too low to create an anti-botnet transaction.;

I didn't have transactions and didn't solve any blocks for the last several hours .
waisted several hours trying to get back to mining .

Code:

 biblepay-cli exec getabnweight 256000 1
{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 333452.4020138889,
  "total_required": 4383360,
  "coin_age_data_pre_select": 
  "581.2655(1.81)=[1054.01] depth=388,          \n
  347177.8183(0.06)=[21827.15] depth=16,          \n
  3905751.1603(0.06)=[245556.01] depth=16,          \n
  </EOF>",
  "weight 256000.00": 268437.1691782408,
  "total_required 256000.00": 4253510
}

I am not sure, but if I'm reading it right... the weight you need is 333k and you only have 268k currently. If you have 4M coins, did you mine a block recently thus making those coins ineligible temporarily?

no I didn't mine any blocks for the last several hours .

abn weight  on the 1st wallet :  weight": 333452.4020138889

same on the 2nd one : 268k 


actually .  it's finally picked up    but still showing different abn weigth in win and linux wallets ( same wallets there)

Code:

 exec getabnweight
{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 706901.3748842593,
  "total_required": 4383360
}

 exec getabnweight
{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 527507.2249305556,
  "total_required": 4383360
}

[tiras]

> exec createabn 256000

I get this error.

Error: std::bad_alloc

I must be on an earlier build. I noticed there's a 1439b which I think works, but I downloaded the windows binary earlier which may not be the right build.

> win and linux wallets ( same wallets there)

Is the wallet.dat from a binary copy from windows to linux or vice versa?

I'm running the same wallet.dat on three different windows machines and they all give me the same data back. there's got to be some divergence
(minor differences in private keys? perhaps divergence after mining blocks?)

yes. I copied a wallet from win to linux .

abnweight win and linux don't match.

abnweight is the same across 2 linux VMs.

Code:

Win:
exec createabn 256000
{
  "Command": "createabn",
.....................
  "coin_age_data_pre_select": "581.2655(1.88)=[1090.14] depth=401,          \n347177.8183(0.16)=[56705.58] depth=29,          \n3905751.1603(0.16)=[637939.33] depth=29,          \n</EOF>",
  "audited_weight": 510685.9252331106
}

Linux :

 exec createabn 256000
{
  "Command": "createabn",
 ..............
  "coin_age_data_pre_select": "581.2655(1.87)=[1087.96] depth=400,          \n347177.8183(0.12)=[42115.30] depth=28,          \n3905751.1603(0.12)=[473798.34] depth=28,          \n</EOF>",
  "audited_weight": 488444.8457239763
}

[capulo]

> exec createabn 256000

I get this error.

Error: std::bad_alloc

I must be on an earlier build. I noticed there's a 1439b which I think works, but I downloaded the windows binary earlier which may not be the right build.

> win and linux wallets ( same wallets there)

Is the wallet.dat from a binary copy from windows to linux or vice versa?

I'm running the same wallet.dat on three different windows machines and they all give me the same data back. there's got to be some divergence
(minor differences in private keys? perhaps divergence after mining blocks?)

yes. I copied a wallet from win to linux .

abnweight win and linux don't match.

abnweight is the same across 2 linux VMs.

Code:

Win:
exec createabn 256000
{
  "Command": "createabn",
.....................
  "coin_age_data_pre_select": "581.2655(1.88)=[1090.14] depth=401,          \n347177.8183(0.16)=[56705.58] depth=29,          \n3905751.1603(0.16)=[637939.33] depth=29,          \n</EOF>",
  "audited_weight": 510685.9252331106
}

Linux :

 exec createabn 256000
{
  "Command": "createabn",
 ..............
  "coin_age_data_pre_select": "581.2655(1.87)=[1087.96] depth=400,          \n347177.8183(0.12)=[42115.30] depth=28,          \n3905751.1603(0.12)=[473798.34] depth=28,          \n</EOF>",
  "audited_weight": 488444.8457239763
}

as you can see, depth increased by 1 when you moved to win. so there was new block and thus coinage increased

[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

[MIP]

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?

[eternalenvoy]

Remember, if anyone has a lag on the next version, try minersleep=5 and verify the HPS is still 99%, and no lag exists.

If you have no lag then keep minersleep=0.

Also, tell us if there is no lag with a proclimit of < 10 as compared to when you overload the proclimit (> machine core count).

Still have a laggy problem after a few minutes on new version 1.4.3.8

conf:
minersleep=5 ( also tried =0)
gen=1
genproclimit=10

I did find the lag; will be fixed in 2 hours in 1.4.3.9.

No any laggy in 1.4.3.9, and the wallet unlock cmd also work.

Let see the depth with ABN weight status...

Is it each thread need 256000 weight?
Example, remaining weight is around 1,000,000 after hit 3 block, however, the weight is around 5,000,000 before found 3 block.


Thx Rob.

[capulo]

yes, money cant be lost, it is almost impoosible on blockchain. if they was there, they must be there also now. (or was moved by someone, but then you must see tx for move). if no tx about move is there, then money never exist (they was real only on fork chain, but on main never exist)

[bible_pay]

yes, money cant be lost, it is almost impoosible on blockchain. if they was there, they must be there also now. (or was moved by someone, but then you must see tx for move). if no tx about move is there, then money never exist (they was real only on fork chain, but on main never exist)

Yes Fenton we both asked you a couple questions about it but never received a reply.

We still need to know if you moved your wallet.dat and resynced in Evo.

[bible_pay]

Remember, if anyone has a lag on the next version, try minersleep=5 and verify the HPS is still 99%, and no lag exists.

If you have no lag then keep minersleep=0.

Also, tell us if there is no lag with a proclimit of < 10 as compared to when you overload the proclimit (> machine core count).

Still have a laggy problem after a few minutes on new version 1.4.3.8

conf:
minersleep=5 ( also tried =0)
gen=1
genproclimit=10

I did find the lag; will be fixed in 2 hours in 1.4.3.9.

No any laggy in 1.4.3.9, and the wallet unlock cmd also work.

Let see the depth with ABN weight status...

Is it each thread need 256000 weight?
Example, remaining weight is around 1,000,000 after hit 3 block, however, the weight is around 5,000,000 before found 3 block.


Thx Rob.

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).

[bible_pay]

- Add POG rule to prevent sanctuary scalping

So is this to prevent unlocking sanc funds that have a lot of coin age to POG ?

Yes.

[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.

[bible_pay]

Macko said he's forking BiblePay.  Does anyone have any info on the ticker or OP post?