Overview
Dividends
Updates
Contacts
Asset_ID: 2632494122289
Issuer: 1FCkCQCnEtHQ3j7NqdkAnkqQUvqfti4XoA
Time Stamp: 2/1/2014 10:45:57 PM
Transaction: 2843 recorded at Block #283652
Tx Hash: 91aed459a4cb1bbd500e1ffea62e84a0c8988971d251d307f7485d6cd57d79a8
Total Amount Issued: [Issue No.1 at Block#283652] 10000000000
Divisible: True
Transfer: False
Remark: Valid
The difference between counterpartyd_build and blockscan.com:
counterpartyd_build:
Asset Name: MPTSTOCK
Asset ID: 101249773934
Total Issued: 200.0
blockscan.com:
Asset Info MPTSTOCKF
Asset_ID: 2632494122289
Issuer: 1FCkCQCnEtHQ3j7NqdkAnkqQUvqfti4XoA
Time Stamp: 2/1/2014 10:45:57 PM
Transaction: 2843 recorded at Block #283652
Tx Hash: 91aed459a4cb1bbd500e1ffea62e84a0c8988971d251d307f7485d6cd57d79a8
Total Amount Issued: [Issue No.1 at Block#283652] 10000000000
My question is , which one is correct? I have marked the difference in red.
I also posted this at: https://bitcointalk.org/index.php?topic=395761.2440
The AssetID is a bit confusing. Previous builds did not include the CHECKSUM character and the AssetID was calculated based on this..
But when the CheckSum character was added to the later releases the MPTSTOCK-became->MPTSTOCKF. And this (MPTSTOCKF) is what its officially referred to in this counterparty client when doing a "asset" command. However, the ASSETID is still calculated based on "MPTSTOCK" and not "MPTSTOCKF
I understand that the code is still alpha and changes like these are to be expected for the betterment of the protocol. However, I don't really have a way to know what gets broken on blockscan whenever these changes take place...
I believe I have already corrected this issue and asset page on blockscan should match what you see in the counterparty client. If I have missed out anything please let me know
I am going to take a step back from the making changes at blockscan and most likely wait till the changes stabilize a bit before trying to fix stuff after this
cheers