EIP-5289 Discussion: Notary Interface

[omnus]

I was wondering if there was a use case for saying, for example, documents 1,2 and 3 are associated with all tokens in the collection, and document 4 was a specific agreement for tokenId 1129, and document 5 for tokenId 2971, etc.

This could then support specific legal arrangements that individual token holders have made. I have something along those kind of lines in the delegation extension built on top of EIP-4886, though not with the sophistication of your solution (I just have the ability to hold a URI).

[Pandapip1]

@omnus

I was wondering if there was a use case for saying, for example, documents 1,2 and 3 are associated with all tokens in the collection, and document 4 was a specific agreement for tokenId 1129, and document 5 for tokenId 2971, etc.

Yes, there is! You can have it revert only when the token ID is a specific number if you want.

[DePONotary]

@Pandapip1

NOTE: None of the authors is a lawyer. If you are a lawyer and would like to contribute to this EIP, please contact Pandapip1 on Discord

Hey, guys, I’m DePONotary founder of an eNotarization StartUp, Software Developer, and US eNotary Public, and I can only provide a personal interpretation of my experience as such because I AM NOT AN ATTORNEY LICENSED TO PRACTICE LAW IN THE US AND MAY NOT GIVE LEGAL ADVICE OR ACCEPT FEES FOR LEGAL ADVICE

I am going to endure the task of going through the entire thread and commenting as I make myself through the lot and if any of my comments receive a response, I will respond after I have finished the thread.

[DePONotary]

@SamWilsn

I would strongly recommend against using a PDF for the document. They are insanely complex, and incorrectly implementing a renderer in the wallet could mean inconsistencies between what two users see and sign.

What exactly makes the Portable Document Format so complex that is so hard to implement a rendering? is it the tampered-evident XML wrap?

[SamWilsn]

@DePONotary

What exactly makes the Portable Document Format so complex that is so hard to implement a rendering? is it the tampered-evident XML wrap?

For one, the most recent standard is managed by ISO and is non-free to access. Second, PDFs can include JavaScript, fillable forms, a multitude of animation and image formats, fonts, and probably a ton of other features I’m neglecting to mention. I would advocate for something simpler and more open as the basis for legal documents in this space.