Bitcoin Forum
May 21, 2019, 04:00:03 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 [363] 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 ... 2567 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2750636 times)
LiveFree
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
December 25, 2013, 12:26:28 AM
 #7241

No more block after 24184?
1558411203
Hero Member
*
Offline Offline

Posts: 1558411203

View Profile Personal Message (Offline)

Ignore
1558411203
Reply with quote  #2

1558411203
Report to moderator
1558411203
Hero Member
*
Offline Offline

Posts: 1558411203

View Profile Personal Message (Offline)

Ignore
1558411203
Reply with quote  #2

1558411203
Report to moderator
1558411203
Hero Member
*
Offline Offline

Posts: 1558411203

View Profile Personal Message (Offline)

Ignore
1558411203
Reply with quote  #2

1558411203
Report to moderator
Get alert of price pumps/dumps beforehand 74% average Win Rate
reported by our users
TRY NOW!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558411203
Hero Member
*
Offline Offline

Posts: 1558411203

View Profile Personal Message (Offline)

Ignore
1558411203
Reply with quote  #2

1558411203
Report to moderator
LiveFree
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
December 25, 2013, 12:29:06 AM
 #7242

Why u no speak englis?
I try but english is not easy language.
laowai80
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
December 25, 2013, 12:29:25 AM
 #7243

Hopefully the blockchain can be rolled back to those .bak files.
Let's wait for CfB to wake up Smiley
afia
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
December 25, 2013, 12:29:41 AM
 #7244

to CfB

plz post check summ when u update client. thx
Damelon
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001



View Profile
December 25, 2013, 12:33:26 AM
 #7245

Do I need to get my "The End is Nigh" pamphlets out of the attic or can I just keep sitting and stuffing my face?  Wink

Member of the Nxt Foundation | Donations: NXT-D6K7-MLY6-98FM-FLL5T
Join Nxt Slack! https://nxtchat.herokuapp.com/
Founder of Blockchain Workspace | Personal Site & Blog
mcjavar
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
December 25, 2013, 12:35:16 AM
 #7246

Do I need to get my "The End is Nigh" pamphlets out of the attic or can I just keep sitting and stuffing my face?  Wink

I don´t think so.
TwinWinNerD
Legendary
*
Offline Offline

Activity: 1680
Merit: 1001


CEO Bitpanda.com


View Profile WWW
December 25, 2013, 12:37:15 AM
 #7247

basically, the chain can be rolled back 720 block if i remember correctly, so if we all agree to reload files from that date, we can roll everything back.

BUT if DfB is asleep for that long, we might be fucked, right?

PaulyC
Member
**
Offline Offline

Activity: 77
Merit: 10


View Profile
December 25, 2013, 12:38:12 AM
Last edit: December 25, 2013, 01:01:05 AM by PaulyC
 #7248

I hate to keep bringing this up, but everytime I get the answer, oh you musta been on a forked chain, etc..

!! but someone really needs to address how added features are susceptible to attacks, leading one to get confirmations of a transaction on a fork (orphaned) block, that may not actually exist..

Meaning. One could potentially pay for an added feature, asset or an alias (as It happened to me) pay a fee, get confirmations, timestamp, and transaction ID, then find out a few hours later your transaction was on an forked chain. And that asset, feature, or alias is now "owned" by someone else, who very likely paid for it after you, but because their client was on the "right" chain.. they lucked out.
 
I believe my fee was returned, still.. These features are very interesting, but in a system with confirmations and blocks it needs to be much much tighter. Personally I think aliases or added features, assets, should go by timestamp, and not value size and only confirmations, etc. It just opens the door for questionable tactics.
What happens when it’s not just a single 1 NXT alias.. something bigger and more valuable?

So are the value of features to the forger, affected by orphaned blocks? I guess is my essential question. Cuz that seems problematic.

.

.

Doge Mars Landing Foundation
(founder)


Check that HASH!
NXT:  14008664550450326382
laowai80
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
December 25, 2013, 12:38:20 AM
 #7249

Do I need to get my "The End is Nigh" pamphlets out of the attic or can I just keep sitting and stuffing my face?  Wink

It's always a good idea to see things in phylosophical light, rise or fall. I guess the blockchain can be rolled back. Don't buy any NXTs now if someone will offer them at 90% discount Smiley
EvilDave
Hero Member
*****
Offline Offline

Activity: 854
Merit: 1000



View Profile
December 25, 2013, 12:38:26 AM
 #7250

Think the Apocalypse might be a little bit later...

I'm on:

24186      4747512364439223888      woensdag 25 december 2013 1:28:56   
      
      0      0 + 0      0 B   
      
      1      5311201058894520581      112 %


and only 140 confirmations away from the 1440  Grin

Nulli Dei, nulli Reges, solum NXT
Love your money: www.nxt.org  www.ardorplatform.org
www.nxter.org  www.nxtfoundation.org
xibeijan
Legendary
*
Offline Offline

Activity: 1190
Merit: 1000


View Profile
December 25, 2013, 12:38:29 AM
 #7251

basically, the chain can be rolled back 720 block if i remember correctly, so if we all agree to reload files from that date, we can roll everything back.

BUT if DfB is asleep for that long, we might be fucked, right?

Sounds good.

Notable projects 2019: Semux, Dero, Wagerr
laowai80
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
December 25, 2013, 12:39:00 AM
 #7252

basically, the chain can be rolled back 720 block if i remember correctly, so if we all agree to reload files from that date, we can roll everything back.

BUT if DfB is asleep for that long, we might be fucked, right?

There are .bak files from about an hour ago, before it all happened.
gbeirn
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
December 25, 2013, 12:40:56 AM
 #7253

Since CfB already slept, can laowai or any other with technical knowledge answer me this question.

I am connected to the network using my local computer without hallmark. I don't care about forging benefit but I would like to support the network as much as I can. Does my computer help the network ? or does it just cause more stresses to some of your hallmarked nodes ?
If my node does not help the network, I would like to close my computer now so I can concentrate on some writing for alias system and asset exchange.

I am not exactly sure, but I think writing for the alias system and asset exchange are much more useful right now Smiley

Local computer helps the network only minimally as far as I can deduce, maybe even hurting at the time of DDOS, which is going on right now and it's big.

Yes I think we came to the conclusion last night that un hallmarked nodes are going to put more strain on the network during a DDoS attack. That said if you can hallmark a node, great, if you can't still feel free to setup an un-hallmarked one....this is your network too!

NXT VPS Server Donations can be sent here: 6044921191674841550
At the end of each month I will donate some of them back to the community.
This is separate from my main wallet so you can keep track of them. I will keep them in there and only use them for hosting.
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
December 25, 2013, 12:41:21 AM
 #7254

Yes, looks like somebody found an integer overflow bug. Account.balance is long, but Transaction.amount and Transaction.fee are integers. My guess is that somewhere in the transaction validation code those are subtracted in a way that gives a value < Integer.MIN_VALUE, which overflows and becomes a positive. So a transaction with fee exceeding the account balance is wrongly considered valid. Or something along those lines.

Anyway, the result is that the blockchain after the corrupted block is invalid, but the current client code does not know that. Once the bug is fixed, and the blockchain rescanned, it should reject the block with the invalid transaction and start a new fork. Hopefully BCNext and CfB can provide a fix soon. In the meantime, I would advise everybody not to do any transactions - because they will all be recorded in a chain that is going to be orphaned after the fix.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
Damelon
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001



View Profile
December 25, 2013, 12:42:57 AM
 #7255

I´ll get the drinks in, then  Cheesy

Member of the Nxt Foundation | Donations: NXT-D6K7-MLY6-98FM-FLL5T
Join Nxt Slack! https://nxtchat.herokuapp.com/
Founder of Blockchain Workspace | Personal Site & Blog
afia
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
December 25, 2013, 12:43:19 AM
 #7256

mastercoin appeared in coinmarketcap on 3d place ^^
xibeijan
Legendary
*
Offline Offline

Activity: 1190
Merit: 1000


View Profile
December 25, 2013, 12:45:47 AM
 #7257

lol...

Notable projects 2019: Semux, Dero, Wagerr
xibeijan
Legendary
*
Offline Offline

Activity: 1190
Merit: 1000


View Profile
December 25, 2013, 12:47:38 AM
 #7258

Yes, looks like somebody found an integer overflow bug. Account.balance is long, but Transaction.amount and Transaction.fee are integers. My guess is that somewhere in the transaction validation code those are subtracted in a way that gives a value < Integer.MIN_VALUE, which overflows and becomes a positive. So a transaction with fee exceeding the account balance is wrongly considered valid. Or something along those lines.

Anyway, the result is that the blockchain after the corrupted block is invalid, but the current client code does not know that. Once the bug is fixed, and the blockchain rescanned, it should reject the block with the invalid transaction and start a new fork. Hopefully BCNext and CfB can provide a fix soon. In the meantime, I would advise everybody not to do any transactions - because they will all be recorded in a chain that is going to be orphaned after the fix.


Yeah, such is the growing pains of a completely new code base.  They did say it was alpha.  I am going to bed.

Notable projects 2019: Semux, Dero, Wagerr
gbeirn
Full Member
***
Offline Offline

Activity: 126
Merit: 100


View Profile
December 25, 2013, 12:47:46 AM
 #7259

What is the appropriate amount of Nxt to keep in a digitalocean 2GB hallmarked account?

I use 100NXT, but the more the more weight the node has, and under DDoS attack, the more likely it will be targeted.

NXT VPS Server Donations can be sent here: 6044921191674841550
At the end of each month I will donate some of them back to the community.
This is separate from my main wallet so you can keep track of them. I will keep them in there and only use them for hosting.
laowai80
Member
**
Offline Offline

Activity: 98
Merit: 10


View Profile
December 25, 2013, 12:49:34 AM
 #7260

Yes, looks like somebody found an integer overflow bug. Account.balance is long, but Transaction.amount and Transaction.fee are integers. My guess is that somewhere in the transaction validation code those are subtracted in a way that gives a value < Integer.MIN_VALUE, which overflows and becomes a positive. So a transaction with fee exceeding the account balance is wrongly considered valid. Or something along those lines.

Anyway, the result is that the blockchain after the corrupted block is invalid, but the current client code does not know that. Once the bug is fixed, and the blockchain rescanned, it should reject the block with the invalid transaction and start a new fork. Hopefully BCNext and CfB can provide a fix soon. In the meantime, I would advise everybody not to do any transactions - because they will all be recorded in a chain that is going to be orphaned after the fix.


Yeah, such is the growing pains of a completely new code base.  They did say it was alpha.  I am going to bed.

Yeah, we're all alpha testers.

Then we get to be beta testers.

Then we all become early adopters Smiley
Pages: « 1 ... 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 [363] 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 ... 2567 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!