It covers:

• health endpoints
• websocket reconnect expectations
• real Algorand signer readiness
• the small smoke command

Health Endpoints

• API: http://127.0.0.1:4001/api/v1/health
• Messaging: http://127.0.0.1:4026/health
• Payments: http://127.0.0.1:4027/health
• Dev signer: http://127.0.0.1:4591/health

Messaging Health

The messaging health payload now reports:

• database readiness
• websocket path
• connected account count
• total open sockets

Payments Health

The payments health payload now reports:

• database readiness
• messaging dependency reachability
• signer dependency reachability
• Algorand mode / chain / asset configuration
• ready for real transfer execution

ok reflects local service health.

ready reflects whether the configured real-transfer path is usable.

Recommended Local Env

Set these in local development when testing real Algorand transfers:

• MESSAGING_SERVICE_URL=http://localhost:4026
• PAYMENTS_SERVICE_URL=http://localhost:4027
• PAYMENTS_ALGORAND_MODE=TESTNET_SIGNER
• ALGOD_TESTNET_URL=https://testnet-api.algonode.cloud
• ALGORAND_SIGNER_URL=http://127.0.0.1:4591/sign/algorand/payment
• ALGORAND_SIGNER_MNEMONIC=...

Never commit a real mnemonic.

Dev Signer Notes

The dev signer is still a deliberate trust boundary for local/test usage.

For payment signing it now:

• validates sender ownership against the configured mnemonic
• fetches live suggested params from algod
• builds a real Algorand payment transaction
• signs it
• returns signed bytes to svc-payments

Websocket Recovery Expectations

The web live connection now:

• reconnects with exponential backoff
• retries on browser online
• retries on focus
• retries when the tab becomes visible again

The call shell now revalidates the active call when the websocket transport reopens.

Smoke Command

Run:

npm run smoke:messaging-payments

Optional real-transfer readiness mode:

MESSAGING_PAYMENTS_SMOKE_EXPECT_SIGNER=1 npm run smoke:messaging-payments

The smoke script validates:

• API health
• messaging health + realtime stats
• payments health + database readiness
• signer health when explicitly expected

Real Transfer Checklist

1. Start the dev signer:

npm run signer:dev

2. Start the platform services.
3. Confirm svc-payments /health reports ready: true.
4. Bind the sender wallet address to the same address derived from the signer mnemonic.
5. Run a small DM transfer and confirm:
   • thread shows payment_intent -> payment_pending -> payment_confirmed
   • payments table has a real transaction id
   • sender/recipient notifications are emitted