it is the most overvalued coin now
exactly not .. check the market depth and you will find a buy/sell overhang by 30%
|
|
|
SIA is saddled with a blockchain. Imagine you own a business and you have a SIA server that you backup your data to. A fire happens, and you need to get a new set of servers up and running right away. With SIA, you have to wait a LONG time to get the blockchain before you can begin to recover your data. And even then, downloads can take awhile to show up. It's not optimal. If you are a business, you want to get back up and running immediately. Not sometime in the next 2 days.
if you loose everything but the passphrase you can easily recover everything quickly with a download of the prepared blockchain.
|
|
|
I suggest to make more use of Bitsquare. Then you won't have any issues with coin withdraws too.
|
|
|
are there some other user who run v3.9 under Win10 x64 ? What is your experience?
|
|
|
... I still have the same issue - v3.7 works seemless and v3.9 does not connect here is the latest debug log tail: init message: Laden abgeschlossen GUI: QObject::connect: No such signal ClientModel::showProgress(QString,int) GUI: QObject::connect: (receiver name: 'navcoin') GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int) GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64) GUI: QObject::connect: (receiver name: 'SendCoinsDialog') No valid UPnP IGDs found upnp thread exit Loading addresses from DNS seeds (could take a while) keypool reserve 10 keypool return 10
at this point the NAVcoin-qt client hangs with a steady process load of 12%. If I exit the client it does not stop but becomes non interactive and hangs with 12% process load. I can kill it then with the task manager. Starting v3.7 with the absolute same configuration connects immediately. Environment is Win10. If somebody has a explanation that leads to solve the problem I will tip 10 NAV Is active UPnP on your router? Must be activated no idea - but v3.7 works seamless and the v3.7 log shows the same entry If somebody has a better explanation that leads to solve the problem I will tip 20 NAV now According to Hi guys,
... I would just let it run a few hours or a day and check again.
I let my node run for more than 19 hours now and it still produces constant 12% processor load and does not connect. But there is another log entry now: ... Loading addresses from DNS seeds (could take a while) GUI: QObject::connect: Cannot connect (null)::numI2PConnectionsChanged(int) to BitcoinGUI::setNumI2PConnections(int) dumpaddr thread stop msghand thread interrupt net thread interrupt
that does not look surprising and may not give a hint - but there is also another log "db.log" that could give a hint: Unacceptable log file C:\Users\<username>\AppData\Roaming\NavCoin2\database\log.0000000059: unsupported log version 17 Invalid log file: log.0000000059: Invalid argument PANIC: Invalid argument process-private: unable to find environment process-private: unable to find environment
is it possible that the upgrade from v3.7 to v3.9 uses a different data structure somewhere?
|
|
|
... I still have the same issue - v3.7 works seemless and v3.9 does not connect here is the latest debug log tail: init message: Laden abgeschlossen GUI: QObject::connect: No such signal ClientModel::showProgress(QString,int) GUI: QObject::connect: (receiver name: 'navcoin') GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int) GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64) GUI: QObject::connect: (receiver name: 'SendCoinsDialog') No valid UPnP IGDs found upnp thread exit Loading addresses from DNS seeds (could take a while) keypool reserve 10 keypool return 10
at this point the NAVcoin-qt client hangs with a steady process load of 12%. If I exit the client it does not stop but becomes non interactive and hangs with 12% process load. I can kill it then with the task manager. Starting v3.7 with the absolute same configuration connects immediately. Environment is Win10. If somebody has a explanation that leads to solve the problem I will tip 10 NAV Is active UPnP on your router? Must be activated no idea - but v3.7 works seamless and the v3.7 log shows the same entry If somebody has a better explanation that leads to solve the problem I will tip 20 NAV now
|
|
|
just updated to 3.9 (from 3.7). Now the wallet does not connect or sync anymore.
What do I have to do?
switched back to the old version until the issue is solved here is the tail of the latest debug log: ... Verifying last 500 blocks at level 1 block index 22743ms init message: Lade Wallet... nFileVersion = 3090000 Keys: 0 plaintext, 211 encrypted, 211 w/ metadata, 211 total wallet 95ms init message: Lade Adressen... ERROR: CAddrman::Read() : I/O error or stream data corrupted Invalid or missing peers.dat; recreating Loaded 32 addresses from peers.dat 28ms fLiteMode 0 nTesseractXDepth 5 Anonsend rounds 2 Anonymize NavCoin Amount 1000 mapBlockIndex.size() = 739997 nBestHeight = 696389 setKeyPool.size() = 100 mapWallet.size() = 2336 mapAddressBook.size() = 5 AddLocal(191.168.0.205:44440,1) dnsseed thread start upnp thread start net thread start addcon thread start opencon thread start msghand thread start dumpaddr thread start init message: Laden abgeschlossen GUI: QObject::connect: No such signal ClientModel::showProgress(QString,int) GUI: QObject::connect: (receiver name: 'navcoin') GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int) GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64) GUI: QObject::connect: (receiver name: 'SendCoinsDialog') No valid UPnP IGDs found upnp thread exit Loading addresses from DNS seeds (could take a while)
it runs quite a while now any ideas? if I switch back to 3.7 everything works fine I still have the same issue - v3.7 works seemless and v3.9 does not connect here is the latest debug log tail: init message: Laden abgeschlossen GUI: QObject::connect: No such signal ClientModel::showProgress(QString,int) GUI: QObject::connect: (receiver name: 'navcoin') GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int) GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64) GUI: QObject::connect: (receiver name: 'SendCoinsDialog') No valid UPnP IGDs found upnp thread exit Loading addresses from DNS seeds (could take a while) keypool reserve 10 keypool return 10
at this point the NAVcoin-qt client hangs with a steady process load of 12%. If I exit the client it does not stop but becomes non interactive and hangs with 12% process load. I can kill it then with the task manager. Starting v3.7 with the absolute same configuration connects immediately. Environment is Win10. If somebody has a explanation that leads to solve the problem I will tip 10 NAV
|
|
|
könnt ihr das nicht in einem extra Thread diskutieren, wirkt sich ja nicht wirklich auf den Kurs aus. Danke
bbands im 30 minuten chart verengen sich bald passiert was... jup - man wird keine Tx mehr durchkriegen, weil die Network Congestion so hoch ist, dass einfach alles steht. Und dann geht's bergab
|
|
|
just updated to 3.9 (from 3.7). Now the wallet does not connect or sync anymore.
What do I have to do?
switched back to the old version until the issue is solved here is the tail of the latest debug log: ... Verifying last 500 blocks at level 1 block index 22743ms init message: Lade Wallet... nFileVersion = 3090000 Keys: 0 plaintext, 211 encrypted, 211 w/ metadata, 211 total wallet 95ms init message: Lade Adressen... ERROR: CAddrman::Read() : I/O error or stream data corrupted Invalid or missing peers.dat; recreating Loaded 32 addresses from peers.dat 28ms fLiteMode 0 nTesseractXDepth 5 Anonsend rounds 2 Anonymize NavCoin Amount 1000 mapBlockIndex.size() = 739997 nBestHeight = 696389 setKeyPool.size() = 100 mapWallet.size() = 2336 mapAddressBook.size() = 5 AddLocal(191.168.0.205:44440,1) dnsseed thread start upnp thread start net thread start addcon thread start opencon thread start msghand thread start dumpaddr thread start init message: Laden abgeschlossen GUI: QObject::connect: No such signal ClientModel::showProgress(QString,int) GUI: QObject::connect: (receiver name: 'navcoin') GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int) GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64) GUI: QObject::connect: (receiver name: 'SendCoinsDialog') No valid UPnP IGDs found upnp thread exit Loading addresses from DNS seeds (could take a while)
it runs quite a while now any ideas? if I switch back to 3.7 everything works fine
|
|
|
just updated to 3.9 (from 3.7). Now the wallet does not connect or sync anymore.
What do I have to do?
switched back to the old version until the issue is solved
|
|
|
just updated to 3.9 (from 3.7). Now the wallet does not connect or sync anymore.
What do I have to do?
|
|
|
...
there seems to be a bug in the Windows wallet. If the wallet is unlocked for staking only it does not allow the creation of new transactions. To create a new transaction the wallet must be locked and then completely unlocked again - then it is possible
I don't consider that a bug. It is a safety feature that stops your coins from being stolen while you are asleep staking. I feel very safe knowing that no-one, not even myself, can send my coins without entering the passcode while the wallet is unlocked for staking only. I would agree if it would be required to enter the passphrase again to create a transaction. But it is necessary first to lock and then to unlock the whole wallet. That cannot be intentional. Its clearly a bug (even a minor one)
|
|
|
Hey guys updated my wallet to 3.7 and sent some coins to Bittrex few hours ago, still shows unconfirmed in wallet and not showing in Bittrex. Anything wrong with with wallet currently or is this amount of time normal?
Make sure you can find the tx id in the Blockchain: https://chainz.cryptoid.info/nav/If you see it: Contact Bittrex. If you don't see it: Check the block # in :https://chainz.cryptoid.info/nav/ and compare with your wallet in: ''Help'' "Debug'' in the QT wallet. If you are in the right blockchain: back up wallet.dat and reinstall wallet + nodes + blockchain. Follow the guides in previous posts. Good Luck! Remember to back up : wallet.dat Ive always had problems sending since 3.5.0 if I have been staking it won't send? Fix for me is to exit Navcoin app and restart it after say 30 seconds and then it sends fine for some reason. (both pc and OS X versions do the same) there seems to be a bug in the Windows wallet. If the wallet is unlocked for staking only it does not allow the creation of new transactions. To create a new transaction the wallet must be locked and then completely unlocked again - then it is possible
|
|
|
is there a way to use wildcards with the SIA renter? I have uploaded some files with foreign characters in the filename and cannot delete them anymore
I have asked the devs on Slack, let's wait for their answer... Can't you just copy the filename from the file-list and insert it into the command? I tried it (and a lot of other work arounds) and was not successful An answer from the devs: It is not (yet) possible to use wildcards in the CLI but it should be possible to select and delete the files in the UI. In the UI it is also possible to select a range of files with Shift+Click. if I try it I get a "Sia-UI Files Error - no file known with that path" maybe I just let the files where they are and ignore them (in hope that * and ? wildcards will be available sometime) @betaboot thank you for the effort For future reference, what foreign characters are a problem? Can they be reproduced here? yes sure - the charcter are these: ä ü ö you may find them here: https://www.lsa.umich.edu/german/hmr/schreiben/umlaute/umlaute_ASCII_html.html
|
|
|
is there a way to use wildcards with the SIA renter? I have uploaded some files with foreign characters in the filename and cannot delete them anymore
I have asked the devs on Slack, let's wait for their answer... Can't you just copy the filename from the file-list and insert it into the command? I tried it (and a lot of other work arounds) and was not successful An answer from the devs: It is not (yet) possible to use wildcards in the CLI but it should be possible to select and delete the files in the UI. In the UI it is also possible to select a range of files with Shift+Click. if I try it I get a "Sia-UI Files Error - no file known with that path" maybe I just let the files where they are and ignore them (in hope that * and ? wildcards will be available sometime) @betaboot thank you for the effort
|
|
|
is there a way to use wildcards with the SIA renter? I have uploaded some files with foreign characters in the filename and cannot delete them anymore
I have asked the devs on Slack, let's wait for their answer... Can't you just copy the filename from the file-list and insert it into the command? I tried it (and a lot of other work arounds) and was not successful
|
|
|
is there a way to use wildcards with the SIA renter? I have uploaded some files with foreign characters in the filename and cannot delete them anymore
still have that problem - suggestions?
|
|
|
is there a way to use wildcards with the SIA renter? I have uploaded some files with foreign characters in the filename and cannot delete them anymore
|
|
|
After reading about all the f*kcing scams I must say that cash and also personal contacts with money exchange are always risky and can turn in a problem that nobody wants to experience. One I have been robbed of my coins myself after someone put some kind of KO drug into my beer. That was an expensive lesson. I was lucky that the loss of money was the only implication to my life. I would highly recommend to prefer Bitsquare.io for small trades. That market is probably the most safe and anonymous market available. Scams are basically not possible. You never need to meet someone in person. If you like to meet people in person for trading then choose a secure place with video surveillance like a bank or a shopping mall in a secure area. The bank may also be useful for the seller because they can check the validity of the notes. Trade only little amounts like $100 which nearly anybody could have in his purse. But always remember that there were people who have been killed for $2. Money attracts all kind of shady guys who want to trick it out of your pocket. Eg. in another contact over MC-localtrader somebody dared to ask me if I can borrow him BTC for one month Another one wanted to sell 125 BTC when the price was around 200€ (makes 25.000€) in one transaction without identifying himself and where the coins came from. I could tell more funny stories like that. Why take a risk if it can be done from home with Bitsquare without ever meeting alien people.
|
|
|
|