|
Btw I have fixed the mobile access!
It was my fault. Sorry for the inconvinience.
regards
shahim
|
|
|
|
|
Hi,
this is very strange. I have never heard of a daemon / wallet getting deleted and recreated autmatically.
So you donÄt have any backup of you wallet.dat? Or of your public key? If you have one backup of your keys, you can rebuild it without problems.
Always remember to backup your wallet files!
Please recheck your folder. Perhaps write me a pm, if you need further help!
|
|
|
|
If 50% are staking ? will you have 2,5% inflation or 5% but the ones staking get more?
I think its the first. Pow ended at 50mil coins in 2014 and in the beginning there was 20% stake, then 10% and now 5%. So it should have been almost 70mil by now otherwise exactly as described here. |
|
|
|
HI. What is the final amount of coins? How looks the curve of extraction? Where can i get those kind of info? Peace You can find all data on the homepage. www.navcoin.org Or on the OP of this thread. regards shahim Still can not find the answer there... Maybe Im noob. Could (someone who know) just answer ? Actually there are 60.5 mill NAV in circulation. We have a annual POS rate of 5%, so a yearly increase of 5% if everybody stakes. regards shahim |
|
|
|
HI. What is the final amount of coins? How looks the curve of extraction? Where can i get those kind of info? Peace You can find all data on the homepage. www.navcoin.org Or on the OP of this thread. regards shahim |
|
|
|
Hello everyone. I'm hoping for some assistance here as I am having no luck trying to restore my backup wallet file. One night good ol' Microsoft decided to update while I was sleeping and then it restarted my computer. Afterwards it somehow messed up my Navcoin which was staking at the time so I reinstalled it. The problem though is my backup file is not displaying the correct address in Transactions: I have no idea what address this is NQf7bM5CaBdgqGS1JNmtpFepmyPM4oNkjVI've only ever had one address NLkEcTHJREEKJ8AXTDYannjdZg7hQEYcot) http://imgur.com/rXqebVbIt also doesn't show any information about NQf7bM5CaBdgqGS1JNmtpFepmyPM4oNkjV when searching the block explorer. The second unusual thing is my address list has some bizarre address that is obviously not real address: http://imgur.com/i2lvpBUI'm pretty lost as to what to do. I've let it sync fully, tried to repairwallet, -rescan, and updated to 3.9 with no success. I do know the wallet address and have unlocked it while doing these various things with no avail. Oh...... crap-a-sauris' rex....... I think I know my problem now. My wallet back up was from the beginning of 2016, so i'm assuming it's from the old coin Nav 1.0........... If this is the case, am I completely screwed and my coins are gone forever because my wallet back up is from the old blockchain? Uuugh  Jump into the Slack channel so we can help you! Hello, thisi sounds like the wallet.dat is damaged due a hard stop of the daemon. Check inside your Appdata/Navcoin2 Folder if there is a file "wallet.dat.dateofrestart" . If so, the restart damaged your wallet.dat and you need to use your backup wallet.dat. I hope you made a backup. regards shahim |
|
|
|
It will be interesting to see the nav tech 100% complete, should bump the price right up. Anyone have any predictions on price? We all love a bit of price speculation.  What do you mean with 100% complete? It actually is, or what do you mean? |
|
|
|
ok tried that [root@debian-2gb-sfo2-01 subchain (master)]# cd src/
[root@debian-2gb-sfo2-01 src (master)]# make -f makefile.unix USE_UPNP=1
g++ -c -O2 -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/root/subchain/src -I/root/subchain/src/obj -DUSE_UPNP=1 -DUSE_IPV6=1 -I/root/subchain/src/leveldb/include -I/root/subchain/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -fpermissive -MMD -MF obj/fugue.d -o obj/fugue.o fugue.c
fugue.c: In function ‘void fugue2_close(sph_fugue_context*, unsigned int, unsigned int, void*, size_t)’:
fugue.c:987:6: warning: invalid conversion from ‘void*’ to ‘unsigned char*’ [-fpermissive]
out = dst;
^
fugue.c: In function ‘void fugue3_close(sph_fugue_context*, unsigned int, unsigned int, void*)’:
fugue.c:1034:6: warning: invalid conversion from ‘void*’ to ‘unsigned char*’ [-fpermissive]
out = dst;
^
fugue.c: In function ‘void fugue4_close(sph_fugue_context*, unsigned int, unsigned int, void*)’:
fugue.c:1091:6: warning: invalid conversion from ‘void*’ to ‘unsigned char*’ [-fpermissive]
out = dst;
^
fugue.c: In function ‘void sph_fugue224_init(void*)’:
fugue.c:1114:29: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue_init(cc, 23, IV224, 7);
^
fugue.c:659:1: note: initializing argument 1 of ‘void fugue_init(sph_fugue_context*, size_t, const sph_u32*, size_t)’
fugue_init(sph_fugue_context *sc, size_t z_len,
^
fugue.c: In function ‘void sph_fugue224(void*, const void*, size_t)’:
fugue.c:1120:27: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue2_core(cc, data, len);
^
fugue.c:743:1: note: initializing argument 1 of ‘void fugue2_core(sph_fugue_context*, const void*, size_t)’
fugue2_core(sph_fugue_context *sc, const void *data, size_t len)
^
fugue.c: In function ‘void sph_fugue224_close(void*, void*)’:
fugue.c:1126:31: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue2_close(cc, 0, 0, dst, 7);
^
fugue.c:964:1: note: initializing argument 1 of ‘void fugue2_close(sph_fugue_context*, unsigned int, unsigned int, void*, size_t)’
fugue2_close(sph_fugue_context *sc, unsigned ub, unsigned n,
^
fugue.c: In function ‘void sph_fugue224_addbits_and_close(void*, unsigned int, unsigned int, void*)’:
fugue.c:1132:32: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue2_close(cc, ub, n, dst, 7);
^
fugue.c:964:1: note: initializing argument 1 of ‘void fugue2_close(sph_fugue_context*, unsigned int, unsigned int, void*, size_t)’
fugue2_close(sph_fugue_context *sc, unsigned ub, unsigned n,
^
fugue.c: In function ‘void sph_fugue256_init(void*)’:
fugue.c:1138:29: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue_init(cc, 22, IV256, 8);
^
fugue.c:659:1: note: initializing argument 1 of ‘void fugue_init(sph_fugue_context*, size_t, const sph_u32*, size_t)’
fugue_init(sph_fugue_context *sc, size_t z_len,
^
fugue.c: In function ‘void sph_fugue256(void*, const void*, size_t)’:
fugue.c:1144:27: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue2_core(cc, data, len);
^
fugue.c:743:1: note: initializing argument 1 of ‘void fugue2_core(sph_fugue_context*, const void*, size_t)’
fugue2_core(sph_fugue_context *sc, const void *data, size_t len)
^
fugue.c: In function ‘void sph_fugue256_close(void*, void*)’:
fugue.c:1150:31: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue2_close(cc, 0, 0, dst, 8);
^
fugue.c:964:1: note: initializing argument 1 of ‘void fugue2_close(sph_fugue_context*, unsigned int, unsigned int, void*, size_t)’
fugue2_close(sph_fugue_context *sc, unsigned ub, unsigned n,
^
fugue.c: In function ‘void sph_fugue256_addbits_and_close(void*, unsigned int, unsigned int, void*)’:
fugue.c:1156:32: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue2_close(cc, ub, n, dst, 8);
^
fugue.c:964:1: note: initializing argument 1 of ‘void fugue2_close(sph_fugue_context*, unsigned int, unsigned int, void*, size_t)’
fugue2_close(sph_fugue_context *sc, unsigned ub, unsigned n,
^
fugue.c: In function ‘void sph_fugue384_init(void*)’:
fugue.c:1162:30: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue_init(cc, 24, IV384, 12);
^
fugue.c:659:1: note: initializing argument 1 of ‘void fugue_init(sph_fugue_context*, size_t, const sph_u32*, size_t)’
fugue_init(sph_fugue_context *sc, size_t z_len,
^
fugue.c: In function ‘void sph_fugue384(void*, const void*, size_t)’:
fugue.c:1168:27: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue3_core(cc, data, len);
^
fugue.c:804:1: note: initializing argument 1 of ‘void fugue3_core(sph_fugue_context*, const void*, size_t)’
fugue3_core(sph_fugue_context *sc, const void *data, size_t len)
^
fugue.c: In function ‘void sph_fugue384_close(void*, void*)’:
fugue.c:1174:28: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue3_close(cc, 0, 0, dst);
^
fugue.c:1004:1: note: initializing argument 1 of ‘void fugue3_close(sph_fugue_context*, unsigned int, unsigned int, void*)’
fugue3_close(sph_fugue_context *sc, unsigned ub, unsigned n, void *dst)
^
fugue.c: In function ‘void sph_fugue384_addbits_and_close(void*, unsigned int, unsigned int, void*)’:
fugue.c:1180:29: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue3_close(cc, ub, n, dst);
^
fugue.c:1004:1: note: initializing argument 1 of ‘void fugue3_close(sph_fugue_context*, unsigned int, unsigned int, void*)’
fugue3_close(sph_fugue_context *sc, unsigned ub, unsigned n, void *dst)
^
fugue.c: In function ‘void sph_fugue512_init(void*)’:
fugue.c:1186:30: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue_init(cc, 20, IV512, 16);
^
fugue.c:659:1: note: initializing argument 1 of ‘void fugue_init(sph_fugue_context*, size_t, const sph_u32*, size_t)’
fugue_init(sph_fugue_context *sc, size_t z_len,
^
fugue.c: In function ‘void sph_fugue512(void*, const void*, size_t)’:
fugue.c:1192:27: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue4_core(cc, data, len);
^
fugue.c:864:1: note: initializing argument 1 of ‘void fugue4_core(sph_fugue_context*, const void*, size_t)’
fugue4_core(sph_fugue_context *sc, const void *data, size_t len)
^
fugue.c: In function ‘void sph_fugue512_close(void*, void*)’:
fugue.c:1198:28: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue4_close(cc, 0, 0, dst);
^
fugue.c:1051:1: note: initializing argument 1 of ‘void fugue4_close(sph_fugue_context*, unsigned int, unsigned int, void*)’
fugue4_close(sph_fugue_context *sc, unsigned ub, unsigned n, void *dst)
^
fugue.c: In function ‘void sph_fugue512_addbits_and_close(void*, unsigned int, unsigned int, void*)’:
fugue.c:1204:29: warning: invalid conversion from ‘void*’ to ‘sph_fugue_context*’ [-fpermissive]
fugue4_close(cc, ub, n, dst);
^
fugue.c:1051:1: note: initializing argument 1 of ‘void fugue4_close(sph_fugue_context*, unsigned int, unsigned int, void*)’
fugue4_close(sph_fugue_context *sc, unsigned ub, unsigned n, void *dst)
^
fugue.c: At global scope:
fugue.c:1207:1: fatal error: opening dependency file obj/fugue.d: No such file or directory
}
^
compilation terminated.
makefile.unix:192: recipe for target 'obj/fugue.o' failed
make: *** [obj/fugue.o] Error 1
[root@debian-2gb-sfo2-01 src (master)]# As I understand it that skips the miniupnp code but I don't think that is the issue as the modual worked when complieing navcoind I'll follow up and try tomorrow. asking on the slack general channel also I just point to this line: "fugue.c:1207:1: fatal error: opening dependency file obj/fugue.d: No such file or directory" You need to create the folder "obj" inside "src" . Also make a chmod 755 on src/leveldb/build_detect_platform . You will be fine with this regards Shahim |
|
|
|
You are talking nonsense! The Blockchain data is like two or three days old! Dec 19 03:59 it was updated. You did not download! |
|
|
|
Wow your download is slow : ) getting papers by pigeon and need to type it manually |
|
|
|
My wallet does not sync for the last 2 months
i have access to everything, every conversation BUT my NAV wallet did not sync
. They said HaShForce101 does not move markets.
NAV has 12 hrs!
4600 sats up 300. I Am the MASTER
Hash, you must be new here! Please download: www.navcoin.org/files/Nav-Blockchain.zipGo to your working directory and clean/delete everything except wallet.dat and navcoin.conf . After that unzip that file to your folder and be happy with a synced wallet!  |
|
|
|
A question, can I send nav coin from my poloniex wallet to wallet android without problems? Grateful.
Yes, there is no problem, doing it that way! |
|
|
|
Ladies and gentlemen, we're experiencing some accelerations.
Ladies and gentlemen, the accelerations that in recent days we have experienced, now seem to be overcome. At the moment, we are traveling at cruise speed again. Thanks for your cooperation, and continue to enjoy this journey. What just came into my mind https://www.youtube.com/watch?v=ygE01sOhzz0 |
|
|
|
I have a problem with nav electrum 3.6 for windows.I downloaded from your site and i use windows 10 enterprise. I create a default wallet as you explain above but i cant never send nav to others addresses i can only receive nav.I tried to unstall and install twice times but nothing. After lots minutes of long pause for signing transaction always failed the sending procedure with this error(watch image) Is there a solution of this problem? I tried also to pass my password from nav electrum to nav for android application but it s impossible to do because password long is different from accepting android application. Thanks for answer  currently Electrum NavCoin is unable to spend staked coins. So according to that, sending mightn't work if you imported some coins from the usual Nav wallet. I I remember right that error is coming from a too low fee, you have set inside the electurm wallet. Try setting it to standard and sending should work. regards shahim |
|
|
|
|
Stop posting double and stop posting insulting comments.
thnx
|
|
|
|
Since when nav will be on the market C-Cex?
They are actually working on it. So can not be so long anymore. |
|
|
|
Why is this coin called "Navajo Coin"
What is the connection with the Navajo ?
This coin is not called Navajo anymore. All switched to name NAV only. There is no connection. regards |
|
|
|
Who cares about deposits to polo .. Withdrawls is what should concern people If your depositing your getting rid of your coins and you will be crying for Christmas and not in a good way You guys should be thanking polo for trying to protect you from yourself. @nav team keep up the great work holding my navvies ! Thnx mate. Yes you could watch the dump happen, right after deposits where working again. no comment on that.... |
|
|
|
Point I was trying to make was us there any other small news items or development news that can
Be posted between main news announcements.
As some members here already recognized, there is a new wallet version 3.9.0 visible on the block explorer. We are working hard to finish and publish this. |
|
|
|
Any advice on how to get more connections for the windows wallet? I am sinced and get some staking rewards, but I only have one connection.
Go to the network section of our block explorer. https://chainz.cryptoid.info/nav/There is a node button where you get latest list for addnodes! |
|
|
|
|
Show Posts
