Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 138. (Read 243386 times)

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.

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)

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.

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?

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

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

yes. I copied a wallet from win to linux .

abnweight win and linux don't match.

abnweight is the same across 2 linux VMs.

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)

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",
  "weight 256000.00": 259472.5925925926,
  "total_required 256000.00": 256000
}


And then

23:13:06

exec createabn 256000


23:13:06

{
  "Command": "createabn",
  "xml": "ABN2a09a4304a2240e192290278901c6a333eaec51e333f84aeaea31709b2351c46H/aHFUnR35zLCtcIZcBEuU8HhTJeUE/aQ2JyXL4F1oH2fMGaoXpKj2tWbtmKnGo504wBmPUBHMPv/po153CRh/0=BPZZtoNfm2qVNt9muG9KB6A4MZb9msXciS256000",
  "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.

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

and the problem with a different abnweight is still there :

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)

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

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

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

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.

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

To prevent that error you can either unlock the wallet, or run the command
./biblepay-cli -headlesspassword

And it will prompt you for one, then it will memorize it and use it in the future for mining.

(You have to script this in a script if you want it to do this every boot) - otherwise re-type it each boot.

The wallet just returns 0 and fails to create the ABN if it cant get 256K, but, please wait for the next version to address the 300K part.

How do we know you didn't find a block between the time you typed the command?  And yes, ABN weight changes over time (as would be expected with coin age), so I wouldnt expect it to necessarily match unless you can guarantee you can type the command into all 3 at the same time, and show us all 3 are mining the same block concurrently with the same number of threads and all 3 synced to the same height.