Quote from: MaWo on December 23, 2015, 03:54:44 PM

... an alias "nrsversion" update,
which is also used to announce new nrs version witihin the hz client.
The last 'nrsversion' alias update was on '12/13/2015 23:00:26 UTC'
Transaction id is 13358822116601159558 and block id is 6751858650703315890.

Interesting to know. Thanks.

Cool system. I like that.

How does it work?

The tx is this one: https://explorer.horizonplatform.io/?page=transaction&id=13358822116601159558 MESSAGE/ALIAS
This is what the API answers:

Code:

{
   "senderPublicKey": "617833867b6301eeff0af39b790427200ca16f14ad0a47316c63f3cf78b97a77",
   "signature": "9e321ee9d47df1263e8817369a54c7531fff12f58e487fd0e1791f57411fa204b76550620cdedd4cdc063f1ab6ff0c90dc2402d6e2fa49e6329a963bed1c4aac",
   "feeNQT": "100000000",
   "transactionIndex": 1,
   "requestProcessingTime": 16,
   "type": 1,
   "confirmations": 8816,
   "fullHash": "86dfa4ddef1164b94e2acf88c96d398b70fdf3a889f3e5ee33787284d540cd40",
   "version": 1,
   "phased": false,
   "ecBlockId": "4297034059307516461",
   "signatureHash": "1eaa1c63905544b800bc22cbd7c9818a4ed064c463a6e3b54ca9c47b6f6bd6a7",
   "attachment": {
   "alias": "nrsversion",
   "version.AliasAssignment": 1,
   "uri": "nhz_v5.4 86a2b00306f1bbee281d29a17678384a4172ed104b82749f7eefd1fcef5695b4"
   },
   "senderRS": "NHZ-ALWB-YDQU-746N-69EPL",
   "subtype": 1,
   "amountNQT": "0",
   "sender": "5284279215227947913",
   "ecBlockHeight": 521217,
   "block": "6751858650703315890",
   "blockTimestamp": 54520685,
   "deadline": 1440,
   "transaction": "13358822116601159558",
   "timestamp": 54520604,
   "height": 521225
}

"alias": "nrsversion",
"version.AliasAssignment": 1,
"uri": "nhz_v5.4 86a2b00306f1bbee281d29a17678384a4172ed104b82749f7eefd1fcef5695b4"

So the alias "alias": "nrsversion" always contains the newest version number?