You still have to wait the same time to have the same confidence that your transaction will not be reversed.
Nope this isnt true, if you look at teh double spend vulnerability study, what matters is how many blocks he falls behind, NOT TIME. Or you are going to have to prove this claim to me, as all the studies show it becomes increasingly harder to double spend for each block you fall behind, NOT FOR EACH MINUTE.
This point needs analysis not argument.
The point of confirmations is not to prevent double spends, it's to prevent transactions getting canceled by replacing the block the transaction was in with a longer one. My point is that it would be far faster to carry out a 51% attack when blocks are generated far faster. The difference in the block propagation time to block generation time ratio in SolidCoin might also have some interesting side effects, none of which will be good.
2. Security - Anyone who runs a decent sized BTC pool could subvert his hashing power to perform double spends on SolidCoin right now as the barrier to a 51% attack is far lower than bitcoin.
um 51% is still 51%. I get it would take less equipment but you also get the double spend attack? It's pretty damn limited, and a rogue pool op, would probably find more luck and less risk, just diverting found blocks into a different wallet, and his users would just think the pool was a but unlucky that day. This is also a weakness with bitcoin, and as such, meaningless. But once again the faster block speeds makes it harder, not easier as his time frame to exploit decreases. It is also mainly a non issue, people wait less confirmations for small transactions, more for larger.
I don't want to pull off a double spend attack. I want to wipe out the SolidCoin to BTC exchanges by depositing SolidCoins to them, cashing out BTC, then revoking the SolidCoin transaction I paid with. I could do this with greater than about 60% of the hash power of the network when the network is at it's lowest hash power. So I could wait until most people bail out after difficulty adjusts upwards and point all my GPUs at SolidCoin. The amount of hash power needed for this attack would be tiny because I can attack the network when it's weakest and the profits would be all BTC held in the SolidCoin to BTC exchanges.
3. We make it easy - You don't even have a client that will run on Debian based Linux.
source is there, so the problem is pebcak. You also dont really need a client, most pools will let you send to an exchange, and you can also create your own keys and just forget having a client. You also claim he made practically no changes to the btc code, and yet claim solidcoin sucks cause it doesnt work on debian.. well can you not get bitcoin to work on debian? sounds like you can, so ONE CLAIM OR THE OTHER HAS TO BE WRONG. I mean you say it is the same client as btc with miner changes and then bitch you cant make it work.
Sure the source is there, but that's not making it easy now is it? Do you really expect every end user of a currency to compile the source involved?
Your second point is invalid as it only takes one very small change to break things. A decent programmer can break a hell of a lot with a single character.
5. A plan for the future - Attacking the bitcoin developers, developers who have released stable clients for all platforms seems low.
when is the last time you saw an update for the client? Hows that encrypted wallet coming?
The BitCoin client still lacks an encrypted wallet. I agree it really needs one as there are programs stealing bitcoin's wallet.dat right now. However the client they have provided appears stable for all major operating systems unlike the SolidCoin client.
Seriously nothing but garbage here. I have a feeling it is someone upset BTC went so far down, or someone who made bad trades for SC. At the very very least, it is someone who did a piss poor job of proving his point.
You failed to understand my points or deliberately ignored them. That's not the same as them being wrong. I've never mined or traded for SolidCoin.