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
summary - let''s make it a requirement / policy to upload / commit / save the image indexed by inscribe id AND num here - i will rewrite the README shortly.
thanks for all your support - i personally prefer numbers because they are more human and easier to use and remember for humans and promote the idea of the "long count" going from 0 to infinity - and bonus - easy to sort / order by date - 0,1,2... .... i see your point about bitcoin / inscribe tx ids ... here's the promise (and suggestion) ... let's always upload both ... indexed by num & id (git itself is content-addressed storage e.g. indexed by content hash and not file name/dir hierarchy - so the image is in the blog store only once and gets referenced in the "commit tree" - that is my understanding of the git internals). note: the only oonstraint is the image size ... i run here on a (personal) free plan (with space limits)
Hi!
I think it may be more robust to issues to use the inscription_id instead of the inscription_number as the "key reference" for orc-721.
Reason:
(this is for num/*.png specifically but may be a good standard to use across the project)
The text was updated successfully, but these errors were encountered: