Bitcoin Forum
April 02, 2020, 12:50:49 AM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 [723] 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 ... 866 »
  Print  
Author Topic: BiblePay | 10% to Orphan-Charity | POBH CPU | Sanctuaries (Masternodes)  (Read 211238 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic. (345 posts by 33 users deleted.)
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 22, 2019, 03:03:12 PM
 #14441

Somehow I can't get my miners to work on the pool.
I copied a fresh wallet without a password on all of them and sent 256k there a couple of hours ago. The wallets don't have any password. However when I start the clients the "getmininginfo" output always shows "gsc_errors: low abn weight 0". Is there any additional requirement?

You just have to have ABN weight in the block, lets look at possible issues.
Its unlocked and unencrypted so that makes it easier.
Type:  exec getabnweight
See if its > 256k?

If its not you need a little more age.  256k = 1 day of coin age * 256,000 bbp.
(Or you can temporarily send more to it).

Another tip:  If your wallet is not mining (IE 0 hps in getmininginfo), you can look in the log and scan for "biblepayminer" or "ABN", and it should have some type of error in there.

PS: That explains why our diff dropped!


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
1585788649
Hero Member
*
Offline Offline

Posts: 1585788649

View Profile Personal Message (Offline)

Ignore
1585788649
Reply with quote  #2

1585788649
Report to moderator
1585788649
Hero Member
*
Offline Offline

Posts: 1585788649

View Profile Personal Message (Offline)

Ignore
1585788649
Reply with quote  #2

1585788649
Report to moderator
Best Rates For Exchanging Cryptocurrency Buy Crypto With Credit Card Smooth Exchange Multiple E-Payment Systems Check Now Check Now
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1585788649
Hero Member
*
Offline Offline

Posts: 1585788649

View Profile Personal Message (Offline)

Ignore
1585788649
Reply with quote  #2

1585788649
Report to moderator
dave_bbp
Jr. Member
*
Offline Offline

Activity: 397
Merit: 3


View Profile
June 22, 2019, 03:51:44 PM
 #14442

You just have to have ABN weight in the block, lets look at possible issues.
Its unlocked and unencrypted so that makes it easier.
Type:  exec getabnweight
See if its > 256k?

If its not you need a little more age.  256k = 1 day of coin age * 256,000 bbp.
(Or you can temporarily send more to it).

Another tip:  If your wallet is not mining (IE 0 hps in getmininginfo), you can look in the log and scan for "biblepayminer" or "ABN", and it should have some type of error in there.

PS: That explains why our diff dropped!

Ah I see, that makes sense. So the abnweight=256k is a coin age weight, not just an amount. Right now getabnweight gives about 60k, so either I wait until tomorrow, or I send more coins now and reduce the waiting time.
But it would also be possible the other way round, right? Let's say I now pull off 128k from this wallet and wait for 2 days, the result is the same and the risk of the unlocked wallet is reduced (if there is any at all...). Nice to know that. Wink
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 22, 2019, 08:51:04 PM
 #14443

At first I was cautious about commenting on ABN when the diff dropped, but I want to say that I think we made the right decision with ABN.

I'm looking at the pool, and with the low difficulty, we are really solving blocks fast now.  We just hit 31 blocks solved (and we've only been on ABN half a day) meaning with this trajectory we should hit 50 blocks by tomorrow morning.
That's good because it means the people being rewarded are the long-term Biblepayers (in contrast to mining pools who jump in and sell the coins).

I might be making an early assessment, but this feels very good that the rewards are going to our own miners and the diff is still low.

This reminds me of our second month (August 2017) when it felt as if all the coins went to our miners, and then we 'assumed' someone jumped on with 300 PCs in Japan and the diff skyrocketed.  With ABN, that risk is mitigated (unless they buy coins for every PC and hold them to mine with).


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 22, 2019, 10:01:32 PM
 #14444

** TestNet Update **

We are ready to start testing in our TestNet thread again!

Please participate:

https://forum.biblepay.org/index.php?topic=391.new#new



🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 22, 2019, 10:06:07 PM
 #14445

I think ABN is a good change. It does mitigate the botnet. Does anyone wanting to participating in BBP need to buy on exchange or do bounty (orphan letter writing) to get BBP?

So, with ABN is the required weight always 256k BBP per block? I guess it fluctuates with the difficulty? Higher diff means you need to stake more BBP of enough min coin age? I found a block, but it spent 600k BBP since the coins weren't in smaller denominations. In between PoG and PoBH, not sure how my coins should be set up. Since my CPU is 0 hash, I'll guess I'll run BOINC again when the CPU percentage if near 0%.

There's a lot of ABN spam on 1.4.3.5:

CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
antibotnetsignature failed on tx xxxxx with purported coin-age of 0.000000
ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)


I'll look at the log spam ASAP, hopefully within the next 36 hours, and we can make a mainnet release to reduce log spam, fix the leaderboard erratic behavior, the detail amount issue, and look at the github permissions.

On the ABN weight used:  It actually is always 256k (except when the block is late or when diff is < 1000, then the ABN requirement is 0), but the reason we take more ABN weight in certain circumstances is if we use a coin with more coin age than 256k then your weight is higher in that block.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
orbis
Newbie
*
Offline Offline

Activity: 156
Merit: 0


View Profile
June 23, 2019, 09:46:32 AM
 #14446

I think ABN is a good change. It does mitigate the botnet. Does anyone wanting to participating in BBP need to buy on exchange or do bounty (orphan letter writing) to get BBP?

So, with ABN is the required weight always 256k BBP per block? I guess it fluctuates with the difficulty? Higher diff means you need to stake more BBP of enough min coin age? I found a block, but it spent 600k BBP since the coins weren't in smaller denominations. In between PoG and PoBH, not sure how my coins should be set up. Since my CPU is 0 hash, I'll guess I'll run BOINC again when the CPU percentage if near 0%.

There's a lot of ABN spam on 1.4.3.5:

CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
antibotnetsignature failed on tx xxxxx with purported coin-age of 0.000000
ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)


I'll look at the log spam ASAP, hopefully within the next 36 hours, and we can make a mainnet release to reduce log spam, fix the leaderboard erratic behavior, the detail amount issue, and look at the github permissions.

On the ABN weight used:  It actually is always 256k (except when the block is late or when diff is < 1000, then the ABN requirement is 0), but the reason we take more ABN weight in certain circumstances is if we use a coin with more coin age than 256k then your weight is higher in that block.


Hi,
yesterday I solved 3 blocks after 127000, but after that something changed and now, I'm not able to mine.
My abnweight is 1225238, but my miner still have "gsc_errors": "low abn weight 0".
When is my miner running (eg on my WIN QT wallet with 8 threads), wallet is really laggy and I have really problems to write command in debug console.
And yes, log is full of ABN spam and something is there something like this:
Code:
2019-06-23 09:40:02
CreateNewBlock::Unable to add ABN because CreateABN::Fail::Insufficient funds.antibotnetsignature failed on tx 73def57d702cbbbfb077473aef33aa6c7f72b27587d1766c1e3e7b3bbc0f3cf1 with purported coin-age of 0.000000
2019-06-23 09:40:02 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)
2019-06-23 09:40:32 keypool return 2337
2019-06-23 09:40:33 keypool reserve 2337

pagalo
Newbie
*
Offline Offline

Activity: 55
Merit: 0


View Profile
June 23, 2019, 10:39:09 AM
 #14447

Hello, all miners works at 0% CPU

I have the following conf.

addnode=explorer.biblepay.org
gen=1
genproclimit=1
poolport=80
workerid=
pool=https://pool.biblepay.org
minersleep=0
tithe=10
tithing=10
nickname=pagalo

getmininginfo result
{
  "blocks": 127260,
  "currentblocksize": 1593,
  "currentblocktx": 1,
  "difficulty": 2816.816655473472,
  "errors": "",
  "pooledtx": 1,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 375372.1147512915,
  "hashps": 0,
  "minerstarttime": "06-23-2019 10:22:28",
  "hashcounter": 0,
  "pooledtx": 1,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "WORKER ID EMPTY IN CONFIG FILE; ",
  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 256000
}


exec getabnweight
{
  "Command": "getabnweight",
  "weight": 483488.1748842592,
  "total_required": 1479267
}

Do I have to change anything?

Thanks
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 02:15:13 PM
Last edit: June 23, 2019, 02:38:36 PM by bible_pay
 #14448

I think ABN is a good change. It does mitigate the botnet. Does anyone wanting to participating in BBP need to buy on exchange or do bounty (orphan letter writing) to get BBP?

So, with ABN is the required weight always 256k BBP per block? I guess it fluctuates with the difficulty? Higher diff means you need to stake more BBP of enough min coin age? I found a block, but it spent 600k BBP since the coins weren't in smaller denominations. In between PoG and PoBH, not sure how my coins should be set up. Since my CPU is 0 hash, I'll guess I'll run BOINC again when the CPU percentage if near 0%.

There's a lot of ABN spam on 1.4.3.5:

CreateNewBlock::Unable to add ABN because Sorry, your coin-age is too low to create an anti-botnet transaction.
antibotnetsignature failed on tx xxxxx with purported coin-age of 0.000000
ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)


I'll look at the log spam ASAP, hopefully within the next 36 hours, and we can make a mainnet release to reduce log spam, fix the leaderboard erratic behavior, the detail amount issue, and look at the github permissions.

On the ABN weight used:  It actually is always 256k (except when the block is late or when diff is < 1000, then the ABN requirement is 0), but the reason we take more ABN weight in certain circumstances is if we use a coin with more coin age than 256k then your weight is higher in that block.


Hi,
yesterday I solved 3 blocks after 127000, but after that something changed and now, I'm not able to mine.
My abnweight is 1225238, but my miner still have "gsc_errors": "low abn weight 0".
When is my miner running (eg on my WIN QT wallet with 8 threads), wallet is really laggy and I have really problems to write command in debug console.
And yes, log is full of ABN spam and something is there something like this:
Code:
2019-06-23 09:40:02
CreateNewBlock::Unable to add ABN because CreateABN::Fail::Insufficient funds.antibotnetsignature failed on tx 73def57d702cbbbfb077473aef33aa6c7f72b27587d1766c1e3e7b3bbc0f3cf1 with purported coin-age of 0.000000
2019-06-23 09:40:02 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)
2019-06-23 09:40:32 keypool return 2337
2019-06-23 09:40:33 keypool reserve 2337



I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).

(Ill take care of this spam ASAP).

EDIT:  Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)?  Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.



🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 02:17:49 PM
Last edit: June 23, 2019, 02:39:43 PM by bible_pay
 #14449

Hello, all miners works at 0% CPU

I have the following conf.

addnode=explorer.biblepay.org
gen=1
genproclimit=1
poolport=80
workerid=
pool=https://pool.biblepay.org
minersleep=0
tithe=10
tithing=10
nickname=pagalo

getmininginfo result
{
  "blocks": 127260,
  "currentblocksize": 1593,
  "currentblocktx": 1,
  "difficulty": 2816.816655473472,
  "errors": "",
  "pooledtx": 1,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 375372.1147512915,
  "hashps": 0,
  "minerstarttime": "06-23-2019 10:22:28",
  "hashcounter": 0,
  "pooledtx": 1,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "WORKER ID EMPTY IN CONFIG FILE; ",
  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 256000
}


exec getabnweight
{
  "Command": "getabnweight",
  "weight": 483488.1748842592,
  "total_required": 1479267
}

Do I have to change anything?

Thanks



EDIT:  if you are not pool mining, ensure the wallet is unlocked.  Scan the log file for any errors related to "ABN".  You have enough ABN weight.
Try restarting with -zapwallettxes=1 first then try mining again.

EDIT2:  If you just sent out a GSC transmission, the wallet cant recycle your abn weight until that transmission is in a block.  



🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
orbis
Newbie
*
Offline Offline

Activity: 156
Merit: 0


View Profile
June 23, 2019, 03:16:44 PM
 #14450

I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).

(Ill take care of this spam ASAP).

EDIT:  Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)?  Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago.
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 05:09:02 PM
Last edit: June 23, 2019, 05:20:46 PM by bible_pay
 #14451

I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).

(Ill take care of this spam ASAP).

EDIT:  Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)?  Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago.

So does this mean somebody with big bbp amount will get all the blocks? I got two blocks too and now nothing. Maybe we just lucky and our hash power is not strong? I think some people have 50 machines with 8 cores ... so 400 processors.


No, it doesnt mean that.  

I for example only have 3.9 mm coinage free and Ive been mining non stop and Im only using 1 machine and Im 10% of the pool-weight, so its possible to mine continuously if you drop more bbp into the mining equation.

Yeah if you had 400 processors you would probably need half of the BBP on the market.

But first of all our investors generally lock coins into sancs so this game is for people with free biblepay.

Lets not jump to quick conclusions - The difference between ABN and no ABN is this:  You live with a botnet and a bunch of rich people with hardware, and solve 1 block per month with a difficulty of 90,000.  Or you live with internal BiblePay users and solve a block a day with diff of 9000.  In the 2nd camp you maintain a free balance of 1 mil.  Which is better?  To me its like night and day.   Additionally there are a lot of factors other than ABN that make block solving fair - the fairness of POW is still in the equation.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 05:10:13 PM
Last edit: June 23, 2019, 05:29:56 PM by bible_pay
 #14452

I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).

(Ill take care of this spam ASAP).

EDIT:  Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)?  Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago.

Please investigate the log and scrape the actual error.



🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
eternalenvoy
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
June 23, 2019, 05:59:21 PM
 #14453

After ABN re-enable, it seem have a serious problem that wallet is really laggy when POBH mode, and it is not working as CPU usage is 0%. I have checked the message and shown "low abn weight 0", however I confirmed the value is over 256000 of abnweight in wallet.

I have try to reindex or restarting with -zapwallettxes=1, but problem is not resolved..

Reference the "networkhashps" and "difficulty" from explorer , it seem really have a problem with POBH...
orbis
Newbie
*
Offline Offline

Activity: 156
Merit: 0


View Profile
June 23, 2019, 06:23:29 PM
 #14454

I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).
(Ill take care of this spam ASAP).
EDIT:  Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)?  Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago.
Please investigate the log and scrape the actual error.
I didn't found any other error except those ABN logs.
But I think, that I found some connection with sanctuaries.
I bought BBP to have enough BBP for sanc. So I have created sanc and put my masternode.conf file to my VPS in faith that my VPS avoid sending locked BBPs. Few blocks away some of my VPS solved block and used locked BBPs to satisfy ABN tx. It destroyed sanc, but my abnweight was enough to solve another block after 8 blocks after first (now I have almost 0 abnweught). It looks, that even if I had enough abnweight with sanc, that was just in some counterpart with sanc. Yes, I know that I can create new wallet not related with sanc, but I want to have only one wallet.

And Sunk, after block 127000 you can look who solved the block. It's the same as it was with CPID before.
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 06:42:17 PM
 #14455

After ABN re-enable, it seem have a serious problem that wallet is really laggy when POBH mode, and it is not working as CPU usage is 0%. I have checked the message and shown "low abn weight 0", however I confirmed the value is over 256000 of abnweight in wallet.

I have try to reindex or restarting with -zapwallettxes=1, but problem is not resolved..

Reference the "networkhashps" and "difficulty" from explorer , it seem really have a problem with POBH...

Yeah, I believe the jerkiness will be fixed in the next few hours, but I really do think it only happens when you run out of coin age (I know you have more than 256k, but its possible your only coin is tied up by one of the other mining threads).

Could you please check your log for this:
::Unable to add ABN because CreateABN::Fail::Insufficient funds.

See if you have an error like this, and if thats it then this can be mitigated in the next version.

Im removing the log spam right now.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 06:44:27 PM
 #14456

I'm glad you mentioned this laginess now (before next mainnet release) as I think we can take care of this very easily (its that you wallet keeps trying to create a new block too frequently when your coin-age is low).
(Ill take care of this spam ASAP).
EDIT:  Can you tell me if this problem goes away 5 blocks after you solved your last block (Of if you just sent a GSC transmission out)?  Its most likely due to the coin-age spent in the last winning block causes a confirmation delay before you can recycle all coin age depending on that tx.
I solved last block more than 150 blocks before. And I turned off sending GSC, so my last was around 350 block ago.
Please investigate the log and scrape the actual error.
I didn't found any other error except those ABN logs.
But I think, that I found some connection with sanctuaries.
I bought BBP to have enough BBP for sanc. So I have created sanc and put my masternode.conf file to my VPS in faith that my VPS avoid sending locked BBPs. Few blocks away some of my VPS solved block and used locked BBPs to satisfy ABN tx. It destroyed sanc, but my abnweight was enough to solve another block after 8 blocks after first (now I have almost 0 abnweught). It looks, that even if I had enough abnweight with sanc, that was just in some counterpart with sanc. Yes, I know that I can create new wallet not related with sanc, but I want to have only one wallet.

And Sunk, after block 127000 you can look who solved the block. It's the same as it was with CPID before.

GSC actually doesn't spend sanctuary funds.  I think maybe the problem is you forgot to restart the sanc and ensure the coins were locked?

They get locked during the service startup phase (when you type masternode status, if it shows "Started" with an IP, thats when they are locked).

EDIT: Just to clarify though Im referring to cold sancs.  

🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
orbis
Newbie
*
Offline Offline

Activity: 156
Merit: 0


View Profile
June 23, 2019, 06:55:38 PM
 #14457


GSC actually doesn't spend sanctuary funds.  I think maybe the problem is you forgot to restart the sanc and ensure the coins were locked?

They get locked during the service startup phase (when you type masternode status, if it shows "Started" with an IP, thats when they are locked).

I'm sure, that I restarted sanc and all of my wallets. When I looked on it in my WIN QT wallet, they were "locked". I made it like this: Stopped mining and daemon, copy masternode.conf to VPS, start wallet, unlock and it starts mining.
Nevermind. It looks that those locked coins was some problem in this, because now it is mining as it should. Now I need just to decide If I want to have sanc, or want to mine, because in my case it is not working side by side. But like you sayd, maybe I just don't know how to set it up correctly.
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 07:09:06 PM
 #14458


GSC actually doesn't spend sanctuary funds.  I think maybe the problem is you forgot to restart the sanc and ensure the coins were locked?

They get locked during the service startup phase (when you type masternode status, if it shows "Started" with an IP, thats when they are locked).

I'm sure, that I restarted sanc and all of my wallets. When I looked on it in my WIN QT wallet, they were "locked". I made it like this: Stopped mining and daemon, copy masternode.conf to VPS, start wallet, unlock and it starts mining.
Nevermind. It looks that those locked coins was some problem in this, because now it is mining as it should. Now I need just to decide If I want to have sanc, or want to mine, because in my case it is not working side by side. But like you sayd, maybe I just don't know how to set it up correctly.

No, I didnt mean to imply your skills or set up Smiley --  I mean for some reason your cold wallet didnt go into the service startup phase that autolocks the coins.

But I see we do skip over that particular collateral and in my personal case I have not accidentally spent any and last night I set myself up with an unlocked wallet and let it send gscs and mine, so I think that part is working properly - for the most part.

But we can continue to work through anything that is a long term issue.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
eternalenvoy
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
June 23, 2019, 07:12:22 PM
 #14459

After ABN re-enable, it seem have a serious problem that wallet is really laggy when POBH mode, and it is not working as CPU usage is 0%. I have checked the message and shown "low abn weight 0", however I confirmed the value is over 256000 of abnweight in wallet.

I have try to reindex or restarting with -zapwallettxes=1, but problem is not resolved..

Reference the "networkhashps" and "difficulty" from explorer , it seem really have a problem with POBH...

Yeah, I believe the jerkiness will be fixed in the next few hours, but I really do think it only happens when you run out of coin age (I know you have more than 256k, but its possible your only coin is tied up by one of the other mining threads).

Could you please check your log for this:
::Unable to add ABN because CreateABN::Fail::Insufficient funds.

See if you have an error like this, and if thats it then this can be mitigated in the next version.

Im removing the log spam right now.



No relevant ABN information found from the log...
Even I set walletpassphrase and do an unlock step still not work and really laggy...
bible_pay
Full Member
***
Offline Offline

Activity: 994
Merit: 215


Jesus is the King of Kings and Lord of Lords


View Profile WWW
June 23, 2019, 07:29:00 PM
 #14460

After ABN re-enable, it seem have a serious problem that wallet is really laggy when POBH mode, and it is not working as CPU usage is 0%. I have checked the message and shown "low abn weight 0", however I confirmed the value is over 256000 of abnweight in wallet.

I have try to reindex or restarting with -zapwallettxes=1, but problem is not resolved..

Reference the "networkhashps" and "difficulty" from explorer , it seem really have a problem with POBH...

Yeah, I believe the jerkiness will be fixed in the next few hours, but I really do think it only happens when you run out of coin age (I know you have more than 256k, but its possible your only coin is tied up by one of the other mining threads).

Could you please check your log for this:
::Unable to add ABN because CreateABN::Fail::Insufficient funds.

See if you have an error like this, and if thats it then this can be mitigated in the next version.

Im removing the log spam right now.



No relevant ABN information found from the log...
Even I set walletpassphrase and do an unlock step still not work and really laggy...


There has to be, if we don't create a block to mine, the miner writes:  CreateNewBlock::Unable to add ABN..... (etc).

Please search again.

In the mean time please run the miner on one thread and the laginess will be much less until the next version comes out.

I would like to know what error you have, so we can make the next version better.


🕇 BiblePay 🕇
🕇  Announcement | ForumSlackDiscordRedditTwitter | SouthXChange  🕇
🕇 A Christian cryptocurrency | Supporting orphans through a decentralized autonomous charity 🕇
Pages: « 1 ... 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 [723] 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 ... 866 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!