Bitcoin Forum
June 23, 2024, 06:51:02 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 [268] 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 ... 1241 »
  Print  
Author Topic: ★[ANN] [NAV] NAV COIN - Community Fund Live!!!  (Read 2085730 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
svider
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile
November 21, 2014, 08:29:12 PM
 #5341

my wallet also does not generate new coins
gregofdoom
Legendary
*
Offline Offline

Activity: 1834
Merit: 1006



View Profile
November 21, 2014, 08:31:13 PM
 #5342

ANON is approaching and this is probably why.   Wink
hashforce101
Legendary
*
Offline Offline

Activity: 1050
Merit: 1000


View Profile
November 22, 2014, 05:03:49 AM
 #5343

gregofdoom
Legendary
*
Offline Offline

Activity: 1834
Merit: 1006



View Profile
November 22, 2014, 08:49:19 AM
 #5344

Nice color, but I like the beige  Wink
bspus
Legendary
*
Offline Offline

Activity: 2165
Merit: 1002



View Profile
November 22, 2014, 09:15:27 AM
 #5345

ANON is approaching and this is probably why.   Wink

You haven't been messing with your system time again, right? Just making sure Tongue

Seriously, this is getting frustrating. A hard fork to fix this is urgently needed.

gorian
Sr. Member
****
Offline Offline

Activity: 336
Merit: 250


View Profile
November 22, 2014, 09:45:25 AM
 #5346

ANON is approaching and this is probably why.   Wink

You haven't been messing with your system time again, right? Just making sure Tongue

Seriously, this is getting frustrating. A hard fork to fix this is urgently needed.

Unless and I am shitty my!
This must be corrected immediately and permanently!
Ginger Ninja
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


They walk among us...


View Profile
November 22, 2014, 10:23:25 AM
 #5347

Staking has stopped for me too  Sad
Remy_5
Hero Member
*****
Offline Offline

Activity: 1194
Merit: 502


View Profile
November 22, 2014, 11:37:26 AM
 #5348


You haven't been messing with your system time again, right? Just making sure Tongue

Seriously, this is getting frustrating. A hard fork to fix this is urgently needed.

Another way of looking at the situation is that we can now say with absolute certainty
and without fear of contradiction, that the Navajo Coin is so directed toward the stars
and projected for the future, that at this very moment is already gone in the tomorrow.

I will not take off work to hashforce101, it's just a (sad but true) joke.  Embarrassed

Who knows, maybe repeat the warning to check the system clock in other languages
harder to comprise, for example, Mandarin Chinese, could help.
silvapaso85
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile
November 22, 2014, 11:38:23 AM
 #5349

Staking has stopped for me too  Sad

+1
The same problem. Any info?
bspus
Legendary
*
Offline Offline

Activity: 2165
Merit: 1002



View Profile
November 22, 2014, 11:52:59 AM
 #5350


I will not take off work to hashforce101, it's just a (sad but true) joke.  Embarrassed

Who knows, maybe repeat the warning to check the system clock in other languages
harder to comprise, for example, Mandarin Chinese, could help.


I'm having a hard time understanding what you are trying to say, especially about hashforce.

But giving a warning is not enough and could actually even make things worse if people decide to actively exploit this.

What I'm most worried about is that double spending could happen very easily if all the staking is concentrated to a few people. After all some people are staking like crazy right now. Blocks keep coming.
There will be no coming back from a second double spend attack.

I admit I am not a (professional) programmer and I have never looked at the source code. But I imagine that a straightforward solution would be for the nodes to negotiate a concensus for the actual date-time  by querying a known ntp server. So even if a rogue client tries to exploit their own local system time, the stake would not be accepted.

Does that make sense as a fix and if so, how hard and (time consuming) is it to implement?

SUM2dev (OP)
Sr. Member
****
Offline Offline

Activity: 356
Merit: 251


Official account of NAV Development Team


View Profile
November 22, 2014, 12:22:41 PM
 #5351

Hello Everyone!
We are aware of the stake issue and we are in process of investigation to integrate a solution to the next wallet update Smiley
We apologize for the trouble.
Be sure that we are working on sorting this out and it is our highest priority right now Wink
Thank You for support & stay tuned!
Cheers

- Navajo Coin Development Team

Official account of NAV Coin [NAV] Development TeamVisit the Thread!
Remy_5
Hero Member
*****
Offline Offline

Activity: 1194
Merit: 502


View Profile
November 22, 2014, 01:03:42 PM
 #5352


I will not take off work to hashforce101, it's just a (sad but true) joke.  Embarrassed

Who knows, maybe repeat the warning to check the system clock in other languages
harder to comprise, for example, Mandarin Chinese, could help.


I'm having a hard time understanding what you are trying to say, especially about hashforce.

But giving a warning is not enough and could actually even make things worse if people decide to actively exploit this.



I am always too cryptic, sorry.

I was referring to hashforce101 only for its constant commitment to NavajoCoin propaganda,
and in the way he still find the bright side of everything.

Do not really want to offend anyone, I want to be clear on this.

Regarding the technical side, there are always many ways of doing things, each with its
pros and cons, and often even the best ideas can hide potential pitfalls.

So IMHO, any intervention requires a acute analysis of the DevTeam, to properly evaluate the effects
possible in every scenario.

Personally I would not want it to be made a modification too botched, forced by the urgency,
which can create more damage than it solves, as sometimes I've seen in other currencies,
but this is just my opinion.

For the rest, I basically agree with you.

It seems to me that from the block 663085 there are only four addresses, it is probably a single (heavy) user.

Bye Bye
hashforce101
Legendary
*
Offline Offline

Activity: 1050
Merit: 1000


View Profile
November 22, 2014, 01:20:14 PM
 #5353

I have turned my wallet off until the new sun! Good Night
Ginger Ninja
Sr. Member
****
Offline Offline

Activity: 373
Merit: 250


They walk among us...


View Profile
November 22, 2014, 02:06:51 PM
 #5354

Hello Everyone!
We are aware of the stake issue and we are in process of investigation to integrate a solution to the next wallet update Smiley
We apologize for the trouble.
Be sure that we are working on sorting this out and it is our highest priority right now Wink
Thank You for support & stay tuned!
Cheers

- Navajo Coin Development Team


Thanks for the update! Much appreciated  Smiley
tokyopotato
Legendary
*
Offline Offline

Activity: 812
Merit: 1000


View Profile
November 22, 2014, 09:17:00 PM
 #5355

I'm following this out of curiosity.

Blocks are being generated: http://navajocoin.org/block-explorer

The question is did a fork somehow occur and are there now two or multiple separate chains.  In theory, everyone should get back on the longest chain...  
Remy_5
Hero Member
*****
Offline Offline

Activity: 1194
Merit: 502


View Profile
November 22, 2014, 11:05:43 PM
 #5356


The question is did a fork somehow occur and are there now two or multiple separate chains.  In theory, everyone should get back on the longest chain...  


There is a command of the wallet, who writes in debug.log a representation of the entire tree of blockindex,
with all blocks which have been registered in the database of the wallet, including orphans blocks and incomplete chains.

After a long wait, the result is a huge mass of shapeless text, in this case about 100MB, difficult to manage.

Now to answer your question, with all the necessary precautions, as far as I can understand, from the block  662 984
which is prior to the current problem, until the block 665 908, they form a single chain.

At least we have one good news.

Bye Bye
IMJim
Legendary
*
Offline Offline

Activity: 1260
Merit: 1000


View Profile
November 22, 2014, 11:17:45 PM
 #5357

Should we close our wallets until this is resolved?
hashforce101
Legendary
*
Offline Offline

Activity: 1050
Merit: 1000


View Profile
November 22, 2014, 11:21:08 PM
Last edit: November 22, 2014, 11:36:19 PM by hashforce101
 #5358

I am buying more NAV / BTC on Tuesday as part of my Navember Target goal. Also should I not move any NAV from exchanges to my wallet at this current time.

I need the full story on how I should handle trading until new wallet please.  Smiley

In the mean time I am keeping my wallet off.

I am fully confident that the new wallet is going to be awesome
hashforce101
Legendary
*
Offline Offline

Activity: 1050
Merit: 1000


View Profile
November 22, 2014, 11:21:30 PM
 #5359

Should we close our wallets until this is resolved?

Perfect question!
Remy_5
Hero Member
*****
Offline Offline

Activity: 1194
Merit: 502


View Profile
November 22, 2014, 11:35:56 PM
Last edit: November 22, 2014, 11:52:39 PM by Remy_5
 #5360

Should we close our wallets until this is resolved?

Perfect question!

+1  Embarrassed

Personally I think to leave the wallet open, at least I can follow the events.

And then we can always hope for a small blackout very localized. Wink


Bye Bye
Pages: « 1 ... 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 [268] 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 ... 1241 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!