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
I had thought of this and i wanted to make the paycrypto URI scheme compatible with the actual HTTPS URI scheme (https://datatracker.ietf.org/doc/html/rfc1738#section-3.3 and https://datatracker.ietf.org/doc/html/rfc2616#section-3.2.2) for reducing friction when implementing. But it would make sense to use json since its a lot easier to prepare a json and add it to the end of the url in its stringified form. I will investigate if there is already an standard version of using the json format in a URI
I'm proposing a different parameter scheme, allowing for different addresses in different chains. I'd rather go for an array of objects, such as:
The text was updated successfully, but these errors were encountered: