Nxt Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client 1.11.9 - NEW RELEASE: Ardor 2.0.3e TestNet IS LAUNCHED!

Pages: [1]

Author Topic: Can someone explain ecBlockId & ecBlockHeight  (Read 694 times)

slothbag

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 454
    • View Profile
  • Karma: +74/-4
Can someone explain ecBlockId & ecBlockHeight
October 09, 2014, 02:22:31 am

What are they, and what benefit are they in the API calls?

Edit: Ok, something to do with economic clustering it seems.
« Last Edit: October 09, 2014, 02:25:12 am by slothbag »

jones

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 1043
  • write code not war
    • View Profile
    • jNxt
  • Karma: +310/-8

To my knowledge they aren't really even contributing that much/anything to the transactions, usually when I send transactions from bytes, I use a block 5 blocks before the current one as the ecblock, not entirely sure if this is a safe practice though
-- Jones NXT-RJU8-JSNR-H9J4-2KWKY

ScripterRon

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 457
    • View Profile
  • Karma: +72/-2

Economic Clustering is discussed here: https://nxtforum.org/news-and-announcements/economic-clustering/

The current code (NRS 1.3) includes the EC block identification in each transaction but currently ignores it when validating a transaction (other than putting out a debug message when the EC check fails). 

JL added the getECBlock API request for applications (such as NxtCore) which create the transaction bytes themselves.
NXT-XM86-4ZNA-65L5-CDWUE
Pages: [1]