-
Notifications
You must be signed in to change notification settings - Fork 232
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
In subscription channel, topic proposed_transaction
keeps inactive
#4521
Comments
how large is the number of transactions, it may related to this performance issue: 117 is release with a fix for it. |
If you want to subscribe to a
|
just the same as the online chains; we do not push pressure directly on it. currently is like 20/min according to the explorer
this might be the problem. will add it and do a re-test |
I have added my context. maybe we can add a new subscription topic to get notice of transaction packed? |
after following this, the |
Bug Report
Current Behavior
When using rpc's subscription, topic
proposed_transaction
has no notify at all. https://github.com/nervosnetwork/ckb/tree/develop/rpc#proposed_transactionIt all returns a successful subscription id when sub to these two topic(
new_transaction
,proposed_transaction
); but only topicnew_transaction
has notification pushesExpected Behavior
Proposed transaction will also push notification followed by the status of txpool
Environment
uname -a
]Additional context/Screenshots
What I'm implementing is as follows:
I want to be notified when a specific rule of transactions is posted to nodes. I will then perform certain actions and determine when the transaction is committed to the block. Depending on the different statuses of the transaction, I will trigger different business logic branches.
It might be more convenient to add a new topic like "transaction packed." Currently, we can only poll results from get_transaction to get status updates.
The text was updated successfully, but these errors were encountered: