Entry Submitted by Fireswan at 6:48 PM EDT on May 9, 2019
"A Quick Question for Fireswan" by MJM - 5.9.19
I work in Cybersecurity, financial sector. State-side and International. Civilian.
I saw some data flows awhile ago with a hash of two signatures. I was able to reverse engineer how the signatures were “created” using hidden-in-plain sight protocols published by NIST having to do with cryptographic key generation. There’s standards and protocols for scanning gold (in ground or vaulted) and how scanning equipment generates a unique signature to create a gold certificate. There is also information for associating the gold certificate with a human being (again using a signature by scanning the human). A hash of [human::gold] creates an unique identifier that tags transactions in a distributed ledger. Also, the XBRL reporting language was expanded to report on gold certs hashed with account owners. Hummm. More validation.
I have posted in the past on IDC in geeky detail how I figured it out. I included links to documents that led to which documents, etc. Just do a search on Fireswan on IDC and you can follow along. Pretty geeky stuff.
I have for some time seen data flows with these unique identifiers and expanded XBRL tagging. I am assuming that the QFS is generating these as a mirror to the fiat (old system) flows. We have flagged discrepancies so that other white hats can obtain evidence to catch bad guys (from being able to compare the two). Certs are missing from illegitimate flows. XBRL has been tremendously helpful. Everything will be logged and reported making all transactions transparent after the new financial system starts up for everyone.
I am just a tech., so I’m not told anything directly. I am just observant and did a lot of research reading painfully boring compliance documentation and specifications.
That being said, there was an announcement at the Fintech Conference in London during the American Thanksgiving last year. Gold certificates (and how they’re created) is becoming mainstream in the IT community and was announced at the conference. The FinTechs (my former employer is a FinTech) are ahead of the mainstream so that we can write and implement the support systems so that there’s a smooth transition when the QFS is “ready” for everyone.
Oh... and I saw a bank system programmer creating a “back screen” that shows gold backed currency with fields for the cert. The millennial programmer had no idea what the data he was displaying was for. You don’t need a vault ID for the cert. You can also have a geographic location for in-ground gold if the Cert. is for in-ground.
Hope that helps
Fireswan
______________________________________________________
All articles, videos, and images posted on Dinar Chronicles were submitted by readers and/or handpicked by the site itself for informational and/or entertainment purposes.
Dinar Chronicles is not a registered investment adviser, broker dealer, banker or currency dealer and as such, no information on the website should be construed as investment advice. We do not intend to and are not providing financial, legal, tax, political or any other advice to readers of this website.
Copyright © 2019 Dinar Chronicles
"A Quick Question for Fireswan" by MJM - 5.9.19
I work in Cybersecurity, financial sector. State-side and International. Civilian.
I saw some data flows awhile ago with a hash of two signatures. I was able to reverse engineer how the signatures were “created” using hidden-in-plain sight protocols published by NIST having to do with cryptographic key generation. There’s standards and protocols for scanning gold (in ground or vaulted) and how scanning equipment generates a unique signature to create a gold certificate. There is also information for associating the gold certificate with a human being (again using a signature by scanning the human). A hash of [human::gold] creates an unique identifier that tags transactions in a distributed ledger. Also, the XBRL reporting language was expanded to report on gold certs hashed with account owners. Hummm. More validation.
I have posted in the past on IDC in geeky detail how I figured it out. I included links to documents that led to which documents, etc. Just do a search on Fireswan on IDC and you can follow along. Pretty geeky stuff.
I have for some time seen data flows with these unique identifiers and expanded XBRL tagging. I am assuming that the QFS is generating these as a mirror to the fiat (old system) flows. We have flagged discrepancies so that other white hats can obtain evidence to catch bad guys (from being able to compare the two). Certs are missing from illegitimate flows. XBRL has been tremendously helpful. Everything will be logged and reported making all transactions transparent after the new financial system starts up for everyone.
I am just a tech., so I’m not told anything directly. I am just observant and did a lot of research reading painfully boring compliance documentation and specifications.
That being said, there was an announcement at the Fintech Conference in London during the American Thanksgiving last year. Gold certificates (and how they’re created) is becoming mainstream in the IT community and was announced at the conference. The FinTechs (my former employer is a FinTech) are ahead of the mainstream so that we can write and implement the support systems so that there’s a smooth transition when the QFS is “ready” for everyone.
Oh... and I saw a bank system programmer creating a “back screen” that shows gold backed currency with fields for the cert. The millennial programmer had no idea what the data he was displaying was for. You don’t need a vault ID for the cert. You can also have a geographic location for in-ground gold if the Cert. is for in-ground.
Hope that helps
Fireswan
______________________________________________________
All articles, videos, and images posted on Dinar Chronicles were submitted by readers and/or handpicked by the site itself for informational and/or entertainment purposes.
Dinar Chronicles is not a registered investment adviser, broker dealer, banker or currency dealer and as such, no information on the website should be construed as investment advice. We do not intend to and are not providing financial, legal, tax, political or any other advice to readers of this website.
Copyright © 2019 Dinar Chronicles
0 Comments: