<p>Nah..  just did it. To speed things up you can download the tx index, saving an RPC call.  That increases the chain size by around 60GB.</p>
<p>Traversing all blocks (around 450K as Op_return was introduced in March 2014) is going to take 100 days on a 16GB 4-core with SSD.</p>

CC BY-SA 4.0
2022-11-12T17:46:25.500Z
2022-11-12T17:46:25.500Z
Tom Donnelly
<p>I'm working on a &quot;light client&quot; for ION (Identity Overlay Network), and I'd like to see if there is a better method to grab the OP_RETURN data that it needs in order to build state.</p>
<p>Currently I am iterating through every block starting at a specific height and then iterating through each transaction and each transaction output in order to find the OP_RETURN signature that I am looking for.</p>
<p>Is there a better way to accomplish this by requesting all OP_RETURN data only? The bandwidth requirements for downloading all of the block data is a bottleneck for what I'd like to do, but I don't think what I'm looking for is possible with only the Bitcoin Wire protocol.</p>

<client><op-return><thin-clients>
How can I query for all OP_RETURN data starting at a specific block height (or hash)
user1943442
# How can I query for all OP_RETURN data starting at a specific block height (or hash)

(Asked by: username_0 on 2022-03-28)

I'm working on a "light client" for ION (Identity Overlay Network), and I'd like to see if there is a better method to grab the OP\_RETURN data that it needs in order to build state.

Currently I am iterating through every block starting at a specific height and then iterating through each transaction and each transaction output in order to find the OP\_RETURN signature that I am looking for.

Is there a better way to accomplish this by requesting all OP\_RETURN data only? The bandwidth requirements for downloading all of the block data is a bottleneck for what I'd like to do, but I don't think what I'm looking for is possible with only the Bitcoin Wire protocol.

**Tags:** client, op-return, thin-clients


---

## 1 answers

### Answer by username_1 on 2022-11-12. Score: 0

Nah.. just did it. To speed things up you can download the tx index, saving an RPC call. That increases the chain size by around 60GB.

Traversing all blocks (around 450K as Op\_return was introduced in March 2014) is going to take 100 days on a 16GB 4-core with SSD.


---

