We have a telegram https://t.me/mazatribe and discord https://discord.gg/U7pmxhX that discussions have been going on in. We are currently working on making improvements to the code to provide 51% attack protection, but we need dev help. We've been saying we need Dev help for the last 4 years but no one wants to provide any funding for help or help without being paid, so we are stuck where we are. The Devs don't have a fund to work from and we aren't Maza rich either so we can't fund any dev work ourselves and with other time constraints the work we can put forth is limited. If you would like to come help out with the project feel free. We are currently working on adding in Mazanodes (masternodes) and POS to help with 51% attack mitigation. Again, feel free to come assist. Sorry, but this is not true. I spent a period of a couple of months working on code that the devs said they wanted all for free and upgraded the code base to rebase it on Bitcoin 0.14 with larger block sizes. It then sat there without feedback or support to test it out, until suddenly the team had new plans and they decided they didn't want it and booted me from the github and telegram channel. So saying no one wanted to help without pay is a lie. Right, and I still appreciate that you were willing to help. However, just rebasing to the .14 codebase did nothing to protect the chain, and as protecting the chain became a higher priority the ideas shifted from just a rebase to .14 codebase with larger blocksize to a full on revamp of what we needed to accomplish to provide more features and security to the chain. There were other issues here as well with why you were "booted" and I'd rather not drag anything else out. |
|
|
|
We have a telegram https://t.me/mazatribe and discord https://discord.gg/U7pmxhX that discussions have been going on in. We are currently working on making improvements to the code to provide 51% attack protection, but we need dev help. We've been saying we need Dev help for the last 4 years but no one wants to provide any funding for help or help without being paid, so we are stuck where we are. The Devs don't have a fund to work from and we aren't Maza rich either so we can't fund any dev work ourselves and with other time constraints the work we can put forth is limited. If you would like to come help out with the project feel free. We are currently working on adding in Mazanodes (masternodes) and POS to help with 51% attack mitigation. Again, feel free to come assist. |
|
|
|
Seriously, who releases new code and a fork within 24 hours of the code release? I pulled the code and built on March 6. New code was pushed March 7 with a fork within a day of release? This doesn't give time for any exchanges or pools to update properly. I'd be surprised if you aren't delisted from a bunch of exchanges that were still on the original code and had orders go through that they'd already completed for coins that are no longer valid on your new chain.
Our network was having problems that needed immediate fixing. This wasn't an ideal situation. We began communicating with exchanges about a week and a half prior to the fork, filling them in on the situation. On a whole exchanges and pools understood the need for the update having seen what was going on. Our network suddenly wasn't following the 90s emission schedule, and blocks were coming at random intervals which opened the network up to some serious consequences. Updating ASAP, although inconvenient, was the best option. H2C pool loses all GAME mined after fork (goes to the wrong chain after block although I update wallet at 07.03). The miners are ecstatic. This fork made in a hurry brought a lot of losses to the exchangers and pools and seems not to have solved the problems that had to be solved. All that is very strange. Few days peoples lose GAME because of selfish mining attack then this fussy hardrork. You talk you communicating with pools but I don't see it. I updated wallet when saw the commit with fork code but anyway I let down pool users. P.S. Why discord? Why don't you update coin announce and/or coin homepage post as all other coin developers do? It looks like you liked the turmoil caused by the previous fork and decided to repeat it? I receive an email that I need to update pool wallet. Of course, ASAP in 24 hours. It is a pity but I can not compile a new version. What game are the developers of GAME playing? Why are all forks so hasty and crooked? Let's play the game of try to double spend on exchanges that haven't updated yet again. Should be loads of fun! A total code rebase with thousands of lines of code changed pushed to github with a new fork within 24 hours. What fun could be lurking in that code with such little time to update that someone hasn't found yet. I know any reputable business would want to verify the code is clean before putting it onto their production network, and that would take longer than 24 hours to complete. The update is actually backwards compatible with 0.9.6, exchanges don't have to update immediately. That's why we went to pools first (we also explained that to pools that the update is backwards compatible). Good deal, I just noticed the one most recent update with a block number for the transaction checking and didn't parse through the other 1000's of lines of code changes and I guess just assumed it was another hard fork based on asking pools to update. I'm glad I'm mistaken. |
|
|
|
Seriously, who releases new code and a fork within 24 hours of the code release? I pulled the code and built on March 6. New code was pushed March 7 with a fork within a day of release? This doesn't give time for any exchanges or pools to update properly. I'd be surprised if you aren't delisted from a bunch of exchanges that were still on the original code and had orders go through that they'd already completed for coins that are no longer valid on your new chain.
Our network was having problems that needed immediate fixing. This wasn't an ideal situation. We began communicating with exchanges about a week and a half prior to the fork, filling them in on the situation. On a whole exchanges and pools understood the need for the update having seen what was going on. Our network suddenly wasn't following the 90s emission schedule, and blocks were coming at random intervals which opened the network up to some serious consequences. Updating ASAP, although inconvenient, was the best option. H2C pool loses all GAME mined after fork (goes to the wrong chain after block although I update wallet at 07.03). The miners are ecstatic. This fork made in a hurry brought a lot of losses to the exchangers and pools and seems not to have solved the problems that had to be solved. All that is very strange. Few days peoples lose GAME because of selfish mining attack then this fussy hardrork. You talk you communicating with pools but I don't see it. I updated wallet when saw the commit with fork code but anyway I let down pool users. P.S. Why discord? Why don't you update coin announce and/or coin homepage post as all other coin developers do? It looks like you liked the turmoil caused by the previous fork and decided to repeat it? I receive an email that I need to update pool wallet. Of course, ASAP in 24 hours. It is a pity but I can not compile a new version. What game are the developers of GAME playing? Why are all forks so hasty and crooked? Let's play the game of try to double spend on exchanges that haven't updated yet again. Should be loads of fun! A total code rebase with thousands of lines of code changed pushed to github with a new fork within 24 hours. What fun could be lurking in that code with such little time to update that someone hasn't found yet. I know any reputable business would want to verify the code is clean before putting it onto their production network, and that would take longer than 24 hours to complete. |
|
|
|
Seriously, who releases new code and a fork within 24 hours of the code release? I pulled the code and built on March 6. New code was pushed March 7 with a fork within a day of release? This doesn't give time for any exchanges or pools to update properly. I'd be surprised if you aren't delisted from a bunch of exchanges that were still on the original code and had orders go through that they'd already completed for coins that are no longer valid on your new chain.
Our network was having problems that needed immediate fixing. This wasn't an ideal situation. We began communicating with exchanges about a week and a half prior to the fork, filling them in on the situation. On a whole exchanges and pools understood the need for the update having seen what was going on. Our network suddenly wasn't following the 90s emission schedule, and blocks were coming at random intervals which opened the network up to some serious consequences. Updating ASAP, although inconvenient, was the best option. Problem is with most exchanges inundated with new customers and support requests it really didn't give them time. I know at least cryptopia lost some on this because they were off on the old network still after the fork and still allowed trades to go through. DGW will still have the same random intervals for the coin as long as multipools are hashing your coin as well, it will probably help some, but when a large multipool hashes the diff up high you'll notice a few hours between blocks if you don't have enough hash via dedicated miners to compensate. Giving pools and exchanges at least a week to look over the code changes and get wallets up and functional prior to a fork would have been more beneficial. Exchanges lost money on this fork, I'm sure cryptopia wasn't the only one that had issues, communicating with them early is the right thing to do, but you have to have the code for them to pull, and that wasn't on github until a day before the fork, just seem irresponsible to me. |
|
|
|
|
Seriously, who releases new code and a fork within 24 hours of the code release? I pulled the code and built on March 6. New code was pushed March 7 with a fork within a day of release? This doesn't give time for any exchanges or pools to update properly. I'd be surprised if you aren't delisted from a bunch of exchanges that were still on the original code and had orders go through that they'd already completed for coins that are no longer valid on your new chain.
|
|
|
|
Are you guys planning to do somthing to address the orphan issue?
Multipool.us seems to be the only pool that I've seen having so many orphans. How are the connections into the network? I'm not seeing the blocks claimed as orphans hitting the network as a fork so seems they are hitting the network delayed behind the block that was accepted. But with profit switching pools coming on and off when difficulty changes I'm not surprised that there could be more orphans during the low difficulty periods when large amounts of hashrate move onto the network. |
|
|
|
This coin is a very slow coin by design and it takes 220 blocks before coins are generated and available for payout. Once 220 blocks have passed from the block you have shares in and were credited for, the coins will be available for withdrawal. |
|
|
|
thank you very much...
Can you say me if there is any file with the blockchain bootstrap to download.... or I have to sinchronize the wallet ?
I have a bootstrap from about 3 months ago you can download here http://mazatest.cryptoadhd.com/bootstrap.dat |
|
|
|
Blocks: 66168 Last Block Time: 2017-08-29 16:30:33 (12d. 12h. 3m. 55s. ago) Die  Someone just threw some large hash on the chain and spiked the diff and then pulled off. It will start moving again. |
|
|
|
|
The original premine was 50 million MZC, divided into 2 wallets. The Dev team has control of one of these wallets as it was handed over and the Maza for that is at address MS5LqNWzrRo6DXzjXcafrCpWJL2NUXGRv5 The previous dev in control of the wallet at time of creation had sold some of the MZC in that wallet to try to cover server costs, without disclosing the spending. When it was handed over to the current Dev team in 2014 it had 16.8 million MZC of the 25 million left in it and we have built it back up to around 20 million. The other 25 million from the premine was lost to the block chain due to a forgotten password when someone encrypted a wallet, so it's already been burned.
The original premine addresses are as follows:
MNG15HKzUQeiT8QmtAghvSKpQwwgzZSFzS - password lost to original wallet (13 Million still sitting there) as well as the wallet that coins were transferred to (However, upon further inspection of the blockchain it appears the 12 million transferred out might have been recovered by someone as it seems to have possibly moved since I was told it was lost.
MKhbYDjoEUUJq1xoLqT5Xe4yLCNa1qWKqT - balance of coins stored at MS5LqNWzrRo6DXzjXcafrCpWJL2NUXGRv5
So at present there is around 13 million (possibly more) that is lost. The 20 million is held by stronger willed individuals that will not touch it for any personal gain. So that leaves 17 Million out of the original 50 million that is unaccounted for, and that was unaccounted for when the current dev team took over.
|
|
|
|
|
Maza will not switch to PoS at least while the current dev team is in place. Maza is meant to be spent, not held. Encouraging hoarding of Maza to increase your holdings doesn't help with the economy of spending Maza.
|
|
|
|
Well, I'm just confused as to what is the official latest core wallet or official website. Broken links, links to the encompass wallet from mazaclub. What the hell is going on?
v9.0.1 is the latest official release, we do have code on github for a 10.2 release that we are working on, it appears a pool built that and it can generate v3 blocks as it is based on the bitcoin core 10.2 codebase. When the v9.0.1 client saw the v3 blocks it started to throw the "obsolete" message, the v9.0.1 client will still work until the new code is ready for release. The 10.2 code is stable and should be good, we have just been working on cleaning it up and getting everything ready on it for a full release. |
|
|
|
I'm looking for a step by step guide on how to install a LINUX Mazacoin GUI Wallet. I don't want to install a pre-built wallet, I would like to build it from source.
If anyone knows where I can find the step by step page, please post it.
Thanks
First download and install dependencies: sudo apt-get install build-essential libboost-all-dev libcurl4-openssl-dev libdb5.1-dev libdb5.1++-dev git qt-sdk libminiupnpc-dev qrencode libqrencode-dev git Second, clone the source-code to your local machine: git clone https://github.com/mazacoin/mazacoin.git To compile the QT GUI, in the /mazacoin directory: (cd mazacoin) qmake “USE_UPNP=-“ “USE_QRCODE=1”
make This will compile mazacoin-qt, the icon appears to be blank but you can set it from /mazacoin/src/qt/res/icons. |
|
|
|
hmm seems that there is no mazacoin explorer up anymore..  mazacha.in is dead and a few others are on forked chain or not working... We have a working explorer at http://explorer.cryptoadhd.com:2750/chain/Mazacoin which is on the correct version of code and is accurate while the good folks at maza club work on getting mazacha.in going again. We have also been working on getting code ready to release for a new wallet version which should be coming sometime soon, so keep your eyes peeled on mazacoin.org and the @mazacoin twitter for updates on that. |
|
|
|
I'm trying to start the mazacoin-qt binary on Xubuntu 14.01 and get the following error $ ./mazacoin-qt
./mazacoin-qt: error while loading shared libraries: libdb_cxx-5.1.so: cannot open shared object file: No such file or directory It's possible that download doesn't work right, I just did a quick recompile from source that should work and put it here https://mega.co.nz/#!qURTESYR!q4ZOFX4tJFslzPznJ0tBYWiPTbyNfJRvrU8C2mE777s |
|
|
|
|
Show Posts
