� [MYST] Mystery Coin � Random Rewards � 24 Seconds � Mystery FOUND - ROLLBACK �

[Ezycash]

This is a FUN coin to mine. The random coin rewards make mining this coin like playing the casino.

However if u mine constantly you will average out the coins.

NOW the only thing to see is where this coin can GO.

Hope DEV have some good plans for it as I think this is a good coin.

Too bad not much hype on it but the random features really makes this coin unique.

I guess we would not know how many total coins are available. This is a mystery maybe

Any hint on this DEV and can give us a glimpse of any future plans?

And I more thing the last line of block structure say something like BLOCK 600,000+ 10 coins(FIAT). What is the FIAT for? $$$$

[X7]

BTCBTCBTCBTCBTC btc]BTCBTCBTCBTC

SEAT BELTS ON - STRAPPED IN! #alwaysgofullmoon

[earlz]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

[MineP.it]

https://twitter.com/rjshoemaker/status/494511675056201729

Let's tweet this to Bittrex

[MineP.it]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

So, same shit as USB?

[Voltarius]

https://twitter.com/rjshoemaker/status/494511675056201729

Let's tweet this to Bittrex

Just retweeted

[MineP.it]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

What file and line is that?

[MysteryCoin.org]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

It would just get rejected by all your peers and end up invalid, not showing up on the blockchain. You have, however, found a clue  

You really think I would leave it in there and just comment it out if that was the real secret?

(By the way...just removing or commenting out the code you linked is not how you would actually let invalid values in)

[Ezycash]

So this coins is more like a treasure hunt game.

"Due diligence". In my line of work when this word comes out it usually means bad news.

HOWEVER like I said before this coins seems good to me and all this mystery should either lead to 2 conclusion a GOOD surprise or a BAD surprise.

With all the bad things that is happening recently I think a GOOD surprise is WHAT WE NEED.

Don't u think so DEV.

 

[earlz]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

It would just get rejected by all your peers and end up invalid, not showing up on the blockchain. You have, however, found a clue  

You really think I would leave it in there and just comment it out if that was the real secret?

(By the way...just removing or commenting out the code you linked is not how you would actually let invalid values in)

Well, comparing it to bitcoin 0.8.6 for the "src" directory (note main.cpp diff is not shown on github), nothing else significant appears. If this isn't the flaw, then it's in the qt wallet and thus not affecting the core network.

Also, I see no other calls to GetBlockValue in the entire repository other than CreateNewBlock. CreateNewBlock only determines the block miners create, not what the network accepts. So, yes. this is the bug whether you know it or not.

For reference, here is the line of code

[MysteryCoin.org]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

It would just get rejected by all your peers and end up invalid, not showing up on the blockchain. You have, however, found a clue  

You really think I would leave it in there and just comment it out if that was the real secret?

(By the way...just removing or commenting out the code you linked is not how you would actually let invalid values in)

Well, comparing it to bitcoin 0.8.6 for the "src" directory (note main.cpp diff is not shown on github), nothing else significant appears. If this isn't the flaw, then it's in the qt wallet and thus not affecting the core network.

Also, I see no other calls to GetBlockValue in the entire repository other than CreateNewBlock. CreateNewBlock only determines the block miners create, not what the network accepts. So, yes. this is the bug whether you know it or not.

For reference, here is the line of code

You can create and submit whatever you want. It won't be accepted. I never said you would be able to find it in the code. I only said the code had clues

Just to be clear...there aren't any vulnerabilities pertaining to manipulation of the mainnet post release

[earlz]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

It would just get rejected by all your peers and end up invalid, not showing up on the blockchain. You have, however, found a clue  

You really think I would leave it in there and just comment it out if that was the real secret?

(By the way...just removing or commenting out the code you linked is not how you would actually let invalid values in)

Well, comparing it to bitcoin 0.8.6 for the "src" directory (note main.cpp diff is not shown on github), nothing else significant appears. If this isn't the flaw, then it's in the qt wallet and thus not affecting the core network.

Also, I see no other calls to GetBlockValue in the entire repository other than CreateNewBlock. CreateNewBlock only determines the block miners create, not what the network accepts. So, yes. this is the bug whether you know it or not.

For reference, here is the line of code

You can create and submit whatever you want. It won't be accepted. I never said you would be able to find it in the code. I only said the code had clues

Just to be clear...there aren't any vulnerabilities pertaining to manipulation of the mainnet post release

uh huh... so point to me where GetBlockValue is checked other than that commented out line of code, and when a new block is mined, if you're competent enough to know

I don't have time to waste compiling the wallet, but you can try this without being a miner. Try changing the first line of GetBlockValue to be `return nFees;`. Compile, and then watch it accept all blocks from the network. This would be because the value is never actually being checked

Code:

[earlz diff]$ grep "GetBlockValue" *
main.cpp:int64 static GetBlockValue(int nHeight, int64 nFees, uint256 prevHash)
main.cpp:   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash))
main.cpp:   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (actual=%"PRI64d" vs limit=%"PRI64d")", vtx[0].GetValueOut(), GetBlockValue(pindex->nHeight, nFees, prevHash)));
main.cpp:       pblock->vtx[0].vout[0].nValue = GetBlockValue(pindexPrev->nHeight+1, nFees, pindexPrev->GetBlockHash());

[MysteryCoin.org]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

It would just get rejected by all your peers and end up invalid, not showing up on the blockchain. You have, however, found a clue  

You really think I would leave it in there and just comment it out if that was the real secret?

(By the way...just removing or commenting out the code you linked is not how you would actually let invalid values in)

Well, comparing it to bitcoin 0.8.6 for the "src" directory (note main.cpp diff is not shown on github), nothing else significant appears. If this isn't the flaw, then it's in the qt wallet and thus not affecting the core network.

Also, I see no other calls to GetBlockValue in the entire repository other than CreateNewBlock. CreateNewBlock only determines the block miners create, not what the network accepts. So, yes. this is the bug whether you know it or not.

For reference, here is the line of code

You can create and submit whatever you want. It won't be accepted. I never said you would be able to find it in the code. I only said the code had clues

Just to be clear...there aren't any vulnerabilities pertaining to manipulation of the mainnet post release

uh huh... so point to me where GetBlockValue is checked other than that commented out line of code, and when a new block is mined, if you're competent enough to know

I don't have time to waste compiling the wallet, but you can try this without being a miner. Try changing the first line of GetBlockValue to be `return nFees;`. Compile, and then watch it accept all blocks from the network. This would be because the value is never actually being checked

Code:

[earlz diff]$ grep "GetBlockValue" *
main.cpp:int64 static GetBlockValue(int nHeight, int64 nFees, uint256 prevHash)
main.cpp:   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash))
main.cpp:   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (actual=%"PRI64d" vs limit=%"PRI64d")", vtx[0].GetValueOut(), GetBlockValue(pindex->nHeight, nFees, prevHash)));
main.cpp:       pblock->vtx[0].vout[0].nValue = GetBlockValue(pindexPrev->nHeight+1, nFees, pindexPrev->GetBlockHash());

You will just get stuck on Syncing...Downloaded 0 of x Blocks (x being the current height). Your client wouldn't accept any blocks over that value

You could put GetBlockValue to 1000000 and it would download the chain, but newly submitted blocks with that value would not be accepted by peers, thus kicking it from the blockchain. You can get disagreeing info out, but not put it in

[iGotSpots]

If I am understanding this correctly then I think the point has to do more with what a dev can do than an attack

[earlz]

Here is the mystery:

Code:

-    if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees))
-        return state.DoS(100, error("ConnectBlock() : coinbase pays too much (a
+   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash)
+   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (

Miners, try modifying the reward code to payout something else. It'll be accepted into the network

It would just get rejected by all your peers and end up invalid, not showing up on the blockchain. You have, however, found a clue  

You really think I would leave it in there and just comment it out if that was the real secret?

(By the way...just removing or commenting out the code you linked is not how you would actually let invalid values in)

Well, comparing it to bitcoin 0.8.6 for the "src" directory (note main.cpp diff is not shown on github), nothing else significant appears. If this isn't the flaw, then it's in the qt wallet and thus not affecting the core network.

Also, I see no other calls to GetBlockValue in the entire repository other than CreateNewBlock. CreateNewBlock only determines the block miners create, not what the network accepts. So, yes. this is the bug whether you know it or not.

For reference, here is the line of code

You can create and submit whatever you want. It won't be accepted. I never said you would be able to find it in the code. I only said the code had clues

Just to be clear...there aren't any vulnerabilities pertaining to manipulation of the mainnet post release

uh huh... so point to me where GetBlockValue is checked other than that commented out line of code, and when a new block is mined, if you're competent enough to know

I don't have time to waste compiling the wallet, but you can try this without being a miner. Try changing the first line of GetBlockValue to be `return nFees;`. Compile, and then watch it accept all blocks from the network. This would be because the value is never actually being checked

Code:

[earlz diff]$ grep "GetBlockValue" *
main.cpp:int64 static GetBlockValue(int nHeight, int64 nFees, uint256 prevHash)
main.cpp:   //if (vtx[0].GetValueOut() > GetBlockValue(pindex->nHeight, nFees, prevHash))
main.cpp:   //    return state.DoS(100, error("ConnectBlock() : coinbase pays too much (actual=%"PRI64d" vs limit=%"PRI64d")", vtx[0].GetValueOut(), GetBlockValue(pindex->nHeight, nFees, prevHash)));
main.cpp:       pblock->vtx[0].vout[0].nValue = GetBlockValue(pindexPrev->nHeight+1, nFees, pindexPrev->GetBlockHash());

You will just get stuck on Syncing...Downloaded 0 of x Blocks (x being the current height). Your client wouldn't accept any blocks over that value

You could put GetBlockValue to 1000000 and it would download the chain, but newly submitted blocks with that value would not be accepted by peers, thus kicking it from the blockchain. You can get disagreeing info out, but not put it in

I just did this locally with the daemon, and what do you know, 5045 blocks synced so far. I can't believe you're actually trying to get this piece of shit on an exchange.

This is the equivalent of NJA. Miners can generate however many coins they want

[MysteryCoin.org]

I just did this locally with the daemon, and what do you know, 5045 blocks synced so far. I can't believe you're actually trying to get this piece of shit on an exchange.

This is the equivalent of NJA. Miners can generate however many coins they want

Submit blocks worth millions then. It won't work. I already told you how to sync it up, so no surprise there...

I'm not trying to get it listed anywhere...If it does, cool, but that's not one of my goals. However, I will move on from your hostile tone

[donnyespo]

Well what is your goal? Not to be rude but I did invest some btc to mine this stupid or not I would like to know what of any are the future plans.

Why create a coin to not see it progress

[Ezycash]

Not sure how many miners actually mining this coin but my guess is less than 100.

With all new coins there is a certain amount of RISKS we are taking especially if we invested some BTC in it.

Whether it pays out on your investment we would not know till the future.

However so far I do not sense any SCAM going on from the developer or the coin.

Like a mystery he is just watching what is happening to his coin.

What his master plan ONLY he knows.

So we all just have to wait and see WHAT IS IN STORE for this coin in the future.

And we human always have FEAR of the unknown. That is the mystery.

So just put on your seatbelt and just enjoy the ride to SOMEWHERE.

[MysteryCoin.org]

Well for starters, any other release regarding MYST will have the option to trade your MYST into the newest chain, for equal dollar value to ensure you are always on the newest project

[donnyespo]

ezcash- I get it, and your right only the dev knows. Obviously this is mystery coin wouldn't live up to its name if all was released.

I do feel this is a solid coin, its stable and wallet has no issues.

The dev is around and tries to address concerns, so I guess it really could be worse.

Interested to see where this one takes us, will wait patiently