https://www.smartrac-group.com/pr/smartrac-launches-dloc.html"
The solution can be applied to almost any document, using a printed barcode representing a number, as well as linking personalized data to the document itself. A dLoc sticker is applied to the document. That sticker contains a Smartrac Bullseye NFC inlay, within which is integrated a security chip chosen from a range of different chip platforms with storage capacities between 1kB and 64kB. In addition, dLoc stickers support all the security features, like guilloches, UV print, micro text or latent image normally found in high-security documents.
To enable document authentication in the course of the issuance process, document data is married with the unique ID of the NFC tag to create a 32-bit hash value, which is only recognizable by the issuing agency using a private key. The hash value is stored in Smart Cosmos and backed up in a public blockchain. Once that has happened, the document with the dLoc sticker can be verified using a desktop reader, or more likely, a mobile app on an NFC-enabled phone."
Does one entry credit only allow one hash up to 1kb or can it contain multiple hashes up to 1kb?
If multiple hashes can be put into one entry credit, Smartrac could put 250 (8000 / 32 bit) tags into one entry credit. A yearly production of 2.6 billion RFID transponders would account for a usage of 10.4 million (2.6 billion / 250) entry credits, assuming every tag is stored on the Factom blockchain.
I got the yearly production from:
https://www.smartrac-group.com/files/content/About%20us/SMARTRAC_Company_Presentation.pdfPlease correct me if I'm wrong.
As far as i know only one kb can be stored for every kb, so they prob need max 64 entry credits for a document, you might think thats insane expansive, but thats only 6 dollar cent for the bigest ones.
Not whole documents/data will be stored on the blockchain, but just hashes of documents/data:
http://media.coindesk.com/uploads/2014/11/Factom.jpgSmartrac states they will create a 32-bit hash value per tag, so the previous calculations made a few pages back might be too ambitious, unfortunately.
Edit: data won't be hashed as the link will show
Every application is free to store any kind of data it wants, up to 10kb per entry for 1EC per 1kb. That may be (multiple) hashes, plaintext or both. It all depends on how the application works and what data it needs.
