Do not forget to support the Thunderclap:
https://www.thunderclap.it/projects/47929-navcoin-powered-by-the-people
Topic: ★[ANN] [NAV] NAV COIN - Community Fund Live!!! - page 248. (Read 2085654 times)
Do not forget to support the Thunderclap:
https://www.thunderclap.it/projects/47929-navcoin-powered-by-the-people
It seems, anonymity again becomes an important part of our lives - Nav - Xmr - Sdc. An interesting trend....
Congrats to the team and the community as a whole on hitting page 1000 as well as the incredible achievements that are being made in the background.
Huge props to Soopy, Package and co for all your hard work over the years. Really paying off.
Huge props to Soopy, Package and co for all your hard work over the years. Really paying off.
A 5th transaction and same issue. 
But 4 transactions in a row? Between the 1st two was about 11 hour gap. Then about a 12 hour gap between 2nd and 3rd. Then a 5 minute gap between 3rd and 4th.
Do you have checked if the system time of your computer is currently on the accurate time?
Great to see Remy_5 back . Hello from Viking
A 5th transaction and same issue.
But 4 transactions in a row? Between the 1st two was about 11 hour gap. Then about a 12 hour gap between 2nd and 3rd. Then a 5 minute gap between 3rd and 4th.
Do you have checked if the system time of your computer is currently on the accurate time?
OMG I miss page number 1000 ? I hope not.
Yeah I am on the page 1000 !!!! Wow its huge. But Nav is fine too
? I hope not.Yeah I am on the page 1000 !!!! Wow its huge. But Nav is fine too
When will anon send be released?
The beta is underway now. If you want to get involved then message me your email and I will add you to our slack channel.We are aiming to have the public release ready for when the Thunderclap campaign ends on 20 Oct.
Is there a command to clean up the orphan blocks from the transaction list?
Better management of the orphan blocks is part of the wallet update we are putting out tomorrow
In regards to the syncing issues, Soopy has put together a wallet which addresses this. I was able to sync 24 hours of transactions in about 30 seconds which is nothing short of amazing. We are in our final stages of testing the new wallet source and hope to have it available for the public as part of tomorrows update.
Fantastic. This is great news
When will anon send be released?
Is there a command to clean up the orphan blocks from the transaction list?
We The NAV Community & Dev Team have today reached a new Milestones of 1000 pages 
WoW Congratulations!
With so much to look forward to and so much happening behind the scenes in Development this prooves NAV COIN can go the distance.
From Sunmercoin to today, NAV
Everything has changed for the better.
This coin has now become World Class
Marketing,Developments and a rock solid Project plan keeps us talking on Bitcointalk.org!
Congratulations every one
WoW Congratulations!With so much to look forward to and so much happening behind the scenes in Development this prooves NAV COIN can go the distance.
From Sunmercoin to today, NAV
Everything has changed for the better.
This coin has now become World Class
Marketing,Developments and a rock solid Project plan keeps us talking on Bitcointalk.org!
Congratulations every one
Bump
Page 1000
Gentlemen, do you think, what can we expect capitalization after starting anon and after decentralization?
On Trex support 184BTC
Gentlemen, do you think, what can we expect capitalization after starting anon and after decentralization?
On Trex support 184BTC
A 5th transaction and same issue.
But 4 transactions in a row? Between the 1st two was about 11 hour gap. Then about a 12 hour gap between 2nd and 3rd. Then a 5 minute gap between 3rd and 4th.
This is normal, it happens when 2 wallets stakes at same moment
Having issues with recent transactions on a staking wallet.
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
This is normal, it happens when 2 wallets stakes at same moment
Having issues with recent transactions on a staking wallet.
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
to resolve conflicted stakes, you can open the debug console and use the command "repairwallet"
Did as you suggested and it returned the following:

{
"wallet check passed" : true
}
waiting new wallet
This is normal, it happens when 2 wallets stakes at same moment
Having issues with recent transactions on a staking wallet.
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
to resolve conflicted stakes, you can open the debug console and use the command "repairwallet"
Did as you suggested and it returned the following:

{
"wallet check passed" : true
}
But 4 transactions in a row? Between the 1st two was about 11 hour gap. Then about a 12 hour gap between 2nd and 3rd. Then a 5 minute gap between 3rd and 4th.
This is normal, it happens when 2 wallets stakes at same moment
Having issues with recent transactions on a staking wallet.
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
Wow page 1000, what a journey.
WOW indeed !!!
An incredible and at the same time incontestable milestone.
Congratulations to DevTeam, Foundation and all supporter.
This is normal, it happens when 2 wallets stakes at same moment
Having issues with recent transactions on a staking wallet.
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
First, I don't have any sync issues. Everything had been working fine with the full node wallet on MAC OS X with 4 to 5 connections. I received 2 transactions on the 2nd day of staking with no issues. Now the last 4 all have had the following status and never get confirmed.
Status: conflicted, broadcast through 3 nodes
Generated but not accepted.
Can someone explain what happened. Is there an issue on my end?
to resolve conflicted stakes, you can open the debug console and use the command "repairwallet"
would be nice to see NAV COIN added to Bitsquare:
https://forum.bitsquare.io/t/how-to-add-your-favorite-altcoin/46
can someone of the core team add it to the list?
https://forum.bitsquare.io/t/how-to-add-your-favorite-altcoin/46
can someone of the core team add it to the list?
Great idea, i am emailing them now
Jump to: