Wire Soroban contract stubs into vote submission and result tally

[grantfox-oss]

The roadmap marks Soroban smart contracts as complete
but the note reads "stub — correct stellar-sdk v12 APIs,
ready to wire." The contracts/ directory exists in core
with the correct Stellar SDK v12 API surface but no
contract calls are made from any route handler. The
public verifiability guarantee — that anyone can
independently verify a result on the Stellar ledger —
cannot be fulfilled until these stubs are wired in.

Scope:

• POST /api/votes — after a successful vote write,
  call record_vote on the Soroban contract and store
  the returned transaction ID against the vote record
• POST /api/results/:ballotId/tally — after tally
  computation, call finalise_result and store the
  transaction ID against the result record
• Surface the Stellar transaction ID on
  GET /api/results/:ballotId so the frontend can
  display it on the public verification page
• Both calls must fail gracefully — a Stellar network
  error must not roll back the vote or tally, mark
  the record as pending_anchor and queue a retry

Acceptance Criteria:

• record_vote called after every successful vote write
• finalise_result called after every successful tally
• Stellar transaction ID returned in results response
• Stellar failure marks record pending_anchor without
  rolling back the vote or tally
• SOROBAN_CONTRACT_ID read from environment —
  app logs a warning on startup if it is missing

[teethaking]

hello maintainer may i work on this issue?
ill submit PR within 1-3 days

[Krishna41357]

Hi! I'd like to take this one.
The contracts are already set up correctly, they're just not being called yet - so votes and results aren't actually anchored on Stellar, which means no one can independently verify them right now. I'll wire in record_vote after a vote is saved and finalise_result after a tally, store the transaction IDs, and surface them on the results endpoint.
If a Stellar call fails, I'll make sure the vote or tally itself is never rolled back - it'll just be marked pending_anchor and retried (I checked, there's no existing queue setup, so I'll add something lightweight). Also adding the startup warning for a missing SOROBAN_CONTRACT_ID.
Let me know if I can be assigned!

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.
My PR will be submitted in under 10hours.

[grantfox-oss]

🦊 GrantFox — @teethaking has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.