Swapping coins will also be held at the exchange Livecoin?
No, not likely, we plan a web service swap. We'll get back to that later. Keep this thread to what is happening with the current system. Which swap are you talking about here?! I thought the swap is completed. Is there yet another coin swap planned (to MOJO v3)?  Have a look at: MOJOv3 'spook' is being planned and built - DETAILSThis is still some way off, but as we are seeking to make the current system work, we have decided to move on. I will open the new thread for discussion as soon as the finer details have been decided upon. Please keep this thread for MOJOv2 for now. 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. |
|
|
|
Swapping coins will also be held at the exchange Livecoin?
No, not likely, we plan a web service swap. We'll get back to that later. Keep this thread to what is happening with the current system. |
|
|
|
Can everyone please upgrade to v2.3.0.1 and protocol version 90001
There is a mandatory upgrade coming soon that will lock out all protocol versions below 90001Get the latest wallets:
https://github.com/MojocoinV2/mojocoin/releasesED: The planned update is: - add Zapwallet Command - change Blocktime to 5 min (Block 200K) - disable POW (Block 200K) - Add Nodes (only protocol 90001)
|
|
|
|
thanks for the help Limx Dev, Make opening the wallet, access depuration, tab in the console insert command addnode 85.214.68.75 onetry, not yet solved problem, help!
Do you have the new version? Is there a newer one as v2.3.0.1? v2.3.0.1 is the latest one And when will be new version with protocol 9001 only, you promised for past week? We are working out the plans for the next release. Times change, the cryptocurrency landscape change and we learn and research and need to stay with the times, so expect an update re. MOJOv3 in the next 2-3 weeks. |
|
|
|
thanks for the help Limx Dev, Make opening the wallet, access depuration, tab in the console insert command addnode 85.214.68.75 onetry, not yet solved problem, help!
Do you have the new version? Is there a newer one as v2.3.0.1? v2.3.0.1 is the latest one |
|
|
|
|
Livecoin is back up and open again, so you can deposit and withdraw.
|
|
|
|
|
Can someone please tell me which version of OpenSSL BTC use for client communication?
|
|
|
|
|
Was the alleged broken ring signatures reported in February 2016 fixed? I was trying to find out but couldn't find any documentation
|
|
|
|
|
We are working on this today and it should be fixed soon. We have to sort out some basic issues and make sure the network is running fine before we start any kind of marketing. Once we are satisfied that the network is healthy we will start PR.
|
|
|
|
This info on livecoin.net just now:
Exchange is undergoing scheduled maintenance!
Programmers are arduously working on the update, but hardly get it done in less than an hour. Sorry for inconvenience, we don't like it too . And don't worry, your orders and funds are in safe.
Livecoin has a technical issue with the Mojo wallet and we are working to fix it. Hopefully it should be resolved today at some point. We are also working to fix the connection issues and we think we have found that it is caused by different versions of OpenSSL, so we will build new binaries with a slightly older OpenSSL and that should solve any connection issues. The Livecoin issue is being worked on. Sorry about few updates but work is happening... Thank you for your work. Can you tell us, what version of OpenSSL we will have to use to compile from source? We are trying to work it out. There will be an update tomorrow at some point. Just be patient. |
|
|
|
This info on livecoin.net just now:
Exchange is undergoing scheduled maintenance!
Programmers are arduously working on the update, but hardly get it done in less than an hour. Sorry for inconvenience, we don't like it too . And don't worry, your orders and funds are in safe.
Livecoin has a technical issue with the Mojo wallet and we are working to fix it. Hopefully it should be resolved today at some point. We are also working to fix the connection issues and we think we have found that it is caused by different versions of OpenSSL, so we will build new binaries with a slightly older OpenSSL and that should solve any connection issues. The Livecoin issue is being worked on. Sorry about few updates but work is happening... |
|
|
|
This project is dead? wallet not's work... right?
Wallets ok just having a nightmare getting it built personally Will you let me know if the above works? gave same error! /usr/bin/ld: cannot find -lsecp256k1
collect2: error: ld returned 1 exit status
Makefile:984: recipe for target 'mojocoin2.3.0.1' failed
make: *** [mojocoin2.3.0.1] Error 1
This is everything I've done: git clone https://github.com/MojocoinV2/mojocoin
edited Makefile, added -lgmp to libs //without this libgmp isnt found (thanks again dsutil)
cd mojocoin
chmod 775 src/leveldb/build_detect_platform
chmod +x src/leveldb/build_detect_platform
cd src/leveldb/
make libleveldb.a libmemenv.a //without this leveldb.a & libmemenv.a don't compile giving compilation error
cd ../secp256k1/
chmod +x ./autogen.sh
./autogen.sh
./configure --enable-module-recovery
make
commented out mojocoin.pro#L213
cd ../..
qmake
make
Did you build secp256k1 manually? We will try to build and see if we get the same error |
|
|
|
This project is dead? wallet not's work... right?
Wallets ok just having a nightmare getting it built personally Will you let me know if the above works? |
|
|
|
This project is dead? wallet not's work... right?
No, this project is not dead, if you follow us on GitHub you will see what we are currently doing |
|
|
|
Morning guys, yesterday i did a fresh install of mint on my staking box built wallets for 1337, Espers, Syndicate & OKCash without issues, still failing to compile mojocoin though current error I'm getting: /usr/bin/ld: cannot find -lsecp256k1
collect2: error: ld returned 1 exit status
Makefile:984: recipe for target 'mojocoin2.3.0.1' failed
make: *** [mojocoin2.3.0.1] Error 1
Syndicate also has secp256k1 in the src folder and built without any issues, any advice? Have a look in this section here, and you can extract the actual commands to build it manually https://github.com/MojocoinV2/mojocoin/blob/master/mojocoin.pro#L208-L218basically run these commands. cd src/secp256k1 ./autogen.sh ./configure --enable-module-recovery make once built, comment out this line https://github.com/MojocoinV2/mojocoin/blob/master/mojocoin.pro#L213then try building the rest again |
|
|
|
Just a word of warning. Crypto-Trade has added MOJO of their own accord and they have not been in contact with us. We can not verify or endorse any service so always do you own research before using any service. |
|
|
|
4. Deactivate PoW blocks.
Why? I have seen PoW helping to move some stuck blockchains. Things happen... so why not to keep it just in case? I would prefer to reduce the PoW reward, perhaps to 2 MOJO. PoW should be remain as a backup, if PoS stuck. Statements once taken should be valid: 2. Activate PoW blocks for X11 mining for around 6 months w/ a block reward of 20 MOJO
3. Keep PoW activated for around 2 years past the 6 months with a zero reward as a backup measure to ensure the chain doesn’t get stuck with low stake weight / MN issues.
It's really a dynamic process and it doesn't seem wise to me to stick to things that no longer make sense. There are no longer any issues around staking addresses and I think that the small PoW blocks are disrupting the PoS. Ok, I understand you. Nearly 40% of the last 100 blocks were found by PoW. I suppose, the difficaulty calculation for PoS and PoW are independent. How about to setup a much higher block time for PoW, so it could remain as backup? I think the issue was really the lack of staking addresses and the lack of people being able to stake due to the calculation error in the previous version. This shouldn't be a problem any more and so I think we can safely remove the PoW. |
|
|
|
4. Deactivate PoW blocks.
Why? I have seen PoW helping to move some stuck blockchains. Things happen... so why not to keep it just in case? I would prefer to reduce the PoW reward, perhaps to 2 MOJO. PoW should be remain as a backup, if PoS stuck. Statements once taken should be valid: 2. Activate PoW blocks for X11 mining for around 6 months w/ a block reward of 20 MOJO
3. Keep PoW activated for around 2 years past the 6 months with a zero reward as a backup measure to ensure the chain doesn’t get stuck with low stake weight / MN issues.
It's really a dynamic process and it doesn't seem wise to me to stick to things that no longer make sense. There are no longer any issues around staking addresses and I think that the small PoW blocks are disrupting the PoS. |
|
|
|
I can't get any connections, I have added all the nodes from the block explorer and let it run for hours but not a single connection???
Hmmmm, kinda like your coin Mojocoin. Haven't had a good connection to your coin in three weeks. Fix your own coin man before you come here and complain. There are only a few people unable to connect, and so what if I have a coin, should I not be allowed to run other coins? |
|
|
|
|
Show Posts
