Add r/inscriptions/block/<BLOCK_HEIGHT> to retrieve inscription ID's

[Blockamoto]

Let's mirror the explorer feature of retrieving inscriptions from blocks. This could be done simply with the following recursive endpoint:

r/inscriptions/block/<BLOCK_HEIGHT> : query any block height and return inscription ID's on that block

Should only need to return inscription ID as we can gather INFO, CONTENT, METADATA, and PARENT/CHILD recursively from ID.

Specifically, this would allow inscription-based indexers to be built, which is vital for the future of bitmap and other namespaces.

[NRCHST]

Yes please!

[Zmakin]

Please allow this, it would substantially benefit all indexers as they could reduce their API calls to limit specifically to relevant transactions containing inscriptions.

[cryptoni9n]

Let's mirror the explorer feature of retrieving inscriptions from blocks. This could be done simply with the following recursive endpoint:

r/inscriptions/block/<BLOCK_HEIGHT> : query any block height and return inscription ID's on that block

Should only need to return inscription ID as we can gather INFO, CONTENT, METADATA, and PARENT/CHILD recursively from ID.

Specifically, this would allow inscription-based indexers to be built, which is vital for the future of bitmap and other namespaces.

Hi blockamoto,

Could you use this instead? I get 878 inscription ID's from the following curl script:

curl -s -H "Accept: application/json" 'http://localhost:80/block/840000' | jq '.inscriptions' > \block840000.json

[billpan69]

Yes please!!!

[bitlodo]

very useful!

[astralarkitekt]

Let's mirror the explorer feature of retrieving inscriptions from blocks. This could be done simply with the following recursive endpoint:
r/inscriptions/block/<BLOCK_HEIGHT> : query any block height and return inscription ID's on that block
Should only need to return inscription ID as we can gather INFO, CONTENT, METADATA, and PARENT/CHILD recursively from ID.
Specifically, this would allow inscription-based indexers to be built, which is vital for the future of bitmap and other namespaces.

Hi blockamoto,

Could you use this instead? I get 878 inscription ID's from the following curl script:

curl -s -H "Accept: application/json" 'http://localhost:80/block/840000' | jq '.inscriptions' > \block840000.json

Unfortunately, this is inaccessible on-chain. Security policies of the ordinals iframe sandbox prevent access to that.

A recursive endpoint is required to be able to access this info on-chain.

[SpyrosKoTV]

Yes please!!!!

[colorshifterz]

awesome, let's go