Godot: sistema de turnos con fases commit/reveal (integración Soroban)

[leocagli]

Objetivo

Implementar el sistema de turnos con las fases Commit → Reveal → Resolve integradas con el flujo ZK del contrato Soroban existente.

Alcance

• Autoload TurnManager con máquina de estados de fases
• Fases: COMMIT (el jugador envía acción cifrada), REVEAL (revela clave), RESOLVE (aplica resultado on-chain)
• Integración con funciones del contrato contracts/src/lib.rs: init_game, commit_action, reveal_action, finalise_turn
• Botón "Finalizar turno" en HUD que dispara la fase correcta
• Ejecución de turno de bots (aleatoria / IA simple en primer sprint)
• Señales emitidas al EventBus en cada cambio de fase

Skill de referencia

/godot-turn-system

Tareas

• Crear autoloads/TurnManager.gd con enum Phase y var current_phase
• Métodos begin_commit(), submit_commit(hash), begin_reveal(), submit_reveal(key), resolve()
• Conectar submit_commit / submit_reveal con JavaScriptBridge (ver #godot-web-bridge)
• Lógica de turno de bot: recopilar acciones aleatorias y llamar a commit_action vía bridge
• Botón "Fin de turno" en HUD que llama TurnManager.begin_commit()
• Emitir EventBus.turn_phase_changed(phase) en cada transición

Aceptación

Una partida completa de 3 turnos finaliza sin errores, las transacciones Soroban se invocan en orden correcto y el estado on-chain refleja las acciones del jugador.

🎁 Evidencia = reward mayor

• Si tu PR incluye capturas de pantalla mostrando esto andando end to end, entra a reward de GrantFox en esta issue.
• Si además sumás un video demo corto, califica para reward mayor.
• No es obligatorio, pero pesa mucho en la evaluación.

Qué conviene mostrar en esta issue:

• Video corto de una partida de 3 turnos completa donde se ve el HUD pasando por COMMIT, REVEAL y RESOLVE cada vez que apretás "Fin de turno".
• Captura del indicador de fase en pantalla junto a la consola de Godot con los EventBus.turn_phase_changed emitidos en orden.
• Captura del estado on-chain o del explorador de Stellar mostrando init_game, commit_action, reveal_action y finalise_turn invocados en la secuencia correcta.

Pegá las capturas directo en la descripción del PR, arrastrándolas al cuadro de texto de GitHub.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[leocagli]

🟢 Reopened for assignment. The only interest so far was from accounts flagged for automated mass-claiming (gloskull). This issue is open — comment /assign to take it.

[leocagli]

🟢 Reopened for assignment. The only interest so far was from accounts flagged for automated mass-claiming (gloskull). This issue is open — comment /assign to take it.

[Vinaystwt]

I can take this.

I’ll implement the Godot-side turn phase state machine for COMMIT → REVEAL → RESOLVE, using TurnManager and the existing WebBridge/EventBus direction so commit and reveal actions are routed through the browser/Soroban bridge instead of being hardcoded into UI nodes.

I’ll add methods like begin_commit, submit_commit, begin_reveal, submit_reveal, and resolve, emit phase-change signals on every transition, and keep the payload shape documented for init_game, commit_action, reveal_action, and finalise_turn. I’ll keep this focused on the turn-flow integration and avoid unrelated gameplay systems.

[grantfox-oss]

🦊 GrantFox — @Vinaystwt has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #35)
2. Your PR will be reviewed by the Bitcoindefi maintainers

Good luck! Track your progress on GrantFox.

[rupesh-kumar-sah]

Hello @maintainers,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Implement Godot: sistema de turnos con fases commit/reveal (integración Soroban) with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Testing: Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.

I am ready to start immediately—please assign this to me!