At Tierion, we think the inclusion of the NIST Beacon in every Chainpoint 3.0 proof we generate is a powerful feature. We announced that we had started includi

At Tierion, we think the inclusion of the NIST Beacon in every Chainpoint 3.0 proof we generate is a powerful feature. We announced that we had started including the Beacon in our new proofs at Consensus in May. The first of its kind. https://tierion.com/blog/chainpoint-innovations-in-blockchain-timestamp-proofs/ https://tierion.com/blog/chainpoint-innovations-in-blockchai... Its also featured in our white paper if you'd like to read more about how we're using it. https://tokensale.tierion.com/whitepaper https://tokensale.tierion.com/whitepaper Tierion has been collaborating with the leader of the Random Beacon project at NIST and we've been providing feedback on their new release, expected this summer. Every Chainpoint 3.0 proof has the most current available NIST timestamp and its associated random value merged into the proof directly, allowing easy manual audit and cross-check. This is in addition to server NTP time in the form of a v1 UUID, which contains both a timestamp and randomness. We also include the NIST Beacon in a new Calendar block every time it is updated so our Calendar blocks can have enhanced temporal anchoring, even in the absence of aggregated Merkle roots being anchored to the Calendar. We've thought for a while that the NIST Beacon it pretty cool and we're glad to see others coming around to the idea as well.