Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict transactions result in local variable values differing from on-chain variable values #4426

Open
sdjasj opened this issue May 7, 2024 · 0 comments
Assignees

Comments

@sdjasj
Copy link

sdjasj commented May 7, 2024

Describe the bug
I continuously send conflicting transactions with a fixed QPS to different shards of the local four-node private chain. These conflicting transactions conflict in reading and writing variables in this contract or others. At the same time, I simulate changes of the variables on-chain locally, and only when I receive a successful transaction receipt will the local variable's value be modified. After testing for several hours, I found that the values of local variables were different from those on-chain.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy contract.
  2. Send transactions with conflicts, such as different functions of a contract accessing different state variables of the same contract, or functions of different contracts accessing each other's state variables.
  3. Simulate transaction execution of the chain locally (a transaction is considered successful only when the transaction receipt status is successful.).
  4. Inconsistency between local and on-chain results.

Expected behavior
Local and on-chain results should be consistent.

Screenshots
ce1da3463fe1f35355188eda6ba0cc8

Environment (please complete the following information):

  • OS: Ubuntu 20.04
  • FISCO BCOS Version 3.5.0

Additional context
The complete output log of the test program is as follows:
fisco_output.txt
The partial log of the node is as follows:
log_2024050620.00.log.gz.zip

@bxq2011hust bxq2011hust self-assigned this May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants