Pages:
Author

Topic: [MOJO] MOJOv3 has been taken over by new devs - page 27. (Read 167315 times)

full member
Activity: 245
Merit: 100
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)?  Huh

Have a look at:

MOJOv3 'spook' is being planned and built - DETAILS

This 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.

good to hear! good job.
hero member
Activity: 1162
Merit: 500
CryptoTalk.Org - Get Paid for every Post!
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)?  Huh

Yes please tell us about this swap. Mojo doesn't seem to be doing so well as it should be so will the swap save it ? I wanted to buy some mojo to stake but I want to know what is going on first before I make my final decision.
legendary
Activity: 1148
Merit: 1000
A Wound in Eternity
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)?  Huh

Have a look at:

MOJOv3 'spook' is being planned and built - DETAILS

This 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.
full member
Activity: 245
Merit: 100
Yes, thank you very much! v2.4 is staking away like a champ for me now. Ah today is a good day.
legendary
Activity: 2576
Merit: 1073
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)?  Huh
member
Activity: 116
Merit: 10
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:

        ldd mojocoin2.4.0.0 |grep libdb
        libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)

Can you check it?

hero member
Activity: 792
Merit: 501
Hi,

all 3 Masternodes are updated to 2.4.0.0

addnode=213.136.88.142
addnode=213.136.94.226
addnode=93.104.209.17

Regards
sr. member
Activity: 465
Merit: 250
Finally I managed to sync the wallet.

v2.3.0.1 and protocol version 90001
working nodes
92.222.87.172
180.216.158.17
66.11.122.218
79.146.239.10
85.214.68.75

Please use the version 2.4.

Thanks, working fine!
copper member
Activity: 2324
Merit: 1348
BTW, this version should be v2.4 not v2.3.0.1 ?

what is this logic you speak of!? Tongue

but seriously, I agree. Having a protocol bump equate to only a single increment in VERSION_BUILD is rather senseless. I would really urge the powers that be here to put a lot more consideration into the versioning schema.

for reference, it should be as follows (what is outlined in the source, at least):

VERSION_MAJOR.VERSION_MINOR.VERSION_REVISION.VERSION_BUILD

The github Version is 2.4.0.0, but v2.3.0.1 was announced here.

@Limx Dev: The v2.4 is running smooth and I have 2 connections now.  Smiley

Yes, we need but more updates. Look here https://chainz.cryptoid.info/mojo/#!network
hero member
Activity: 601
Merit: 500
BTW, this version should be v2.4 not v2.3.0.1 ?

what is this logic you speak of!? Tongue

but seriously, I agree. Having a protocol bump equate to only a single increment in VERSION_BUILD is rather senseless. I would really urge the powers that be here to put a lot more consideration into the versioning schema.

for reference, it should be as follows (what is outlined in the source, at least):

VERSION_MAJOR.VERSION_MINOR.VERSION_REVISION.VERSION_BUILD

The github Version is 2.4.0.0, but v2.3.0.1 was announced here.

@Limx Dev: The v2.4 is running smooth and I have 2 connections now.  Smiley
copper member
Activity: 2324
Merit: 1348
Finally I managed to sync the wallet.

v2.3.0.1 and protocol version 90001
working nodes
92.222.87.172
180.216.158.17
66.11.122.218
79.146.239.10
85.214.68.75

Please use the version 2.4.
sr. member
Activity: 465
Merit: 250
Finally I managed to sync the wallet.

v2.3.0.1 and protocol version 90001
working nodes
92.222.87.172
180.216.158.17
66.11.122.218
79.146.239.10
85.214.68.75
copper member
Activity: 2324
Merit: 1348
BTW, this version should be v2.4 not v2.3.0.1 ?

what is this logic you speak of!? Tongue

but seriously, I agree. Having a protocol bump equate to only a single increment in VERSION_BUILD is rather senseless. I would really urge the powers that be here to put a lot more consideration into the versioning schema.

for reference, it should be as follows (what is outlined in the source, at least):

VERSION_MAJOR.VERSION_MINOR.VERSION_REVISION.VERSION_BUILD

Windows is online. I have currently 13 connection and my full node already hard coded in the source.

https://github.com/MojocoinV2/mojocoin/releases

Note: This Version works only with protocol 90001
hero member
Activity: 750
Merit: 500
BTW, this version should be v2.4 not v2.3.0.1 ?

what is this logic you speak of!? Tongue

but seriously, I agree. Having a protocol bump equate to only a single increment in VERSION_BUILD is rather senseless. I would really urge the powers that be here to put a lot more consideration into the versioning schema.

for reference, it should be as follows (what is outlined in the source, at least):

VERSION_MAJOR.VERSION_MINOR.VERSION_REVISION.VERSION_BUILD
hero member
Activity: 601
Merit: 500
Is there a mojocoind binary (Linux, Win) available?
hero member
Activity: 601
Merit: 500
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 90001


Get the latest wallets:

https://github.com/MojocoinV2/mojocoin/releases


ED: The planned update is:
- add Zapwallet Command
- change Blocktime to 5 min (Block 200K)
- disable POW (Block 200K)
- Add Nodes (only protocol 90001)

Updated and waiting for sync

BTW, this version should be v2.4 not v2.3.0.1 ?
hero member
Activity: 604
Merit: 500
So debugging process will end soon and some marketing moves will start? holding coin from the beggining, price is quite bad at the moment :/
copper member
Activity: 2324
Merit: 1348
Wallet don't sync again?

Same problem here.

Yes the network has problems. We work on that...but we need more updates.

sr. member
Activity: 465
Merit: 250
Wallet don't sync again?

Same problem here.
full member
Activity: 234
Merit: 100
Wallet don't sync again?
Pages:
Jump to: