Wire up settlement engine and indexer in API main.go

[dotunv]

Description

The API server's main.go creates the settlement engine and indexer but assigns them to blank identifiers, meaning they are never actually used:

File: cmd/api/main.go (lines 119, 122)

_ = engine  // settlement engine
_ = idx     // indexer

Impact

• Settlement engine is never initialized
• Indexer never starts syncing
• These subsystems are completely dead in the API process

Proposed Fix

Wire up the engines properly:

1. Initialize settlement engine with required dependencies
2. Start indexer as a background goroutine
3. Ensure graceful shutdown

Acceptance Criteria

• Settlement engine is properly initialized
• Indexer starts syncing in the background
• Both shut down gracefully on server stop
• No blank identifier assignments remain

Labels

bug backend

[Hafgans-oss]

Hi! I'd love to work on this issue. I've reviewed the description and acceptance criteria, and I'm confident I can deliver a high-quality solution. I'll ensure all acceptance criteria are fully met, thoroughly test the implementation, and submit a clean, well-documented PR. I'd appreciate it if you could assign this issue to me. Thank you!

[Okorie2000-code]

Hi Maintainer, I'd love to work on this issue. I understand the requirements and will submit a clean, well-tested PR within 24hrs. Please assign it to me

[retkatmun]

Hi,

I’m a full-stack software engineer with experience building scalable web apps, backend systems,

I’d love to work on this issue. I’ve reviewed the requirements and have a clear implementation plan to deliver a clean, well-tested solution that meets all acceptance criteria and aligns with the project’s standards.

I can start immediately and provide timely updates throughout the implementation.

[Babigdk]

Hi! I'd like to work on this issue.

I have experience with Go backend services, background workers, and graceful shutdown patterns. I'll wire the settlement engine and indexer into the application lifecycle, start the indexer as a background goroutine, ensure both components shut down cleanly with the server, remove the unused blank identifier assignments, and add any necessary validation to ensure the integration is reliable. I'll submit a clean, well-tested PR that satisfies all the acceptance criteria.