Topic: [MNB]💰 MoneyBagCoin X11+POS+MasterNodes 💰 - page 3. (Read 12678 times)

never change a running system!

the new wallet 1.2.0.0 is buggy, no connection to the network and the old wallet 1.1.0.0 has 10 connections, but no more staking since 7:30 am

short time firewall and antivirus program off, test it. Maybe it prevents connection.

ive also had that before. had to close and open the wallet a few times for it to keep syncing. it starts to sync, then stops, then you close and open and it syncs again

When a wallet do this with me, i normal close the wallet, copy the wallet.dat file out, remove everything in data folder, then copy wallet.dat file back agin, and then open my wallet agin, i have seen it on many wallets so its not a moneybag issue, its a general QT issue i ges.

yes, thats the one i have. been syncing for 48 hours and are still 2 weeks behind

Did you already load the new wallet ?, I also had the problem with the last version. It's all ok now. https://github.com/MoneyBagCoin/MoneyBagCoin/releases/tag/1.2.0.0

I think nothing good will come of it. Because there are no special valuable differences from other projects.

Hello. When will a big exchange like bittrex or cryptopia finally come? CM is dead, southx and stock.exchange are saturated because too few users. A grandiose coin, which falls more and more in value. The transmission speed is top, staking unsurpassed. I love this coin

im having a hard time getting the wallet to sync, anyone else having the same problem?

Amen!

Hi dev! Tell me what are the listing plans for the new stock exchanges? What are the plans to expand the zone of application? What are you working on now?
If this continues, the value of the coin will continue to fall

MoneyBagCoin is now being mined on D3Pool.eu - high profitability multipool

Link: D3pool.eu
ANN: https://bitcointalksearch.org/topic/annpool-d3pooleu-40-x11-coins-profit-switching-auto-exchange-2904614
Fee: only 0.5%

We have an active team & fast responding support - join us on Facebook - Twitter

Hi guys,
here we've a compiling problem with 1.2 version, needed after we loose MN state.
Deleted old path, upgraded and then reinstalled, but we get this error:

 makefile.unix:217: recipe for target 'obj/crypto/hmac_sha256.o' failed make: *** [obj/crypto/hmac_sha256.o] Error 1

Then we downloaded the compiled zip file, after that the daemon start correctly but we get error 104 on the debug.log, not capable to start as mn.

We found the  blk0001.dat is about 88MB and is synchronized, instead of 85MB on another wallet (just wallet not MN) on another ub 16.04 vps. The port 4321o0 is reachable. It could be we upgraded the MN leaving 30100 MNB not just 30000 MNB? Do we have to import the wallet.dat?

We are on a ubuntu 16.04.
Pls find a fix asap we are loosing money.

Many thanks

---
2018-02-07.15:55:09 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=0.0.0.0:43210, peer=67.87.156.185:51629
2018-02-07.15:55:09 - Added time data, samples 3, offset +2 (+0 minutes)
2018-02-07.15:55:13 - socket recv error 104
2018-02-07.15:55:13 - socket recv error 104
2018-02-07.15:55:14 - dseep - Asking source node for missing entry CTxIn(COutPoint(6a48725509, 1), scriptSig=)
2018-02-07.15:55:15 - P2P peers available. Skipped DNS seeding.
2018-02-07.15:55:15 - dnsseed thread exit
2018-02-07.15:55:16 - CActiveMasternode::ManageStatus() - Checking inbound connection to 'OUR-PUBLIC-IP:43210'
2018-02-07.15:55:16 - CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
2018-02-07.15:55:16 - CActiveMasternode::ManageStatus() - Could not find suitable coins!
2018-02-07.15:55:16 - CActiveMasternode::Dseep() - Error: masternode is not in a running status
2018-02-07.15:55:16 - CActiveMasternode::ManageStatus() - Error on Ping: masternode is not in a running status2018-02-07.15:55:16 - connected to self at OUR-PUBLIC-IP:46508, disconnecting
2018-02-07.15:55:16 - Successfully synced, asking for Masternode list and payment list
2018-02-07.15:55:16 - Successfully synced, asking for Masternode list and payment list
2018-02-07.15:55:21 - connect() to 45.76.23.187:43210 failed after select(): Connection refused
2018-02-07.15:55:22 - socket recv error 104
2018-02-07.15:55:22 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:44938, them=45.32.201.119:43210, peer=45.32.201.119:43210
2018-02-07.15:55:22 - Added time data, samples 4, offset +0 (+0 minutes)
2018-02-07.15:55:23 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=155.94.191.228:40044, peer=155.94.191.228:60286
2018-02-07.15:55:23 - Added time data, samples 5, offset +0 (+0 minutes)
2018-02-07.15:55:23 - nTimeOffset = +0  (+0 minutes)
2018-02-07.15:55:27 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=173.249.27.226:43210, peer=173.249.27.226:34414
2018-02-07.15:55:27 - Added time data, samples 6, offset +0 (+0 minutes)
2018-02-07.15:55:28 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=0.0.0.0:43210, peer=211.24.106.62:63613
2018-02-07.15:55:28 - Added time data, samples 7, offset -1 (+0 minutes)
2018-02-07.15:55:28 - nTimeOffset = +0  (+0 minutes)
2018-02-07.15:55:28 - Successfully synced, asking for Masternode list and payment list
2018-02-07.15:55:28 - Successfully synced, asking for Masternode list and payment list
2018-02-07.15:55:28 - Successfully synced, asking for Masternode list and payment list
2018-02-07.15:55:28 - Successfully synced, asking for Masternode list and payment list
2018-02-07.15:55:29 - socket recv error 104
2018-02-07.15:55:30 - Misbehaving: 45.77.101.196:43210 (0 -> 1)
2018-02-07.15:55:30 - ProcessMessage(dseep, 116 bytes) FAILED
2018-02-07.15:55:31 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=0.0.0.0:43210, peer=81.150.15.210:55402
2018-02-07.15:55:31 - Added time data, samples 8, offset +0 (+0 minutes)
2018-02-07.15:55:34 - Misbehaving: 45.77.101.196:43210 (1 -> 2)
2018-02-07.15:55:34 - ProcessMessage(dseep, 116 bytes) FAILED
2018-02-07.15:55:36 - socket recv error 104
2018-02-07.15:55:39 - connect() to 79.144.153.171:43210 failed after select(): No route to host
2018-02-07.15:55:40 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=0.0.0.0:43210, peer=5.167.236.22:52164
2018-02-07.15:55:40 - Added time data, samples 9, offset -20 (+0 minutes)
2018-02-07.15:55:40 - nTimeOffset = +0  (+0 minutes)
2018-02-07.15:55:40 - socket recv error 104
2018-02-07.15:55:42 - receive version message: version 69110, blocks=118589, us=OUR-PUBLIC-IP:43210, them=[2001:0:9d38:6abd:10c5:16b1:2cc1:4b90]:43210, peer=211.62.180.111:55289
2018-02-07.15:55:42 - Added time data, samples 10, offset -4 (+0 minutes)
2018-02-07.15:55:45 - ProcessBlock: ORPHAN BLOCK 0, prev=fa113f57f5b7e2f2c71e00bed1aef0306cfdd3635d730e95e4e54791593f8455
2018-02-07.15:55:46 - ProcessBlock: ORPHAN BLOCK 1, prev=00000000000051b303c4b2c7ec5d1e258ab5767cde780c944aafd43c9ac23cf8
2018-02-07.15:55:46 - SetBestChain: new best=ac2d4fa3625e5d9d6bdf16b2b0bbbaa559cff4a8d45efb62c63473c6b27aa465  height=118535  trust=96283935512177691465  blocktrust=166194369779805  date=02/07/18 14:24:00
2018-02-07.15:55:46 - ProcessBlock: ACCEPTED

Hi MoneyBag

When can we expect to see the coin on bigger exchanges eg. cryptopia?

Indeed, if you have added some nodes definitely give the wallet some time before giving up.  I let mine hang there for awhile and it did nothing then all of a sudden took off.  I'd say if after 2 hours you don't make any progress then you know something is wrong.

Do Nothing, just dont close it. For 1st open the wallet, its need very long long time to sync even with hundreds of nodes

my wallet still not sync how to solve it

i get 28 MNB

In one day with One D3, i got only 21 MNB. just curious what everyone is getting with one D3. thanks