I was looking at the spec https://developers.libra.org/docs/libra-protocol#transactions and couldn’t find info about transaction related information.
IMHO - this query in-turn relates to,
- LinkedData (rdf namespaces - including but not limited to: http://ogp.me/ )
- RDF Transaction Information (ie: digital receipts)
I then looked at https://w3c.github.io/web-ledger/ and couldn’t find a transaction information URI field in those examples either. I do note access to the transaction information may have different permissions, but that it seemed an important point to raise. With respect to user-stories / use-cases that may be employed by libra, this could take into account open badges ( https://www.imsglobal.org/sites/default/files/Badges/OBv2p0Final/index.html ) ie: ‘bob donates to environmental projects’ or ‘bob is an authorised uber driver’,
noting also, there’s a bunch of DID related verifiable claims and credentialing works, that have extended beyond the old works on w3c web-payments CG & Credentials CG incubated beginnings.
There’s now several W3C projects that relate to the work of Libra - how are they being taken into account as to form a scalable web-infrastructure solution?