NXT :: descendant of Bitcoin - Updated Information

[NWO]

Yes, everyone. BUY BUY BUY. Open source will put this on parity with BTC! GO GO GO!

[1714828631]

1714828631

[1714828631]

1714828631

[1714828631]

1714828631

[1714828631]

1714828631

[1714828631]

1714828631

[Kaliber1]

Yes, everyone. BUY BUY BUY. Open source will put this on parity with BTC! GO GO GO!

No.

Now the passcode is: Think Think Think.

Because like on Finance Yahoo the analysers said this coin can easily overtake Peercoin, let's imagine that the coin can arrive to $1 in a short time. The real point is BTC, how can we arrive to it?

[matt4054]

I still believe there should be a better way to distribute the money supply.

I have bought a small amount of NXT already (about 3000) but even so, I can't imagine forging more than a few, hopefully, every month.

There should be some clever incentive to bring more coins during a 'land rush' phase of some kind

[CIYAM]

There are ways to make a crypto currency QC proof but not if your public key has been seen.

So my question/concern is why the 2^64 approach rather a hash of the public key like Bitcoin?

[fmiboy]

Hi all,

Today is the big day... history will be made We humans after years think back of this day and how NXT changed the world and its first steps...

I am sure to look through the code and get some bounties, today..

Please donate some 13792774143018875909 if possible!

Thank you very much! Have a great day and brilliant mood

[Meizirkki]

Guys, something weird happened!

Either I screwed up big or maybe it's some bug?

I've sent today 14699 NXT to a customer in response for his withdrawal request, but money went into another account #434692873790144579 (tx 4799337629054063359).

So are there any checks for validity of addresses or can it be absolutely any number?

Anybody owns this account by any chance?

The weird thing is I am very careful and I do copy-paste from the form that my backend shows me. I have no idea where this erroneous number could appear from, because there are no users with such number in my database. There are no passwords, or accounts with that number which I could have accidentally copied. All my passwords and phrases are alphanumeric.

My client is 0.4.8 and has correct hash (I checked after reports today).

So how could this happen???

If it was a mistake, I guess there is no chance to find a key for this account?

Still, I absolutely can't understand, how, during a simple copy-paste, this could have happened...

Framewood and intel (sorry if I am not aware of others) have reported exactly the same thing.   

someone publish a problematic address so others can test for the same behavior?

[S3MKi]

today is a great day!:)

[rickyjames]

Hey, EpicThomas, I like superheroes too.  Mine are old-school noir detectives that always get their man.



http://www.hardcasecrime.com/

[Come-from-Beyond]

CfB,  can you comment on the probability of upcoming DDOS attacks that tracks in on transparent forging to attack whatever node is scheduled to be the next block generator?

How can we best prepare so that we dont have to learn things the hard way like we all did with the first wave?

Noone proved that it's possible to detect IP of a forging node.

[Come-from-Beyond]

@CfB and others
How to use the feature of transparent forging?
I dont find different display or things with 30000 block before.

Someone should support TF in his client.

[Come-from-Beyond]

1) the ability to create an address offline (without the online version ever knowing your password or its hash) so that you can safely have nxt sent to cold storage even if your online computer has a keylogger

This is planned to be implemented after the 1st Shrinking (in ~1 year)

2) the ability to assign the "forging rights" from one address to another so that you don't need to risk being "signed in" with an address that has a huge balance in order to forge

https://bitcointalk.org/index.php?topic=345619.msg4256929#msg4256929

[marcus03]

@CfB and others
How to use the feature of transparent forging?
I dont find different display or things with 30000 block before.

Someone should support TF in his client.

Based on which API documentation?

[kunibopl]

what is the most elegant way to prove, that I have access to a specific account without revealing my passphrase?
adding a specific alias would be one way.

[lr127]

what is the most elegant way to prove, that I have access to a specific account without revealing my passphrase?
adding a specific alias would be one way.

Or generating & verifying the AuthorizationToken

[Come-from-Beyond]

There are ways to make a crypto currency QC proof but not if your public key has been seen.

So my question/concern is why the 2^64 approach rather a hash of the public key like Bitcoin?

If someone creates a QC he will pick a Bitcoin private key even before the very 1st transaction is confirmed. 2^64 vs 2^256 for QC owner is like 2^8 vs 2^16. No difference at all.

Answering ur question:
- 2^64 approach is used on purpose and will be revealed when the time comes.

[Come-from-Beyond]

Based on which API documentation?

getAccountPublicKey

[marcus03]

Based on which API documentation?

getAccountPublicKey

Which returns the PublicKey I assume. I fail to see how using this command can help to implement support for TF in clients.

Let me get my point over: Client developers need an API that is well documented. This includes list of parameters and return values, with types, max. lengths, etc., explanations of what a command does and examples to get things into context.

[kunibopl]

what is the most elegant way to prove, that I have access to a specific account without revealing my passphrase?
adding a specific alias would be one way.

Or generating & verifying the AuthorizationToken

how do I do that?

[Come-from-Beyond]

Based on which API documentation?

getAccountPublicKey

Which returns the PublicKey I assume. I fail to see how using this command can help to implement support for TF in clients.

Let me get my point over: Client developers need an API that is well documented. This includes list of parameters and return values, with types, max. lengths, etc., explanations of what a command does and examples to get things into context.

Sorry, I was busy. Here is an extended explanation:

1. Do http://localhost:7874/nxt?requestType=getState to get value of "lastBlock"
2. Do http://localhost:7874/nxt?requestType=getBlock&block=10621696942372068326 (assuming 10621696942372068326 is the value of "lastBlock")
3. Convert "generationSignature" into binary and append public key bytes returned by getAccountPublicKey
4. Calculate SHA256(generationSignature, publicKey)
5. First 8 bytes as unsigned long in little-endian notation is HIT
6. Value of "baseTarget" multiplied by effective balance of the account is STATIC_TARGET
7. Do steps 3-6 for each account and find the one with lowest HIT/STATIC_TARGET ratio, this account will forge next block

[lophie]

selling 50k NXT for 0.00009 each. Make this quick, I need the coins, you make profit over the arbitrage. PM me NOW

37500NXT are on the table at 0.00008 each the total is 3 BTC! Make this happen before someone else takes it!

Why did you post here . I need the coins in the next 20 minutes, sorry desperate times desperate measures, just profit over my desperate ass and buy them already!