Claude Project Tracker

What's pending across every project

8 open · sorted by priority then due-date

kind all blockers todos decisions notes

priority all urgent high low

Filtered by tag db clear

todo urgent

Close Cloud SQL to the internet: remove 0.0.0.0 authorized network and require SSL

Instance crypto-track-321e8b45 has a public IP (34.57.238.28), requireSsl=false (ALLOW_UNENCRYPTED_AND_ENCRYPTED), and an authorized network "for EV Connection" = 0.0.0.0 — effectively open to the internet with only the postgres password protecting it. Instance is shared with AdaptiveSAT, Vajra, CitrineOS, tracker. Coordinate with Vajra before removing the EV entry; prefer Cloud SQL connector/Auth Proxy for all clients.

security db infra

gcloud sql instances describe crypto-track-321e8b45

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: The database is effectively open to the internet: public IP, SSL optional, authorized network 0.0.0.0. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:08

todo urgent

Rotate the postgres superuser password and remove it from code

Password is committed/hardcoded in crypto538-core-service/config/production.yaml + staging.yaml, ml-core-service/main.py, and every CoinTrends_Python script (with the public DB IP). Rotation affects every service on the shared instance. Move to Secret Manager (db_password secret already exists) and read at runtime.

security secrets db

crypto538-core-service/config/production.yamlcrypto538-core-service/config/staging.yamlml-core-service/main.py::get_db_connectionCoinTrends_Python/*.py

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: The postgres superuser password is committed in several places and every service connects as that superuser. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:08

todo high

Create least-privilege DB users per service and a read-only analysis role

core-service, ml-core-service and web-service all connect as postgres superuser on a shared instance. Create e.g. cointrends_core (rw on CryptoTrack_Prod.dbo), cointrends_ml (read + prediction tables), cointrends_web (CryptoUserBilling_Prod), cointrends_ro (SELECT only, for analysis/Claude).

security db

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: There's no read-only database role, and every service connects as the superuser. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:09

todo high

Generalise per-asset hard-coding — prerequisite for stocks, commodities and indexes

Each coin has its own table family (pricedata, ohlcv, predictiondata, indicators, indicators_plus + view). Coin list is hard-coded in CASE statements in getcryptodata, getpricedataforcurrencies, getcurrencydetails, and in crypto_id == 1 or ... lists in ml-core-service and CoinTrends_Python. Design an asset-agnostic schema (asset master + long-format tables keyed by asset_id) and drive code from cryptomaster/asset master.

architecture db roadmap

dbo.getcryptodatadbo.getpricedataforcurrenciesdbo.getcurrencydetailsml-core-service/main.py::func

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: Coin-specific logic is hard-coded everywhere; adding any asset means editing many places by hand. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:09

todo

Use one shared DB connection pool in core-service instead of a new pool per call

getDbConnection() → connectWithConnector() builds a new sql.DB (and Cloud SQL dialer) on nearly every call, with defer db.Close(). Create one pool at startup and reuse it; set pool limits once.

performance core-service db

crypto538-core-service/main.go:570-650

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: A new connection pool is created on almost every call, instead of one shared pool. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:09

note

Users/billing live in CryptoUserBilling_Prod; market/ML data in CryptoTrack_Prod — both on shared instance crypto-track-321e8b45

Instance (POSTGRES_14, 1 vCPU / 3.75 GB, 20 GB) is shared with AdaptiveSAT, Vajra, CitrineOS and the tracker. Schema digests in the claude.ai CoinTrends project: claude/cointrends-db-schema-notes.md and claude/cointrends-architecture-notes.md.

db context

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: user lives in cryptouserbilling_prod claude: Got it — pulled that schema too; user, payment_details, user_reviews plus TypeORM bookkeeping.

10d ago
10-16 19:10

note

DB snapshot 2026-10-19: what's fresh and what stopped

Fresh (5-min): pricedata (~518k rows/coin since 2024-10-29), indicators, marketindex, metalsdata, predictiondata, pricedatacache. Stopped: OHLCV Mar/Apr 2025; tradingrecommendation 2025-03-26; cryptonews & feargreedindex 2025-10-03; gainers/losers/trending 2025-10-13; updatetracking last 2025-01-30 (so the retrain baseline is 20 months old); TON price 2026-06-17. Empty: predictionvsactual, predictiontracking. Slice master has 24 slices per coin (5..120 min) all flagged active with modelfile set, but only slice 24 (120 min) models exist in GCS and are used. Legacy usertable 8 rows, paymentdetails 5 rows.

db context data

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: I want you to access the database and query how the data looks like claude: Ran read-only queries via Cloud SQL export; summary of fresh vs stopped feeds.

💬 1 comment

7d ago
10-19 14:07

todo low

Clean up CryptoTrack_Prod junk and legacy objects

Duplicate public.getcryptodata variants, public.gainers_json, public.market_metal_data, dbo.table_1, dbo.table_2, dbo.debugtable, dbo.jsondatatowork; legacy dbo.usertable / dbo.paymentdetails / manageuserandpayments() (users now live in CryptoUserBilling_Prod). Check row counts and archive before dropping.

cleanup db

CoinTrends.ai · cointrends · by saravanan@scrumclaw.ai

from the conversationsaravanan: what are the issues you identified in cointrends? claude: The database carries MSSQL heritage: duplicate functions in public, junk tables, legacy usertable/paymentdetails. saravanan: create cointrends in tracker and push these items there

10d ago
10-16 19:10

What's pending across every project

Add an item