Topic: � [MYST] Mystery Coin � Random Rewards � 24 Seconds � Mystery FOUND - ROLLBACK � - page 10. (Read 26861 times)
July 30, 2014, 05:59:09 PM
Can we just get a peek of the middle part of the book Lol
July 30, 2014, 05:49:42 PM
So I guess this Mystery project is for long term.
And I have a feeling if not now maybe in the future something might work out.
We just have to endure the roads ahead.
Anyway I will stick with you DEV and see where it goes.
I have a feeling u have a GOOD plan and I am just betting on U and this MYSTERY to be something BIG and GOOD.
Let's hope we can garner more support for this MYSTERY project.
And I have a feeling if not now maybe in the future something might work out.
We just have to endure the roads ahead.
Anyway I will stick with you DEV and see where it goes.
I have a feeling u have a GOOD plan and I am just betting on U and this MYSTERY to be something BIG and GOOD.
Let's hope we can garner more support for this MYSTERY project.
It's more like a book series. One chapter at a time
July 30, 2014, 05:21:35 PM
So I guess this Mystery project is for long term.
And I have a feeling if not now maybe in the future something might work out.
We just have to endure the roads ahead.
Anyway I will stick with you DEV and see where it goes.
I have a feeling u have a GOOD plan and I am just betting on U and this MYSTERY to be something BIG and GOOD.
Let's hope we can garner more support for this MYSTERY project.
And I have a feeling if not now maybe in the future something might work out.
We just have to endure the roads ahead.
Anyway I will stick with you DEV and see where it goes.
I have a feeling u have a GOOD plan and I am just betting on U and this MYSTERY to be something BIG and GOOD.
Let's hope we can garner more support for this MYSTERY project.
July 30, 2014, 05:11:47 PM
Just retweeted it. 
Tweet guys
July 30, 2014, 05:10:42 PM
Here is the mystery:
Miners, try modifying the reward code to payout something else. It'll be accepted into the network
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)
GetBlockValue(pindex->nHeight, nFees) should need the prevHash to be able to compare this block with the previous one, no?
July 30, 2014, 05:01:12 PM
One more thing DEV when u say dollar value it means that this coin must be in an exchange to have a value tie to it.
So maybe what u trying to say is that it will HIT the exchange.
And actually I like the idea of a coin when we can port over to other coins. Not thru exchange site but maybe by exchanging it, the old coin A for new coin B.
This way we can exchange existing coins and develop NEW coins until we HIT one that works and will be valuable.
Just a thought.
So our mining investment would not be wasted as the value can be ported over to NEW develop coins.
In this way I see longevity and loyalty in this MYSTERY project.
So maybe what u trying to say is that it will HIT the exchange.
And actually I like the idea of a coin when we can port over to other coins. Not thru exchange site but maybe by exchanging it, the old coin A for new coin B.
This way we can exchange existing coins and develop NEW coins until we HIT one that works and will be valuable.
Just a thought.
So our mining investment would not be wasted as the value can be ported over to NEW develop coins.
In this way I see longevity and loyalty in this MYSTERY project.
That's the plan. To offer an optional upgrade for your coins to the new network as we go. Not something you need to worry about this early, though
Ideally, both networks would remain active, so the choice would be yours at launch of the new coin whether you want to exchange them or not. Not sure how well that will work out, so it might be mandatory once the time comes, but that won't be soon and you'll have plenty of time as a warning
July 30, 2014, 04:19:39 PM
So this is like Protoshare/Bitshares concept?
July 30, 2014, 03:37:25 PM
One more thing DEV when u say dollar value it means that this coin must be in an exchange to have a value tie to it.
So maybe what u trying to say is that it will HIT the exchange.
And actually I like the idea of a coin when we can port over to other coins. Not thru exchange site but maybe by exchanging it, the old coin A for new coin B.
This way we can exchange existing coins and develop NEW coins until we HIT one that works and will be valuable.
Just a thought.
So our mining investment would not be wasted as the value can be ported over to NEW develop coins.
In this way I see longevity and loyalty in this MYSTERY project.
So maybe what u trying to say is that it will HIT the exchange.
And actually I like the idea of a coin when we can port over to other coins. Not thru exchange site but maybe by exchanging it, the old coin A for new coin B.
This way we can exchange existing coins and develop NEW coins until we HIT one that works and will be valuable.
Just a thought.
So our mining investment would not be wasted as the value can be ported over to NEW develop coins.
In this way I see longevity and loyalty in this MYSTERY project.
July 30, 2014, 03:29:54 PM
Did we ever figure out what the mystery is? I know , its how to sell it.
July 30, 2014, 03:22:08 PM
So Dev what u saying is that this project can evolve to maybe MYST V2 coin or any other coins that is develop under MYST group.
So let say u come out with new coin called SURPRISE coin, we could exchange our MYST for SURPRISE coin with equal dollar value?
Is this exchange vice versa or only for MYST to other coins.
Hope I get what u trying to say when u say we can exchange our MYST coin.
So let say u come out with new coin called SURPRISE coin, we could exchange our MYST for SURPRISE coin with equal dollar value?
Is this exchange vice versa or only for MYST to other coins.
Hope I get what u trying to say when u say we can exchange our MYST coin.
July 30, 2014, 03:17:34 PM
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
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
July 30, 2014, 03:10:38 PM
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
July 30, 2014, 02:15:01 PM
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.
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.
July 30, 2014, 02:03:34 PM
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
Why create a coin to not see it progress
July 30, 2014, 01:42:52 PM
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
July 30, 2014, 01:39:37 PM
Here is the mystery:
Miners, try modifying the reward code to payout something else. It'll be accepted into the network
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
July 30, 2014, 01:32:04 PM
If I am understanding this correctly then I think the point has to do more with what a dev can do than an attack
July 30, 2014, 01:23:32 PM
Here is the mystery:
Miners, try modifying the reward code to payout something else. It'll be accepted into the network
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
July 30, 2014, 01:00:54 PM
Here is the mystery:
Miners, try modifying the reward code to payout something else. It'll be accepted into the network
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());
July 30, 2014, 12:49:27 PM
Here is the mystery:
Miners, try modifying the reward code to payout something else. It'll be accepted into the network
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
Jump to: