fanlong
fanlong
@yangzhe1990, we should investigate this when we have time. Probably after the first phase main-net release
It sounds like a potentially serious issue we need to investigate. I raise it to top priority
@yangzhe1990 , after my experience with the block reward record. I am not sure whether we should put it into receipt/log. Or alternatively, we can just maintain some full node...
This will improve the performance under attacked TreeGraph state
I think make confirmationRisk configurable is possible
We should not use assigning as a way to catch attention here. Let's see whether @yangzhe1990 wants to self-assign on this. What's the source code line number around this?
Yeah. It is out-dated and we should update it soon. cargo format will touch too many files, so it is hard for us to update it often without interrupting existing...
Basic functionality is to periodically run the test mentioned in rigorous-testing.md
@peilun-conflux implemented the scripts. I will downgrade the priority for creating dashboard for it
We should investigate this after the feature freeze