Here's a strange thing, if I un-click/un-select all in coin control window, Quantity 31 and ~ 8792 GRW get added on top of my balance. So when I select everything in Coin Control I have 8792 GRW more to send. But the Bytes ~ goes to red. What you see on the picture below, is the extra GRW, that has appeared in my coin control window, without any reason. if some coin were selected (checked) before staking, it's going to throw off the balance (only a restart would clear that mismatch balance). the bytes in red means that the bytes are over limit (transaction could be accepted or might not.) If you are trying to combine multiple blocks into one, and it doesn't work. try doing multiple transaction to achieve that. if you seem to have unaccounted coins, I suspect that those coins were marked selected before they staked and the selection remained in the memory after they staked. so restarting the client should clear the memory for that selection.
|
|
|
SHAME ON THE DEVS OF THIS COIN FOR NOT BEING MORE AGGRESSIVE AND GETTING THIS COIN LISTED ON MORE THAN ONE EXCHANGE.
THEIR LACK OF EFFORT TO GET THIS COIN LISTED ON MORE THAN ONE EXCHANGE HAS LED TO A 40% DECLINE IN VALUE IN THE LAST 12 HOURS.
I DON'T KNOW WHO IS MORE INCOMPETENT - THEM OR CRYPTSY - THIS COIN SHOULD BE TAKEN OVER BY THE COMMUNITY - IT'S CLEAR THEY COULD CARE LESS ABOUT THEIR ABANDONED CREATION.
CTYPTSY HAS HAD THE COIN HOSTAGE FOR THE LAST WEEK - THIS SHOULD NEVER BE ALLOWED TO HAPPEN AGAIN
LET'S TRY AND GET ON POLONIEX OR MINTPAL ALSO
MY HUMBLE 2 SATOSHI
this attitude is not going to get you anywhere. you're concern about having more exchanges is justified, but your rant against the devs is not. It's a community effort after all if a coin gets somewhere. instead of shamefully blaming dev about this issue, you should use your energy and words to get people work together in achieving a desired goal. did you contact poloniex? did you contact allcoin? did you contact bittrex? did you contact atomic-trade ? do so before complaining about this. and then when it's done... just DON'T COMPLAIN!
|
|
|
yes it's safe, if the address is not showing up on the list, likely it's because the script has been stuck somewhere, it doesn't not mean something is wrong with your address. I need to put some more work into the explorer before it is fully functional. Soon I will have more time (hopefully )
|
|
|
Oh! How do I disable POS minting before launching the wallet?
Add reservebalance=987654321 in configuration file or add -reserverbalance=999999999 to your shortcut to the qt (in windows). also if you wallet is locked, it wont stake until you unlock it, so you wait until synced before unlocking also, in the next release of the qt, staking should be disabled until sync is complete. this is already on the github, for those who want to try it out now.
|
|
|
I'm loving those clickable icons They are really useful and give plenty of cool information! According to my wallet I should have 50% chance to stake in 17 minutes a 6 days old block, sweet! We need to work on an RPC command that will list all of the blocks held by a wallet. That would be super useful. Almost like the coincontroldialog without the coincontrol.
I'm not sure I see why this would be useful!? You would want the rpc command to give out what exactly? block hash/number ? I'm not sure a wallet "holds" a block. since in a block you could have n number of transactions. Maybe clarify what you meant. What I mean is an rpc command like "getblocks" that will return each block, the number of confs, and the stake weight oh you were talking about blocks of GRW. I was thinking about blocks from the blockchain. Is that correct?
|
|
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right? Yep 9 days. I tend to think it is correlated because it came through just an hour or two after I rebuilt, but it could also be coincidence. it might be, but we'll see on next round of staking... It mostly always took around 9 days to successfully stake a block. It's a good thing if that fixed it! EDIT: we might know sooner, I just checked and I have 3 blocks from the 13th, only 6 days old! I will rebuild my client and see what happens Something might be off in the calculations My client says I'm about to get stake but my weight is far above the network weight. I'm trying to figure this out EDIT: Nothing is off, it's just how network stakes is calculated vs how own stake is calculated, but stakes seems to get in at around 9 days of age still
|
|
|
I'm loving those clickable icons They are really useful and give plenty of cool information! According to my wallet I should have 50% chance to stake in 17 minutes a 6 days old block, sweet! We need to work on an RPC command that will list all of the blocks held by a wallet. That would be super useful. Almost like the coincontroldialog without the coincontrol.
I'm not sure I see why this would be useful!? You would want the rpc command to give out what exactly? block hash/number ? I'm not sure a wallet "holds" a block. since in a block you could have n number of transactions. Maybe clarify what you meant.
|
|
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right? Yep 9 days. I tend to think it is correlated because it came through just an hour or two after I rebuilt, but it could also be coincidence. it might be, but we'll see on next round of staking... It mostly always took around 9 days to successfully stake a block. It's a good thing if that fixed it! EDIT: we might know sooner, I just checked and I have 3 blocks from the 13th, only 6 days old! I will rebuild my client and see what happens
|
|
|
done, I was currently working on that file to add Fast stake My stake came through on my daemon after rebuilding this morning Excellent , but I wonder if it's because of that commit or just because they were mature enough... it's been about 9 days right?
|
|
|
Unick I recommend that you clean out the /src/obj folder on github so that I don't have to clone it and can build from scratch no problem Good catch, it's done thanks
|
|
|
anyone tried to send mined coins it to crypsy lately ?
is it safe that they arrive with the incoming fork now ?
Cannot currently create an address at Cryptsy - you just get a notice about wallet downtime. I'd hold off until service resumes and we can see whats what After expensiencing the long update on the blockchain, it's most likely that Crytsy is also experiencing the same problem as us. DEV, on the next update, can you create a similar CAPS wallet to TEK? TEK wallet doesn't need nodes manually added and it syncs faster.DNS seed are already activated for CAP. no need to manually add nodes!
|
|
|
my wallet address is not showing up on cap.blockx.info/richlist/
and i was wondering why? i am running wallet V2.0.0.0
I don't think iamunick was ready to fully release it. correct, The explorer is up but the features are not fully functionnal, so I haven't officially released it (but still some people found the link ). Being busy with updating the Growthcoin client, I didn't have time to work on what I need to update for all the cool features of the new explorer to be compatible with the updates Abe did to their code. Thanks for being patient with this
|
|
|
done, I was currently working on that file to add Fast stake
|
|
|
We need to get the new and correct block explorer updated on http://coinmarketcap.com/The block explorer is not correct, and coinmarketcap is therefore understating Mintcoin's market capitalization!Mintcoin has more than 19,228,164,406 coins in circulation now, but coinmarketcap is using this number, from the time the old block explorer went down. We need to contact them and get them to use http://mint.blockexplorer.cc/chain/MintCoinI contacted Gliss here on Btt. No reply so far... http://mint.blockx.info/get/chain/MintCoin is catching up, sorry for the downtime Thanks! What's your Mint address btw? I believe you will find his address right here. lol, that is correct
|
|
|
We need to get the new and correct block explorer updated on http://coinmarketcap.com/The block explorer is not correct, and coinmarketcap is therefore understating Mintcoin's market capitalization!Mintcoin has more than 19,228,164,406 coins in circulation now, but coinmarketcap is using this number, from the time the old block explorer went down. We need to contact them and get them to use http://mint.blockexplorer.cc/chain/MintCoinI contacted Gliss here on Btt. No reply so far... http://mint.blockx.info/get/chain/MintCoin is catching up, sorry for the downtime
|
|
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine UPDATE: I did get a stake with the latest build. it took just under 9 days. On a side note, it always took around midway to max stake weight to get a valid PoS block with GRW. So I'd say you should have yours in around 2 days from now.
|
|
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine Have you also had success staking with the daemon rather than the Qt gui? I have successfully staked with the lastest build of the daemon. But I'm continously forking. I have to stop the daemon, restart with -reservebalance=999999, repairwallet to remove orphans and return to the correct fork and then restart the daemon. Sometimes I cannot connect to any peer since they close the connections: they say closed socket or connection timeout. This is new, I haven't got stuck on a fork since adding the checkpointing node. Have you tried just to let your client do it's thing? When generating PoS blocks, they still have to be accepted by the network, so what you refer to as a fork might just be that those blocks were not all confirmed and a better block was accepted instead of yours. If you let the client go, it should reorganize by itself and clean get back on the right fork. repairwallet won't get you back on the correct fork. All it does is repair your wallet by removing orphans and fixing mismatched coins (transactions no accepted by the network but marked as spent in your wallet) so this steps has no influence over you getting back on the right fork. The connection timeout issue is something I haven't had time to dig deeper in. but likely not an issue for what you are describing. And reserve balance is only used to mark a certain amount has not available for minting. So I really suspect that what you refer to as forking is just orphaned blocks and should normally be fixed by itself. The other thing that might be happening, is that if you generate PoS block BEFORE being fully synced to the network, you might indeed get stuck on a fork. I'll try to get that fixed for the next release. the quick fix for that is to start your client with -reservebalance=99999999
|
|
|
No I haven't yet staked with the latest build, but I wouldn't be worried yet. It seems to take around 8 days of age to get stakes with GRW. I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine Have you also had success staking with the daemon rather than the Qt gui? No, I always used the Qt GUI for PoS and the daemon for PoW. But I don't see why it shouldn't work either way
|
|
|
|