Scheduling, privacy and limits

Scheduling, privacy and limits for sigstar. Collect market, on-chain, news and macro data, and explain, forecast and alert on crypto price moves from every…

sigstar run is safe to repeat. Daily at 00:30 UTC, after the day's candles close:

cron (crontab -e; cron uses the machine's time zone, so adjust the hour):

30 0 * * * cd /home/you/my-sigstar && /home/you/.local/bin/sigstar run >> sigstar.log 2>&1

Put SIGSTAR_FRED_API_KEY=... on its own line above it if you use FRED.

systemd (user units): ~/.config/systemd/user/sigstar.service

[Unit]
Description=sigstar daily run

[Service]
Type=oneshot
WorkingDirectory=%h/my-sigstar
EnvironmentFile=-%h/.config/sigstar.env
ExecStart=%h/.local/bin/sigstar run

and ~/.config/systemd/user/sigstar.timer

[Unit]
Description=Run sigstar daily

[Timer]
OnCalendar=*-*-* 00:30:00 UTC
Persistent=true

[Install]
WantedBy=timers.target

then systemctl --user enable --now sigstar.timer. Keep keys in ~/.config/sigstar.env (chmod 600), one NAME=value per line.

Privacy and limits

• No telemetry: dlt's and dbt's anonymous usage statistics are switched off; sigstar itself reports nothing anywhere.
• First-run history is bounded by the sources: Binance open interest goes back 30 days, OKX funding about three months, GDELT three months, Kraken 720 candles. History beyond that builds up as you keep running sigstar.
• 90 days is a short sample. Correlations, Granger tests, regimes and backtests on it are rough; the outputs say so.
• Prices from USDT venues (Binance) are not converted to USD; the cross-venue spread uses USD venues only.
• GDELT sometimes refuses requests even at its published pace (on 2026-10-21 it refused most of them); a skipped GDELT stream is caught up on a later run, and days where GDELT itself had an outage are blanked rather than counted as zero coverage.
• Postgres is not a target in this version: the dbt models use DuckDB SQL (regular expressions, max_by, generate_series, ATTACH), and the chainstar link is a DuckDB file. A chainstar warehouse in Postgres is not read yet.