bitshares / bitshares/bitshares-core
Check EOS issue #4649 speculation node performance
Open
performance
question
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 660
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 26
Description
Do we have the same issue? https://github.com/EOSIO/eos/pull/4649
And this: https://github.com/EOSIO/eos/pull/4706
It's related to re-validating pending transactions after pushed new blocks.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing EOS pull requests #4649 and #4706, then trace BitShares node handling for re-validating pending transactions after a new block is pushed. Compare the behavior and measure whether the same speculation-node performance issue exists; done means recording a clear conclusion and any affected entry points or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- blockchain, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100