Author

Topic: ★[ANN] [NAV] NAV COIN - Community Fund Live!!! - page 283. (Read 2085654 times)

legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card

19:17:13

repairwallet


19:17:33

{
"wallet check passed" : true
}
Sent TX are still there

both have a - in front but one all digits are red (-3500.001)the other all digits are black (-4958.0001)

I started it last night will check it when I get home tonight.

I have 2 transactions that show in my wallet with over 4000 confirms but not in block explorer on in destination wallet.

Status: 4670 confirmations, broadcast through 8 nodes
Date: 9/9/2016 21:02
To: crypto-trade NXxFBeCbE7dA47JswGZpctEmCJQ4sfy1Ko
Debit: -4958.00 NAV
Transaction fee: -0.0001 NAV
Net amount: -4958.0001 NAV
Transaction ID: bae3bcff9c4de6b1d7ec1cd9be06825010e5e0d694a89dd811df33a24f272b02-000


Status: 4761 confirmations, broadcast through 7 nodes
Date: 9/9/2016 20:20
To: crypto-trade NXxFBeCbE7dA47JswGZpctEmCJQ4sfy1Ko
Debit: -3500.00 NAV
Transaction fee: -0.0001 NAV
Net amount: -3500.0001 NAV
Transaction ID: 8578f5257203db56809846d08c0a12cb2fea0db6fa56fb78856acf49f1d209f3-000

wallet is ver v3.6.0.0-UT-ZAH-HA-DEZ-BIN  on TOR

I can't see either of those Transaction ID's on the block explorer: https://chainz.cryptoid.info/nav/

Can you try to run "repairwallet" from the debug console and see if the funds reappear in your wallet?
legendary
Activity: 1302
Merit: 1001
Founder - NavCoin Ⓝ
Hi Nav Coiners,

It's time for the Nav Coin weekly update and this week I come bearing two amazing pieces of news for you all!

Nav Coin Thin Clients for Windows and OSX

We are very pleased to announce that we have finished the first release of our range of Thin Clients for desktop! These allow you to store and send NAV without having to download the entire block chain yourself. They work using the same electrum server technology that the mobile wallet uses which means they're instantly on and ready to go all the time.

Grab your new thin client from the downloads page: http://www.navcoin.org/downloads

For more information, please head over to our news page and read the great press release Sophia has written up for us:

http://www.navcoin.org/news/articles/post/nav-coins-new-lite-wallet

There are two types of wallet available for Windows and OSX. We have built an Installer for each which will set the application up into your program files or applications directory. Then we have also built a portable version which you don't need to install and could even run from a USB drive if you wanted to.

This marks the first official OSX wallet we have for Nav Coin. We are working hard to bring also the full node OSX wallet live in the coming days.

Please note that the OSX wallet has a couple of bugs, the preferences wont open and QR code scanning is unavailable. These are bugs within the electrum base code and we are waiting on them to provide a fix for these issues at which point we will update our wallet also.

Anonymous Transaction Test Network is Live

The second big piece of news is that we have successfully deployed the new anon scripts to the live environment and sent our first anonymous transactions using the live system!

This week the system will be undergoing stress tests and other QA measures to make sure that when we release it to the public it is robust and functions flawlessly. Depending on what comes from the stress testing, we are hoping to re-launch the anon system as early as next week. We will keep you updated on this progress as more information becomes available to us.

The wallet is all configured to use the new system. It has some exciting new tweaks which I will detail in full in my forthcoming whitepaper or at the latest in our release notes for the client when we launch the system.

If you want to have a look at the new wallet code, you can see it on this branch here:

https://github.com/navcoindev/navcoin2/commits/anon-test

Our progress has been reflected in our projects page with the Thin Client project moving to the completed section and the decentralisation implementation percentage being bumped up to 70%!

We have also been making progress with the Web Wallet which is now at 95%, we hope to get this finished and out to the public in the coming days.

http://www.navcoin.org/projects

It's very exciting times here at Nav Coin HQ, we are super proud of what we have achieved this week, but we are also showing no signs of slowing down!

This weeks focus is the OSX full node wallet, the web wallet and stress testing the Anon Network.

We have a lot great features in the lab and with decentralisation just around the corner, we are in such a good place right now and the future is bright.

Talk Soon,
Craig.




So we are starting the week so far. Here some insight into what we were upto and plans ahead.

Warm Regards,
~SoopY~
newbie
Activity: 31
Merit: 0
Don't forget to

Code:
sudo apt-get update

before installing the packages. You may have an old version of one of them.

Then try

Code:
make -f makefile.unix clean
make -f makefile.unix USE_UPNP=1

Pretty sure I've seen this particular build error before, i can't quite remember what fixed it.


I updated and used your commands but it still not works
Here the complete output:
Code:
node@node-V ~/navcoin2-master/src $ make -f makefile.unix clean
rm -f navcoind
rm -f obj/*.o
rm -f obj/*.P
rm -f obj/build.h
node@node-V ~/navcoin2-master/src $ make -f makefile.unix USE_UPNP=1
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/alert.d -o obj/alert.o alert.cpp
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/version.d -o obj/version.o version.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/checkpoints.d -o obj/checkpoints.o checkpoints.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/netbase.d -o obj/netbase.o netbase.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/addrman.d -o obj/addrman.o addrman.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/crypter.d -o obj/crypter.o crypter.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/key.d -o obj/key.o key.cpp
key.cpp: In member function ‘bool CPubKey::VerifyCompact(const uint256&, const std::vector&) const’:
key.cpp:632:10: warning: unused variable ‘fComp’ [-Wunused-variable]
     bool fComp = IsCompressed();
          ^
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/eckey.d -o obj/eckey.o eckey.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/init.d -o obj/init.o init.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/bitcoind.d -o obj/bitcoind.o bitcoind.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/keystore.d -o obj/keystore.o keystore.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/core.d -o obj/core.o core.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/main.d -o obj/main.o main.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/net.d -o obj/net.o net.cpp
net.cpp:1099:20: warning: ‘strDNSSeed’ defined but not used [-Wunused-variable]
 static const char *strDNSSeed[][2] = {
                    ^
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/protocol.d -o obj/protocol.o protocol.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcclient.d -o obj/rpcclient.o rpcclient.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcprotocol.d -o obj/rpcprotocol.o rpcprotocol.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcserver.d -o obj/rpcserver.o rpcserver.cpp
rpcserver.cpp:324:1: warning: missing initializer for member ‘CRPCCommand::reqWallet’ [-Wmissing-field-initializers]
 };
 ^
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcmisc.d -o obj/rpcmisc.o rpcmisc.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcnet.d -o obj/rpcnet.o rpcnet.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcblockchain.d -o obj/rpcblockchain.o rpcblockchain.cpp
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=1 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcrawtransaction.d -o obj/rpcrawtransaction.o rpcrawtransaction.cpp
In file included from /usr/include/boost/iterator/iterator_categories.hpp:22:0,
                 from /usr/include/boost/iterator/iterator_facade.hpp:14,
                 from /usr/include/boost/range/iterator_range_core.hpp:27,
                 from /usr/include/boost/range/iterator_range.hpp:13,
                 from /usr/include/boost/assign/list_of.hpp:20,
                 from rpcrawtransaction.cpp:6:
/usr/include/boost/variant/get.hpp: In instantiation of ‘typename boost::add_reference::type boost::strict_get(boost::variant&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = CSecretAddress; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference::type = const CScriptID&]’:
/usr/include/boost/variant/get.hpp:284:25:   required from ‘typename boost::add_reference::type boost::get(boost::variant&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = CSecretAddress; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference::type = const CScriptID&]’
rpcrawtransaction.cpp:221:77:   required from here
/usr/include/boost/variant/get.hpp:178:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE
     BOOST_STATIC_ASSERT_MSG(
     ^
makefile.unix:221: recipe for target 'obj/rpcrawtransaction.o' failed
make: *** [obj/rpcrawtransaction.o] Error 1



I use linux to navigate, I do not like windows because it is dangerous.
Exactly this is the reason why I don't want to use Windows, I don't trust it.
To run the client on linux, is more safe.

To your problem.. if you think your system is corrupt, then dont connect it to the internet.
1. Run your wallet on a offline computer and extract the private keys to the adresses with your coins.
2. Import this keys on a fresh/clean system and client.
3. Transfer the coins to a new clean wallet to be safe.
4. Dont try to repair a corrupt system, better install the system new.
full member
Activity: 200
Merit: 100
Got my first 170 NAV Coins !
legendary
Activity: 1050
Merit: 1000
SETUP a security question for all withdrawals and lock your wallet. This should be apart of basic house keeping. for everyone .Also backup your wallet.dat regularly  Smiley
newbie
Activity: 34
Merit: 0
It is possible obtain the private key? and then open my wallet in electrun wallet?

it seems that my computer to run bad, the attacker has corrupted everything, i can not connect to the network.

I have many computers to try and also have a backup created with acronis 4 days ago.

Hopefully i can connect to the network and to extract the coins, only use few coins to mine.

first of all, do not open that wallet.exe again until we can figure out some stuff. do not let it synch or it might send out those 500k coins.

secondly: hmm are you sure these are not your addresses? or sent them yourself?

since the 599k coins are not shown on the block explorer. than if you were hacked. it seemed like they did not have a copy of your wallet and tried to sent from their own computer but it seems they are trying to send from your computer. this means you have a scryt somewhere running. but it also means that the request to send never made it outside your network therefore outside nodes have not accepted anything. Which is good. so DO NOT synch your wallet. if you have to open your wallet, disconnect your internet.

maybe you can delete this last request and hope it never was seen outside.

also check for malware.

open task manager and look for suspicious behavior.
check you configuration "config file"  and see if some one tried to change stuff.

was there any other coin you downloaded recently. a lot of shitcoin have a lot of malware for this purpose.


Good advice. Don't sync it. You could try restoring your wallet to a different computer (assuming you have a backup) and resyncing the block chain using one of our blockchain downloads from the downloads page http://navcoin.org/downloads

If the transaction hasn't been submitted to the network, the balance might return to your wallet. If it's been broadcast there's pretty much nothing anyone can do.

Thanks for the help!

Blockchain confirms my balance, that's good against the attacker,  can not hack NAV!

I haven't sent 8,000 nav, only 2 navcoin to electrun wallet. I'm no expert, I like repairing hardware, especially reballing.

The first time  entered the attacker, steal me 8k navcoin, in other 2 attempts to failed.

newbie
Activity: 34
Merit: 0
Yesterday my computer has little mine but more quantity NAV, today has entered the attacker.


The password is outside the computer and it has minimum 250 bit.

The password is outside the computer. Once I have saved with keypass, when used to NEM wallet. Some time ago, i hurt a wallet of NEM. Bloodyrockye helped me, he repair my wallet (thanks!). Strange things happen to me.

I guess keepass be sure, or... maybe not, best distrust.

I have copied NAV wallet on 2 micro sd and two pen drive, i'm too suspicious.

Now I will install acronis security copy, then change the password and download blockchain.


I use linux to navigate, I do not like windows because it is dangerous.
hero member
Activity: 794
Merit: 510
NavCoin Founder
hero member
Activity: 794
Merit: 510
NavCoin Founder
It is possible obtain the private key? and then open my wallet in electrun wallet?

it seems that my computer to run bad, the attacker has corrupted everything, i can not connect to the network.

I have many computers to try and also have a backup created with acronis 4 days ago.

Hopefully i can connect to the network and to extract the coins, only use few coins to mine.

first of all, do not open that wallet.exe again until we can figure out some stuff. do not let it synch or it might send out those 500k coins.

secondly: hmm are you sure these are not your addresses? or sent them yourself?

since the 599k coins are not shown on the block explorer. than if you were hacked. it seemed like they did not have a copy of your wallet and tried to sent from their own computer but it seems they are trying to send from your computer. this means you have a scryt somewhere running. but it also means that the request to send never made it outside your network therefore outside nodes have not accepted anything. Which is good. so DO NOT synch your wallet. if you have to open your wallet, disconnect your internet.

maybe you can delete this last request and hope it never was seen outside.

also check for malware.

open task manager and look for suspicious behavior.
check you configuration "config file"  and see if some one tried to change stuff.

was there any other coin you downloaded recently. a lot of shitcoin have a lot of malware for this purpose.


Good advice. Don't sync it. You could try restoring your wallet to a different computer (assuming you have a backup) and resyncing the block chain using one of our blockchain downloads from the downloads page http://navcoin.org/downloads

If the transaction hasn't been submitted to the network, the balance might return to your wallet. If it's been broadcast there's pretty much nothing anyone can do.
legendary
Activity: 1274
Merit: 1000
It is possible obtain the private key? and then open my wallet in electrun wallet?

it seems that my computer to run bad, the attacker has corrupted everything, i can not connect to the network.

I have many computers to try and also have a backup created with acronis 4 days ago.

Hopefully i can connect to the network and to extract the coins, only use few coins to mine.

first of all, do not open that wallet.exe again until we can figure out some stuff. do not let it synch or it might send out those 500k coins.

secondly: hmm are you sure these are not your addresses? or sent them yourself?



since the 599k coins are not shown on the block explorer. than if you were hacked. it seemed like they did not have a copy of your wallet and tried to sent from their own computer but it seems they are trying to send from your computer. this means you have a scryt somewhere running. but it also means that the request to send never made it outside your network therefore outside nodes have not accepted anything. Which is good. so DO NOT synch your wallet. if you have to open your wallet, disconnect your internet.

maybe you can delete this last request and hope it never was seen outside.



also check for malware.

open task manager and look for suspicious behavior.
check you configuration "config file"  and see if some one tried to change stuff.

was there any other coin you downloaded recently. a lot of shitcoin have a lot of malware for this purpose.




hero member
Activity: 794
Merit: 510
NavCoin Founder
It is possible obtain the private key? and then open my wallet in electrun wallet?

it seems that my computer to run bad, the attacker has corrupted everything, i can not connect to the network.

I have many computers to try and also have a backup created with acronis 4 days ago.

Hopefully i can connect to the network and to extract the coins, only use few coins to mine.

Hi igona, i am sorry to hear you have been the victim of a computer hacker. If someone has remote access to your computer and your wallet is unlocked, there's no stopping someone sending your coins out. This is the same with all coins, bitcoin included. Was your wallet locked at the time? I can see that it is locked in your screen shots.

If it was locked, the only way that someone could have sent the funds is if they have your wallet unlock password. It is not possible to send coins from a locked wallet without the passphrase. I would highly recommend changing your wallet passphrase to a very secure one.

Please remember to back up your wallet regularly and make sure you implement strong passphrases and never keep them stored on your computer in plain text.

Regards,
Craig.
newbie
Activity: 34
Merit: 0
It is possible obtain the private key? and then open my wallet in electrun wallet?

it seems that my computer to run bad, the attacker has corrupted everything, i can not connect to the network.

I have many computers to try and also have a backup created with acronis 4 days ago.

Hopefully i can connect to the network and to extract the coins, only use few coins to mine.
newbie
Activity: 34
Merit: 0
There is an attacker, some pirate on the NAV network, I lost 8,000 NAV .  Before my balance was: 1,246,508

Maybe I lost my old investment because attacker entered 3 times in my wallet.


My old coins NEM are valued much. Cry


Attacker:  NS1FHJSXysvirmMMBaCG1cBu4runQEgNw7


My wallet: NRGhvnK3Y39P5WDpK7pfu5QunSTUNufTSW


I am dedicated to computer science. The Windows 10 system is not used for business, just for programs. I use the backup Acronis True Image, and a standard user account for windows, i do not use the administrator account. I not attain to use NAV wallet in linux, I'll try to get all the coins to electrum-NAV.3.6.0-portable wallet.





https://s12.postimg.org/nodx553p9/NAV_danger.png

https://s21.postimg.org/7ptohfzrb/attacker.png

https://s9.postimg.org/tzo8idz1r/my_nav_go.png






hero member
Activity: 794
Merit: 510
NavCoin Founder
What have you installed before?

Apt-get install...? 

sudo apt-get install build-essential
sudo apt-get install libssl-dev
sudo apt-get install libdb++-dev
sudo apt-get install libboost-all-dev
sudo apt-get install libqrencode-dev
sudo apt-get install libgmp3-dev
sudo apt-get install libzmq3-dev
sudo apt-get install libgmp3-dev

Yes, I installed all of them

Don't forget to

Code:
sudo apt-get update

before installing the packages. You may have an old version of one of them.

Then try

Code:
make -f makefile.unix clean
make -f makefile.unix USE_UPNP=1

Pretty sure I've seen this particular build error before, i can't quite remember what fixed it.

newbie
Activity: 40
Merit: 0
Can someone tell me why NAV is better than ShadowProject? Thank you.

Please see this post:

I have invested a pretty substantial amount of Bitcoin into NAV. Seems like it has a great community, and very active devs.... But, I'm starting to wonder if I've made a mistake. What features does NAV have that others don't? There are other anonymous coins. What features will NAV have that others won't? People seem to shy away from inflationary coins. Why go that route? Please help me feel comfortable with my NAV holdings. Again, I love how active the community and Devs are, but I still worry.

I think its a matter of different approaches to anonymous transactions. We use a secondary block chain called a "Subchain" to direct and manage our anonymous transactions as they are encrypted, randomised and routed through the Anonymous Network. This approach is unique to Nav Coin and it has some inherent benefits, the primary one being its resilience. The system runs purely off two block chains, not relying on a database or any extra data storage to mark transactions as "waiting to process" or "processed". This means if our anonymous servers were blocked / deleted / taken down / destroyed or whatever, we could simply start up a new server somewhere else, restore the wallet.dat files and the servers would resume processing transactions without loss and without needing to worry about backing anything else up apart from the wallet.dat files.

Secondly, because we use two block chains, we are able to break the transaction chain between sender and receiver. We have a pool of NAV waiting to be sent on the outgoing server, which can be sent as soon as the outgoing server receives the instruction from the subchain. It doesnt have to wait for the real NAV to arrive because of the nature of how block chains work and the way the server is coded, we can trust the amounts recorded to the subchain as correct and send the amount of NAV from the pool before the sent NAV arrive. This means the NAV recieved are not able to be traced back to the NAV which were sent no matter how hard you look at the NAV block chain.

Third, we are coming fast to the point where we can decentralise the anonymous network and allow other users to setup their own processing servers. When this happens, users will be able to earn NAV for processing transactions and we will become the first fully decentralised, double encrypted, anonymous system running purely off block chain tech! Wow, what a mouthful!

So that's the technology, lets talk about features.

We are working towards being the first anonymous crypto which can send anon transactions from the mobile wallet. That will be massive. As well as anonymous merchant integrations, the raspberry pi staking unit and a few other things currently on our road map: http://www.navcoin.org/projects

Even if you were just to consider us to have the same features as DASH or XMR, then that still makes us hugely undervalued by at least 10x - 100x

By the way, i think the other anon coins are great and you should definitely look into them. See if they fit your needs and if the technology fits your ideals. Having multiple options in the financial privacy sector of cryptocurrencies is definitely a good thing. If there was just one, then firstly there is no competition to innovate and secondly it becomes a single point of failure. We offer a secure alternative, based on different technology served in a way which we believe is the best approach. We are part of the array of tools you can use to protect your financial privacy on the internet and we support the efforts of all the other anon coins.

That's my 2c anyway Smiley
Thank you, it's definitely interesting and project has quite a drive although I'll have to read it again, first point doesn't make much sense to me as I think in any blockchain you can just easily add/replace nodes. Second point is probably clear to me - mixing with two blockchains will confuse tracking even more, that makes sense. And third point I don't get it. It's quite common that you can add your own servers (nodes) into network, so what's so special here? Maybe it's reffering something like Dash Master Nodes.

One more specific thing when I was trying NAV - http://www.navcoin.org/downloads offers you Linux Wallet Download but redirect you only to source code. That's not nice. People mostly don't wish to build anything they want just try. Especially when often there are building issues when you don't have reference OS. Would be nice to provide builds.

1) Yes, but if we're talking about a system which truly disconnects sender from receiver there needs to be some data store in the middle between the incoming and outgoing node other wise all transactions could just be traced back to sender (eventually) through the main blockchain. A common way to manage data for reading between two servers is a traditional database, something like MySQL. If you used a common database to be the middleman between incoming and outgoing nodes, then you leave yourself open to all sorts of known vulnerabilities. All someone would have to do is figure out how to inject some rows into the database and they could make your outgoing server send coins to them. Thus you would have departed from the vast majority of benefits of using blockchains in the first place. We get around this problem by using an encrypted subchain as this data store which both servers can read. As you know, blockchains are immutable and it is very difficult to fake records, plus they're fully restorable.

2) Great, glad you understand Smiley

3) Anyone who has the full node NAV client can be a part of the NAV network. But up until now, the only people who have the subchain and also the code which processes the anonymous transactions have been us. We have kept it private and offered a set of servers which were open to the public for anonymizing transactions. This will be how the new setup first launches, after that, we will create a distributable version of the anonymous transaction processing code which any user (with some crypto and linux knowledge) will be able to configure, run and process anon transactions with which will earn them the 0.5% processing fee.

Make sense?

Feel free to ask any more questions you may have.

Cheers,
Craig.

Thanks, it makes sense and I believe I see the points. In general, it proves that NAV takes anonymization very seriously. To me, NAV 1.0 anonymity provided was probably more than enough. When I see how difficult  is hunting bitcoin thieves I'm wondering if we really need that complex anonymity model. But yeah, if you wish to eliminate all the traces you need stuff like this.
newbie
Activity: 31
Merit: 0
Yes, I installed all of them
legendary
Activity: 1082
Merit: 1002
What have you installed before?

Apt-get install...?  

sudo apt-get install build-essential
sudo apt-get install libssl-dev
sudo apt-get install libdb++-dev
sudo apt-get install libboost-all-dev
sudo apt-get install libqrencode-dev
sudo apt-get install libgmp3-dev
newbie
Activity: 31
Merit: 0

got to source code >>doc>>>(your OS you're trying to build)   and follow those instructions.

so for Linux  : https://github.com/navcoindev/navcoin2/blob/master/doc/build-unix.txt


it should be easy to follow the instruction. it's typical same instructions as most of coins.

I get this error:

Code:
make -f makefile.unix
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wunused-function -Wunused-variable -fpermissive -Wconversion-null -g -DBOOST_SPIRIT_THREADSAFE -I/home/node/navcoin2-master/src -I/home/node/navcoin2-master/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/node/navcoin2-master/src/secp256k1/include -I/home/node/navcoin2-master/src/leveldb/include -I/home/node/navcoin2-master/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcrawtransaction.d -o obj/rpcrawtransaction.o rpcrawtransaction.cpp
In file included from /usr/include/boost/iterator/iterator_categories.hpp:22:0,
                 from /usr/include/boost/iterator/iterator_facade.hpp:14,
                 from /usr/include/boost/range/iterator_range_core.hpp:27,
                 from /usr/include/boost/range/iterator_range.hpp:13,
                 from /usr/include/boost/assign/list_of.hpp:20,
                 from rpcrawtransaction.cpp:6:
/usr/include/boost/variant/get.hpp: In instantiation of ‘typename boost::add_reference::type boost::strict_get(boost::variant&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = CSecretAddress; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference::type = const CScriptID&]’:
/usr/include/boost/variant/get.hpp:284:25:   required from ‘typename boost::add_reference::type boost::get(boost::variant&) [with U = const CScriptID&; T0 = CNoDestination; T1 = CKeyID; T2 = CScriptID; T3 = CSecretAddress; T4 = boost::detail::variant::void_; T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = boost::detail::variant::void_; typename boost::add_reference::type = const CScriptID&]’
rpcrawtransaction.cpp:221:77:   required from here
/usr/include/boost/variant/get.hpp:178:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE
     BOOST_STATIC_ASSERT_MSG(
     ^
makefile.unix:221: recipe for target 'obj/rpcrawtransaction.o' failed
make: *** [obj/rpcrawtransaction.o] Error 1

legendary
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
I started it last night will check it when I get home tonight.

I have 2 transactions that show in my wallet with over 4000 confirms but not in block explorer on in destination wallet.

Status: 4670 confirmations, broadcast through 8 nodes
Date: 9/9/2016 21:02
To: crypto-trade NXxFBeCbE7dA47JswGZpctEmCJQ4sfy1Ko
Debit: -4958.00 NAV
Transaction fee: -0.0001 NAV
Net amount: -4958.0001 NAV
Transaction ID: bae3bcff9c4de6b1d7ec1cd9be06825010e5e0d694a89dd811df33a24f272b02-000


Status: 4761 confirmations, broadcast through 7 nodes
Date: 9/9/2016 20:20
To: crypto-trade NXxFBeCbE7dA47JswGZpctEmCJQ4sfy1Ko
Debit: -3500.00 NAV
Transaction fee: -0.0001 NAV
Net amount: -3500.0001 NAV
Transaction ID: 8578f5257203db56809846d08c0a12cb2fea0db6fa56fb78856acf49f1d209f3-000

wallet is ver v3.6.0.0-UT-ZAH-HA-DEZ-BIN  on TOR

I can't see either of those Transaction ID's on the block explorer: https://chainz.cryptoid.info/nav/

Can you try to run "repairwallet" from the debug console and see if the funds reappear in your wallet?
legendary
Activity: 1274
Merit: 1000


I just wanted to say that the (ZIP) Windows client now works well.

But would be nice, if someone could tell me how to build a working Linux client.
I read the readme-qt.rst, but for me it doesnt work.

got to source code >>doc>>>(your OS you're trying to build)   and follow those instructions.

so for Linux  : https://github.com/navcoindev/navcoin2/blob/master/doc/build-unix.txt


it should be easy to follow the instruction. it's typical same instructions as most of coins.
Jump to: