Author

Topic: [ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained] - page 444. (Read 1369778 times)

hero member
Activity: 868
Merit: 1000
So stormia,

are you saying that this statement:
Quote
Mint attack 51% of POW part was successful no POS block was generated during test attack.

is demonstrably untrue?  Cheesy

Yes, but I urge people to have a look themselves. Even more importantly it doesn't seem to matter that they were in control of PoW because PoW was not allowed to do any transaction confirmations. The PoS blocks had to interrupt in order to confirm a transaction.
newbie
Activity: 42
Merit: 0
I've just noticed something while going over the block chain.

First of all, the attack was really just from 203231 to 203405 before it started to be interrupted by even more PoS blocks:
http://mintcoin-explorer.info/chain/MintCoin?hi=203233&count=50
http://mintcoin-explorer.info/chain/MintCoin?hi=203433&count=50


Secondly, even within this period, there are still some PoS blocks that occur:
https://i.imgur.com/LydCerH.png

Most importantly of all. Through the ENTIRE attack period, not a single transaction was confirmed by one of the PoW blocks (aside from the PoW blocks producing their 1 MINT). The only transaction confirmations were done by the few PoS blocks which interrupted. How is this possible? There are way, way more PoW blocks, but none of them confirmed transactions over an entire hour? Is that because PoW blocks cannot confirm transaction during this "attack"? If so, then this "attack" cannot be used to double spend or do any real damage. Right?

Yes. exactly
sr. member
Activity: 364
Merit: 250
So stormia,

are you saying that this statement:
Quote
Mint attack 51% of POW part was successful no POS block was generated during test attack.

is demonstrably untrue?  Cheesy
hero member
Activity: 868
Merit: 1000
I've just noticed something while going over the block chain.

First of all, the attack was really just from 203231 to 203405 before it started to be interrupted by even more PoS blocks:
http://mintcoin-explorer.info/chain/MintCoin?hi=203233&count=50
http://mintcoin-explorer.info/chain/MintCoin?hi=203433&count=50


Secondly, even within this period, there are still some PoS blocks that occur:
https://i.imgur.com/LydCerH.png

Most importantly of all. Through the ENTIRE attack period, not a single transaction was confirmed by one of the PoW blocks (aside from the PoW blocks producing their 1 MINT). The only transaction confirmations were done by the few PoS blocks which interrupted. How is this possible? There are way, way more PoW blocks, but none of them confirmed transactions over an entire hour? Is that because PoW blocks cannot confirm transaction during this "attack"? If so, then this "attack" cannot be used to double spend or do any real damage. Right?
legendary
Activity: 1344
Merit: 1001
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector

Actually, the only reason PoS kicked back in is because we stopped the attack. One could easily stop the PoS chain for 24 hours+ if he'd wanted to. Hell, even a year is possible.

Also, this is a 2 part attack:

1) Make the coin PoW only
2) 51% attack.

The second part we did not perform, but we could've done a double spend then.

Anyhow, good that the dev finally reacted, hope to see a fix soon!

they said they would release a fix if one becomes necessary because theoretical possibilities are not much to worry about



You would rather it's not theoretical and he actually 51% attacks your mint blockchain??  Cheesy

You should be careful what you wish for. He reduced the network to relying on almost zero difficulty proof of work mining, a 51% attack at that point is trivial.
sr. member
Activity: 364
Merit: 250
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector

Actually, the only reason PoS kicked back in is because we stopped the attack. One could easily stop the PoS chain for 24 hours+ if he'd wanted to. Hell, even a year is possible.

Also, this is a 2 part attack:

1) Make the coin PoW only
2) 51% attack.

The second part we did not perform, but we could've done a double spend then.

Anyhow, good that the dev finally reacted, hope to see a fix soon!

they said they would release a fix if one becomes necessary because theoretical possibilities are not much to worry about


The dev should try to reproduce this and see if it is a problem. For all we know rat4 and his team could have tried this over and over and when they finally manage to get 100 blocks in a row they posted that result as if it is an easy task...

they know what they are doing, these guys are just trying to scare you
full member
Activity: 210
Merit: 100
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector

Actually, the only reason PoS kicked back in is because we stopped the attack. One could easily stop the PoS chain for 24 hours+ if he'd wanted to. Hell, even a year is possible.

Also, this is a 2 part attack:

1) Make the coin PoW only
2) 51% attack.

The second part we did not perform, but we could've done a double spend then.

Anyhow, good that the dev finally reacted, hope to see a fix soon!

they said they would release a fix if one becomes necessary because theoretical possibilities are not much to worry about


The dev should try to reproduce this and see if it is a problem. For all we know rat4 and his team could have tried this over and over and when they finally manage to get 100 blocks in a row they posted that result as if it is an easy task...
legendary
Activity: 1302
Merit: 1002
What is the nature of the attack and what are the risks to people currently holding Mint?

Was a 51 attack over POW part, cant go further since POS kick back in

If you are paranoid use more than 120 confirmations, this will exclude this attack since POS will always kick back in less than an hour

No double spend can be made with this attack.
https://en.bitcoin.it/wiki/Proof_of_Stake
then
https://en.bitcoin.it/wiki/Double-spending
and finaly:

>50% attack

If the attacker controls more than half of the network hashrate, the previous attack has a probability of 100% to succeed. Since the attacker can generate blocks faster than the rest of the network, he can simply persevere with his private fork until it becomes longer than the branch built by the honest network, from whatever disadvantage.

No amount of confirmations can prevent this attack; however, waiting for confirmations does increase the aggregate resource cost of performing the attack, which could make it unprofitable or delay it long enough for the circumstances to change or slower-acting synchronization methods to kick in.
_______________________________________________________________________________ ____________
Mint attack 51% of POW part was successful no POS block was generated during test attack.
Just becouse test attack wasn't created to enebled double spend that doesn't meant it is impossible.
Do you realy want attack to create panic ?

"Successfully tested on Mintcoin: no PoS blocks from 203231 up to 203441, more than 1 hour of real time."
just check blocks in explorer to see it was for real...
Mint just need fast fix that is all
member
Activity: 65
Merit: 10
Thanks for the panic!

Just bought some very cheap Mint! Wink

like people who do not know how to wait and give time for a currency will have remorse later
full member
Activity: 210
Merit: 100
What is the nature of the attack and what are the risks to people currently holding Mint?

Was a 51 attack over POW part, cant go further since POS kick back in

If you are paranoid use more than 120 confirmations, this will exclude this attack since POS will always kick back in less than an hour

No double spend can be made with this attack.
How to configure how many confirmations to use?
sr. member
Activity: 364
Merit: 250
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector

Actually, the only reason PoS kicked back in is because we stopped the attack. One could easily stop the PoS chain for 24 hours+ if he'd wanted to. Hell, even a year is possible.

Also, this is a 2 part attack:

1) Make the coin PoW only
2) 51% attack.

The second part we did not perform, but we could've done a double spend then.

Anyhow, good that the dev finally reacted, hope to see a fix soon!

they said they would release a fix if one becomes necessary because theoretical possibilities are not much to worry about

full member
Activity: 132
Merit: 100
Thanks for the panic!

Just bought some very cheap Mint! Wink
sr. member
Activity: 476
Merit: 250
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector

Actually, the only reason PoS kicked back in is because we stopped the attack. One could easily stop the PoS chain for 24 hours+ if he'd wanted to. Hell, even a year is possible.

Also, this is a 2 part attack:

1) Make the coin PoW only
2) 51% attack.

The second part we did not perform, but we could've done a double spend then.

Anyhow, good that the dev finally reacted, hope to see a fix soon!
hero member
Activity: 868
Merit: 1000

I recommend you go with black coin

Why is blackcoin's price falling, too? I see big dumps. I would have thought bad news for Mint == good news for BC.
legendary
Activity: 1344
Merit: 1001
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector

1 hour worth of blocks in the block chain were reduced to proof of work only. And the proof of work difficulty is ridiculously low due to the 1 block reward being no incentive to proof of work miners.

A double spend attack in that 1 hour block would be a piece of cake. You're lucky the blackcoin developer isn't malicious or your MINT would have lost 500% of it's value right now... but that could still happen anyway the way the market is reacting to this news
sr. member
Activity: 364
Merit: 250

I recommend you go with black coin
newbie
Activity: 14
Merit: 0
We have been made aware of potential security issues for MintCoin recently. As we always do, we're actively looking into these issues if any. If there is anything to fix, we'll do it, and we'll do it the best way possible.

I'd like to take this opportunity to point out to all the people who FREAKED OUT and said the devs are douchebags and losers, that the dev team replied within an hour of all this bellyaching and name calling.

People get pissed off when I call individuals out by name for being turds, but you know who you are. Others and newcomers reading this part of the thread should take note of the people who obviously have ulterior motives. Don't be fooled by people trying to scare you. Use your brain and think for yourself. Bottom line, the dev team is on it, Mintcoin is all systems go.


Uh what. Blackcoin team emailed Mintcoin dev over 20 hours ago about this privately and Mintcoin dev wouldn't regonise the problem.

Even now when it's gone public the mintcoin dev still states he'll fix it if it's a problem. Good luck putting your faith in a dev who can't read the blockchain and recognise what has happened  Cheesy

i dumped my mint already. I may buy back in if the dev pulls his finger out of his ass or I may convert the rest into blackcoin. They do seem to have one of the best devs around who actually understands the code. Proven by their mint vulnerability discovery
sr. member
Activity: 364
Merit: 250
Stop with the FUD it's already been shown that the attack was foiled by the proper functioning of the coin and no doublespend is achievable by that vector
full member
Activity: 126
Merit: 100
We have been made aware of potential security issues for MintCoin recently. As we always do, we're actively looking into these issues if any. If there is anything to fix, we'll do it, and we'll do it the best way possible.

I'd like to take this opportunity to point out to all the people who FREAKED OUT and said the devs are douchebags and losers, that the dev team replied within an hour of all this bellyaching and name calling.

People get pissed off when I call individuals out by name for being turds, but you know who you are. Others and newcomers reading this part of the thread should take note of the people who obviously have ulterior motives. Don't be fooled by people trying to scare you. Use your brain and think for yourself. Bottom line, the dev team is on it, Mintcoin is all systems go.


Uh what. Blackcoin team emailed Mintcoin dev over 20 hours ago about this privately and Mintcoin dev wouldn't regonise the problem.

Even now when it's gone public the mintcoin dev still states he'll fix it if it's a problem. Good luck putting your faith in a dev who can't read the blockchain and recognise what has happened  Cheesy
Whoa! You're kidding me!

legendary
Activity: 1344
Merit: 1001
We have been made aware of potential security issues for MintCoin recently. As we always do, we're actively looking into these issues if any. If there is anything to fix, we'll do it, and we'll do it the best way possible.

I'd like to take this opportunity to point out to all the people who FREAKED OUT and said the devs are douchebags and losers, that the dev team replied within an hour of all this bellyaching and name calling.

People get pissed off when I call individuals out by name for being turds, but you know who you are. Others and newcomers reading this part of the thread should take note of the people who obviously have ulterior motives. Don't be fooled by people trying to scare you. Use your brain and think for yourself. Bottom line, the dev team is on it, Mintcoin is all systems go.


Uh what. Blackcoin team emailed Mintcoin dev over 20 hours ago about this privately and Mintcoin dev wouldn't regonise the problem.

Even now when it's gone public the mintcoin dev still states he'll fix it if it's a problem. Good luck putting your faith in a dev who can't read the blockchain and recognise what has happened  Cheesy
Jump to: