gldcoin (OP)
Newbie
Offline
Activity: 8
Merit: 0
|
|
June 03, 2013, 03:09:32 AM Last edit: July 01, 2013, 02:49:56 AM by gldcoin |
|
.
|
|
|
|
Hazard
Legendary
Offline
Activity: 980
Merit: 1000
|
|
June 03, 2013, 03:20:58 AM |
|
No explanation? Seems legit
|
|
|
|
BitshireHashaway
|
|
June 03, 2013, 03:31:49 AM |
|
No explanation? Seems legit It was to decrease the difficulty update time, which was too high. when people attacked the networks to jump the difficulty, it was taking to long for the difficulty to come down. as a result high difficulty meant a long time for transactions and such.
|
|
|
|
Hazard
Legendary
Offline
Activity: 980
Merit: 1000
|
|
June 03, 2013, 03:41:45 AM |
|
Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.
I'm grabbing my popcorn and waiting for the shitstorm to play out.
|
|
|
|
BitshireHashaway
|
|
June 03, 2013, 03:51:21 AM |
|
Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.
I'm grabbing my popcorn and waiting for the shitstorm to play out.
Depends. We decided in this case not to do that due to the risk of attacks which could slow down the time it takes to reach a fork if we wait for a certain block to be reached. Therefore we decided to give it to the exchanges/cryptsy and then release it at one time in order to decrease the chance of such an attack. There was risk involved in this, however, the coin was dying without a fork due to the high difficulty.
|
|
|
|
smoothie
Legendary
Offline
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
|
|
June 03, 2013, 03:51:45 AM |
|
NO list of changes...good job. No reason...just update now lolz
|
███████████████████████████████████████
,╓p@@███████@╗╖, ,p████████████████████N, d█████████████████████████b d██████████████████████████████æ ,████²█████████████████████████████, ,█████ ╙████████████████████╨ █████y ██████ `████████████████` ██████ ║██████ Ñ███████████` ███████ ███████ ╩██████Ñ ███████ ███████ ▐▄ ²██╩ a▌ ███████ ╢██████ ▐▓█▄ ▄█▓▌ ███████ ██████ ▐▓▓▓▓▌, ▄█▓▓▓▌ ██████─ ▐▓▓▓▓▓▓█,,▄▓▓▓▓▓▓▌ ▐▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▌ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓─ ²▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓╩ ▀▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▀ ²▀▀▓▓▓▓▓▓▓▓▓▓▓▓▀▀` ²²² ███████████████████████████████████████
| . ★☆ WWW.LEALANA.COM My PGP fingerprint is A764D833. History of Monero development Visualization ★☆ . LEALANA BITCOIN GRIM REAPER SILVER COINS. |
|
|
|
kr4x
Member
Offline
Activity: 112
Merit: 10
|
|
June 03, 2013, 03:52:26 AM |
|
Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.
I'm grabbing my popcorn and waiting for the shitstorm to play out.
It was decided as a community to keep this hard for private until released
|
|
|
|
smoothie
Legendary
Offline
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
|
|
June 03, 2013, 03:53:26 AM |
|
No explanation? Seems legit It was to decrease the difficulty update time, which was too high. when people attacked the networks to jump the difficulty, it was taking to long for the difficulty to come down. as a result high difficulty meant a long time for transactions and such. This is the exact same problem FTC had. These new alt coins need to come up with a different POW. Then at least the development of new GPU mining software will take time to implement. Fixing these things by lowering the diff in a hard fork or capping max diff adjustments is a result of poor planning and foresight. Trash IMHO.
|
███████████████████████████████████████
,╓p@@███████@╗╖, ,p████████████████████N, d█████████████████████████b d██████████████████████████████æ ,████²█████████████████████████████, ,█████ ╙████████████████████╨ █████y ██████ `████████████████` ██████ ║██████ Ñ███████████` ███████ ███████ ╩██████Ñ ███████ ███████ ▐▄ ²██╩ a▌ ███████ ╢██████ ▐▓█▄ ▄█▓▌ ███████ ██████ ▐▓▓▓▓▌, ▄█▓▓▓▌ ██████─ ▐▓▓▓▓▓▓█,,▄▓▓▓▓▓▓▌ ▐▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▌ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓─ ²▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓╩ ▀▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▀ ²▀▀▓▓▓▓▓▓▓▓▓▓▓▓▀▀` ²²² ███████████████████████████████████████
| . ★☆ WWW.LEALANA.COM My PGP fingerprint is A764D833. History of Monero development Visualization ★☆ . LEALANA BITCOIN GRIM REAPER SILVER COINS. |
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
June 03, 2013, 03:59:48 AM |
|
Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.
I'm grabbing my popcorn and waiting for the shitstorm to play out.
Anyone interested knew that hard fork is coming for days Fixing these things by lowering the diff in a hard fork or capping max diff adjustments is a result of poor planning and foresight. Agree with this though. People should never start with such big adjustments after TRC, FTC or CNC problems.
|
|
|
|
Hazard
Legendary
Offline
Activity: 980
Merit: 1000
|
|
June 03, 2013, 04:00:31 AM |
|
Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.
I'm grabbing my popcorn and waiting for the shitstorm to play out.
Anyone interested knew that hard fork is coming for days All 6 of you that still care about this coin? As for the "risk of attack", do you really think anyone gives a shit enough to attack this premined garbagecoin? Let's be honest here.
|
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
June 03, 2013, 04:02:16 AM |
|
Hilarious. When you plan out a hard fork, you need to give AMPLE warning and be very precise about when the fork is going to occur. It would appear that has not been done in this case. Developer incompetence at it's finest.
I'm grabbing my popcorn and waiting for the shitstorm to play out.
Anyone interested knew that hard fork is coming for days All 6 of you that still care about this coin? I certainly don't care what you care about, I'll be fine with other stuff
|
|
|
|
Hazard
Legendary
Offline
Activity: 980
Merit: 1000
|
|
June 03, 2013, 04:15:19 AM |
|
I'm sure you guys informed users that a hard fork was coming using the Alert System to ensure a smooth transition. Oh wait, you didn't, because I looked at your source code and it's using the Litecoin master keys. Maybe if coblee is nice, you can get him to broadcast a message for you
|
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
June 03, 2013, 04:23:01 AM |
|
Can someone post current conf file please, haven't saved it
|
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
June 03, 2013, 04:23:39 AM |
|
I'm sure you guys informed users that a hard fork was coming using the Alert System to ensure a smooth transition. Oh wait, you didn't, because I looked at your source code and it's using the Litecoin master keys. Maybe if coblee is nice, you can get him to broadcast a message for you I can alert all 20 or so people easily lol... no need for all that It's 5, not 20
|
|
|
|
BitshireHashaway
|
|
June 03, 2013, 04:33:39 AM |
|
Can someone post current conf file please, haven't saved it rpcuser=1 rpcpassword=1 rpcallowip=127.0.0.1 rpcport=8122 port=8121 daemon=1 server=1 gen=0 addnode=99.132.231.140 addnode=72.11.149.185 addnode=207.12.89.2 addnode=208.115.109.157 addnode=80.229.2.127
|
|
|
|
seleme
Legendary
Offline
Activity: 2772
Merit: 1028
Duelbits.com
|
|
June 03, 2013, 04:34:03 AM |
|
Cheers Eh, what was it's name - gldcoin.conf or goldcoin.conf
|
|
|
|
bobbix
Newbie
Offline
Activity: 42
Merit: 0
|
|
June 03, 2013, 04:45:29 AM |
|
is this about to happen or has it already happened....the fork?
|
|
|
|
BitshireHashaway
|
|
June 03, 2013, 05:01:40 AM |
|
is this about to happen or has it already happened....the fork?
Already happened... download the new client!
|
|
|
|
BitshireHashaway
|
|
June 03, 2013, 05:05:36 AM |
|
is this about to happen or has it already happened....the fork?
Already happened... download the new client! Well already released... the fork is some blocks in the future!
|
|
|
|
|
|