21–30 of 48 posts
I don't like the idea of this using bitcoin. I wonder if it's possible to build this off of regular PKI - certificate transparency logs for instance encode the proof of commitment, while the signature can be an X509 certificate.
Loved it until I saw its using Bitcoin. With proof of work doesn’t it tie this project to a bit of an environmental nitemare? Bitcoin isn’t the best place for this, no? I would have imagined Ethereum or some other ledger would have been better no? Anyone with more crypto ledger knowledge be able to say what I’m trying to say more precisely.
I love the concept, it would be great to see broader uptake of an open standard for this sort of space.
Any benefits over DocuSeal? https://github.com/docusealco/docuseal
Nice idea but with all related things the ultimate question remains whether courts will actually recognize it. Currently courts will still consider paper-signed and scanned PDFs as legally binding, so any verification on top of that is superfluous to them. More realistically, you take an oauth when you take the stand at the court, and if a signed document was altered by the counterparty you'd say so truthfully, if it…
Is this PAdES B-B only ? As far as I know, PAdES B-T requires a QTSP timestamp.
DocuSign/Adobe/whomever is trust anchor, it's an entity you can sue or subpoena if something goes wrong. Someone who's actually on the hook for making sure whatever's signed is accurate and truthful (outside of the reputational risk of fraud completely obliterating any trust in your platform)...
No amount of cryptographic verification substitutes for having a legal person on the other end who can be held accountable for actually verifying the document was signed accurately/process was followed.
Due to how the code signing works, timestamping servers are provided by all major CAs with full public access, e.g. timestamp.digicert.com, timestamp.comodoca.com, timestamp.sectigo.com, etc.
PS. OP, your comments are auto-killed for some reason. You may want to message mods to get this sorted.
I don't like the idea of this using bitcoin. I wonder if it's possible to build this off of regular PKI - certificate transparency logs for instance encode the proof of commitment, while the signature can be an X509 certificate.
Earlier quoted context omitted.
Sure, lets say this lacks an RFC/ISO number, or any semblance of what is usually called a standard.
What I think you're trying to say, but don't seem to be getting across super clearly, is that this standard hasn't yet gone through an open third party review