"poolinfo5": "Internal ABN: Invalid 1564736955; ",
"abninfo": "No block to mine... Please wait... 1564737052; No block to mine... Please wait... 1564737058; ",
"gsc_errors": "low abn weight 0",
"poolmining": false,
"pool_url":
"required_abn_weight": 125000 I have amount 125000 BBP in wallet for solo mining but it always show No block to mine ? Wallet v1.4.4.5. Anyone please help. Please paste exec getabnweight 125000 1 It should shed light on this issue. |
|
|
|
Dear BBP community,
I would like some help to understand what happen.
When I register for my christian key, My coins disappeared from my wallet.
I used pog_coinagepercentage=0.90...
And I was expected that they come back, but nothing yet.
Can someone explain?
Where are they? in a sanctuary?
Thank you for your help.
Welcome to the community Aram! So when you explained to me via email you were out of sync while mining I wanted to explain what 'mining on a fork' is. If your machine is out of sync when mining, the difficulty drops to 0, and you are able to solve many blocks that generate BBP that is not really truly yours (as its not part of the main chain). So after you resynced, you lost all your generated coins (IE, this really has nothing to do with GSC transmissions or POG). Could you please confirm that when you resynced, all your credits from mining have been reversed? So in a nutshell, you dont get to keep coins mined on a fork. You will still have all your BBP you bought on the exchange though, or that you mined in prior legal versions of BBP. |
|
|
|
Sorry for the hassle, but I still don't have enough info - if you want you can e-mail me, or we can continue.
So, with a POG GSC transmission, the wallet is scanning the available coins, and finding 298.436615MM coin age available.
Then it says, I need 238.749292MM for this transaction of coin age (80% of the age).
Then it tries to create a set containing this amount and fails to find that much age in an amount of 5.73MM.
So lets try this (those 3 pastes above didnt have enough coin age selected).
Please re-paste 'exec getabnweight 238749292 1' and 'exec createabn 238749292' and lets see where those fail now?
No problem. Alas, I think I went one step "too far" now for this kind of troubleshooting. I selected that 4.5 M chunk in coin control and did "exec bankroll 20 200000" and this actually worked (which is quite logical, since this requires no coin age). So now my wallet is pretty much spent regarding coin age. Next couple of days and weeks are pretty busy for me. I think I'll just let it sit for a couple of days and see where this is leading. Then I'll try again next week. If it still doesn't work, I'll get back on that. Thanks for your efforts. No problem - and on a side note - if you were trying to find a way to use the coin age of an unlocked sanctuary - it is not possible, as the wallet will skip by those amounts - and if a hacker modifies the wallet to force it in the gsc transmission, the sanctuaries will skip by those points anyway (rewarding 0 for them) - just like the sancs skip by 666 tithe variations.  So the only way to start pogging from an unlocked sanc coin, is to run it through the bankroll command first. (Or spend it into a different amount). |
|
|
|
yes, it failed again. Here's the log: SmartContract-Client::Creating Client side transaction for campaign POG
CreateGSCClientTransmission - Total Bal 5736765.318842, Needed 4591906.227281, Coin-Age 209436615.932199, Target-Spend-Pct 0.800000, FoundationDonationAmount 2500.000000 Donating 2500.000000 to the foundation.
Created client side transmission - <MT>GSCTransmission</MT><abnmsg>8223ed00bf6e7c746b2938d9e90d6d1695af35fc78c9dc82cea87790548f0e8b</abnmsg><gscsig>IO/rwZPs3gwbWjmu8mHSl/Z7AX6gb4hlZxfuwE5UUUeLZ4bEmDE96T8hWXZyrjIrfhT7QBt0CPx8+9tBj0lOqHQ=</gscsig><abncpk>BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U</abncpk><gsccampaign>POG</gsccampaign><abnwgt>167549293</abnwgt><diary></diary> [] with txid 0000000000000000000000000000000000000000000000000000000000000000 I always used pog_coinagepercentage=.50, but today also tried 0.8. No luck so far. Sorry for the hassle, but I still don't have enough info - if you want you can e-mail me, or we can continue. So, with a POG GSC transmission, the wallet is scanning the available coins, and finding 298.436615MM coin age available. Then it says, I need 238.749292MM for this transaction of coin age (80% of the age). Then it tries to create a set containing this amount and fails to find that much age in an amount of 5.73MM. So lets try this (those 3 pastes above didnt have enough coin age selected). Please re-paste 'exec getabnweight 238749292 1' and 'exec createabn 238749292' and lets see where those fail now? |
|
|
|
All right, here we go: {
"Command": "getabnweight",
"version": 2.7,
"weight": 209170826.2300579,
"total_required": 5736757,
"coin_age_data_pre_select": "1970.6000(0.22)=[429.59] depth=48, <ROW>2763.7000(1.22)=[3357.52] depth=262, <ROW>9228.6300(1.00)=[9187.73] depth=214, <ROW>1222793.8541(2.01)=[2457545.03] depth=431, <ROW><TOTALREQ>1236756.78</TOTALREQ><TOTALAGE>2470520</TOTALAGE>",
"weight 25000.00": 2470519.879999999,
"total_required 25000.00": 1236756
}
{
"Command": "getabnweight",
"version": 2.7,
"weight": 209153894.8350926,
"total_required": 5736757,
"coin_age_data_pre_select": "1970.6000(0.22)=[423.78] depth=47, <ROW>2763.7000(1.21)=[3349.37] depth=261, <ROW>9228.6300(0.99)=[9160.50] depth=213, <ROW><TOTALREQ>13962.93</TOTALREQ><TOTALAGE>12934</TOTALAGE>",
"weight 10000.00": 12933.64689814815,
"total_required 10000.00": 13962
}
{
"Command": "getabnweight",
"version": 2.7,
"weight": 209186960.8534954,
"total_required": 5736757,
"coin_age_data_pre_select": "1970.6000(0.22)=[435.13] depth=49, <ROW>2763.7000(1.22)=[3365.30] depth=263, <ROW><TOTALREQ>4734.30</TOTALREQ><TOTALAGE>3800</TOTALAGE>",
"weight 2500.00": 3800.42849537037,
"total_required 2500.00": 4734
}
{
"Command": "createabn",
"xml": "<MT>ABN</MT><abnmsg><nonce>32e90172039812f670ee554e7de77b2d475909ec1e0cc82058bf6ee602638252</nonce><ppk>ppk</ppk></abnmsg><abnsig>H0hduxZ8MI49s+0H+C9EpyMfUWD4NgQMByXztIA+wQJdO7xm+RXKsOWhaxoLh+vLjFkb8BNByRJffZhofEqvzDA=</abnsig><abncpk>BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U</abncpk><abnwgt>2500</abnwgt>",
"err": "",
"coin_age_data_selected": "1970.6000(0.22)=[435.13] depth=49, <ROW>2763.7000(1.22)=[3365.30] depth=263, <ROW><TOTALREQ>4734.30</TOTALREQ><TOTALAGE>3800</TOTALAGE>",
"success": "dd21389b880dad2fb99a1a852cdbc0b5c288b5bfeb9b0ed3093a01918918e0d1",
"coin_age_data_pre_select": "1970.6000(0.22)=[435.13] depth=49, <ROW>2763.7000(1.22)=[3365.30] depth=263, <ROW><TOTALREQ>4734.30</TOTALREQ><TOTALAGE>3800</TOTALAGE>",
"audited_weight": 3810.014570600166,
"vin_coin_age_data": "\nGetVINCoinAge: Output #0, Weight: 439.12, Age: 0.22, Amount: 1970.00, TxTime: 1564581832...Output #1, Weight: 3370.89, Age: 1.22, Amount: 2763.00, TxTime: 1564495682..."
}"Edit: It just came to my mind: could this be somehow sanc related? Because I'm currently trying to migrate my sanc to another ISP/server and those coins just linger in my wallet ... But if they aren't locked via masternode.conf, they are just normal coins, aren't they? " -> Ahh yes, thats possibly it, but we do skip by them both in select and spend. So could you try this first please, try locking the coins in coin control manually, then manually send the GSC again, and if it fails, could you please paste the portion of the log with the whole snippet, and also the target coinage percentage? |
|
|
|
Hello again. Today I wanted to do "exec sendgscc" as I always do it manually every couple of days. However I only get this error: 19:41:26

{
"Command": "sendgscc",
"Error!": "CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds."
}
How is that possible? My wallet doesn't have less coins than usual, it didn't use any coin age for mining (at least I think so), and I get this error no matter how much "pog_coinagepercentage" and "pog_foundationdonation" I chose in the config file. Has there anything changed about the process? Thanks. Its possible if the amount of coins designated for the coinagepercentage are all less than 5 in depth. Take a look at coin control, and see if they are < 5 depth? Once 5 passes, it will be able to send again. No, that can't be it. Confirmation numbers range from 40 to 27k. There are some positions without an entry under "received with address". Could that be the cause? Althogh there are plenty of other coins to choose from ... Hard to say, more info needed. Next step, try dumping 'exec getabnweight N 1' and 'exec createabn N' where N is roughly the total value of coins it failed to select (and be sure to include the 1 in the first command) and we'll have to analyze each output. |
|
|
|
Hello again. Today I wanted to do "exec sendgscc" as I always do it manually every couple of days. However I only get this error: 19:41:26

{
"Command": "sendgscc",
"Error!": "CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds."
}
How is that possible? My wallet doesn't have less coins than usual, it didn't use any coin age for mining (at least I think so), and I get this error no matter how much "pog_coinagepercentage" and "pog_foundationdonation" I chose in the config file. Has there anything changed about the process? Thanks. Its possible if the amount of coins designated for the coinagepercentage are all less than 5 in depth. Take a look at coin control, and see if they are < 5 depth? Once 5 passes, it will be able to send again. |
|
|
|
Dear all,
for me it really not clear how to mining right now.
Is there a simple guide to understand how to configure the wallet and what I need to do?
I moved from this reward every day
6/27/2019 08:44 Confermato (7193 conferme). Ottenuto dal mining (nessuna etichetta) BNsCD3pRWJ4C48Uwh8oc3CBGZqah7oYPoA 3201.27269775
to this reward right now
7/30/2019 21:24 Confermato (129 conferme). Smart-Contract Reward (CHRISTIAN-PUBLIC-KEY) BQkeLHUg6PXSjoGfGa9pShe6ngiv6i68Tz 8.34000000
For sure I make a mistake in some way.
Can I have a little help ?
Thank a lot
Ale
If you want to mine solo, you need to unlock the wallet, although I recommend you to connect to Biblepay pool for this purpose. You can also obtain rewards participating in Generic Smart Contract campaigns (which is the second reward you show in your post). You can check here about both mining and GSC: https://www.reddit.com/r/BiblePay/comments/6umlqq/how_to_mine_biblepay_on_windows/Belowe my config file, I'm in the leaderboard too addnode=node.biblepay.org nickname=lalexcross genproclimit=6 minersleep=0 pool=https://pool.biblepay.org workerid=my worker id Can I use more than one pc with same config file to mining ? Thanks I'm glad you asked. Pool.biblepay.org requires you to have a separate workerid for every machine. So please create separate workerids. Other than that, the config file could be the same. Also, please read the section about ABN. We require 125K ABN weight if you set up a non-funded (self funded) miner: https://wiki.biblepay.org/Quick_Start |
|
|
|
I had a 50% discounted offer in SatoshiSolutions of $250 back in 2018 but I guess that doesn't apply any more.
They asked me about the potential MN number of hosted nodes (no idea, does anyone have the BBP nodes in GIN?) and if we were ipv6 compatible (yes).
Finally they are doing an expansion plan so before quoting and comitting they want to confirm a couple of things with technicians.
I'll come back when I have more info.
We have some feedback. They will do the setup and testing in the next few days. Listing fee is $250 in BTC, I will pay it myself upfront to gain time as we are close to the end of this month's superblock I will inform when the service is live. Meanwhile some links: https://www.swyft.network/https://host.swyft.network/Great! And responding to Togo's message about Apollon still being in business, MIP is going to see about adding BBP. |
|
|
|
We're about to test chainlocks in testnet if anyone wants to help, we could use one more sanc: https://forum.biblepay.org/index.php?topic=391.new#newAnd if you dont have a sanc we could still use the help to ensure our llmq quorums are good and our blocks are locked with chainlocks. Also, there is a post on the last page on how to sync from 0 using the new feature in less than 5 minutes. |
|
|
|
*** ATTN: Sanctuary Owners ***
This message is for every sanctuary that is hosted on GIN: Note that first of all, I wish that you stay with BiblePay regardless of how hard the configuration setup is for your next node whether its manually hosted or if we find another turnkey service. But, I understand some of you might consider selling your sanctuary and leaving because you believe the manual hosting of a sanc is just too technically daunting. I just want to ensure that you are aware of another option: Right now, our GSC (generic smart contracts) are paying more in rewards per BiblePay invested than sanctuaries. So please consider utilizing your unlocked BBP in this way - before deciding to leave BBP. All you have to do is: - Create a CPK (Create a Christian Public Keypair, with a single command) - (exec cpk nickname) - Decide if you want to leave the default daily tithe of 2.50 BBP, or if you want to change it to zero or a higher figure - Join POG (exec join pog) - Leave your miner running on one thread, or alternatively, manually send a GSC transmission each day (exec sendgscc). If you mine on one thread, the miner will send a GSC once every 12 hours. - Once you are setup, wait 24 hours then check the Leaderboard to ensure you are in it See our quick start guide to get started in POG: https://wiki.biblepay.org/Quick_Start
|
|
|
|
|
Could we please have some people vote on the outgoing pool letters, as they are very stagnant. We need a few more votes so they can be auto approved and sent.
(Vote by clicking : Orphans | Outgoing Letters | Right click on a letter to vote up or down) Or Left click a letter to view it first.
I will also be increasing the letter writing bounty today so please consider writing a letter.
|
|
|
|
Hello all.
Just two questions about the new wallet:
1. I tried the "changequantity" command together with exec sendgscc and it worked perfectly, giving me (in my case) 50 denominations as change. Now if I was to send another donation, would this take one of those denominations and again return 50 new ones? Because this would result in an enormous amount of small chunks over quite a short time. Or would it be wiser to set it to "1" for the next 50 donations?
2. Is it now possible to use the dual mining mode (funded/non-funded) with the Linux binaries?
Thanks!
Hi Dave, On #1, You should be able to leave it as-is, as the wallet recycles by using up the percentage designated first, then emitting 50. So if your target coinagepercentage for pog is .50, its using half of the free transactions in the wallet first, then emitting 50. So on day #3, if you had 150 tx, 75 are consumed and 50 are emitted meaning it would be contained. On #2, Yes. Im still going to be upgrading the pool to 2.0 in 2 days, but in the mean time it should be honoring the dual mining mode. |
|
|
|
If anyone is looking to store food for the Great Tribulation, check out this method for nitrogen sealing grains: https://www.youtube.com/watch?v=pg5rob9sBF8&feature=youtu.beIll add this to our gospel links. Btw, you can find 50 lbs bags of deer corn for $7. (You can store it unground and grind it later for cornbread etc). |
|
|
|
I have put a new pc to test solo mining @ 1.4.4.5
Is it can be ignore the message in "poolinfo5" if that ensure the wallet have enough ABN weight?
"poolinfo5": "Internal ABN: Invalid 1564161497; ",
"abninfo": "ABN: OK; ",
"weight 125000.00": 161401.5844444444,
"total_required 125000.00": 403854
Yes, that poolinfo5 just shows that the internal ABN is still low, but in abninfo, the funded one is OK, so yes that is normal. We made the latest version clear poolinfo5 after about 3 mins or so. Understood. Can I know that in the latest version 1.4.4.5 or later in pool mining and solo mining, is it no need to use command #bankroll 125000 for ABN weight adjust? And some machine using 1.4.4.x for pool mining, since that the message shown:"Warning: Every masternode (out of 184 known ones) is running on a newer software version. Please check latest releases, it's very likely that you missed a major/critical update." So now the old version is no longer working properly? Furthermore, will have a impact if have multiple machine using same wallet in pool mining / solo mining? Thanks Rob. Hi Envoy! So first I want to explain that between the mandatory upgrade (that we believe fixed our prior syncing issues) and the upgrade to the new pool protocol (v2.0 in 1.4.4.4) the older miners will need to upgrade to 1.4.4.5 within a few more days, as soon pool.biblepay.org will increase its minimum required mining version. This new version will allow more flexible configs and more accurate health reports. As far as the exec bankroll, the newest versions (1.4.4.4+) sends out more denominated change, but only in GSC created transactions. So you actually have to be in POG or Healing or Cameroon One to get the benefit of automatic change. For example, if you tithe 2.50 in POG per day, the wallet will send back change in 10 bills - meaning you wont have to create bankrolls. If your miner only heat mines, you only have to create the bankrolls every so often~ after the initial bankroll (as the wallet will pick the minimum amount of coins for a new abn). But yes you would have to keep an eye on them manually so they dont all get used up. But in general, if you have 10 200K notes the abn creator will use the least and you will still have 10 after you get the change. |
|
|
|
I have put a new pc to test solo mining @ 1.4.4.5
Is it can be ignore the message in "poolinfo5" if that ensure the wallet have enough ABN weight?
"poolinfo5": "Internal ABN: Invalid 1564161497; ",
"abninfo": "ABN: OK; ",
"weight 125000.00": 161401.5844444444,
"total_required 125000.00": 403854
Yes, that poolinfo5 just shows that the internal ABN is still low, but in abninfo, the funded one is OK, so yes that is normal. We made the latest version clear poolinfo5 after about 3 mins or so. |
|
|
|
** GIN is closing on August 1st **
Dear Client, This is an official notice regarding the GIN Platform suspending of masternode hosting services as of Aug 01, 2019. Why? The recent drop in number of hosted nodes while at the same time GIN Platform using a scaled-up infrastructure, became a huge red flag on this business line profitability. Basically it became financially impossible for the platform to keep up operations. As the monthly margin was reinvested in the company, there are no buffers that could allow us to maintain operations at a daily loss. We have seen this coming recently and we tried to keep afloat the masternodes service as much as we could by optimizing masternode allocations, trimming down all non-essential indirect costs etc. We reached this unfortunate day when we need to take a sorrow and tough decision for us and for the community. Why not keep it up at a loss until the market recovers? We think the masternode landscape changed a lot in the past year. Blockchain technology is moving fast, staking appeared as a new promised consensus mechanism. The masternodes market proved to be quite resilient during the alts winter. While some thinkers in the space opine that there are signs that the masternodes space is getting some traction again, we cannot assume anything on our end. We have been bootstrapped from the beginning and what played as a great way to be flexible, did not help us now when a cash flow injection was needed. As you know, we looked for fresh money for GIN Platform through a strategic investor, but the downtrend of the market and the complexity of the business did not favour us. At the same time, our service is more expensive than the competition's which does not perform very well in a market where customers at this stage of the masternodes space will almost always choose the cheapest. While we set the standards in the industry, we did not adapt well to the cheap price strategy as we saw and believed beyond the hosting service for the masternode spaces. This time, we might have been proven wrong. Why the urgency in closing? We are making all endeavors to return all the customer balances and prorated payments for committed nodes to minimize the impact on the customer. The only way we can do this is if we eliminate all costs immediately and start the refund procedures. What happens with the nodes you paid for in advance? Your GIN Platform balance shall be credited with the prorated GIN amount for the remaining days of service. E.g. for a 30 GIN payment for 30 days, you shall be credited 10 GIN if only 10 days of paid service remain. To be eligible for this refund, do not delete the committed nodes How to get my balance back? Send an email to refunds@ginplatform.io from the same address you use to login to the platform by Sep 01, 2019, containing your GIN address where to receive the funds. Refunds shall be processed in maximum 30 days. Is there any alternative to closing down the platform? We evaluated all possible scenarios, it is with great pain that we have decided on this. If anyone from the community thinks they can do a better job and keep the service running, we are open to a handover to a different entity. Even today, at this hour, we stand ready to discuss with any potential buyer for the GIN Platform if this can help maintain the customer base and the service unaffected, with the hope that the market will get well soon. Email alex.andreescu@ginplatform.io if you are interested. What happens to Gincoin & GEA? It is important to note that GINcoin and GIN Foundation have a different activity. While the Platform and the Coin where operationally interconnected, GINcoin and GEA Protocol will be the focus of our remaining activities related to GIN. We aim to take the GEA plans towards the public beta as per the roadmap that we announced from early stages.. The required assets that were part of the GIN Platform shall be handed to the GIN Foundation which will continue receiving funds and will try to make the best in promoting GEA and GIN. On a personal note, we are also exhausted by the whole situation. We had a year of great achievements together with our clients and community. We believed that a project that aimed at providing huge utility in a coin ecosystem cannot lose. We created the first platform, had the first utility coin to pay for its services, notarized GIN blockchain, never incurred a serious 51% attack and we grew fast in just a couple of months. This is a sad moment, but we believe that while one maintains the right compass of honesty, transparency and hard work, there is always a second chance at some point in time. We would like for all our masternode holder clients for trusting in our services. We will continue in this space, even though we will take some time to digest the whole year and understand the crypto business better. We understand the frustration of many, and we want to transparently discuss any issues related to the masternode hosting service provided by GIN Platform. Thus, we aim to organize an AMA session with the community. A proposal date will be announced very soon. Thank you, GIN Platform Team
|
|
|
|
|
Show Posts
