tronprotocol / tronprotocol/pm
GreatVoyage-v4.8.3(Antisthenes) planning
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 27
- Forks
- 19
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 4
Description
This issue will be used to track the planning and coordination of TIPs and features targeted for inclusion in GreatVoyage-v4.8.3 (Antisthenes). Details of the included changes are still under discussion, and the v4.8.3(Antisthenes) is expected to be released in Q4, 2026.
The scope of the release:
TIP:
TBD
API:
Issue 6298: FullNode API based on determining chain state
Issue 6936: Standardize HTTP API Error Messages
Issue 6941: Standardize JSON-RPC error mapping and exception boundaries
Issue 6951: Standardize JSON-RPC null parameter handling
Network:
Issue 6932: Improve thread safety of shared mutable state
Issue 6942: Harden sync message validation and resource controls
Issue 6675: Add timestamp validation and deduplication to hello handshake messages
Issue 129: Avoid duplicate connection attempts to active nodes before handshake completion
Issue 144: Improve pre-handshake connection handling
Security:
TBD
TVM:
Issue 6697: Standardize precompile execution with fine-grained timeout checks
Others:
Issue 6921: Tracking: code refactor and cleanup
Issue 6939: Fix RocksDB table option setters in v4.8.2.1
Issue 6926: Fix field mappings in GRPC GetStatsInfo and GetNodeInfo
Issue 6940: Fix toolkit db mv to prevent data loss
Issue 6929: Improve event delivery and ZeroMQ queue configuration
Issue 6969: Robustness fixes for multiple issues
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is a release-planning tracker for GreatVoyage-v4.8.3, with scope still under discussion and multiple linked API, network, TVM, and cleanup issues. Start by reviewing the linked issues and their current status; done means the release scope and included changes are finalized, rather than implementing a self-contained change here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100