Difference between QuickNode and plublic endpoint response for eth_subscribe

General
1

Hi guys, I have a quick question about the response I get from eth_filter. I’m running this code in Python using a BNB endpoint.

while True:
     tx_filter = w3.eth.filter('pending')
     pending_tx = tx_filter.get_new_entries()
     print(pending_tx)

I’m wondering if you guys do something extra in the backend? In this case, the public endpoint and other providers only return the tx hash, but QuickNode returns the entire tx object. Do you run an extra step in the back, or is it how the client software is set up?

2

Hey David,

Can you please provide us with a public endpoint or other providers that only return the tx hash so we can jump in a little deeper.

-Nick

3

Thank you for looking into it. This is the public endpoint I used and only returns hashes. Thank you!
https://bsc-dataseed.binance.org/

4

Hey David,

We do indeed output the entire tx data. Our nodes are on the latest version. A new BSC version dropped today with a hard fork, so others will have to update.

-Nick

5

Thank you for looking into it, but I noticed that well before today. Do you think the version is the main thing?

6

Hey David, yes, that should be the main reason.

Provided public endpoint is on 1.2.5 ,
the change in response format occurred is with 1.2.8

-Nick