Data integrity
Beyond RFC 3161: The Failures of Legacy Timestamping and a Solution
RFC-3161 timestamps often fall short in a number of important use cases. We examine the problems and a solution.
Dan Averbukh
3 reasons why GitHub timestamps shouldn’t be trusted
GitHub timestamps can be trivially altered and should not be trusted for recording the provenance of code or data. Proceed with caution.
Dan Averbukh
Fundraising requires a track record
A credible track record is required for managers to win the trust of potential investors. Creating and maintaining one can be a costly challenge.
Dan Averbukh
Financial data must be made point-in-time
Financial analysis will often yield incorrect results if the underlying data is not point-in-time.
Dan Averbukh
4 reasons blockchains are excellent for data validation
Ensuring integrity and trust: learn how blockchains can and should be used for data validation, data integrity and data provenance systems.
Dan Averbukh
Who cares about data provenance?
Knowing where data comes from is critical to understanding the data. This is particularly true for financial data due to its time sensitive nature.
Dan Averbukh