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

You are entitled to an opinion but that does not mean that we are giving up on this, just because you don't like what is happening. This forum is always the same, people just moan endlessly and sit back and wait for their coins to appreciate. Very few people contribute to the value of the coins they hold. We were unfortunate that one of the devs involved in the V2 code delivered a dysfunctional code that we have to keep fixing. This is the reason why progress is slow and we can't focus on the utility and PR of the coin. It simply doesn't work they way it was intended and therefore there is a decision to move to a new code base and make sure that works so we can concentrate on other sides of the project.

There is no point at all in just posting complaints, we are working towards goals but it may take some time. We are not doing any PR as there are problems. We will do PR once we are happy that we have a good product.

I'm looking for privacy and the whole masternode idea is deeply flawed, wait and see what the long term effects are on DASH, DNET and others. The mixing, if and when it works does not provide any privacy and the mixing does not provide the privacy you think it does. There is a new breed to coins that will leave DASH and others behind. The reckoning will happen when the majority of people see that the coins that promote privacy, like DASH, does not provide this at all. I want MOJO to be something different than this code can provide.

Sorry .. but remember .. the ico price was around 250 sat. now we see 1/10the left. this is not an ordinary up/down.

What about the funds you raised - how much was it 150 BTC ? What will you do - what will be the next steps - which of your goals did you ever reached.

Sorry - but this is more and more a grave ..

Why ditch the masternodes? Synx and dnet have very functional masternodes. Can't you borrow their code?

I think I'm going to export all privkeys into a fresh wallet and see what happens. That had worked once in the past.

It's not going to close down, we will continue. You must know that crypto goes up and down and there are no guarantees of price. We will take it into the next version which will be a new code base and away from all the issues and ditch the masternodes. If you want to get out, that would be your choice.

Hi all,

anyone seen the latest prive @ livecoin ? The Coin is dying !

Today 16 sat price. That's we all lost our investment and dev sitting on our BTC ?

My proposal - pay  the investors their coins back and close it - It don't make sense - the 3rd swap without a running wallet.

Limx Dev tries the best he can to fix things but there is a point when giving up is the better option

regards

I have read your "old" debug.log and you have sent many tx from your masternodes. And you have many masternodes. Hmm....

Even with the newest version, I keep getting:

2016-11-12 01:27:06 partner 45.63.43.114:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:06 ProcessMessage(version, 101 bytes) FAILED
2016-11-12 01:27:12 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-12 01:27:12 ProcessMessage(version, 101 bytes) FAILED


Edit: Instead of addnode, I used the connect= line to many of my MN's. I'm no longer connecting to those obsolete addresses.

Now let's just wait and see if the transaction eventually broadcasts.


(BTW, what does server=1 do as opposed to server=0?)


Edit: Still no luck broadcasting transactions.

Is it possible to run POS and MN's in the same wallet? If so, what will prevent the 200,000 MOJO MN collateral from Staking? I don't see the option to lock the collateral balances like other MN wallets do. Or is the collateral automatically locked if it's specified in the masternode.conf file?

Gonna try it now. Any special instructions.

Edit: Updated, rezapped and attempted once more. If transaction doesn't confirm soon, I'll send you a new debug.log.

Okay, i have write a new installer with "peers.dat" replacement. And we a new Mojo version online.

https://github.com/MojocoinV2/mojocoin/releases/tag/v2.4.5.1.0
-stake improvement

Thank you for your debug file. I see you have many wrong nodes in your source (old protocol version). I recommend to delete the peers.dat. I write a new installer with peers.dat replacement.

Status: 0/unconfirmed
Date: 08.11.2016 16:57

Zapped, restarted, selected transactions that had 10,000+ confirms via coin control. Now I have to wait and see what happens. How long are people waiting on average to see their transactions get their first confirmation?

Debug.log file was pretty huge. Deleted it, then restarted wallet with the -zapwallettxes=1 flag, then created a new transaction. This is using version 2.4.5. - Let me know if this info suffices, or you need more from the debug.log file. It nearly instantly grew to 8MB in size.

CTransaction(hash=17e5a2dd4f1033202b85cc6dffd3aaa21ab288c2dc3c6c0edaea572d12b0b13c, nTime=1478882390, ver=1, vin.size=30, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(9735214ff7, 0), scriptSig=30450221008f197855e28d5f)
    CTxIn(COutPoint(9e5f807a8d, 3), scriptSig=3045022100fdb5406da866dc)
    CTxIn(COutPoint(60aaa3b2e9, 3), scriptSig=3045022100aa7c8e067b5ff8)
    CTxIn(COutPoint(b9fbff264b, 3), scriptSig=304402201d2e39708e08e28c)
    CTxIn(COutPoint(093074b86e, 3), scriptSig=3045022100a36dd31a9f42a5)
    CTxIn(COutPoint(5120b7a5e3, 3), scriptSig=3045022100a756a7df19ff6b)
    CTxIn(COutPoint(8e4ac11cf3, 3), scriptSig=3044022077eaafe381ff0d00)
    CTxIn(COutPoint(d20c34af3b, 3), scriptSig=3045022100b8b25c5cd0360a)
    CTxIn(COutPoint(90b13d0ab5, 3), scriptSig=304402205cd9c3019220c999)
    CTxIn(COutPoint(f57fd0e3ed, 3), scriptSig=304402206d4aa3e0054c1bad)
    CTxIn(COutPoint(1fcea73015, 3), scriptSig=3045022100e8eb0504cad61b)
    CTxIn(COutPoint(e489b84454, 3), scriptSig=3045022100a4bf205a65e696)
    CTxIn(COutPoint(5edb7e1e2d, 3), scriptSig=3045022100c68b5a099a0317)
    CTxIn(COutPoint(3e68ffe0d6, 3), scriptSig=3045022100f054eecaacf712)
    CTxIn(COutPoint(84aa7065ce, 3), scriptSig=304502210084560a4fc3cd60)
    CTxIn(COutPoint(38708c63f2, 3), scriptSig=3045022100aa0a752a25c05b)
    CTxIn(COutPoint(c79ce12cf9, 3), scriptSig=3045022100f47a5aedcfcb0d)
    CTxIn(COutPoint(deefa5a740, 3), scriptSig=30440220046fad3d59f3c243)
    CTxIn(COutPoint(8640545fd8, 3), scriptSig=3045022100a4998a85d6b12a)
    CTxIn(COutPoint(4bc2f3b30d, 3), scriptSig=3045022100e8992c35ed55c3)
    CTxIn(COutPoint(d5a5a54a5b, 3), scriptSig=3044022040dc4056302e8212)
    CTxIn(COutPoint(daedf04f1c, 3), scriptSig=3045022100cd5af1e164a00b)
    CTxIn(COutPoint(220758f4f4, 2), scriptSig=3045022100fd8129c44c7d1d)
    CTxIn(COutPoint(aa33fc7cb6, 3), scriptSig=3045022100f8c255c5015275)
    CTxIn(COutPoint(0cd30e41d8, 2), scriptSig=30450221008ccc66968212f4)
    CTxIn(COutPoint(09dacecb10, 3), scriptSig=30450221009ab22126f312ea)
    CTxIn(COutPoint(c2103edc39, 2), scriptSig=30440220589150b68c7146f3)
    CTxIn(COutPoint(fbe44648dd, 3), scriptSig=30450221008dd64e55b341fe)
    CTxIn(COutPoint(f8f3a2384b, 3), scriptSig=304402201b6db42fee0e04a8)
    CTxIn(COutPoint(34b0a07c5a, 3), scriptSig=30450221008956287165ebc5)
    CTxOut(nValue=0.7964423, scriptPubKey=OP_DUP OP_HASH160 c12ef6802c3c568a6540e6ed55ea2e8fabfe2c1f OP_EQUALVERIFY OP_CHECKSIG)
    CTxOut(nValue=13674.00, scriptPubKey=OP_DUP OP_HASH160 51c12d03b31ac3cc0fd0f3eab2e8b00c7c3f24e4 OP_EQUALVERIFY OP_CHECKSIG)
2016-11-11 16:39:51 keypool keep 30
2016-11-11 16:39:51 AddToWallet 17e5a2dd4f1033202b85cc6dffd3aaa21ab288c2dc3c6c0edaea572d12b0b13c  new
2016-11-11 16:39:51 AddToWallet 17e5a2dd4f1033202b85cc6dffd3aaa21ab288c2dc3c6c0edaea572d12b0b13c  
2016-11-11 16:39:51 AddToWallet 17e5a2dd4f1033202b85cc6dffd3aaa21ab288c2dc3c6c0edaea572d12b0b13c  
2016-11-11 16:39:51 Relaying wtx 17e5a2dd4f1033202b85cc6dffd3aaa21ab288c2dc3c6c0edaea572d12b0b13c
2016-11-11 16:39:52 CoinControlDialog::updateLabels() - Time elapsed: 0.001000
2016-11-11 16:39:52 socket recv error 10054
2016-11-11 16:39:55 CoinControlDialog::updateLabels() - Time elapsed: 0.000000
2016-11-11 16:39:55 keypool return 29
2016-11-11 16:39:57 socket recv error 10054
2016-11-11 16:39:59 socket recv error 10054
2016-11-11 16:40:00 socket recv error 10054
2016-11-11 16:40:02 partner 45.32.234.45:22255 using obsolete version 90000; disconnecting
2016-11-11 16:40:02 ProcessMessage(version, 101 bytes) FAILED
2016-11-11 16:40:06 socket recv error 10054

Okay so now I deleted all files in my appdata/roaming folder except for wallet.dat and masternode.conf - ran the deinstaller, then reinstalled. Do I now have to start the wallet with the -zapwallettxes=1 flag ? Or just try sending a transaction again?

Sorry for the delayed response. Did you want me to paste my debug info here? I'll run the deinstaller now.

Guys, where can I find info about SWAP for v3?

Hello, PR manager vacancy still relevant? I am engaged in a professional promotion at various venues.My topic on the forum: https://bitcointalksearch.org/topic/service-on-professional-translation-of-your-topics-and-websites-1630074

I'll check the nodes and update