You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way I see it, a fully 'decentralized' spend aggregation feature (i.e., no central sequencer) would require searching the mempool for spends & building your transaction on top of them. I've tried doing something similar and was surprised to find out that the full node RPC only allows you to get mempool items either by the transaction id (which is the sha256 of the spend bundle) or all at once. I'm writing this message to request a new endpoint that would take a coin name (id) as an argument and return the mempool item that spends that coin, if it exists.
The current workaround is getting all items at once and filtering them, which is very inefficient. I've seen that, for the current ~1700 items on testnet10, my python script took more than 30 seconds to decode the response (that's useless, given that the block time is lower than 60s).
This is not urgent, but I'm sure it would be a great addition to the Full Node RPC API.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
The way I see it, a fully 'decentralized' spend aggregation feature (i.e., no central sequencer) would require searching the mempool for spends & building your transaction on top of them. I've tried doing something similar and was surprised to find out that the full node RPC only allows you to get mempool items either by the transaction id (which is the sha256 of the spend bundle) or all at once. I'm writing this message to request a new endpoint that would take a coin name (id) as an argument and return the mempool item that spends that coin, if it exists.
The current workaround is getting all items at once and filtering them, which is very inefficient. I've seen that, for the current ~1700 items on testnet10, my python script took more than 30 seconds to decode the response (that's useless, given that the block time is lower than 60s).
This is not urgent, but I'm sure it would be a great addition to the Full Node RPC API.
Thank you,
yakuhito
Beta Was this translation helpful? Give feedback.
All reactions