Recursion Improvement Proposal (RIP)

[Blockamoto]

I'd like use this discussion to talk about recursive endpoints, what I feel is missing, and pick up a discussion about them.

Are any of these being addressed or implemented? What problems could there be? How can we mitigate them? Etc.

The goal here to to COMPLETE recursion based upon what is available in the explorer.

Please suggest your own if you have any additions, or if I missed anything.

/r/address/{address} : sats, tx, inscriptions
/r/address/{address}/sats : sats amount
/r/address/{address}/tx : list of transactions
/r/address/{address}/inscriptions : list of inscriptions

/r/block/{height/hash}/tx : transactions on specific block
/r/inscriptions/block/ : inscriptions on latest block
/r/inscriptions/block/{height/hash} : inscriptions on specific block

/r/properties/{id} : properties of an inscription

/r/gallery/{id} : list of inscriptions in gallery
/r/galleries : index of all galleries

/r/metaprotocol/{id} : name of metaprotocol
/r/metaprotocols : index of metaprotocols

/r/inscription/self : finds current inscription ID

These next additions are already resolvable with mathematics, but could easily be added as recursive endpoints with little concern:
/r/sat/{name} : find sat by sat name (and allow this across ALL /r/sat endpoints) 
/r/satinfo/{sat} : expose all alternative sat signifiers

That's all I've got for now, but let me know if any of these are already in the works, already resolvable, or controversial! I tried to plug all the current holes in recursion. Any issues regarding bandwidth can be handled by node-operator / service rate-limit level.

[dave4506]

+1 to this;

/r/block/{height/hash}/tx : transactions on specific block would be esp useful to us.

[dave4506]

Added a PR for /r/block/{height/hash}/tx #4496