Pages:
Author

Topic: ▉ANN▉ MTNC ▉▉▉▉░ Masternodecoin ░▉▉▉ Multiple Privacy Center Platform - page 57. (Read 239101 times)

sr. member
Activity: 1015
Merit: 289
we will update client asap , if you have such question above ,just follow it


we are working at one key bounty function now . will be released soon.

airdrop will open soon and will burn next 10M MTNC before release new version/

Good to hear that something is boiling in the pot. Dev Activity is badly needed now to resume attention to the coin, which I'm sensing had a bit faded lately. All the best!
legendary
Activity: 3108
Merit: 1531
yes
I overwrote the existing files when updating to V2.0 (windows) and updated the blockchain info with the new snapshot of the blockchain. The wallet is still synching but it seems to work. Will update when (or .... if  Kiss ) the wallet has synched.
sud
sr. member
Activity: 826
Merit: 301
we will update client asap , if you have such question above ,just follow it


we are working at one key bounty function now . will be released soon.

airdrop will open soon and will burn next 10M MTNC before release new version/

All good news! Also remember to send the rest of coins for the latest airdrop. For some people these are the first MNTC they ever get.
sr. member
Activity: 630
Merit: 252
Masternodecoin Team
we will update client asap , if you have such question above ,just follow it


we are working at one key bounty function now . will be released soon.

airdrop will open soon and will burn next 10M MTNC before release new version/
full member
Activity: 714
Merit: 117
How does upgrading the Wallet works in terms of masternodes. Can I just simply overwrite the exe with the v2.0 wallet or do I have to set up everything again including the masternode?

Good question. If I remember well for me it was sufficient to overwrite the exe. But on the other side, I've noticed that when doing little changes (like moving the masternode to another PC) it may happen that it does not work and then I have to setup the masternode again. I guess you'll have to try to find out for sure Smiley
legendary
Activity: 3108
Merit: 1531
yes
How does upgrading the Wallet works in terms of masternodes. Can I just simply overwrite the exe with the v2.0 wallet or do I have to set up everything again including the masternode?
full member
Activity: 714
Merit: 117
maybe someone knows the reason, why suddenly the masternodes go offline after 2-3 hours and then you have to start then manually again Huh
have this problem for 2-3 days. on my system, nothing has changed and my ip is still the same

I guess I've found a possibly working solution. You have to have a Masternodecoin.conf file in your data directory with the following information:

masternodeaddr=your IP:12990
masternode=1
externalip=your IP:12990
masternodeprivkey=your private key

just change "your private key" and "your IP" with your actual private key and IP.

so i dont need to change anything on the masternodecoin.conf

So you already had those data on the masternodecoin.conf and yet it didn't work? Very strange. Did you try to restart the wallet several times? And you're sure that you are not confusing the masternodecoin.conf with the masternode.conf ?
legendary
Activity: 1513
Merit: 1040
OK, looks like my MN is working properly again, but I still have conflicted transaction on the history tab and no coins either on MN nor on my other wallet. I've tried dumpwallet on version 1.0 and importwallet on 2.0, but i have an error.

I'm back up again with blockchain data source from 2018/03/13 and client version 2.0.0.0. I lost about 4000 MTNC of masternode reward (it's not a real loss, because some days ago the staking went crazy) and my coins sent to cryptopia are back in the meanwhile. This tx was already confirmed but never showed up at cryptopia. Not sure what happened exactly, but there was some kind of chainsplit for sure. Maybe only few users were effected of this because the number of postings about issues are limited.

To all of you with issues:
- dump your privatekey(s)
- install wallet version 2.0.0.0
- use blockchain data source from 2018/03/13
- import your privatekey(s)

Dumping/importing avoids the transfer of a defective wallet.dat to the new wallet version.

@allthebitandbobs and all others:
Don't use any file, use your private key(s) instead. In the wallet go to debug window -> console.
Old wallet:
Code:
dumpprivkey YOUR_PUBLIC_ADDRESS
New wallet with latest blockchain data from dev:
Code:
importprivkey YOUR_PRIVATE_KEY_YOU_GOT_FROM_ABOVE
The import process will take a while because of the rescan of all previous blocks.

Use the blockexplorer (http://mtnc.snodo.de:3001/) to check your account. If your coins show up, then everything is fine and it's just a wallet issue.
legendary
Activity: 3304
Merit: 8633
icarus-cards.eu
maybe someone knows the reason, why suddenly the masternodes go offline after 2-3 hours and then you have to start then manually again Huh
have this problem for 2-3 days. on my system, nothing has changed and my ip is still the same

I guess I've found a possibly working solution. You have to have a Masternodecoin.conf file in your data directory with the following information:

masternodeaddr=your IP:12990
masternode=1
externalip=your IP:12990
masternodeprivkey=your private key

just change "your private key" and "your IP" with your actual private key and IP.

so i dont need to change anything on the masternodecoin.conf
full member
Activity: 714
Merit: 117
maybe someone knows the reason, why suddenly the masternodes go offline after 2-3 hours and then you have to start then manually again Huh
have this problem for 2-3 days. on my system, nothing has changed and my ip is still the same

I guess I've found a possibly working solution. You have to have a Masternodecoin.conf file in your data directory with the following information:

masternodeaddr=your IP:12990
masternode=1
externalip=your IP:12990
masternodeprivkey=your private key

just change "your private key" and "your IP" with your actual private key and IP.
sr. member
Activity: 327
Merit: 251
SmartHoldem.IO
HELPPPPPPPPPPPPP Huh Huh Huh Huh

I done the update to wallet 2.0 and downloaded the blockchain  as suggested but my balance aint showing up .Instead of the 30k 40k coins i have before the issues happens it is now showing i have 0.3   coins  Shocked Shocked   .  Help for the love of god  Embarrassed

Help - Debug window - Console - repairwallet
sr. member
Activity: 1162
Merit: 252
HELPPPPPPPPPPPPP Huh Huh Huh Huh

I done the update to wallet 2.0 and downloaded the blockchain  as suggested but my balance aint showing up .Instead of the 30k 40k coins i have before the issues happens it is now showing i have 0.3   coins  Shocked Shocked   .  Help for the love of god  Embarrassed
legendary
Activity: 2660
Merit: 1154
Hello guys i have problem with the new version of the Wallet on the pi, anyone have a solution?

Quote
cd /home/pi
sudo rm -r .Masternodecoin
sudo rm -r db-4.8.30.NC

Danach:

sudo apt-get update
sudo apt-get install git build-essential qt5-default libtool autotools-dev autoconf pkg-config libssl-dev libprotobuf-dev protobuf-compiler libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev libboost-all-dev
sudo apt-get install libssl1.0-dev libssl1.0.2 # downgrade SSL from 1.1 to 1.0.2


wget 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
# verify it's really the file we are looking for
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c
# ONLY CONTINUE if there is no error - should be a line like this:
# -> db-4.8.30.NC.tar.gz: OK
tar -xzvf db-4.8.30.NC.tar.gz

# Build the library and install to /usr/local
cd db-4.8.30.NC/build_unix/
../dist/configure --prefix=/usr/local --enable-cxx
make -j4 # compile on 4 cores
sudo make install

# I added LD_LIBRARY_PATH to my .bashrc, so the bdb lib can be found by the executable we will compile later on
export LD_LIBRARY_PATH="/usr/local/lib/"


# Get MasterNodeCoin sources from github and compile it
#
cd /home/pi
mkdir masternodecoin
cd masternodecoin
git clone https://github.com/masternodecoin/masternodecoin.git .

# these scripts need to be executable
chmod +x src/leveldb/build_detect_platform
chmod +x src/secp256k1/autogen.sh


sudo touch dummy.sh
sudo chmod +x dummy.sh
sudo mv dummy.sh /usr/bin/
sudo ln -s /usr/bin/dummy.sh /usr/lib/arm-linux-gnueabihf/qt5/bin/lrelease

# ensure using the right version of qt
export QT_SELECT=qt5

# Now we can build the MasterNodeCoin-QT binary ...
qmake
make

sudo chmod 755 Masternodecoin-qt

# to run it simply type "./Masternodecoin-qt" to a terminal

After the compile, and start the new v2 wallet i become this error (the wallet v1 runs successful)?



Any ideas for the solution?
full member
Activity: 476
Merit: 100
Well, the official website can't get in and expect to learn more about project information from telegraph channels.
full member
Activity: 714
Merit: 117
maybe someone knows the reason, why suddenly the masternodes go offline after 2-3 hours and then you have to start then manually again Huh
have this problem for 2-3 days. on my system, nothing has changed and my ip is still the same

I am afraid nobody knows the reason - it has occasionally happened to me too, and then eventually has stopped happening after a while with no clear reason.
legendary
Activity: 3304
Merit: 8633
icarus-cards.eu
maybe someone knows the reason, why suddenly the masternodes go offline after 2-3 hours and then you have to start then manually again Huh
have this problem for 2-3 days. on my system, nothing has changed and my ip is still the same
newbie
Activity: 58
Merit: 0
Staking is really generous now, ive been hitting a stake almost daily for 5 days now with just 400 coins i am getting 6 MTNC coins per day Cheesy
Several coins got terrible troubles after switching from PoW to PoS. Hope that MTNC will not get such a unexpected problem.
full member
Activity: 714
Merit: 117
Same crazy behaviour happened to me. I updated to version 2.0.0.0 now and most of the mined amount from my three masternodes are gone. It looks like that a fork happened somewhere in the past.
Version 1.1.1.2 is at block 269,563 with 67 masternodes
Version 2.0.0.0. resynched from chain database in the OP is at block 269,790 with about 125 masternodes.
This is really really bad!

Damn, we need dev to take some action quick if this is true. I still have version 1.1.1.1 so it's even more complicated. How long ago could that fork happened?

Also transactions not going thru...

blockchain in official VPS is synchronize with cryptopia, we will confrim your status and if really like you said ,we will release new version quickly.

I have sent coins to cryptopia 4-5 days ago and they have still not showed up in my account. This is not very good, which would be the cause?
sr. member
Activity: 630
Merit: 252
Masternodecoin Team
OK, looks like my MN is working properly again, but I still have conflicted transaction on the history tab and no coins either on MN nor on my other wallet. I've tried dumpwallet on version 1.0 and importwallet on 2.0, but i have an error.

I'm back up again with blockchain data source from 2018/03/13 and client version 2.0.0.0. I lost about 4000 MTNC of masternode reward (it's not a real loss, because some days ago the staking went crazy) and my coins sent to cryptopia are back in the meanwhile. This tx was already confirmed but never showed up at cryptopia. Not sure what happened exactly, but there was some kind of chainsplit for sure. Maybe only few users were effected of this because the number of postings about issues are limited.

To all of you with issues:
- dump your privatekey(s)
- install wallet version 2.0.0.0
- use blockchain data source from 2018/03/13
- import your privatekey(s)

Dumping/importing avoids the transfer of a defective wallet.dat to the new wallet version.


try to use your wallet,dat file ,and you can found backup wallet.dat by system in backup file
Pages:
Jump to: