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
Ecosystem teams have reported challenges regarding the use of the celestia-node API for transaction submission. The difficulties largely revolve around two factors:
The transaction submission methods are synchronous, leading to the code hanging while waiting for a response, which can sometimes take a considerable amount of time. This results in inefficient use of resources and can lead to suboptimal user experience.
The current API setup prevents more than one transaction from a single account to a given namespace within one block due to the manner in which cosmos-sdk/tendermint manages nonces. Although the team facing this issue has overcome similar hurdles with other software, such as Metro, they note the issue here.
The teams suggest that a shift to a REST API could prove more beneficial and user-friendly. They argue that developers are generally more familiar and comfortable with REST APIs over RPC APIs, as the former typically offer better tooling and efficiency.
Their feedback further indicates that the current API setup may impose a considerable engineering burden on external teams, potentially deterring them from adopting new releases.
📄 Relevant Issues
The teams have also identified a few open issues on GitHub that are relevant to this topic:
This GitHub discussion aims to tackle the nuances and comparisons between REST and JSON-RPC, providing an open forum for community users to discuss and share their insights on the API's current state and potential improvements.
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
-
✍️ Summary
Ecosystem teams have reported challenges regarding the use of the celestia-node API for transaction submission. The difficulties largely revolve around two factors:
The teams suggest that a shift to a REST API could prove more beneficial and user-friendly. They argue that developers are generally more familiar and comfortable with REST APIs over RPC APIs, as the former typically offer better tooling and efficiency.
Their feedback further indicates that the current API setup may impose a considerable engineering burden on external teams, potentially deterring them from adopting new releases.
📄 Relevant Issues
The teams have also identified a few open issues on GitHub that are relevant to this topic:
☀️ Proposed Next Steps
I am proposing the following actions to assess and improve the situation:
This GitHub discussion aims to tackle the nuances and comparisons between REST and JSON-RPC, providing an open forum for community users to discuss and share their insights on the API's current state and potential improvements.
Beta Was this translation helpful? Give feedback.
All reactions