Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: purpose -1 to return all unconfirmed transactions in UnconfirmedTxs RPC #1675

Open
wants to merge 3 commits into
base: v0.34.x-celestia
Choose a base branch
from

Conversation

rach-id
Copy link
Member

@rach-id rach-id commented Mar 12, 2025

Description

Instead of creating a new RPC method that returns all the unconfirmed mempool transactions, I used -1 as a special flag to do that. I think it's fine to do so. If it's not, can always define a new endpoint.

PR checklist

  • Tests written/updated
  • Changelog entry added in .changelog (we use
    unclog to manage our changelog)
  • Updated relevant documentation (docs/ or spec/) and code comments

@rach-id rach-id self-assigned this Mar 12, 2025
@rach-id rach-id requested a review from a team as a code owner March 12, 2025 17:30
@rach-id rach-id requested review from rootulp and evan-forbes and removed request for a team March 12, 2025 17:30
@celestia-bot celestia-bot requested a review from tzdybal March 12, 2025 17:30
@rach-id rach-id marked this pull request as draft March 12, 2025 17:49
evan-forbes
evan-forbes previously approved these changes Mar 12, 2025
@rach-id
Copy link
Member Author

rach-id commented Mar 12, 2025

I won't merge this PR until I finish all the changes in app in case I need something else from core :D

Done

Copy link
Contributor

@cmwaters cmwaters left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this limit existed in the past as some attempt at DoS prevention. We should just be considerate about nodes with public endpoints

@rach-id
Copy link
Member Author

rach-id commented Mar 13, 2025

The issue is that core doesn't know about fees. What we could do is run custom queries to get the fees from the app for a set of transactions, but it's the same as just returning the whole thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants