NXT :: descendant of Bitcoin - Updated Information

[ZeroTheGreat]

We need clear reason (well, investigation can wait) and solution. Maybe somehow set ability to send only 1 NXT to empty acc and only then allow to send more (sender can recheck data)? It doesn't look so hard to implement for me.

Ofc, better if there'll be almost guarantied way to send coins exacty to typed address.

[1714934377]

1714934377

[1714934377]

1714934377

[1714934377]

1714934377

[1714934377]

1714934377

[Come-from-Beyond]

CfB + jean-luc + nexern,

There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.

The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?

This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?

James

P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.

I hope nexern will fix this issue on client side.

[ZeroTheGreat]

It was found?

[landomata]

WE NEED IPHONE APP TESTERS....PLS CHECK OUT THE BELOW LINK:


https://nextcoin.org/index.php/topic,1505.msg21703.html#msg21703

[Voodah]

Oh wow my Nxt investment is off to a horrible start.

Lost 15% in one day and then some more thanks to the sneak in the back fee from dgex.  

EDIT: What happened with the code release? why did the price tank?

[chanc3r]

WE NEED IPHONE APP TESTERS....PLS CHECK OUT THE BELOW LINK:


https://nextcoin.org/index.php/topic,1505.msg21703.html#msg21703

already had it on my phone 2 days and providing feedback 

[landomata]

WE NEED IPHONE APP TESTERS....PLS CHECK OUT THE BELOW LINK:


https://nextcoin.org/index.php/topic,1505.msg21703.html#msg21703

already had it on my phone 2 days and providing feedback 

   keep em coming

[mr_random]

Questions for DGEX operator

1. Regarding the 800,00 NXT you need to cover. You seem to blame the NXT code yet you posted earlier today that you was also hacked? How much of the 800,000 NXT was lost in the hack and how much was lost due to the software error? And how much of that NXT is due to your own coding errors?

My opinion is if you are out of pocket that much due to NXT software errors or blockchain faults then I can understand somewhat. However server hacks and your own coding errors are your own responsibility.

2. Is the withdrawal fee for new deposits only, or does it include existing deposits? If it covers existing deposits that is quite frankly taking the piss. You can't take people's money and then say ok I'm now charging you to get it back. At least give people notice to withdraw their funds out first - I certainly saw no notice on the site.

[opticalcarrier]

CfB + jean-luc + nexern,

There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.

The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?

This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?

James

P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.

i like the idea of a warning and a chance to cancel rather than not allow

[mr_random]

Does anyone have concrete examples of the problems Graviton is referring to that cause him to lose so much money?

If these problems exist we need to fix them as high priority please. No good or reliable services will appear until it is sorted.  

[pinarello]

WE NEED IPHONE APP TESTERS....PLS CHECK OUT THE BELOW LINK:


https://nextcoin.org/index.php/topic,1505.msg21703.html#msg21703

Volunteered ayay

Pin

[visaco]

did someone finished reading the source code ......?
conclusion?

[laowai80]

When coins are sent to a wrong account, there is no way to prove it was not a human error, I guess.

[nexern]

CfB + jean-luc + nexern,

There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.

The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?

This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?

James

P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.

I hope nexern will fix this issue on client side.

already wrote about this two weeks ago.
the client wil handle it this way:

1. check if address is within own address book  -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red

simple visual control.

[pinarello]

CfB + jean-luc + nexern,

There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.

The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?

This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?

James

P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.

I think we really do understand you loud and clear...

just as I understand the answer that this should can and (can be) resolved with a client.

so we depend on a CLIENT who and when will this be delivered and will it solve this problem?

Pin

[elbill]

https://bitbucket.org/JeanLucPicard/nxt-public

1 file. OMG!

I am not a developer, but I would say that´s not the best program design... isn´t it?

Less than a month working a few, in my opinion very far from being a 2nd generation  

[ZeroTheGreat]

already wrote about this two weeks ago.
the client wil handle it this way:

1. check if address is within own address book  -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red

simple visual control.

Thx. But what about after clicking "Send"? As I recall wrong sends happened after correct address was set.

[jl777]

already wrote about this two weeks ago.
the client wil handle it this way:

1. check if address is within own address book  -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red

simple visual control.

Thx. But what about after clicking "Send"? As I recall wrong sends happened after correct address was set.

This is why I addressed my request to jean-luc also. We need to PREVENT darkNXT for all except the most motivated API users. darkNXT has no real world benefit as far as I can think of, in fact it could attract NXT miners who will look at 64 bits and their petahash ASICS and start drooling when NXT gets to $1

James

[landomata]

already wrote about this two weeks ago.
the client wil handle it this way:

1. check if address is within own address book  -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red

simple visual control.

This is a big step forward....Nexern we love you

[Come-from-Beyond]

It was found?

No. I mean that client soft should show warning if a user attempts to send money to an empty account.