Itis highly recommended to backup your wallet regularly, and especially before every update.
Keep your wallet.dat copy offline. You can rename it like wallet-current-date-wallet-version.dat
Look for your wallet.dat file in C:\Users\YourUserName\Appdata\Roaming\Mooncoin
or in C:\Documents and Settings\YourUserName\Application data\Mooncoin (Windows XP),
if you don't see the dir with wallet.dat on your PC, then switch on 'show hidden files' in your PC settings.
Your wallet.dat file = your coins, if you lose it or overwrite, you'll be not able to get an access to your coins.
The updateto a new version is 2 steps: saving your wallet.dat and running a new version, in some cases you may have to resync a new wallet.
Topic: [MOON] Mooncoin 🌙 move to a new thread - page 2. (Read 317677 times)
so I download 0.17.1 make an update and then everything is fine for the moment?
THX
THX
Reminder:
don't use 0.13.9 wallet!
Looks like everyone agreed that it had a security issue, very serious vulnerability with block validation.
It was not recommended to use 0.17.1 before, that does not mean it's insecure itself. Only devs and experts can review the code and can say if it is secure or not. Currently no dev/expert/coder said that 0.17.1 is insecure.
Why it was not recommended to use 0.17.1 before? Even if the wallet (the code) itself is secure, it could be insecure to use a wallet, if it is on a separate chain, when coins go nowhere, let's say you send coins from a wallet which is on one chain, and exchanges are on another chain, your coins will not come to exchanges in this case.
It is important to have all pools, exchanges, services and users on the same chain. It is important to avoid split of chain/community.
Now we move to one chain, it is necessary to stop using other wallets and update your wallet to 0.17.1.
don't use 0.13.9 wallet!
Looks like everyone agreed that it had a security issue, very serious vulnerability with block validation.
It was not recommended to use 0.17.1 before, that does not mean it's insecure itself. Only devs and experts can review the code and can say if it is secure or not. Currently no dev/expert/coder said that 0.17.1 is insecure.
Why it was not recommended to use 0.17.1 before? Even if the wallet (the code) itself is secure, it could be insecure to use a wallet, if it is on a separate chain, when coins go nowhere, let's say you send coins from a wallet which is on one chain, and exchanges are on another chain, your coins will not come to exchanges in this case.
It is important to have all pools, exchanges, services and users on the same chain. It is important to avoid split of chain/community.
Now we move to one chain, it is necessary to stop using other wallets and update your wallet to 0.17.1.
Cryptoid.info block explorer is on 0.17.1 now.
Hi Mooncoin!
I would like to invite you to showcase your project to our community: http://holdex.io/
We are missing you there
I would like to invite you to showcase your project to our community: http://holdex.io/
We are missing you there
Hello, please fill this form for listing on Pars Exchange :
https://docs.google.com/forms/d/e/1FAIpQLScjem42XIcsZrEMPH-3RB53IAcmZvphSk9qC3XlSvzivvjFsQ/viewform
you can apply for voting for free, if you wanted to get listed faster and on all Pairs (BTC,LTC,ETH,USDT and RIAL Fiat) we had a 50% discount offer for a limited time.
https://docs.google.com/forms/d/e/1FAIpQLScjem42XIcsZrEMPH-3RB53IAcmZvphSk9qC3XlSvzivvjFsQ/viewform
you can apply for voting for free, if you wanted to get listed faster and on all Pairs (BTC,LTC,ETH,USDT and RIAL Fiat) we had a 50% discount offer for a limited time.
After the entire situation was reviewed and discussed with community members, devs and independent experts, the conclusion is that the only way for Mooncoin now is update to 0.17.
When 0.18 update was announced and released, there was no certainty about what 0.17 release will contain and will it be secure or not. There was no information that there would be separate chains after the release of 0.18 and 0.17.
Moreover, MooncoinCore devs now confirmed that they are active and really want to continue Mooncoin development, what is also important they took responsibility for the 0.17 code and published it at https://github.com/mooncoincore/wallet/releases.
It took almost 2 years comparing to about 2 days (barrysty1e), however it gives hope that the release was prepared carefully. No one yet said that 0.17 release was insecure.
Why not use 0.18.1? It is not compatible with 0.17, which was released after 0.18.1
0.18.1 was released when there was lack of information and it was necessary to fix the security issue ASAP.
0.17 and 0.18 have different consensus agreements implemented, 0.17 overtook the 0.13.9 & 0.18.1 chainwork so that 0.13.9 now follows 0.17. It is easier for everyone to update to 0.17 and unify the chains that way.
After that the 0.18 wallet can be developed to be compatible with 0.17 and to be an optional wallet. The community will have to come to the consensus what should be in next versions of Mooncoin, and looks like everyone agrees that there must not be different directions of development, different wallets must remain on one chain, with the same consensus rules, or it would be just chaos.
How to update? First, as usually, you save your wallet.dat file offline.
If you know how it works, you can also export your private keys and keep them in a safe place, offline.
Then you run 0.17 version from https://github.com/mooncoincore/wallet/releases.
Please don't use 0.18.1 wallet any longer! It has to be developed first, to be compatible with 0.17.
Please don't move coins until we are on one chain again, or it can lead to losses.
There are different chains now, and any delay with update to 0.17 would lead to additional losses.
There were no big movements of coins after the block 1'801'000 and Altilly, a primary exchange for Mooncoin keeps the wallet in maintenance with deposits and withdrawals disabled.
To miners of 0.18: please report your losses of MOON related to the update from 0.18 to 0.17, how many MOON you lost and your Mooncoin address for compensation, please report it to agswinner or to me.
When 0.18 update was announced and released, there was no certainty about what 0.17 release will contain and will it be secure or not. There was no information that there would be separate chains after the release of 0.18 and 0.17.
Moreover, MooncoinCore devs now confirmed that they are active and really want to continue Mooncoin development, what is also important they took responsibility for the 0.17 code and published it at https://github.com/mooncoincore/wallet/releases.
It took almost 2 years comparing to about 2 days (barrysty1e), however it gives hope that the release was prepared carefully. No one yet said that 0.17 release was insecure.
Why not use 0.18.1? It is not compatible with 0.17, which was released after 0.18.1
0.18.1 was released when there was lack of information and it was necessary to fix the security issue ASAP.
0.17 and 0.18 have different consensus agreements implemented, 0.17 overtook the 0.13.9 & 0.18.1 chainwork so that 0.13.9 now follows 0.17. It is easier for everyone to update to 0.17 and unify the chains that way.
After that the 0.18 wallet can be developed to be compatible with 0.17 and to be an optional wallet. The community will have to come to the consensus what should be in next versions of Mooncoin, and looks like everyone agrees that there must not be different directions of development, different wallets must remain on one chain, with the same consensus rules, or it would be just chaos.
How to update? First, as usually, you save your wallet.dat file offline.
If you know how it works, you can also export your private keys and keep them in a safe place, offline.
Then you run 0.17 version from https://github.com/mooncoincore/wallet/releases.
Please don't use 0.18.1 wallet any longer! It has to be developed first, to be compatible with 0.17.
Please don't move coins until we are on one chain again, or it can lead to losses.
There are different chains now, and any delay with update to 0.17 would lead to additional losses.
There were no big movements of coins after the block 1'801'000 and Altilly, a primary exchange for Mooncoin keeps the wallet in maintenance with deposits and withdrawals disabled.
To miners of 0.18: please report your losses of MOON related to the update from 0.18 to 0.17, how many MOON you lost and your Mooncoin address for compensation, please report it to agswinner or to me.
Good morning . It's a good news because we need one chain. So, I am satisfied from this announcement.
After the entire situation was reviewed and discussed with community members, devs and independent experts, the conclusion is that the only way for Mooncoin now is update to 0.17.
When 0.18 update was announced and released, there was no certainty about what 0.17 release will contain and will it be secure or not. There was no information that there would be separate chains after the release of 0.18 and 0.17.
Moreover, MooncoinCore devs now confirmed that they are active and really want to continue Mooncoin development, what is also important they took responsibility for the 0.17 code and published it at https://github.com/mooncoincore/wallet/releases.
It took almost 2 years comparing to about 2 days (barrysty1e), however it gives hope that the release was prepared carefully. No one yet said that 0.17 release was insecure.
Why not use 0.18.1? It is not compatible with 0.17, which was released after 0.18.1
0.18.1 was released when there was lack of information and it was necessary to fix the security issue ASAP.
0.17 and 0.18 have different consensus agreements implemented, 0.17 overtook the 0.13.9 & 0.18.1 chainwork so that 0.13.9 now follows 0.17. It is easier for everyone to update to 0.17 and unify the chains that way.
After that the 0.18 wallet can be developed to be compatible with 0.17 and to be an optional wallet. The community will have to come to the consensus what should be in next versions of Mooncoin, and looks like everyone agrees that there must not be different directions of development, different wallets must remain on one chain, with the same consensus rules, or it would be just chaos.
How to update? First, as usually, you save your wallet.dat file offline.
If you know how it works, you can also export your private keys and keep them in a safe place, offline.
Then you run 0.17 version from https://github.com/mooncoincore/wallet/releases.
Please don't use 0.18.1 wallet any longer! It has to be developed first, to be compatible with 0.17.
Please don't move coins until we are on one chain again, or it can lead to losses.
There are different chains now, and any delay with update to 0.17 would lead to additional losses.
There were no big movements of coins after the block 1'801'000 and Altilly, a primary exchange for Mooncoin keeps the wallet in maintenance with deposits and withdrawals disabled.
To miners of 0.18: please report your losses of MOON related to the update from 0.18 to 0.17, how many MOON you lost and your Mooncoin address for compensation, please report it to agswinner or to me.
When 0.18 update was announced and released, there was no certainty about what 0.17 release will contain and will it be secure or not. There was no information that there would be separate chains after the release of 0.18 and 0.17.
Moreover, MooncoinCore devs now confirmed that they are active and really want to continue Mooncoin development, what is also important they took responsibility for the 0.17 code and published it at https://github.com/mooncoincore/wallet/releases.
It took almost 2 years comparing to about 2 days (barrysty1e), however it gives hope that the release was prepared carefully. No one yet said that 0.17 release was insecure.
Why not use 0.18.1? It is not compatible with 0.17, which was released after 0.18.1
0.18.1 was released when there was lack of information and it was necessary to fix the security issue ASAP.
0.17 and 0.18 have different consensus agreements implemented, 0.17 overtook the 0.13.9 & 0.18.1 chainwork so that 0.13.9 now follows 0.17. It is easier for everyone to update to 0.17 and unify the chains that way.
After that the 0.18 wallet can be developed to be compatible with 0.17 and to be an optional wallet. The community will have to come to the consensus what should be in next versions of Mooncoin, and looks like everyone agrees that there must not be different directions of development, different wallets must remain on one chain, with the same consensus rules, or it would be just chaos.
How to update? First, as usually, you save your wallet.dat file offline.
If you know how it works, you can also export your private keys and keep them in a safe place, offline.
Then you run 0.17 version from https://github.com/mooncoincore/wallet/releases.
Please don't use 0.18.1 wallet any longer! It has to be developed first, to be compatible with 0.17.
Please don't move coins until we are on one chain again, or it can lead to losses.
There are different chains now, and any delay with update to 0.17 would lead to additional losses.
There were no big movements of coins after the block 1'801'000 and Altilly, a primary exchange for Mooncoin keeps the wallet in maintenance with deposits and withdrawals disabled.
To miners of 0.18: please report your losses of MOON related to the update from 0.18 to 0.17, how many MOON you lost and your Mooncoin address for compensation, please report it to agswinner or to me.
Hi all,
As promised;
* Mooncoin using classic consensus rules rebased over Bitcoin 0.19.1
* Full validation of block target from block zero to chain tip
* Rewritten equivalency 'forbiddentx' code
* All tests corrected and compiled
https://github.com/barrystyle/mooncoin
Will keep it up to date as time allows,
james
As promised;
* Mooncoin using classic consensus rules rebased over Bitcoin 0.19.1
* Full validation of block target from block zero to chain tip
* Rewritten equivalency 'forbiddentx' code
* All tests corrected and compiled
https://github.com/barrystyle/mooncoin
Will keep it up to date as time allows,
james
just noticed something as well at https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L3557-L3571 and https://github.com/MooncoinCommunity/wallet/blob/0.18/src/chainparams.cpp#L70-L73.
if we do a bit of substitution here (for the non-coders amongst us), this reads as follows:
meaning nbits for every block before 1801000 is not being tested.
just for fun, i've put together a client based on bitcoin 0.19.1, considering quickly rebasing it over what is available for bitcoin 0.20; community is free to decide whether they support it or not.
edit derp - just checked past couple pages..
james
Code:
consensus.nPoWForkOne = 26850;
consensus.nPoWForkTwo = 1100000;
consensus.nPoWForkThree = 1250000;
consensus.nRestoreValidation = 1801000;
Code:
if (nHeight >= consensusParams.nRestoreValidation) {
// Check proof of work
if(nHeight >= consensusParams.nPoWForkOne && nHeight < consensusParams.nPoWForkTwo){
unsigned int nBitsNext = GetNextWorkRequired(pindexPrev, &block, consensusParams);
double n1 = ConvertBitsToDouble(block.nBits);
double n2 = ConvertBitsToDouble(nBitsNext);
if (std::abs(n1-n2) > n1*0.5){
return state.DoS(100, error("%s : incorrect proof of work (DGW pre-fork) - %f %f %f at %d", __func__, abs(n1-n2), n1, n2, nHeight),
REJECT_INVALID, "bad-diffbits");
}
} else if (block.nBits != GetNextWorkRequired(pindexPrev, &block, consensusParams)){
return state.DoS(100, error("%s : incorrect proof of work at %d", __func__, nHeight),
REJECT_INVALID, "bad-diffbits");
}
}
if we do a bit of substitution here (for the non-coders amongst us), this reads as follows:
Code:
if height is equal to or greater than 1801000 then
if height is equal to or greater than 26850 AND height is less than 1100000 then
meaning nbits for every block before 1801000 is not being tested.
just for fun, i've put together a client based on bitcoin 0.19.1, considering quickly rebasing it over what is available for bitcoin 0.20; community is free to decide whether they support it or not.
edit derp - just checked past couple pages..
james
Quote
We brought up a solution which could be adopted by the communtiy that only certain outputs should be blocked, but again thats a community decision to change the "forbidden tx" protection solution.
Only certain inputs are blocked.
Phrased like that - it sounds like youre saying all uxto's are blocked, which would mean the chain cant move.
Having said that, the 65 million/billion (if memory serves?) is not a legitimate claimable amount - it is common knowledge that this amount came from Cryptsy, and was most likely moved by Big Vern himself.
There was a class action suit against Cryptsy where people were able to state what they lost, prove it and receive compensation.
This time has passed, well and truly (was during 2018).
Alright I try to explain it again.
Mooncoin_Foundation gave the 3 Addresses:
- 3 Adresses are blocked via consensus
2QovBjnVke4fgn9UXdz9osheNLxQCk3d8R (the 1st one with 62B)
2DMfpxPiMtpVDVyrxQAAmfBbZnDH4XCMfK (Dec, 2014 thefts)
2JA3Cqf9on8YuxngxdXStCFKanAGnaQU5A (Dec, 2014 thefts)
I relayed these 3 Addresses to Peter.
Peter used the same technique to block these coins as already done in 0.13.9
Who did implement these protection in first place? -> Barry ( 0.13.9 codebase )
How does this protection work?
Barry did implement it that way that it blocks all UTXOs that were sent to these addresses, so all TX'es that had a destination to those 3 addresses are blocked.
So what got changed in 0.18.1?
Same as in 0.13.9 - All Tx'es towards these addresses got blocked, but now on the consensus level instead of the mempool level. These completely ensures that the coins can't be spent. ( On 0.13.9 you could mine your own blocks and include these transactions )
So to sum it up. - This exact protection was in place since the 0.13.9 release as said ( @Michi your 23f1ade1a9 is in the list on 0.13.9 of blocked transactions )
Here are the 2 links again to the Github of 0.13.9 and 0.18.1
Protection in 0.13.9
https://github.com/MooncoinCommunity/wallet/blob/0.13.9.1-segwit/src/main.cpp#L1160
Protection in 0.18.1
https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L573
Now to the "insecure wallet problem"
Mebagger is partly right on that one, 0.18.1 should add the historical validation I completely agree with that. But it couldnt have been done on the initial release, otherwise it would have rejected 0.13.9 instantly which shouldnt be done that way.
0.17 has the historical validation in place which works and was a good job of the 0.17 team, it just should have done ( in my opinion ) after the 0.18.1 set height to set validation in place. But as said, should be added to 0.18.1 whatever that version will be called then, lets call it 0.18.5.
So what would need to be done right now is porting the 0.17 historical validation to 0.18.1 and make 0.18.5.
About the "forbidden tx" protection, thats up to the community how you guys want to handle that. 0.18.1 - As its part of the consensus right now, if you guys decide to lift that protection, pools and exchanges would need to update on the 0.18.5 release, but again thats up to you.
I've talked to Peter and the best would be to modify the "forbidden tx" protection that it only blocks specific UTXOs ( But that would be a new system, not the one that got introduced in 0.13.9 which blocks all UTXOs )
So that issue should have been brought up way earlier, but seems like nobody looked into it until now, as that "issue" persisted for over 2 years ( since 0.13.9 ) release.
Happy to help/assist on the 0.18.5 or to clarify any other questions that come up.
Kind regard,
ChekaZ
Mooncoin_Foundation gave the 3 Addresses:
- 3 Adresses are blocked via consensus
2QovBjnVke4fgn9UXdz9osheNLxQCk3d8R (the 1st one with 62B)
2DMfpxPiMtpVDVyrxQAAmfBbZnDH4XCMfK (Dec, 2014 thefts)
2JA3Cqf9on8YuxngxdXStCFKanAGnaQU5A (Dec, 2014 thefts)
I relayed these 3 Addresses to Peter.
Peter used the same technique to block these coins as already done in 0.13.9
Who did implement these protection in first place? -> Barry ( 0.13.9 codebase )
How does this protection work?
Barry did implement it that way that it blocks all UTXOs that were sent to these addresses, so all TX'es that had a destination to those 3 addresses are blocked.
So what got changed in 0.18.1?
Same as in 0.13.9 - All Tx'es towards these addresses got blocked, but now on the consensus level instead of the mempool level. These completely ensures that the coins can't be spent. ( On 0.13.9 you could mine your own blocks and include these transactions )
So to sum it up. - This exact protection was in place since the 0.13.9 release as said ( @Michi your 23f1ade1a9 is in the list on 0.13.9 of blocked transactions )
Here are the 2 links again to the Github of 0.13.9 and 0.18.1
Protection in 0.13.9
https://github.com/MooncoinCommunity/wallet/blob/0.13.9.1-segwit/src/main.cpp#L1160
Protection in 0.18.1
https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L573
Now to the "insecure wallet problem"
Mebagger is partly right on that one, 0.18.1 should add the historical validation I completely agree with that. But it couldnt have been done on the initial release, otherwise it would have rejected 0.13.9 instantly which shouldnt be done that way.
0.17 has the historical validation in place which works and was a good job of the 0.17 team, it just should have done ( in my opinion ) after the 0.18.1 set height to set validation in place. But as said, should be added to 0.18.1 whatever that version will be called then, lets call it 0.18.5.
So what would need to be done right now is porting the 0.17 historical validation to 0.18.1 and make 0.18.5.
About the "forbidden tx" protection, thats up to the community how you guys want to handle that. 0.18.1 - As its part of the consensus right now, if you guys decide to lift that protection, pools and exchanges would need to update on the 0.18.5 release, but again thats up to you.
I've talked to Peter and the best would be to modify the "forbidden tx" protection that it only blocks specific UTXOs ( But that would be a new system, not the one that got introduced in 0.13.9 which blocks all UTXOs )
So that issue should have been brought up way earlier, but seems like nobody looked into it until now, as that "issue" persisted for over 2 years ( since 0.13.9 ) release.
Happy to help/assist on the 0.18.5 or to clarify any other questions that come up.
Kind regard,
ChekaZ
I implemented the forbiddentx routines way back in Mooncoin 0.10 (https://github.com/mooncoindev/mooncoin/blob/master/src/main.cpp#L939-L1073).
Mooncoin 0.13.9 is not mine, this was done afterwards by Valhalis (https://github.com/mooncoincore/wallet), who based it on my initial port (https://github.com/mooncoindev/mooncoin-0.13).
My forbiddentx routine did its job, but certainly had its flaws; and I have since improved (vastly) my methods for blocking given inputs.
Contained within are the blocked funds inputs from the court case I mentioned, which were passed onto me by Mooncoin Foundation.
james
Thanks for clarifying. 0.18.1 did nothing else than Valhalis did on 0.13.9 then, the same structure of your initial implementation did get carried over. It surely has its flaws as you said, but it wasn't on us to change the original designed protection.
We brought up a solution which could be adopted by the communtiy that only certain outputs should be blocked, but again thats a community decision to change the "forbidden tx" protection solution.
Alright I try to explain it again.
Mooncoin_Foundation gave the 3 Addresses:
- 3 Adresses are blocked via consensus
2QovBjnVke4fgn9UXdz9osheNLxQCk3d8R (the 1st one with 62B)
2DMfpxPiMtpVDVyrxQAAmfBbZnDH4XCMfK (Dec, 2014 thefts)
2JA3Cqf9on8YuxngxdXStCFKanAGnaQU5A (Dec, 2014 thefts)
I relayed these 3 Addresses to Peter.
Peter used the same technique to block these coins as already done in 0.13.9
Who did implement these protection in first place? -> Barry ( 0.13.9 codebase )
How does this protection work?
Barry did implement it that way that it blocks all UTXOs that were sent to these addresses, so all TX'es that had a destination to those 3 addresses are blocked.
So what got changed in 0.18.1?
Same as in 0.13.9 - All Tx'es towards these addresses got blocked, but now on the consensus level instead of the mempool level. These completely ensures that the coins can't be spent. ( On 0.13.9 you could mine your own blocks and include these transactions )
So to sum it up. - This exact protection was in place since the 0.13.9 release as said ( @Michi your 23f1ade1a9 is in the list on 0.13.9 of blocked transactions )
Here are the 2 links again to the Github of 0.13.9 and 0.18.1
Protection in 0.13.9
https://github.com/MooncoinCommunity/wallet/blob/0.13.9.1-segwit/src/main.cpp#L1160
Protection in 0.18.1
https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L573
Now to the "insecure wallet problem"
Mebagger is partly right on that one, 0.18.1 should add the historical validation I completely agree with that. But it couldnt have been done on the initial release, otherwise it would have rejected 0.13.9 instantly which shouldnt be done that way.
0.17 has the historical validation in place which works and was a good job of the 0.17 team, it just should have done ( in my opinion ) after the 0.18.1 set height to set validation in place. But as said, should be added to 0.18.1 whatever that version will be called then, lets call it 0.18.5.
So what would need to be done right now is porting the 0.17 historical validation to 0.18.1 and make 0.18.5.
About the "forbidden tx" protection, thats up to the community how you guys want to handle that. 0.18.1 - As its part of the consensus right now, if you guys decide to lift that protection, pools and exchanges would need to update on the 0.18.5 release, but again thats up to you.
I've talked to Peter and the best would be to modify the "forbidden tx" protection that it only blocks specific UTXOs ( But that would be a new system, not the one that got introduced in 0.13.9 which blocks all UTXOs )
So that issue should have been brought up way earlier, but seems like nobody looked into it until now, as that "issue" persisted for over 2 years ( since 0.13.9 ) release.
Happy to help/assist on the 0.18.5 or to clarify any other questions that come up.
Kind regard,
ChekaZ
Mooncoin_Foundation gave the 3 Addresses:
- 3 Adresses are blocked via consensus
2QovBjnVke4fgn9UXdz9osheNLxQCk3d8R (the 1st one with 62B)
2DMfpxPiMtpVDVyrxQAAmfBbZnDH4XCMfK (Dec, 2014 thefts)
2JA3Cqf9on8YuxngxdXStCFKanAGnaQU5A (Dec, 2014 thefts)
I relayed these 3 Addresses to Peter.
Peter used the same technique to block these coins as already done in 0.13.9
Who did implement these protection in first place? -> Barry ( 0.13.9 codebase )
How does this protection work?
Barry did implement it that way that it blocks all UTXOs that were sent to these addresses, so all TX'es that had a destination to those 3 addresses are blocked.
So what got changed in 0.18.1?
Same as in 0.13.9 - All Tx'es towards these addresses got blocked, but now on the consensus level instead of the mempool level. These completely ensures that the coins can't be spent. ( On 0.13.9 you could mine your own blocks and include these transactions )
So to sum it up. - This exact protection was in place since the 0.13.9 release as said ( @Michi your 23f1ade1a9 is in the list on 0.13.9 of blocked transactions )
Here are the 2 links again to the Github of 0.13.9 and 0.18.1
Protection in 0.13.9
https://github.com/MooncoinCommunity/wallet/blob/0.13.9.1-segwit/src/main.cpp#L1160
Protection in 0.18.1
https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L573
Now to the "insecure wallet problem"
Mebagger is partly right on that one, 0.18.1 should add the historical validation I completely agree with that. But it couldnt have been done on the initial release, otherwise it would have rejected 0.13.9 instantly which shouldnt be done that way.
0.17 has the historical validation in place which works and was a good job of the 0.17 team, it just should have done ( in my opinion ) after the 0.18.1 set height to set validation in place. But as said, should be added to 0.18.1 whatever that version will be called then, lets call it 0.18.5.
So what would need to be done right now is porting the 0.17 historical validation to 0.18.1 and make 0.18.5.
About the "forbidden tx" protection, thats up to the community how you guys want to handle that. 0.18.1 - As its part of the consensus right now, if you guys decide to lift that protection, pools and exchanges would need to update on the 0.18.5 release, but again thats up to you.
I've talked to Peter and the best would be to modify the "forbidden tx" protection that it only blocks specific UTXOs ( But that would be a new system, not the one that got introduced in 0.13.9 which blocks all UTXOs )
So that issue should have been brought up way earlier, but seems like nobody looked into it until now, as that "issue" persisted for over 2 years ( since 0.13.9 ) release.
Happy to help/assist on the 0.18.5 or to clarify any other questions that come up.
Kind regard,
ChekaZ
I implemented the forbiddentx routines way back in Mooncoin 0.10 (https://github.com/mooncoindev/mooncoin/blob/master/src/main.cpp#L939-L1073).
Mooncoin 0.13.9 is not mine, this was done afterwards by Valhalis (https://github.com/mooncoincore/wallet), who based it on my initial port (https://github.com/mooncoindev/mooncoin-0.13).
My forbiddentx routine did its job, but certainly had its flaws; and I have since improved (vastly) my methods for blocking given inputs.
Contained within are the blocked funds inputs from the court case I mentioned, which were passed onto me by Mooncoin Foundation.
james
Has anyone checked up on the court case, where the blocked funds originated from?
Thank you for the information.
My vote is that we have to move to one chain, a new one with consensus rules which are accepted by the entire community, any disagreement with consensus rules means a separate chain.
After that there will be enough pages in this ANN thread for accusations, if there are any which were not already presented.
My vote is that we have to move to one chain, a new one with consensus rules which are accepted by the entire community, any disagreement with consensus rules means a separate chain.
After that there will be enough pages in this ANN thread for accusations, if there are any which were not already presented.
I agree. Finding an independent dev “illique et immediate” will be difficult, I hope in a collaboration of all Mooncoin devs to do it.
Thank you for the information.
My vote is that we have to move to one chain, a new one with consensus rules which are accepted by the entire community, any disagreement with consensus rules means a separate chain.
After that there will be enough pages in this ANN thread for accusations, if there are any which were not already presented.
My vote is that we have to move to one chain, a new one with consensus rules which are accepted by the entire community, any disagreement with consensus rules means a separate chain.
After that there will be enough pages in this ANN thread for accusations, if there are any which were not already presented.
Alright I try to explain it again.
Mooncoin_Foundation gave the 3 Addresses:
- 3 Adresses are blocked via consensus
2QovBjnVke4fgn9UXdz9osheNLxQCk3d8R (the 1st one with 62B)
2DMfpxPiMtpVDVyrxQAAmfBbZnDH4XCMfK (Dec, 2014 thefts)
2JA3Cqf9on8YuxngxdXStCFKanAGnaQU5A (Dec, 2014 thefts)
I relayed these 3 Addresses to Peter.
Peter used the same technique to block these coins as already done in 0.13.9
Who did implement these protection in first place? -> Barry ( 0.13.9 codebase )
How does this protection work?
Barry did implement it that way that it blocks all UTXOs that were sent to these addresses, so all TX'es that had a destination to those 3 addresses are blocked.
So what got changed in 0.18.1?
Same as in 0.13.9 - All Tx'es towards these addresses got blocked, but now on the consensus level instead of the mempool level. These completely ensures that the coins can't be spent. ( On 0.13.9 you could mine your own blocks and include these transactions )
So to sum it up. - This exact protection was in place since the 0.13.9 release as said ( @Michi your 23f1ade1a9 is in the list on 0.13.9 of blocked transactions )
Here are the 2 links again to the Github of 0.13.9 and 0.18.1
Protection in 0.13.9
https://github.com/MooncoinCommunity/wallet/blob/0.13.9.1-segwit/src/main.cpp#L1160
Protection in 0.18.1
https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L573
Now to the "insecure wallet problem"
Mebagger is partly right on that one, 0.18.1 should add the historical validation I completely agree with that. But it couldnt have been done on the initial release, otherwise it would have rejected 0.13.9 instantly which shouldnt be done that way.
0.17 has the historical validation in place which works and was a good job of the 0.17 team, it just should have done ( in my opinion ) after the 0.18.1 set height to set validation in place. But as said, should be added to 0.18.1 whatever that version will be called then, lets call it 0.18.5.
So what would need to be done right now is porting the 0.17 historical validation to 0.18.1 and make 0.18.5.
About the "forbidden tx" protection, thats up to the community how you guys want to handle that. 0.18.1 - As its part of the consensus right now, if you guys decide to lift that protection, pools and exchanges would need to update on the 0.18.5 release, but again thats up to you.
I've talked to Peter and the best would be to modify the "forbidden tx" protection that it only blocks specific UTXOs ( But that would be a new system, not the one that got introduced in 0.13.9 which blocks all UTXOs )
So that issue should have been brought up way earlier, but seems like nobody looked into it until now, as that "issue" persisted for over 2 years ( since 0.13.9 ) release.
Happy to help/assist on the 0.18.5 or to clarify any other questions that come up.
Kind regard,
ChekaZ
Mooncoin_Foundation gave the 3 Addresses:
- 3 Adresses are blocked via consensus
2QovBjnVke4fgn9UXdz9osheNLxQCk3d8R (the 1st one with 62B)
2DMfpxPiMtpVDVyrxQAAmfBbZnDH4XCMfK (Dec, 2014 thefts)
2JA3Cqf9on8YuxngxdXStCFKanAGnaQU5A (Dec, 2014 thefts)
I relayed these 3 Addresses to Peter.
Peter used the same technique to block these coins as already done in 0.13.9
Who did implement these protection in first place? -> Barry ( 0.13.9 codebase )
How does this protection work?
Barry did implement it that way that it blocks all UTXOs that were sent to these addresses, so all TX'es that had a destination to those 3 addresses are blocked.
So what got changed in 0.18.1?
Same as in 0.13.9 - All Tx'es towards these addresses got blocked, but now on the consensus level instead of the mempool level. These completely ensures that the coins can't be spent. ( On 0.13.9 you could mine your own blocks and include these transactions )
So to sum it up. - This exact protection was in place since the 0.13.9 release as said ( @Michi your 23f1ade1a9 is in the list on 0.13.9 of blocked transactions )
Here are the 2 links again to the Github of 0.13.9 and 0.18.1
Protection in 0.13.9
https://github.com/MooncoinCommunity/wallet/blob/0.13.9.1-segwit/src/main.cpp#L1160
Protection in 0.18.1
https://github.com/MooncoinCommunity/wallet/blob/0.18/src/validation.cpp#L573
Now to the "insecure wallet problem"
Mebagger is partly right on that one, 0.18.1 should add the historical validation I completely agree with that. But it couldnt have been done on the initial release, otherwise it would have rejected 0.13.9 instantly which shouldnt be done that way.
0.17 has the historical validation in place which works and was a good job of the 0.17 team, it just should have done ( in my opinion ) after the 0.18.1 set height to set validation in place. But as said, should be added to 0.18.1 whatever that version will be called then, lets call it 0.18.5.
So what would need to be done right now is porting the 0.17 historical validation to 0.18.1 and make 0.18.5.
About the "forbidden tx" protection, thats up to the community how you guys want to handle that. 0.18.1 - As its part of the consensus right now, if you guys decide to lift that protection, pools and exchanges would need to update on the 0.18.5 release, but again thats up to you.
I've talked to Peter and the best would be to modify the "forbidden tx" protection that it only blocks specific UTXOs ( But that would be a new system, not the one that got introduced in 0.13.9 which blocks all UTXOs )
So that issue should have been brought up way earlier, but seems like nobody looked into it until now, as that "issue" persisted for over 2 years ( since 0.13.9 ) release.
Happy to help/assist on the 0.18.5 or to clarify any other questions that come up.
Kind regard,
ChekaZ
Ok, I will prove that I am not a boss and that I am not personally interested.
My suggestion to the community:
to invite an independent dev, not ChekaZ , not MooncoinCore devs.
This dev had to be experienced, responsible, trusted, and with respect to decentralisation,
with respect to Mooncoin history and looking into the future,
and not affiliated with current devs, and not affiliated with agswinner and me.
He will start his own Bitcointalk ANN thread, Telegram channel and will unite the community.
I will not participate in important questions when I see that Mooncoin development is in trusted hands, and Mooncoin will remain decentralised with volunteers.
There will be another Bitcointalk ANN thread, and I will be just a topic starter of inactive thread obviously.
Of course, I am still responsible, if coins of normal members were locked by mistake in 0.18, but it had to be proved with research. No one, except Michi, reported it before, or show me a post. After the research and comments from ChekaZ we will know the truth.
My suggestion to the community:
to invite an independent dev, not ChekaZ , not MooncoinCore devs.
This dev had to be experienced, responsible, trusted, and with respect to decentralisation,
with respect to Mooncoin history and looking into the future,
and not affiliated with current devs, and not affiliated with agswinner and me.
He will start his own Bitcointalk ANN thread, Telegram channel and will unite the community.
I will not participate in important questions when I see that Mooncoin development is in trusted hands, and Mooncoin will remain decentralised with volunteers.
There will be another Bitcointalk ANN thread, and I will be just a topic starter of inactive thread obviously.
Of course, I am still responsible, if coins of normal members were locked by mistake in 0.18, but it had to be proved with research. No one, except Michi, reported it before, or show me a post. After the research and comments from ChekaZ we will know the truth.
A Big Thank You MF for your transparency and your help so far! This is a very precious suggestion!
Edit: I will expect the same suggestion from Mark Barry and Mooncoire Core Team!
Thank you? Seriously? Thank you for what?
You are thanking the person that is responsible for the blocking of 1,500 transactions but doesn't know who's coins are blocked. None knows how many coins are blocked nor how many wallets are blocked,
It took a senior developer to find out that her coins were blocked.
Do YOU know if YOUR coins are blocked?
You talk of transparency. How transparent is Mooncoin Foundation?
You then edit to say you expect the same from our team. It was OUR team that found out that coins other than the 62+12 were blocked. Is your type of transparency one that keeps these things hidden?
We found that out because WE were looking into how both wallets could be combined. Through all this crap WE are still working on a suitable solution.
And WE ARE TRANSPARENT.
A few small talk from now on, only serious proposals for a future development of Mooncoin.
I ask you again. Do you and your team accept MF's proposal to give up, reset everything and start over with an independent third party or not? It is a simple answer, YES or NO. Proposals will follow.
Mooncoiners need lucidity in the community, for more than 2 years the telegram group mooncoineco only serves for gossip and lies. I don't need to list too many facts, I will mention just 3 facts that already show how wrong the telegram group's attitude is against the pioneers of the ANN currency.
#The absolute majority of the 62B was owned by Mooncoin ANN veterans, all of whom are in favor of burning these coins.
#Vasillis was able to give security to the community by being able to lock the coin in an address, keeping them away from people with bad intentions. Even so, he was slandered to the point of leaving the community.
#ANN pioneers managed to correct several flaws thanks to Chekaz's new 0.18 wallet (the 0.17 wallet took so long to be ready and there was no correction of critical flaws, this posture is very doubtful)
Anyone who still has doubts, just start comparing the facts presented in the ANN Mooncoin with the information without facts presented in the mooncoineco telegram.
What makes a person spend years trying to manipulate and 'own' a decentralized currency through lies and gossip? Since you disagree so much with ANN pioneers, it would be wiser to use your time to create a new currency and develop projects based on it. For years there are thousands of cryptocoins, I have already invested in several that I ended up selling for not agreeing with the community or for seeing that the currency has no future. You have already spent more than 2 years trying to transform ANN members into Mexican soap opera characters, how much more time are you willing to waste?
It is evident that most Mooncoiners credit ANN pioneers, and not a telegram group who spends his life conspiring. Want proof? At the time of this posting 54.5% of Mooncoin users are using the 0.18 wallet as recommended by pioneering ANNs, 31.8% have not yet upgraded and still use the old 0.13 wallet and only 13.6% were innocent and uninformed to point of installing version 0.17.
#The absolute majority of the 62B was owned by Mooncoin ANN veterans, all of whom are in favor of burning these coins.
#Vasillis was able to give security to the community by being able to lock the coin in an address, keeping them away from people with bad intentions. Even so, he was slandered to the point of leaving the community.
#ANN pioneers managed to correct several flaws thanks to Chekaz's new 0.18 wallet (the 0.17 wallet took so long to be ready and there was no correction of critical flaws, this posture is very doubtful)
Anyone who still has doubts, just start comparing the facts presented in the ANN Mooncoin with the information without facts presented in the mooncoineco telegram.
What makes a person spend years trying to manipulate and 'own' a decentralized currency through lies and gossip? Since you disagree so much with ANN pioneers, it would be wiser to use your time to create a new currency and develop projects based on it. For years there are thousands of cryptocoins, I have already invested in several that I ended up selling for not agreeing with the community or for seeing that the currency has no future. You have already spent more than 2 years trying to transform ANN members into Mexican soap opera characters, how much more time are you willing to waste?
It is evident that most Mooncoiners credit ANN pioneers, and not a telegram group who spends his life conspiring. Want proof? At the time of this posting 54.5% of Mooncoin users are using the 0.18 wallet as recommended by pioneering ANNs, 31.8% have not yet upgraded and still use the old 0.13 wallet and only 13.6% were innocent and uninformed to point of installing version 0.17.
This response is so pitiful it doesn't warrant an answer.
All it does is to serve my point that a very small group see themselves as gatekeepers in Mooncoin and anyone else attempting progress is seen as a competitor.
You confirmed my point.
My argument is that you are dishonest, thanks for confirming, there really are no arguments and facts to prove your words. Have you thought about writing Mexican novels? I think Televisa would pay you very well, few authors manage to invent a plot with as much intrigue and gossip as you have been doing over 2 years. I'm sorry Mark, but you're not going to get your hands on the 62B and you're not going to manipulate Moonchain according to your will, get yourself another life goal.
Again, the response doesn't warrant a reply.
But as you've persisted I will let the community know of my involvement with you.
Do you remember me initiating contact with you on Twitter in 2018?
Ok, I will prove that I am not a boss and that I am not personally interested.
My suggestion to the community:
to invite an independent dev, not ChekaZ , not MooncoinCore devs.
This dev had to be experienced, responsible, trusted, and with respect to decentralisation,
with respect to Mooncoin history and looking into the future,
and not affiliated with current devs, and not affiliated with agswinner and me.
He will start his own Bitcointalk ANN thread, Telegram channel and will unite the community.
I will not participate in important questions when I see that Mooncoin development is in trusted hands, and Mooncoin will remain decentralised with volunteers.
There will be another Bitcointalk ANN thread, and I will be just a topic starter of inactive thread obviously.
Of course, I am still responsible, if coins of normal members were locked by mistake in 0.18, but it had to be proved with research. No one, except Michi, reported it before, or show me a post. After the research and comments from ChekaZ we will know the truth.
My suggestion to the community:
to invite an independent dev, not ChekaZ , not MooncoinCore devs.
This dev had to be experienced, responsible, trusted, and with respect to decentralisation,
with respect to Mooncoin history and looking into the future,
and not affiliated with current devs, and not affiliated with agswinner and me.
He will start his own Bitcointalk ANN thread, Telegram channel and will unite the community.
I will not participate in important questions when I see that Mooncoin development is in trusted hands, and Mooncoin will remain decentralised with volunteers.
There will be another Bitcointalk ANN thread, and I will be just a topic starter of inactive thread obviously.
Of course, I am still responsible, if coins of normal members were locked by mistake in 0.18, but it had to be proved with research. No one, except Michi, reported it before, or show me a post. After the research and comments from ChekaZ we will know the truth.
In my previous comment I had suggested that, only a new and independent dev should resolve this situation.
Jump to: