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
The more I think about it, the more I think it's a bad idea to allow inclusion of ABI or other information by (non-file) URL.
For one, this requires that the consumer has an Internet connection.
For two, and more importantly, content hosted outside the specfile* can change or disappear at any time. It is not possible to, e.g., sign over the spec, if it includes an external resource. Even if you add a checksum of the content at the time of creation, if the resource disappears, you can no longer reconstruct its contents and the spec becomes worthless.
*) what's a good term for the individual JSON descriptions? spec? specfile? descriptor?
The text was updated successfully, but these errors were encountered:
Only valid points yes 👍 Relates to #2, for now our answer to this is that descriptors are snapshot/converted to resolved form at import time in our private/Ledger specific repository. It might be worth standardizing this part as all consumers/integrators will face this problem.
The more I think about it, the more I think it's a bad idea to allow inclusion of ABI or other information by (non-file) URL.
For one, this requires that the consumer has an Internet connection.
For two, and more importantly, content hosted outside the specfile* can change or disappear at any time. It is not possible to, e.g., sign over the spec, if it includes an external resource. Even if you add a checksum of the content at the time of creation, if the resource disappears, you can no longer reconstruct its contents and the spec becomes worthless.
*) what's a good term for the individual JSON descriptions? spec? specfile? descriptor?
The text was updated successfully, but these errors were encountered: