zemyblue
zemyblue
@ulbqb , Is it completed?
If this issue is completed, #674 will be fixed.
We need to check `lbm.base.ostracon.v1.Query.GetBlockResultsByHeight` and `lbm.base.ostracon.v1.Query.GetBlockByHash` of #291 are removed. This apis are provided in REST api in cosmos-sdk's cometbft api. I think we need to check it later....
When you add this feature, please add all sub contract not only `hackatom`.
I think it is unnecessary. I think it's enough the callee function for dynamic link only be called by dynamic link caller.
How about replacing the current `v1.1.1-0.7.0` with `v1.0.0`? And how about setting the version with the dynamic link function to `v1.0.0+dynamiclink1`?
Is it possible? I don't think it can happen because there are several confirmed blocks can't occur, so I don't think it can happen that new proposer can choose it....
Oh, I see. This issue is a situation in same block height. But I also this is not a problem. Even if a malicious proposer creates a new block in...
If the probability of validator being elected as proposer is determined by the ratio of staking power, it seems that byzantine can be prevented from continuing to be elected. Even...