跳到主要内容

Known Issues

This document lists known issues for the Chia Gaming system, organized by developer and user-facing concerns.

Troubleshooting

If you're experiencing issues not listed here, or need help resolving these known issues, see the Troubleshooting Guide for detailed solutions and workarounds.

Developer Issues

Common Setup Issues

IssueSolution
Old Docker VersionInstall Docker via Snap instead of apt to ensure you get the latest stable version.
Docker PermissionsDocker often installs with root privileges. To allow your user to run Docker commands without sudo:
1. Run: sudo usermod -aG docker $USER
2. Run: newgrp docker
3. Reattempt the image build or command.

Easy Developer Configuration Not Available

The easy developer configuration is still in development. Currently, developers must manually update various parameters in the codebase before building and deploying.

Workaround: See the Manual Configuration section in the Developers Guide for detailed instructions on how to manually configure network settings, WalletConnect project info, ports, and domain.

User-Facing Issues

UI/UX Issues

  • "Generate Room" button is light-gray on medium-gray: The button may be difficult to see due to low contrast between the button color and background.

  • UX has limited information regarding what is happening during handshake: The interface will be improved to provide better feedback about the current state of operations, particularly during handshaking and connection processes.

Gameplay Issues

  • Funds left on-chain after shutdown: When using a live WalletConnect instance, funds will be left on-chain after shutdown. Upon shutdown, a new game is created, leading to one game's worth of funds being left on-chain and not returned to users. For example, if the game stake is 10 mojo, then 10 mojos will remain on-chain after shutting down the session (once per lobby not per game). Use the simulator for development to avoid this issue. This is a high priority issue which we are working to fix ASAP.

  • When you leave the game, both sides have to keep browser open until shutdown completes: Both players must keep their browsers open until the shutdown process completes. Closing the browser prematurely may cause issues.

  • Chia Wallet does not raise to the foreground when a WalletConnect auth dialog appears: The chia reference wallet will be updated to automatically come to the foreground when authentication is required, but this does not currently occur. Users need to manually bring the wallet application to the foreground.

  • Save and load/reload is not functional: Game sessions are not persisted. If a user refreshes their browser or clears browser storage (localStorage, cache, etc.), the game session will be lost and a new session will need to be created. This can lead to lost funds if a session is interrupted during gameplay.

Performance Issues

  • Handshaking on-chain takes a long time: Before the game starts, 3 nodes (player wallet nodes and coinset.org) have to observe 2 on-chain transactions (in order). The lobby will take a long time to appear for Bob (Player 2). This is expected behavior due to blockchain confirmation requirements, but the wait time can be significant.

  • Game server and lobby server interaction: The current implementation of how the game server and lobby server interact may have performance limitations. This connection may be refactored in future versions to improve performance and scalability.