|
nearmiss
|
 |
October 02, 2013, 01:30:47 PM |
|
Cryptsy needs to fix their shit. The 'right' chain has already been mentioned a bunch of times, with both block explorers and a bunch of pools all on it.
|
Profit-Switching Pool w/ Vardiff -> http://hashco.ws Optionally keep the alts we mine or auto-trade for BTC. In addition can be paid out in any of: 365, AC, BC, BTC, C2, CINNI, COMM, FAC, HBN, MINT, PMC, QRK, RDD, WC, XBC |
|
|
|
|
|
|
|
The forum strives to allow free discussion of any ideas. All policies are built around this principle. This doesn't mean you can post garbage, though: posts should actually contain ideas, and these ideas should be argued reasonably.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
ortchi
|
|
October 02, 2013, 02:15:48 PM |
|
http://coin-base.net/infinitecoin/The old pool will be disabled. The existing coins can you Transfer. The unconfirmed block I will manually calculate and Transfer. I will write to the individual user. If you have not entered your correct email and you have not Adress, please report back to me! The damage caused by the error I will pay out of my pocket, so no one should have something Be Lost. http://coin-base.net/infinite/I've been in the new pool, all your settings and imported all users. mmcfe-ng updated The next 6 days, 0% POOL FEE I have changed the port numbers: PUSH POOL PORT: 8444 STRATUM PORT: 3444 The first block was found!
|
|
|
|
|
Petr1fied
|
|
October 02, 2013, 02:21:49 PM |
|
Cryptsy needs to fix their shit. The 'right' chain has already been mentioned a bunch of times, with both block explorers and a bunch of pools all on it.
Do you honestly expect cryptsy to monitor 70+ coin threads on this forum 24/7 on the off chance one of the coin devs releases a hard fork? If a coin dev releases a hard fork then they should take it upon themselves to at the very least advise the exchanges and pools that they should update as a matter of urgency. |
|
|
|
|
|
captainfuture
|
|
October 02, 2013, 02:34:48 PM |
|
why isnt there an autopudate in the clients  |
|
|
|
|
|
nearmiss
|
|
October 02, 2013, 02:41:51 PM |
|
Cryptsy needs to fix their shit. The 'right' chain has already been mentioned a bunch of times, with both block explorers and a bunch of pools all on it.
Do you honestly expect cryptsy to monitor 70+ coin threads on this forum 24/7 on the off chance one of the coin devs releases a hard fork? If a coin dev releases a hard fork then they should take it upon themselves to at the very least advise the exchanges and pools that they should update as a matter of urgency. While I agree coin devs should be pro-active in this for the sake of their coin...if you are running a damn exchange, yes, you should 100000% be monitoring places for client updates, and watch every single launch thread for coins you deal with, it comes with the territory. Just like a pool operator should be staying on top of coin clients they run,and its way more important for an exchange to do. If they can't stay on top of it then maybe they need to think about not adding so many damn coins, or adding more staff. They are dealing with peoples money here. |
Profit-Switching Pool w/ Vardiff -> http://hashco.ws Optionally keep the alts we mine or auto-trade for BTC. In addition can be paid out in any of: 365, AC, BC, BTC, C2, CINNI, COMM, FAC, HBN, MINT, PMC, QRK, RDD, WC, XBC |
|
|
|
c1010010
|
|
October 02, 2013, 03:23:27 PM |
|
http://coin-base.net/infinitecoin/The old pool will be disabled. The existing coins can you Transfer. The unconfirmed block I will manually calculate and Transfer. I will write to the individual user. If you have not entered your correct email and you have not Adress, please report back to me! The damage caused by the error I will pay out of my pocket, so no one should have something Be Lost. http://coin-base.net/infinite/I've been in the new pool, all your settings and imported all users. mmcfe-ng updated The next 6 days, 0% POOL FEE I have changed the port numbers: PUSH POOL PORT: 8444 STRATUM PORT: 3444 The first block was found! Allright, man... all in. Lets hope this sticks. My eMail is correct, so it should be all set. Thanks for making this right. |
|
|
|
|
c1010010
|
|
October 02, 2013, 03:26:03 PM |
|
fisheater - Can you reach out to cryptsy and let them know they are on the wrong chain? As it is right now, I've got a few transfers in to them that will never appear it seems. What happens to those transactions? Since transfers are irreversible, I have no way of pulling it back. What does one do in this situation? Fact is there is no way for the sender to know what the receiver is sync'd to... so it seems like a major problem for a lot of people. Fact is, anybody transferring ANYTHING into IFC:Cryptsy is flushing IFCs down the toilet. |
|
|
|
|
saamxx
|
|
October 02, 2013, 03:36:36 PM
Last edit: October 02, 2013, 03:56:43 PM by saamxx |
|
Cryptsy just confirm what we are crying the whole day and yesterday 'Mullick: @nearmiss: Well the blockchain we are on is stuck. I fond out this morning there was a hard fork 48 hours after release that happened yesterday it seems' 'Mullick: @nearmiss: vern will update tonight and get it back on track' All coin will appear, don't worry  What happens to those transactions? Since transfers are irreversible, I have no way of pulling it back. All transactions are in right chain, so as cryptsy is on forked chain, they can't see them and fund you balance. The problem exist for those who withdrawing ifc from cryptcy today. Seems they have to lose them. Perhaps, this time cryptsy reimburse losses via its own coins,but if it persists, Cryptsy will kick IFC ass and throw it from the exchange at all |
|
|
|
|
|
fisheater (OP)
|
|
October 02, 2013, 04:01:01 PM |
|
Hope the problem in cryptsy is corrected. Both block explorers here are correct.
We are almost at block 270000. Please upgrade to version 1.8 if you haven't done so.
|
|
|
|
|
|
NaNaec
|
|
October 02, 2013, 04:10:50 PM |
|
It seems that this situation is beneficial to someone, but not for us - simple traders\miners ... bigvern, fisheater, may you be able to sit down at the negotiating table and resolve problems? We are people too, and we want our little plan of action rather than seek out rumors on the forum and etc. Be honest with people and tell how long it will continue this shit with infinitecoins. thank you.
PS: Last transaction from netcoin.pl not coming to crypsy again...
|
|
|
|
|
|
fisheater (OP)
|
|
October 02, 2013, 04:15:22 PM |
|
It seems that this situation is beneficial to someone, but not for us - simple traders\miners ... bigvern, fisheater, may you be able to sit down at the negotiating table and resolve problems? We are people too, and we want our little plan of action rather than seek out rumors on the forum and etc. Be honest with people and tell how long it will continue this shit with infinitecoins. thank you.
PS: Last transaction from netcoin.pl not coming to crypsy again...
NaNaec, dev can't monitor all the exchanges' blockchain, all I can do is to make sure the block explorers are on the right chain. I will help if there are any technical issues of the coin. |
|
|
|
|
|
NaNaec
|
|
October 02, 2013, 04:21:26 PM |
|
OK, one says that he can not control all of the chain, the second says it's not his fault that there is a lot of forks, it seems that traders\miners are to blame and they will pay for everything...
|
|
|
|
|
|
saamxx
|
|
October 02, 2013, 04:29:49 PM |
|
OK, one says that he can not control all of the chain, the second says it's not his fault that there is a lot of forks, it seems that traders\miners are to blame and they will pay for everything...
You are very perspicacious ))))) |
|
|
|
|
|
nearmiss
|
|
October 02, 2013, 04:30:49 PM |
|
nothing (should) be lost here.....Cryptsy just needs to update their client. If you sent the coins via the proper fork (which is most likely the case if they aren't showing up in Cryptsy), then they should all show up once Cryptsy updates. This is, imo, a Cryptsy problem. Yes, the IFC dev could have been pro-active and talked to Vern about the update, but at the end of the day, an exchange as large as Cryptsy needs to be responsible for the coin daemons they run, and keep them up to date, as does any other exchange.
People are right about one thing, its the miners who get screwed, as we sit and wait for 36hrs and counting.
|
Profit-Switching Pool w/ Vardiff -> http://hashco.ws Optionally keep the alts we mine or auto-trade for BTC. In addition can be paid out in any of: 365, AC, BC, BTC, C2, CINNI, COMM, FAC, HBN, MINT, PMC, QRK, RDD, WC, XBC |
|
|
|
fisheater (OP)
|
|
October 02, 2013, 04:36:30 PM |
|
nothing (should) be lost here.....Cryptsy just needs to update their client. If you sent the coins via the proper fork (which is most likely the case if they aren't showing up in Cryptsy), then they should all show up once Cryptsy updates. This is, imo, a Cryptsy problem. Yes, the IFC dev could have been pro-active and talked to Vern about the update, but at the end of the day, an exchange as large as Cryptsy needs to be responsible for the coin daemons they run, and keep them up to date, as does any other exchange.
People are right about one thing, its the miners who get screwed, as we sit and wait for 36hrs and counting.
After 1.8 released, I notified all the exchanges and pool owners for upgrades. But this is not because of the new version. New algorithm will kick in only after block 272000, in less than a day time. We are still in the old algorithm of 1.7. Nothing should be different than the current 1.7 code. |
|
|
|
|
|
fisheater (OP)
|
|
October 02, 2013, 11:35:33 PM |
|
We are at block 270719, last call to upgrade to new version ( 1.8 ), otherwise you may be on a forked blockchain and your mined coins can be lost... Please upgrade to V1.8 as soon as possible!
|
|
|
|
|
|
fisheater (OP)
|
|
October 07, 2013, 05:51:01 AM |
|
I am happy to report that with Version 1.8 the diff retarget issue is finally fixed. I observed some attempts to drag the diff down by pushing hard the diff then suddenly remove the hash power and let the diff drop, unfortunately for them now, the attacker can never get the diff very low  The diff retargets work perfectly now, happy mining! Infinitecoin, infinite possibilities, and infinite opportunities! |
|
|
|
|
yogg
Legendary
 Offline
Activity: 2464
Merit: 3158
|
|
October 07, 2013, 10:09:15 AM |
|
I am happy to report that with Version 1.8 the diff retarget issue is finally fixed. I observed some attempts to drag the diff down by pushing hard the diff then suddenly remove the hash power and let the diff drop, unfortunately for them now, the attacker can never get the diff very low The diff retargets work perfectly now, happy mining! Infinitecoin, infinite possibilities, and infinite opportunities!Very happy to read that ! :-) You did great work, fisheater. Thanks. |
|
|
|
|
|
|
|
|
|
