Topic: NXT :: descendant of Bitcoin - Updated Information - page 1909. (Read 2761645 times)
Why is everyone selling?
something wrong with the new nxt client 0.4.8
i 'm trying send money from my old account to the new one
i click send ...the client respond "wrong paraphrase" ....no where to fill the pass
i 'm trying send money from my old account to the new one
i click send ...the client respond "wrong paraphrase" ....no where to fill the pass
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!
I remember you were desparate to sell 5 days ago too, is that a way of life?
I have my long term holdings and even short term ones. But from time to time I do this and generously pay for my convenience. This is why I am selling at 0.00008BTC. that is 0.000012 GUARENTEED profit in a couple of minutes...
But no one is taking advantage.. kinda sad....
I am also offering hundreds of BTC for sale with 5% discount and I am pretty much amazed they are still there... eventually I canceled he sale...
dgex is under ddos?very slowly load page
price will go to da moon, buy from me already! it is 0.00008 each!
dgex is under ddos?very slowly load page
price will go to da moon, buy from me already! it is 0.00008 each!
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!I remember you were desparate to sell 5 days ago too, is that a way of life?
dgex is under ddos?very slowly load page
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! Based on which API documentation?
getAccountPublicKeyWhich 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
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 AuthorizationTokenadding a specific alias would be one way.
how do I do that?
Based on which API documentation?
getAccountPublicKeyWhich 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.
Based on which API documentation?
getAccountPublicKey
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?
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.
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 adding a specific alias would be one way.
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.
adding a specific alias would be one way.
@CfB and others
How to use the feature of transparent forging?
I dont find different display or things with 30000 block before.
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?
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://bitcointalksearch.org/topic/m.4256929
@CfB and others
How to use the feature of transparent forging?
I dont find different display or things with 30000 block before.
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.
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?
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.
Hey, EpicThomas, I like superheroes too. Mine are old-school noir detectives that always get their man.
http://www.hardcasecrime.com/
http://www.hardcasecrime.com/
Jump to: