Search content
Sort by
Showing 20 of 228 results by tiras
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
If anyone in QT has trouble seeing their sanc list in the GUI, please reboot and ensure they are started.
all Sancs are in pre-enabled status in controller GUI .
running "masternode status" on the Sanc returns " "status": "Not capable masternode: Masternode not in masternode list""
attempting to start a sanc from the controller doesn't do anything .
I did try rebooting the sanc and re-downloading the blockchain as well .
It didn't help either.
blockhash on controller and sanc:
19:02:46
getblockhash 129427
d053f86021908481059fbc65b5e8d257882c1d5cb5f097a0d949fef8cfdca947
Looks like they are coming back up now; about 140 out of 182 have re-propagated into the active sanc list (I think this takes about an hour).
I just tested one that I started (in my case I pushed Start-All), then went to the sanc itself, and it did start (masternode status) is fine now.
On a side note in this case no one should have to re-sync the whole chain, its just a re-synchronization issue of the masternode list data.
(IE mnsync reset will also help).
I think in an hour or two we will see 90%+ coverage again in enabled.
as of now at 128469 I can see only 4 sanc in "ENABLED" status .
the rest are mostly "expired" .
about 18 are "pre-enabled"
difficalty is low : 1233
00:01:48
getblockhash 129469
77eff1a802c98e7fbb222ca62f4054b8e2ce60a3fefca3c09399708cb13f1117
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
If anyone in QT has trouble seeing their sanc list in the GUI, please reboot and ensure they are started.
all Sancs are in pre-enabled status in controller GUI .
running "masternode status" on the Sanc returns " "status": "Not capable masternode: Masternode not in masternode list""
attempting to start a sanc from the controller doesn't do anything .
I did try rebooting the sanc and re-downloading the blockchain as well .
It didn't help either.
blockhash on controller and sanc:
19:02:46
getblockhash 129427
d053f86021908481059fbc65b5e8d257882c1d5cb5f097a0d949fef8cfdca947
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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 ?
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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 .....
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
it's happening right now at the pool :
Whats happening? Should we all sell?
probably
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
> 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?)
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",
"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",
"audited_weight": 488444.8457239763
}
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",
"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",
"audited_weight": 488444.8457239763
}
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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 .
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
",
"weight 256000.00": 268437.1691782408,
"total_required 256000.00": 4253510
}
{
"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
",
"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
}
{
"Command": "getabnweight",
"version": 1.2,
"weight": 706901.3748842593,
"total_required": 4383360
}
exec getabnweight
{
"Command": "getabnweight",
"version": 1.2,
"weight": 527507.2249305556,
"total_required": 4383360
}
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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
"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
}
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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!
"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!
yeah , i'm also wondering why mining won't start :
Code:
{
"Command": "getabnweight",
"version": 1.1,
[b] "weight": 274797.669525463,[/b]
"total_required": 4383370,
"coin_age_data": "696007.5834(0.04)=[29612.52] depth=13, \n3471778.8328(0.04)=[147711.30]
depth=13, \n165899.5165(0.34)=[56169.48] depth=75, \n581.2655(1.38)=[802.40] dept
h=296, \n5456.2700(1.87)=[10177.65] depth=402, \n0.0648(2.28)=[0.00] depth=479,
\n36413.3417(0.42)=[15434.22] depth=86, \n",
"weight 259000.00": 259907.5719097223,
"total_required 259000.00": 4376136
}
"Command": "getabnweight",
"version": 1.1,
[b] "weight": 274797.669525463,[/b]
"total_required": 4383370,
"coin_age_data": "696007.5834(0.04)=[29612.52] depth=13, \n3471778.8328(0.04)=[147711.30]
depth=13, \n165899.5165(0.34)=[56169.48] depth=75, \n581.2655(1.38)=[802.40] dept
h=296, \n5456.2700(1.87)=[10177.65] depth=402, \n0.0648(2.28)=[0.00] depth=479,
\n36413.3417(0.42)=[15434.22] depth=86, \n",
"weight 259000.00": 259907.5719097223,
"total_required 259000.00": 4376136
}
Code:
"poolinfo3": "",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
mining started although after my abnweight went a bit up from 274797
I am mining as well but very slowly and intermittently, and it still says my abn is 0 even though it's over 300k.
3 miners running the same wallet showing different abnweight
Code:
{
"Command": "getabnweight",
"version": 1.1,
"weight": 878829.5629976852,
"total_required": 4383370
{
"Command": "getabnweight",
"version": 1.1,
"weight": 165733.9069791667,
"total_required": 911591
}
{
"Command": "getabnweight",
"version": 1.1,
"weight": 189473.1778125,
"total_required": 911591
}
}
"Command": "getabnweight",
"version": 1.1,
"weight": 878829.5629976852,
"total_required": 4383370
{
"Command": "getabnweight",
"version": 1.1,
"weight": 165733.9069791667,
"total_required": 911591
}
{
"Command": "getabnweight",
"version": 1.1,
"weight": 189473.1778125,
"total_required": 911591
}
}
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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!
"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!
yeah , i'm also wondering why mining won't start :
Code:
{
"Command": "getabnweight",
"version": 1.1,
[b] "weight": 274797.669525463,[/b]
"total_required": 4383370,
"coin_age_data": "696007.5834(0.04)=[29612.52] depth=13, \n3471778.8328(0.04)=[147711.30]
depth=13, \n165899.5165(0.34)=[56169.48] depth=75, \n581.2655(1.38)=[802.40] dept
h=296, \n5456.2700(1.87)=[10177.65] depth=402, \n0.0648(2.28)=[0.00] depth=479,
\n36413.3417(0.42)=[15434.22] depth=86, \n",
"weight 259000.00": 259907.5719097223,
"total_required 259000.00": 4376136
}
"Command": "getabnweight",
"version": 1.1,
[b] "weight": 274797.669525463,[/b]
"total_required": 4383370,
"coin_age_data": "696007.5834(0.04)=[29612.52] depth=13, \n3471778.8328(0.04)=[147711.30]
depth=13, \n165899.5165(0.34)=[56169.48] depth=75, \n581.2655(1.38)=[802.40] dept
h=296, \n5456.2700(1.87)=[10177.65] depth=402, \n0.0648(2.28)=[0.00] depth=479,
\n36413.3417(0.42)=[15434.22] depth=86, \n",
"weight 259000.00": 259907.5719097223,
"total_required 259000.00": 4376136
}
Code:
"poolinfo3": "",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
mining started although after my abnweight went a bit up from 274797
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
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!
"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!
yeah , i'm also wondering why mining won't start :
Code:
{
"Command": "getabnweight",
"version": 1.1,
[b] "weight": 274797.669525463,[/b]
"total_required": 4383370,
"coin_age_data": "696007.5834(0.04)=[29612.52] depth=13, \n3471778.8328(0.04)=[147711.30]
depth=13, \n165899.5165(0.34)=[56169.48] depth=75, \n581.2655(1.38)=[802.40] dept
h=296, \n5456.2700(1.87)=[10177.65] depth=402, \n0.0648(2.28)=[0.00] depth=479,
\n36413.3417(0.42)=[15434.22] depth=86, \n",
"weight 259000.00": 259907.5719097223,
"total_required 259000.00": 4376136
}
"Command": "getabnweight",
"version": 1.1,
[b] "weight": 274797.669525463,[/b]
"total_required": 4383370,
"coin_age_data": "696007.5834(0.04)=[29612.52] depth=13, \n3471778.8328(0.04)=[147711.30]
depth=13, \n165899.5165(0.34)=[56169.48] depth=75, \n581.2655(1.38)=[802.40] dept
h=296, \n5456.2700(1.87)=[10177.65] depth=402, \n0.0648(2.28)=[0.00] depth=479,
\n36413.3417(0.42)=[15434.22] depth=86, \n",
"weight 259000.00": 259907.5719097223,
"total_required 259000.00": 4376136
}
Code:
"poolinfo3": "",
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
"gsc_errors": "low abn weight 0",
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"required_abn_weight": 256000
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
Thats probably outdated, Id use:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt
The major change Im aware of is the new "depends" folder that has to be compiled first, theres probably some other changes
Those reddit mining guides should probably get merged into the website and/or wiki so others can edit them
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt
The major change Im aware of is the new "depends" folder that has to be compiled first, theres probably some other changes
Those reddit mining guides should probably get merged into the website and/or wiki so others can edit them
thanks Togo
I waisted another couple of hours trying to compile it.
seems like biblepay.org needs a major clean-up
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
[
is this script still usable to compile the latest version ?
Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b
PS: MIP is traveling and unable to build linux for 14 more hours, please self-compile linux and Mac.
is this script still usable to compile the latest version ?
Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
Rob,
Do I need 2 separate wallets to participate in both POG and HEALING ?
for some reason my prominence in HEALING was always 0
Do I need 2 separate wallets to participate in both POG and HEALING ?
for some reason my prominence in HEALING was always 0
No just one wallet and one CPK. To score Healing points you have to add a Diary entry. To do that go to the QT send-money UI, click diary entry checkbox, add a diary entry in the prayer line, and click send (it sends 1 BBP to the foundation).
Then check it in about 6 blocks.
You do have to join healing with : exec join HEALING
thank you !