You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2024. It is now read-only.
This structure doesn't exist in the specification, furthermore, it seems to be incorrect because if we POST this data to admin API and then try to GET it from public API, the test$example.com is omitted (this information isn't written to the database) and replaced with the top-level pay id verifiabledemo$127.0.0.1. And as long as, the JWS verification requires the original payload, it will be failed.
It leads to the conclusion that verifiedAddresses should be created from Address interface and signed without additional wrapping into an unknown structure.
please correct me if I'm wrong
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The structure of the Verifiable PayID seems to be wrong according to the current interface description at https://docs.payid.org/payid-interfaces
This is Verifiable PayID from docs (https://docs.payid.org/verifiable-payid-tutorial):
so the payload of the verified address contains:
This structure doesn't exist in the specification, furthermore, it seems to be incorrect because if we POST this data to admin API and then try to GET it from public API, the
test$example.com
is omitted (this information isn't written to the database) and replaced with the top-level pay idverifiabledemo$127.0.0.1
. And as long as, the JWS verification requires the original payload, it will be failed.It leads to the conclusion that
verifiedAddresses
should be created fromAddress
interface and signed without additional wrapping into an unknown structure.please correct me if I'm wrong
The text was updated successfully, but these errors were encountered: