MicroGuy (OP)
Legendary
Offline
Activity: 2506
Merit: 1030
Twitter @realmicroguy
|
|
November 04, 2013, 04:24:01 AM |
|
Over 200 confirms and I still haven't gotten a transfer I made over 6 hours ago. I made it from a 0.7.1.2 wallet to a 0.7.1.3 wallet on different computers. I'm afraid to upgrade the other wallet at the risk of losing those coins from what other people are saying. Losing coins is completely unacceptable.
The only way you can lose valid coins is by losing your wallet. There is no reason to fear upgrading. The people talking about losing coins were mining "magic coins" on their own chains when the network was segmented.
|
|
|
|
akumaburn
Sr. Member
Offline
Activity: 281
Merit: 250
The Gold Standard of Digital Currency.
|
|
November 04, 2013, 04:28:21 AM |
|
Ok, so basically this new attack protection says to anyone with a significant hashrate, "Fuck you". What about pools with large hashrates (large in comparison to the GLD network)? There are two main pools for GLD that I can see, what happens if one of those pools bumps over 51%? Will they go into the ban list noted in the pdf and be forbidden to solve new blocks? Likewise, What if an individual with 49% of the coins hashrate quits mining GLD and leaves another person who had 27% of the network now with over 51%? Will they get banned from solving new blocks as well?
No, the new client has a built in mechanism which stops you from triggering the defense accidentally.. Essentially once you've mined 5 blocks in less than 10 minutes.. you'll get rejects until the 10 minutes is over before you can mine the 6th block(that is if no one beat you to it). Only a modified/old client can trigger the defense.
|
|
|
|
akumaburn
Sr. Member
Offline
Activity: 281
Merit: 250
The Gold Standard of Digital Currency.
|
|
November 04, 2013, 04:33:43 AM |
|
Over 200 confirms and I still haven't gotten a transfer I made over 6 hours ago. I made it from a 0.7.1.2 wallet to a 0.7.1.3 wallet on different computers. I'm afraid to upgrade the other wallet at the risk of losing those coins from what other people are saying. Losing coins is completely unacceptable.
The only way you can lose valid coins is by losing your wallet. There is no reason to fear upgrading. The people talking about losing coins were mining "magic coins" on their own chains when the network was segmented. This is true.. older clients have trouble syncing to the correct chain, which is probably why your transaction failed to show.. The coins are not lost(assuming they were mined prior to the network segmentation), they are still available to you, simply upgrade to the latest client.
|
|
|
|
kelsey
Legendary
Offline
Activity: 1876
Merit: 1000
|
|
November 04, 2013, 04:37:19 AM |
|
Over 200 confirms and I still haven't gotten a transfer I made over 6 hours ago. I made it from a 0.7.1.2 wallet to a 0.7.1.3 wallet on different computers. I'm afraid to upgrade the other wallet at the risk of losing those coins from what other people are saying. Losing coins is completely unacceptable.
The only way you can lose valid coins is by losing you wallet. There is no reason to fear upgrading. The people talking about losing coins were mining "magic coins" on their own chains when the network was segmented. Yeah think the biggest complainers are not normal gldcoin backers/miners but those who saw ridiculous profit figures at coinchoice (or watever), cryin that they lost a few fairy coins on their own chain. If the dev team is experimenting (nothing ventured nothing gained) then treat current mining as beta testing, these guys are trying stuff that could benefit the entire crypto community (and results of which they have/will openly sharing with other devs etc)....cut them a bit of slack. Great to have an active dev team, who won't just settle for being another copy paste alt. Keep up the good work!
|
|
|
|
dnelsonfl
Newbie
Offline
Activity: 20
Merit: 0
|
|
November 04, 2013, 04:39:29 AM |
|
OK So I read the documentation you referred to. As you pointed out, it is very skimpy on details. The block chain explorer indicates we are currently at block 102,067. So we are past block 100,000 and only rule #1 applies (no clauses). No miner may produce more than 5 blocks every 10 minutes. It's interesting. The lost coins I do agree were probably a result of either the wallet.dat not being backed up or the miner being on the wrong block chains. However, seeing and having experienced all or nearly all the mined blocks being rejected, there's no way that can be normal or even expected behavior. The documentation would make me think I should have cleared at least 5 blocks every ten minutes minimum. I understand it's experimental, and to tell the truth, that's part of what makes all of this mining so darn fun. However, hearing the new system described as more of a lottery was a poor choice of words. Lotteries have only a handful of winners and a whole ton of losers. Nobody wants to be a loser, and I wonder if any serious miner with an eye on his or her bottom line would be interested in sticking with mining a lottery. They'd be more interested in guaranteed results. Perhaps it would appeal to a few gamblers and speculators. All that being said, I am impressed by your attempts to invent new ways of tackling the 51% problem. I hope you are able to work out the kinks and make the network stable. In the mean time, I'm going to mine some other coins while I keep an eye on the thread and perhaps once stable give it another go. So please keep us updated on the progress. -David
|
|
|
|
akumaburn
Sr. Member
Offline
Activity: 281
Merit: 250
The Gold Standard of Digital Currency.
|
|
November 04, 2013, 05:15:14 AM Last edit: November 04, 2013, 05:28:08 AM by akumaburn |
|
OK So I read the documentation you referred to. As you pointed out, it is very skimpy on details. The block chain explorer indicates we are currently at block 102,067. So we are past block 100,000 and only rule #1 applies (no clauses). No miner may produce more than 5 blocks every 10 minutes. It's interesting. The lost coins I do agree were probably a result of either the wallet.dat not being backed up or the miner being on the wrong block chains. However, seeing and having experienced all or nearly all the mined blocks being rejected, there's no way that can be normal or even expected behavior. The documentation would make me think I should have cleared at least 5 blocks every ten minutes minimum. I understand it's experimental, and to tell the truth, that's part of what makes all of this mining so darn fun. However, hearing the new system described as more of a lottery was a poor choice of words. Lotteries have only a handful of winners and a whole ton of losers. Nobody wants to be a loser, and I wonder if any serious miner with an eye on his or her bottom line would be interested in sticking with mining a lottery. They'd be more interested in guaranteed results. Perhaps it would appeal to a few gamblers and speculators. All that being said, I am impressed by your attempts to invent new ways of tackling the 51% problem. I hope you are able to work out the kinks and make the network stable. In the mean time, I'm going to mine some other coins while I keep an eye on the thread and perhaps once stable give it another go. So please keep us updated on the progress. -David The difficulty update should address that.. what I believe is happening is that some parts of the network have high enough hashpower to get the next block out the fastest to the point of mining 5 blocks before anyone else even has a chance to. This is possible because of the broken difficulty code which allows valid blocks to be mined without much effort otherwise there would be time for you to mine your own block in between. With regards to your comments about it being a lottery, keep in mind that all mining(even on bitcoin/litecoin etc) is essentially a lottery... you're betting on your ticket being the one that the chain announces/accepts, there could be n number other tickets out there each with different numbers but only one of them gets announced and accepted. That said, the new difficulty algorithm will give you a far higher chance of winning than the current one which essentially gives higher hash-rate/lower latency portions of the network all the advantage. I've just finished coding the new difficulty algorithm and it should help greatly. I want be sure it works first though so I will be going over it step by step prior to release/announcement.
|
|
|
|
blazin8s
|
|
November 04, 2013, 05:45:52 AM Last edit: November 04, 2013, 09:50:18 AM by blazin8s |
|
So the 60k+ I mined in the last day and a half isn't real and gone forever? What a crock of shit
We should all get retro paid at least the normal rate for the past couple days of losses.
|
|
|
|
dnelsonfl
Newbie
Offline
Activity: 20
Merit: 0
|
|
November 04, 2013, 05:53:26 AM |
|
The difficulty update should address that.. what I believe is happening is that some parts of the network have high enough hashpower to get the next block out the fastest to the point of mining 5 blocks before anyone else even has a chance to. This is possible because of the broken difficulty code which allows valid blocks to be mined without much effort otherwise there would be time for you to mine your own block in between.
So it is 5 blocks per 10 minutes on the network? I mistook it for a speed limit on the individual miner, not the entire network. Your comments about the lottery were noted, thank you for the clarification. -David
|
|
|
|
MicroGuy (OP)
Legendary
Offline
Activity: 2506
Merit: 1030
Twitter @realmicroguy
|
|
November 04, 2013, 01:53:58 PM |
|
[UPDATE] Mandatory Update 0.7.1.4 (Difficulty fixes)Download Links: http://gldcoin.com/get-started/Notes: The difficulty algorithm has been fixed. This is a mandatory update, so be sure to do it before the hard fork at 103000 occurs. The hashrate should correct itself over the next day or so. Sorry for the rather frequent updates of late, we are trying to get the situation resolved as quickly as possible.
|
|
|
|
albon
Legendary
Offline
Activity: 1876
Merit: 1536
|
|
November 04, 2013, 02:28:00 PM |
|
with this update can I mine again? Everytime I have tried latly my miners can not connect. My client says it is on the correct chain and block but even when I use the inbuilt miner in the client it reports 0 hash rate
|
|
|
|
hhs99
Member
Offline
Activity: 103
Merit: 10
|
|
November 04, 2013, 05:01:58 PM |
|
Please correct me if I'm wrong. When you solo mine you setup the conf file then use cgminer or something like it to generate the coins? I tried to use the start mining button but nothing happened and I left it on for a few hours. I looked at the debug console and it said the "The setgenerate command has been disabled" Ive never solo mined before.
|
|
|
|
Bortmehanic
Full Member
Offline
Activity: 153
Merit: 100
Switchercoin.com
|
|
November 04, 2013, 05:27:36 PM |
|
do not fix unbroken I hope Goldcoin comes back to us.
|
|
|
|
ryen123
|
|
November 04, 2013, 05:28:21 PM |
|
Please correct me if I'm wrong. When you solo mine you setup the conf file then use cgminer or something like it to generate the coins? I tried to use the start mining button but nothing happened and I left it on for a few hours. I looked at the debug console and it said the "The setgenerate command has been disabled" Ive never solo mined before.
The mining button does nothing. Look inside your goldcoin.conf file, you should see these few lines: rpcuser=your-username rpcpassword=your-password rpcallowip=127.0.0.1 rpcport=8122 server=1 Put in your own rpcuser and rpcpassword, also I added rpcport. Make sure server=1. For solo-mining, your cgminer should point to the goldcoin wallet as above. Example -------- cgminer.exe --scrypt -o http://127.0.0.1:8122 -u your-username -p your-password
|
|
|
|
hhs99
Member
Offline
Activity: 103
Merit: 10
|
|
November 04, 2013, 05:35:27 PM |
|
So this should work? then run the wallet or the goldcoind?
rpcuser=username rpcpassword=pwd rpcallowip=127.0.0.1 daemon=1 server=1 gen=0 maxconnections=64 dns=1 checkpoints=1 listen=1 rpcport=8122 dnsseed=1 banscore=50 bantime=14400 addnode=50.116.22.43 addnode=88.161.131.83 addnode=24.70.184.213 addnode=208.115.109.157 addnode=72.200.175.240 addnode=192.241.134.49 addnode=76.10.147.84 addnode=150.101.174.85 addnode=212.124.68.161 addnode=82.20.48.48 addnode=199.201.106.33 addnode=78.145.71.105 addnode=209.172.25.95
|
|
|
|
ryen123
|
|
November 04, 2013, 05:38:28 PM |
|
So this should work? then run the wallet or the goldcoind?
rpcuser=username rpcpassword=pwd rpcallowip=127.0.0.1 daemon=1 server=1 gen=0 maxconnections=64 dns=1 checkpoints=1 listen=1 rpcport=8122 dnsseed=1 banscore=50 bantime=14400 addnode=50.116.22.43 addnode=88.161.131.83 addnode=24.70.184.213 addnode=208.115.109.157 addnode=72.200.175.240 addnode=192.241.134.49 addnode=76.10.147.84 addnode=150.101.174.85 addnode=212.124.68.161 addnode=82.20.48.48 addnode=199.201.106.33 addnode=78.145.71.105 addnode=209.172.25.95
Run the wallet. After it has sync, then run cgminer.
|
|
|
|
hhs99
Member
Offline
Activity: 103
Merit: 10
|
|
November 04, 2013, 05:42:07 PM |
|
Thanks, I'm sure it was a total Noob question
|
|
|
|
darkzorger
Sr. Member
Offline
Activity: 302
Merit: 251
Ego Sum Qui Sum
|
|
November 04, 2013, 05:46:25 PM |
|
@ hhs99 rpcuser=username-is-you-wallet-address
|
| | | | [ | | | | ] | | ✓ POW/POS ✓ ANONIMITY ✓ TRANSACTIONS ✓ SECURITY | | |
|
|
|
ryen123
|
|
November 04, 2013, 05:49:51 PM |
|
@ hhs99 rpcuser=username-is-you-wallet-address
darkzorger, as far as i know rpcuser can be anything cause its just to allow cgminer to access the wallet. Its only 'the wallet address' when doing p2p mining.
|
|
|
|
ryen123
|
|
November 04, 2013, 05:51:10 PM |
|
Thanks, I'm sure it was a total Noob question
No prob. I was a noob before as well. Just fyi, there are currently issues with the goldcoin network which is being looked at by the developer. I only had 2 confirmed blocks and tons of rejects. Its "normal" at the moment to get many rejects. Furstrating but you might get lucky.
|
|
|
|
nicksmith
|
|
November 04, 2013, 06:40:16 PM |
|
[UPDATE] Mandatory Update 0.7.1.4 (Difficulty fixes)Download Links: http://gldcoin.com/get-started/Notes: The difficulty algorithm has been fixed. This is a mandatory update, so be sure to do it before the hard fork at 103000 occurs. The hashrate should correct itself over the next day or so. Sorry for the rather frequent updates of late, we are trying to get the situation resolved as quickly as possible. Gave this a try and my first block find was rejected. I don't think your patch worked.
|
|
|
|
|