
Babu Veluru
96 posts

Babu Veluru
@BabuVeluru
crypto entusiast? exlporer? hodler? #crypto #eth #sol



Delegate inscriptions can themselves have unique inscriptions inside their envelopes. These inscriptions are inaccessible! What if you could access this data? Introducing "/r/delegator/:id" Currently when you create a generative engine like I did with Blob you can only seed generation with unique data from the onchain metadata. Each blob is unique because it seeds the blob engine from its metadata. Each blob inscription has no content inscribed only metadata making them incredibly efficient at using blockspace. However metadata is in CBOR and is limited size. This limits your options. However with "/r/delegator/:id" you get the entire content of the inscription which could be a large file maybe even 4mb. You could use this to inscribe file types not supported in the browser. How? You create a rendering engine for the file type as the delegate and in the content of the delegator you put the file. Then anyone who wants to render that filetype can simply delegate the rendering engine. github.com/ordinals/ord/p…















