Bitcoin Forum
December 14, 2017, 01:17:35 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 »  All
  Print  
Author Topic: [Nxt] API of Nxt  (Read 36838 times)
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 01:22:13 PM
 #181

2.) It was said that an account that has no public key in the BC yet (no outgoing transactions) was more prone to a brute force attack. Could anyone explan why? I didn't get it. My idea is that a brute force attack works like this: dictionary words or random input generates a public and private key pair, the latter being the account number. I see no difference in the chances of finding an existing account number when using this procedure depending on if the public key is in the bc or not.  Huh

Search space for unrevealed key is only 2^64.

Always busy, right.  Wink  Not enough info for me to understand...

No problem  - maybe someone else can jump in?
1513257455
Hero Member
*
Offline Offline

Posts: 1513257455

View Profile Personal Message (Offline)

Ignore
1513257455
Reply with quote  #2

1513257455
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513257455
Hero Member
*
Offline Offline

Posts: 1513257455

View Profile Personal Message (Offline)

Ignore
1513257455
Reply with quote  #2

1513257455
Report to moderator
1513257455
Hero Member
*
Offline Offline

Posts: 1513257455

View Profile Personal Message (Offline)

Ignore
1513257455
Reply with quote  #2

1513257455
Report to moderator
1513257455
Hero Member
*
Offline Offline

Posts: 1513257455

View Profile Personal Message (Offline)

Ignore
1513257455
Reply with quote  #2

1513257455
Report to moderator
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 01:34:32 PM
 #182

And anothere one:

Account numbers are returned as json strings by the HTTP API, but they are always numbers.

Can I assume they always will be number inside these strings?
Or is it a bug in the API code?
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 04, 2014, 01:39:33 PM
 #183

And anothere one:

Account numbers are returned as json strings by the HTTP API, but they are always numbers.

Can I assume they always will be number inside these strings?
Or is it a bug in the API code?

They r always numbers. They r represented as strings coz JS may round them.
kjannis
Newbie
*
Offline Offline

Activity: 20


View Profile
January 04, 2014, 02:40:59 PM
 #184

Hi,

I am running a client on a VPS and want to check every x minutes for new transactions.
However I have a feeling it is not downloading the needed data for that account.
How can I make sure my client keeps downloading the data for an account?

Can I force this somehow? Perhaps by using curl every x minutes to a certain url?

Thanks?

NXT: The Next big coin?  *Link Removed*
NXT: 18024643391205620992
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 03:42:19 PM
 #185

(Copied over from the main thread for reference.)

How to find the account that will forge the next block.


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



We have a new block about every two minutes, so to always show the account that forges the next block, I need to do this calculation over all accounts again and again? Plus, I need always up-to-date effective balances.

I could implement this and it would currently run, but it will simply not scale with further adoption of NXT.

For now, I'll not implement this. (And I don't see a huge benefit in showing the account forgiung the next block anyway.)
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 04, 2014, 03:49:53 PM
 #186

I could implement this and it would currently run, but it will simply not scale with further adoption of NXT.

This is made intentionally.
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 03:52:32 PM
 #187

I could implement this and it would currently run, but it will simply not scale with further adoption of NXT.

This is made intentionally.

Then why did you say that clients could support TF? I see no benefit.
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 04, 2014, 03:55:47 PM
 #188

I could implement this and it would currently run, but it will simply not scale with further adoption of NXT.

This is made intentionally.

Then why did you say that clients could support TF? I see no benefit.

It's trivial to find who will forge next block among a million accounts, but impossible to predict who will do it in 1440 blocks.
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 04:02:26 PM
 #189

I could implement this and it would currently run, but it will simply not scale with further adoption of NXT.

This is made intentionally.

Then why did you say that clients could support TF? I see no benefit.

It's trivial to find who will forge next block among a million accounts, but impossible to predict who will do it in 1440 blocks.

What is the benefit of knowing who will forge the next block? From a client end-user perspective and in general?
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 04, 2014, 04:07:45 PM
 #190

What is the benefit of knowing who will forge the next block? From a client end-user perspective and in general?

Users can send transactions directly to the miner. In general this helps to achieve VISA processing volume.
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 04:27:35 PM
 #191

What is the benefit of knowing who will forge the next block? From a client end-user perspective and in general?

Users can send transactions directly to the miner. In general this helps to achieve VISA processing volume.

There is no mining in NXT... Just kidding...  Tongue

Is this supported by the current API? How would I send a transaction to the node that has the account open that will forge the next block?

Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 04, 2014, 04:28:37 PM
 #192

Is this supported by the current API? How would I send a transaction to the node that has the account open that will forge the next block?

This will be implemented later. ETA is about 6 months.
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 04, 2014, 10:40:46 PM
 #193

It's trivial to find who will forge next block among a million accounts, but impossible to predict who will do it in 1440 blocks.

It's not trivial for clients, since they will not have all account balances and private keys.

IMHO this should be implemented in the core. If it's really trivial, just add the next forging account as a return value to the getBlock function.
joefox
Full Member
***
Offline Offline

Activity: 210


View Profile WWW
January 05, 2014, 05:09:42 AM
 #194

Search space for unrevealed key is only 2^64.

Always busy, right.  Wink  Not enough info for me to understand...

No problem  - maybe someone else can jump in?

The account number is only a piece of the public key (the first 64 bytes, I think?), so the mapping of passphrases to account numbers is not one-to-one.  As soon as you find the first possible combination that unlocks that account, it's yours.  Anyone else who finds another possible passphrase after that point will be denied access to that account number, since it's already "taken".

I admin the Nxt Wiki at http://wiki.nxtcrypto.org/ Please support my work by donating to Nxt account #1234567740944417915
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 05, 2014, 05:17:08 AM
 #195

It's not trivial for clients, since they will not have all account balances and private keys.

IMHO this should be implemented in the core. If it's really trivial, just add the next forging account as a return value to the getBlock function.

Ok.
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 05, 2014, 03:52:39 PM
 #196

I would need a call to get the Alias ID for an alias, so I can then call getAlias with the ID.

I will need it in the blockchain explorer part of my client when cleaning up the transactions from orphaned blocks.
wesleyh
Sr. Member
****
Offline Offline

Activity: 308


View Profile
January 06, 2014, 02:36:42 PM
 #197

what is type, subtype of transaction? possible values and explanations of them? thx
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 06, 2014, 02:39:01 PM
 #198

what is type, subtype of transaction? possible values and explanations of them? thx

Look at the output of getConstants or look into source code.
marcus03
Full Member
***
Offline Offline

Activity: 224


View Profile
January 06, 2014, 06:27:50 PM
 #199

Which balance is show in the NRS client? "Unconfirmed balance"?
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 1792

Newbie


View Profile
January 06, 2014, 06:50:34 PM
 #200

Which balance is show in the NRS client? "Unconfirmed balance"?

Yes
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 »  All
  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!