What helps sometimes is to restart the wallet and and open for PoS blocks and that will somehow 'push' the transactions. I don't know why but it seems to work. So, if I try to send whilst my wallet is staking it doesn't always work but it works if my wallet is locked and then unlocked for staking after I have made the transaction. Let's see with the new version and then you should be able to zap your wallets as well...
But I can't open the wallet to Pos because is my masternode wallet, so I can't move my mojo. There will be another fix for this problem before MojoV3? Your coins are in the controller wallet, yes? I mean a 'normal' MOJO wallet? Why can't you open it for staking? |
|
|
|
|
What helps sometimes is to restart the wallet and and open for PoS blocks and that will somehow 'push' the transactions. I don't know why but it seems to work. So, if I try to send whilst my wallet is staking it doesn't always work but it works if my wallet is locked and then unlocked for staking after I have made the transaction. Let's see with the new version and then you should be able to zap your wallets as well...
|
|
|
|
MOJO is currently on block 195,163 so should be another 3 days and we should get the changes in. The block time slowed a bit after we started using 2.4 and should slow down after block 200,000  |
|
|
|
(MOJOv2 and MOJOv1 ) died
MOJOv3? die or fraud
Please write something sensible next time not just fragments, do a tiny bit of research and stop being so lazy |
|
|
|
this ANN needs to be translated into some languages to get the attention of those non-english speaking traders and investors, we have some translator here in the forum, we made translation for a bounty, if in case you need one, i can do the Filipino translation.
I need to rewrite the ANN a bit and then maybe get some translations done |
|
|
|
MOJOv3 no bug  I think MOJOv3 will be good and stable, just because I see LIMX Dev is working on that. To my experience that guy is dedicated to quality. Deutsch Qualität  Yes, Limxdev and another dev has agreed to undertake the work to build a new code base. At the moment this is at the planning stage and the work will begin in late October and hopefully be completed in December 2016. I am looking to hire a PR manager for MOJO to promote MOJO and to promote the new MOJOv3 and to work with us on a long term PR strategy. If anyone is up for this please PM or meet at Skype for a chat. |
|
|
|
can you not convert to dash code base?
keeping the same chain ..
I am sorry to say, but the idea of masternodes for mixing is deeply flawed and it doesn't work for DASH either. Although DASH is 'big' it does not offer any real privacy and I think it was that realisation that brought on the shift towards a different view on privacy. I have done a lot of reading lately on privacy and I think DASH and other coins based around the masternode mixing idea will survive until users realise that they don't offer what they claim. Anonymous transactions is a game changer and we would be left behind with the current code base. There is nothing to say that a coin have to religiously stick to a current code base if there is another option that will be better for what we are trying to do. |
|
|
|
This Error is correct. Version 90000 will not more supported. Here same valid nodes. The Version Mojo 2 ain't bad. She has potential. addnode=128.199.34.210
addnode=178.8.154.64
addnode=184.69.47.154
addnode=185.3.33.200
addnode=192.161.53.47
addnode=194.106.98.24
addnode=213.136.88.142
addnode=213.136.94.226
addnode=222.5.183.201
addnode=45.55.195.243
addnode=46.188.4.74
addnode=5.189.136.83
addnode=66.11.122.218
addnode=73.130.81.250
addnode=79.146.239.10
addnode=79.74.80.85
addnode=81.153.78.92
addnode=84.200.32.238
addnode=84.59.219.33
addnode=88.217.49.37
addnode=88.217.55.208
addnode=92.222.87.172
addnode=92.78.112.97
addnode=93.104.209.17
addnode=95.116.26.67
addnode=95.211.110.151
Thanks for the nodes Christian. But my problem is not the absence of nodes, but the fact they are being immediately disconnected as soon as they connect. What about these two errors? 2016-10-09 23:35:23 socket recv error 10054 2016-10-09 23:35:34 CheckStakeKernelHash() : using modifier 0x619a43beed457013 at height=154441 timestamp=2016-09-24 10:37:42 UTC for block from timestamp=2016-09-23 17:34:08 UTC I am afraid MOJOv2 cannot go much further with all those connection, syncing and sending errors. I believe they have to be fixed before raising awareness and advertising this coin, otherwise new investors will be put off. This is partly the reason why we have decided to build a new code base. If we don't upgrade the code base we will get bogged down in putting out fires as it were and fix endless little issues. |
|
|
|
We need news - the coin need to raise awareness.
Where is the roadmap for the coin ? Where is the PR ?
regards
I am with you here. I am also asking updates for Developers if any or to someone who are willing to pursue or take over this project. My Mojo coin is sleeping on LiveCoin exchange. Is there still a brighter hope for this coin? The roadmap at the moment is a transition to MOJOv3 as detailed here: https://bitcointalk.org/index.php?topic=1629189We are working out the finer details of this and the project of a transition to MOJOv3 is out to tender for additional devs to complete the programming work. We will then be on a Bitcoin core 0.11.0 base w/ a PoSv3 modification w/ anonymous transactions. We have learnt from the experience of MOJOv2 and have done a lot of research around privacy. So, roadmap is (1) Complete MOJOv3 (2) Integrate MOJOv3 in Open Bazaar assess again. Edit: timeframe? MOJOv3 December / January |
|
|
|
I have the same problem: transactions aren't confirmed or confirmed very long.
I am aware of this problem and it has been highlighted so it's being considered. I have a workaround that works in some instances. I know it's not ideal but...if you have problems sending, it helps to restart the wallet and leave it locked and then make the transaction. If the transaction appears to get stuck open the wallet for staking and as you get a stake reward the transaction is normally confirmed. As I said, not ideal but works for me on Mac OSX qt. I agree that more PR should be done and I would welcome any ideas. |
|
|
|
|
Hi, i've sent you a PM re. some project work, pls have a look
|
|
|
|
I have opened up a new poll: Should MOJOv3 coin supply be reduced? i.e should we swap 1:1, swap 1:2 (meaning 2 MOJOv2 for 1 MOJOv3) or further reduction? Please discuss in the thread. The current coin supply is around 106,000,000 MOJO and as we are working on MOJOv3 we can reduce the total coin supply in a swap. Europecoin just did a swap and reduced the total supply 1:10 (i.e. 10 old for 1 new). I am undecided as to whether there is any point in reducing the total supply. I know that the value per coin may go up on a reduced supply but this is relative again. So, I am asking you to offer an opinion as to the pros and cons of a reduced supply. Please vote and discuss. MOJOv3 is some time away but we are working out all the tech. details and I wanted to consider this aspect. MOJOv3: https://bitcointalk.org/index.php?topic=1629189 |
|
|
|
CryptoID block explorer has been updated to v2.4 and appears to show connected nodes correctly. PLS UPDATE TO V2.4 BEFORE BLOCK 200,000
V2.3 AND OLDER W/ PROTOCOL <90001 WILL BE LOCKED OUT FROM THE NETWORK
IF YOU RUNNING OLDER SOFTWARE PLEASE UPDATE ASAP
|
|
|
|
|
I am keeping my Rubies and I trust the team to push this forward in some way or another!
|
|
|
|
With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.
Ok, connection problems seem to be gone. But there are still transaction issues. Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet. Same here - I tried to send transactions between 1K and 500K - all without success - they stay in the wallet. maybe it's the big amount of small transaction caused by 3 masternodes. Regards This is under investigation |
|
|
|
MOJOcoin v2.4 releasedFirst I have to apologise for scant updates over the last few weeks. I have been busy on many fronts. I will make an effort to publish regular updates. Rest assured however that MOJOcoin is pushing forward and we are learning as we progress and we have made some decisions for the future as I will explain later. We have just released the updated code for MOJOv2.4 and also an updated Windows-Qt wallet. A new Mac-Qt will be released in the next day or so. You can always find the most up to date wallet releases at our GitHub repo. https://github.com/MojocoinV2/mojocoin/releases What’s new in MOJOv2.4?We have added the Zapwallet Command to the wallet. This is a useful command that removes all wallet transactions that are not in the blockchain whilst reconstructing all confirmed transactions. It can remove “stuck” transactions and causes the wallet to “forget” any unconfirmed transactions so they will not be reconstructed. You can either add the -zapwallettxes argument on the command line: mojocoin-qt-win-v2.4.0.0.exe --zapwallettxes=1 or Add zapwallettxes=1 to the mojocoin.conf file. PoW blocks will be disabled at block 200,000. This will help to stabilise the PoS system and hopefully provide more consistent rewards for staking. The PoW system was meant as a backup and to move the chain at a time when there were too few addresses staking. This should no longer be an issue. Nodes are added for protocol version 90001 only. That means that older protocols will be ‘banned’ from the network. This aims to avoid forks with older clients. 5 min block time to reduce blockchain size. The initial block target time was 1 min but as the network is running the actual block time is closer to 30 sec. This creates a very large block chain very quickly and we believe this will be an issue as time passes. We have therefore set a new block time of 5 min. All the changes will be ‘activated’ at block 200,000 which should be on or around 11th or 12th October 2016. Make sure you upgrade to MOJOv2.4 before that time. Take care!
|
|
|
|
|
Show Posts
