barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 01:13:22 PM |
|
Seems to be separate chains advertised around block 43869, 43977 and 44176. Catcoin block explorer keeps flicking between 43977 and 44176.
|
my father wears sneakers in the pool
|
|
|
iju76
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 02:00:53 PM |
|
|
|
|
|
barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 02:09:08 PM |
|
Glad to see this isnt just me - i get this exact message with the new wallet. Assert suggests to me that (in src/main.cpp: 1222) that the chain has separated somehow; as Assert is the same error you get when incorrectly cloning a wallet (ie. differs away from chain derived from Genesis block).
|
my father wears sneakers in the pool
|
|
|
barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 05:10:05 PM |
|
Catcoin dev:
On current github source, main.cpp line 1118: unsigned int i;
This needs to be changed to: int i;
Prevents both Linux and Windows QT wallets from dying while importing block 2015.
james
|
my father wears sneakers in the pool
|
|
|
SlimePuppy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 05:20:19 PM Last edit: July 05, 2015, 06:20:37 PM by SlimePuppy |
|
Thanks guys. Blak found the problem - stay tuned for a new wallet. In the mean time, please note that you can find block info on the network chart posted here: http://catcoinwallets.com/ and via the only blockchain explorer that is maintained by the community here: http://catcoinwallets.com:2750/chain/Catcoin Cryptsy maintains a separate block explorer and they keep it current as well. Nobody maintains the old page at catstat.info *** and it is at least one code revision behind. Do not rely on that explorer. Andy *** edit... Apparently that domain has been orphaned and has been gathered by our resident terrorist, hozer. He's running his own hacked clients and is consistently and intentionally creating his own mini-forks with the three nodes he controls. The real CAT network is strong and there's no way his code will harm our network. But that's not stopping him from using that to 'claim' there's a problem. Don't fall for his lies.
|
|
|
|
barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 05:31:29 PM |
|
*blinks*
did that just happen? thanks guys.
|
my father wears sneakers in the pool
|
|
|
|
barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 06:21:38 PM |
|
thats bit harsh, we're all instaminers.. id refer you to the blocks at the start of the chain that saw > 1000mh (especially in early 2014!)
|
my father wears sneakers in the pool
|
|
|
SlimePuppy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 06:23:18 PM Last edit: June 27, 2015, 10:23:44 PM by SlimePuppy |
|
I detailed why it's a problem awhile back. ... let me know where to transfer catstat.info ... Troy - Blak's already outlined why your suggestion is off the mark. Feel free to bring exploit code to -dev if you think you have a leg to stand on. Details talk; BS/FUD walks. New Folks: Disregard Troy/hozer/tmagik/technomagik/catcoiner. Trade with extreme caution. Get deliverables in advance.
|
|
|
|
Blaksmith
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 06:39:22 PM |
|
Seems to be separate chains advertised around block 43869, 43977 and 44176. Catcoin block explorer keeps flicking between 43977 and 44176.
Sadly barrysty1e, around block 43xxx, is the last attempt that hozer tried to derail catcoin using HIS rogue "catbox" code, and (most likely leased) a TON of hash rate. I have added checkpoints that should keep it from actually being derailed. This new release should help stop the galloping of the difficulty at low hash rates, and we should finally start smoothing out and get regular blocks. As stated in the past many times, if EVERYONE runs the "official" code, and keeps steady hashing on the coin, then when switch-pools do pop on and off, it won't affect the difficulty swing as hard, and it will absorb the impact. Blak
|
"Your future is whatever you make it, so make it a good one." Dr. Emmett Brown Donations welcome: Bitcoin: 1 BLAKSMTjnME4ZJX7VzzUyEgbQYLShvqgi Catcoin: 9aw3Ttiz5yMALUm2DUj748cCHYQLatwLPz Unobtanium: uh3bjJua71jFijmz1yAB89KM8mqJEbzrek Pool owner of: geekhash.org
|
|
|
hozer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 06:57:16 PM |
|
thats bit harsh, we're all instaminers.. id refer you to the blocks at the start of the chain that saw > 1000mh (especially in early 2014!)
I have no problem with people that admit it, and that this blockchain was started out by instaminers who profited handsomely. But miners can't profit if nobody buys the coin, and nobody is going to buy the coin if they know that instaminers are the only ones profiting. So there's got to be more going on than just a new code release that is different instaminers trying to game the difficulty adjustment. We've got what looks to me like the same old altcoin pump-and-dump cycle going on here. Someone is going to make a profit instamining by exploiting the new difficulty adjustment. I know it's going to happen, and what I would like is for some discussion about how adjusting the difficulty every block requires re-examining some fundamental assumptions that are made in the Satoshi codebase. Like the assumption that timestamps don't matter. I'd argue that any adjustment that happens every block requires paying very close attention to timestamps, and that it probably requires a minimum block time, as well as that the network reject blocks more than say 10 minutes in the future. The problem is that what I get is some FUD from people who stand to make money instamining instead of rational discussion. Maybe I am expecting to much. Would you all prefer I just said nothing, and silently exploited the code like everyone else? Or would you rather I take the time to develop and publish the code? Or maybe we could possibly admit that the stock PID algorithm with a 3 minute minimum instead of a 30 second one might be a reasonable compromise that instaminers, small miners, and people that like cats can all live with?
|
|
|
|
hozer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 07:03:39 PM |
|
Seems to be separate chains advertised around block 43869, 43977 and 44176. Catcoin block explorer keeps flicking between 43977 and 44176.
Sadly barrysty1e, around block 43xxx, is the last attempt that hozer tried to derail catcoin using HIS rogue "catbox" code, and (most likely leased) a TON of hash rate. I have added checkpoints that should keep it from actually being derailed. This new release should help stop the galloping of the difficulty at low hash rates, and we should finally start smoothing out and get regular blocks. As stated in the past many times, if EVERYONE runs the "official" code, and keeps steady hashing on the coin, then when switch-pools do pop on and off, it won't affect the difficulty swing as hard, and it will absorb the impact. Blak The problem is you have no way to enforce that everyone runs the 'official' code, unless you change the copyright and try to DMCA anyone who runs hacked code. As far as I can tell, someone else leased a ton of hash and brought up a new pool that ran my code, and probably made a reasonable profit doing so. What's going to happen is someone's going to write hacked code (or even just a hacked *miner*) that will mess with the timestamps and then be able to effectively control the difficulty adjustment. I advise you to go *experiment* with a miner that always sets 44 second timestamps on testnet and see what happens.
|
|
|
|
SlimePuppy
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 07:05:44 PM Last edit: June 27, 2015, 07:19:31 PM by SlimePuppy |
|
wallet problem Thanks again iju76 and barrysty1e. This is on me. I built the Windows wallet. I tested each of the previous six builds for this code release and they worked perfectly on my personal database and on a fresh machine with no database. I did not, however, fully test the final build before zipping it - I just made sure it ran and connected to the network and got the latest blocks. I've got the new Windows wallet built and am watching it sync with the network. Once this is done, I'll get a copy on my personal machine and test against my existing CAT wallet. If all goes well, I'll push this to catcoinwallets.com and let you know it's ready to download. Thanks - and again - please accept my apology. Andy
|
|
|
|
barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 07:07:31 PM |
|
thats bit harsh, we're all instaminers.. id refer you to the blocks at the start of the chain that saw > 1000mh (especially in early 2014!)
I have no problem with people that admit it, and that this blockchain was started out by instaminers who profited handsomely. But miners can't profit if nobody buys the coin, and nobody is going to buy the coin if they know that instaminers are the only ones profiting. So there's got to be more going on than just a new code release that is different instaminers trying to game the difficulty adjustment. We've got what looks to me like the same old altcoin pump-and-dump cycle going on here. Someone is going to make a profit instamining by exploiting the new difficulty adjustment. I know it's going to happen, and what I would like is for some discussion about how adjusting the difficulty every block requires re-examining some fundamental assumptions that are made in the Satoshi codebase. Like the assumption that timestamps don't matter. I'd argue that any adjustment that happens every block requires paying very close attention to timestamps, and that it probably requires a minimum block time, as well as that the network reject blocks more than say 10 minutes in the future. The problem is that what I get is some FUD from people who stand to make money instamining instead of rational discussion. Maybe I am expecting to much. Would you all prefer I just said nothing, and silently exploited the code like everyone else? Or would you rather I take the time to develop and publish the code? Or maybe we could possibly admit that the stock PID algorithm with a 3 minute minimum instead of a 30 second one might be a reasonable compromise that instaminers, small miners, and people that like cats can all live with? i can appreciate the fact you've put effort in to prevent this, and it is always disappointing when a coin gets whored out - however a lower block time will deter people looking for 'blocks ahead of time' etc.. increase competition per block but will devalue the coin as well i suppose.. ive got a coin i plan to release soon - and it is *this* that puts me off each time..
|
my father wears sneakers in the pool
|
|
|
|
Blaksmith
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 07:54:10 PM |
|
thats bit harsh, we're all instaminers.. id refer you to the blocks at the start of the chain that saw > 1000mh (especially in early 2014!)
I have no problem with people that admit it, and that this blockchain was started out by instaminers who profited handsomely. But miners can't profit if nobody buys the coin, and nobody is going to buy the coin if they know that instaminers are the only ones profiting. So there's got to be more going on than just a new code release that is different instaminers trying to game the difficulty adjustment. We've got what looks to me like the same old altcoin pump-and-dump cycle going on here. Someone is going to make a profit instamining by exploiting the new difficulty adjustment. I know it's going to happen, and what I would like is for some discussion about how adjusting the difficulty every block requires re-examining some fundamental assumptions that are made in the Satoshi codebase. Like the assumption that timestamps don't matter. I'd argue that any adjustment that happens every block requires paying very close attention to timestamps, and that it probably requires a minimum block time, as well as that the network reject blocks more than say 10 minutes in the future. The problem is that what I get is some FUD from people who stand to make money instamining instead of rational discussion. Maybe I am expecting to much. Would you all prefer I just said nothing, and silently exploited the code like everyone else? Or would you rather I take the time to develop and publish the code? Or maybe we could possibly admit that the stock PID algorithm with a 3 minute minimum instead of a 30 second one might be a reasonable compromise that instaminers, small miners, and people that like cats can all live with? Again Troy, you are trying to start beating on the dead horse again. NOBODY of the community accepts your solution of REJECTING LEGIT BLOCKS BECAUSE 3 MINUTES HAS NOT PASSED. We only had the 30 seconds in there to help stop the galloping, which DID NOT HELP! The only one bringing up the FUD, is YOU! Trying to claim that someone else GOT YOUR CODE .. ummm the only way they can get it is if you post it somewhere, AND ADVERTISE IT! Take your FUD spreading elsewhere.
|
"Your future is whatever you make it, so make it a good one." Dr. Emmett Brown Donations welcome: Bitcoin: 1 BLAKSMTjnME4ZJX7VzzUyEgbQYLShvqgi Catcoin: 9aw3Ttiz5yMALUm2DUj748cCHYQLatwLPz Unobtanium: uh3bjJua71jFijmz1yAB89KM8mqJEbzrek Pool owner of: geekhash.org
|
|
|
hozer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 07:56:11 PM |
|
Interesting discussion about bitcoin: http://cointelegraph.com/news/114657/chinese-mining-pools-call-for-consensus-refuse-switch-to-bitcoin-xtBut we will certainly not switch to the altcoin called 'Bitcoin' XT. It could set a very bad precedent if we do that. No matter who you are, you cannot make a new coin and declare it is 'Bitcoin' simply because you do not agree with other core developers.”
s/bitcoin/catcoin/ If you read the change history, there are two active catcoin developers that have made substantial changes to the code. They don't agree with each other right now. It sets a particularly bad precedent to release a hardfork based on block number that doesn't even do the miner-voting that has been demonstrated successfully in Bitcoin-core multiple times.
|
|
|
|
hozer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 07:56:45 PM |
|
Again Troy, you are trying to start beating on the dead horse again. NOBODY of the community accepts your solution of REJECTING LEGIT BLOCKS BECAUSE 3 MINUTES HAS NOT PASSED. We only had the 30 seconds in there to help stop the galloping, which DID NOT HELP! The only one bringing up the FUD, is YOU! Trying to claim that someone else GOT YOUR CODE .. ummm the only way they can get it is if you post it somewhere, AND ADVERTISE IT!
Take your FUD spreading elsewhere.
https://github.com/CatcoinOfficial/CatcoinRelease/compare/master...tmagik:master
|
|
|
|
Blaksmith
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 08:01:02 PM |
|
There you go... ADVERTISING YOUR NON OFFICIAL CODE...
Take your crap elsewhere!
|
"Your future is whatever you make it, so make it a good one." Dr. Emmett Brown Donations welcome: Bitcoin: 1 BLAKSMTjnME4ZJX7VzzUyEgbQYLShvqgi Catcoin: 9aw3Ttiz5yMALUm2DUj748cCHYQLatwLPz Unobtanium: uh3bjJua71jFijmz1yAB89KM8mqJEbzrek Pool owner of: geekhash.org
|
|
|
barrysty1e
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 27, 2015, 08:05:04 PM |
|
seems to be stuck 6 hours behind? i'm up around 44193..
|
my father wears sneakers in the pool
|
|
|
|