4 ms·
This is certainly a possible implementation and good if you would want to base it on the chain, doable via a minimal node. It would not work offline though, whi
by miunau 5y ago
This is certainly a possible implementation and good if you would want to base it on the chain, doable via a minimal node. It would not work offline though, which would make it harder to use in frontline reporting, so I think the spec itself should not specify such a requirement.
- 3np 5y agoQrdate involves server-side signing and does not work offline either? If the signature involves a hash of a bitcoin block we don't have to trust the site owner to not sign future timestamps.
- miunau 5y agoThere's two proposed ways specified. The web way (called "Dynamic") and a fingerprint-based implementation that can work offline ("Static"), for example in approved apps for some organisations: https://github.com/qrdate/qrdate#static-qr-date-v1-spec https://github.com/qrdate/qrdate#static-qr-date-v1-spec It is still a concept as there's no implementation of it besides the tests in the repo, so it would require further refining for production apps. For example with specifying key exchange formats, which we are looking at right now. Anyone with expertise in this field wanting to contribute is welcome!