CSR
Centerspace
stock NYSE

As I use Keystone, I got AI to review the actual code, it looks good:

# Keystone3 Firmware RNG Security Analysis
## Executive Summary
The Keystone3 firmware has a **robust, multi-source RNG architecture** that is **significantly more secure** than the Coldcard RNG vulnerability (which affected Coldcard Mk2/Mk3 v4, Mk4, Q, and Mk5 devices). The Keystone implementation uses **three independent hardware RNG sources XORed together**, making it resistant to the class of vulnerabilities that affected Coldcard.
However, there are **several security concerns** worth noting:
---
## 1. RNG Architecture (Good)
The Keystone firmware implements a strong `random_buffer()` in `src/managers/keystore.c`:
```c
void random_buffer(uint8_t *buf, size_t len) {
TrngGet(buf, len); // MCU hardware TRNG
SE_GetDS28S60Rng(tempBuf1, len); // DS28C50 secure element
SE_GetAtecc608bRng(tempBuf2, len); // ATECC608B secure element
for (size_t i = 0; i < len; i++) {
buf[i] ^= tempBuf1[i] ^ tempBuf2[i]; // XOR all three
}
}
```
This is a **defense-in-depth** approach: even if one source is compromised, the XOR with the other two maintains entropy.
### RNG Sources Used Across the Firmware:
| Location | RNG Used | Purpose |
|----------|----------|---------|
| `keystore.c::random_buffer()` | TRNG ⊕ DS28C50 ⊕ ATECC608B | Wallet entropy, key generation |
| `drv_trng.c::TrngGet()` | MCU hardware TRNG | Nonces, AES IVs, encryption keys |
| `drv_atecc608b.c::Atecc608bGetRng()` | ATECC608B hardware RNG | SE operations, encrypted reads/writes |
| `slip39.c` | `random_buffer()` (overridden) | Shamir secret splitting |
| `data_parser_task.c` | `TrngGet()` | ECDH private keys for USB pairing |
---
## 2. Critical Difference from Coldcard Vulnerability
The **Coldcard vulnerability** (Block/Coinkite, July 2026) was caused by:
- `MICROPY_HW_ENABLE_RNG` defined as `0`, disabling hardware RNG
- Libngu's `#ifndef` check passed (macro exists, but value is 0)
- Fell back to a **deterministic Yasmarang PRNG** seeded from UID + timer
- Secure-element reseed only updated 32 bits of state
**Keystone does NOT have this vulnerability** because:
- It does not use MicroPython or libngu
- It directly calls hardware TRNG peripherals
- It never has a software PRNG fallback path
- The `mh_rand.c` LCG is explicitly guarded by `#ifndef RAND_PLATFORM_INDEPENDENT` and is only for testing
---
## 3. Security Concerns Found
### 3.1 Trezor Crypto RNG Comment (Low Risk — Mitigated)
The file `src/crypto/slip39/trezor-crypto/rand.c` contains:
```c
#pragma message("NOT SUITABLE FOR PRODUCTION USE! Replace random32() function with your own secure code.")
static uint32_t seed = 0; // LCG with zero initial seed
```
**However**, Keystone overrides the weak `random_buffer()` via the `__attribute__((weak))` mechanism in `keystore.c`. In production builds (`#ifndef COMPILE_SIMULATOR`), the strong triple-RNG version is used. **This is a documentation/code hygiene issue, not an active vulnerability.**
### 3.2 MCU TRNG: No Health Checks
The `TrngGet()` function in `drv_trng.c` simply reads from the TRNG data register:
```c
void TrngGet(void *buf, uint32_t len) {
for (uint32_t i = 0; i < len; i += 16) {
TRNG_Start(TRNG0);
while (0 != TRNG_Get(buf4, TRNG0)); // Wait for S128
memcpy((uint8_t *)buf + i, buf4, 16);
}
}
```
- The TRNG does have an **attack detection flag** (`RNG_CSR_ATTACK`), but it is **not checked** in the production `TrngGet()` path
- If the TRNG detects an attack, the data may be invalid but is still returned
- The `mh_rand.c` does have `mh_trand_buf_attack_get()` but it's not wired into the main entropy flow
**Risk**: If the MCU TRNG is under attack (e.g., voltage glitching), corrupted random data could be used.
### 3.3 Dice Roll Validation is Heuristic
The dice roll feature validates entropy quality with:
- Minimum length check (50 for 128-bit, 100 for 256-bit)
- Maximum frequency check: no single digit > 30% of total rolls
This is a **statistical heuristic**, not cryptographic validation. A user who deliberately inputs biased rolls (e.g., "111111...") would be caught, but the validation is not rigorous (e.g., no chi-squared test, no NIST SP 800-22 compliance).
### 3.4 Slip39 Uses `random_buffer()` for Shamir Shares
`slip39.c` calls `random_buffer()` for Shamir secret splitting:
```c
random_buffer(tempShare[i], enMasterSecretLen);
```
This is OK because Keystone overrides the weak RNG. But if a build configuration accidentally uses the platform-independent (weak) version, Shamir shares would be predictable.
### 3.5 No Periodic Re-seeding
The RNG does not periodically re-seed. Once initialized, the TRNG continues producing data, but there's no mechanism to detect TRNG degradation over the device's lifetime.
---
## 4. Comparison: Keystone vs Coldcard RNG
| Aspect | Keystone3 | Coldcard (vulnerable) |
|--------|-----------|----------------------|
| Primary RNG | MCU TRNG + 2 SE chips | STM32 hardware RNG (disabled in fallback) |
| Fallback | None | Deterministic Yasmarang PRNG |
| Entropy sources | 3 independent hardware sources | 1 (when working) |
| RNG composition | XOR of 3 sources | Single source or fallback |
| Re-seed mechanism | Not needed (always hardware) | 32-bit reseed (weak) |
| Attack detection | Present but not enforced | None in fallback path |
| Software PRNG risk | None (overridden) | **Critical** (deterministic) |
---
## 5. Recommendations
1. **Enforce TRNG attack detection**: Check the `RNG_CSR_ATTACK` flag in `TrngGet()` and refuse to return data if an attack is detected.
2. **Add NIST SP 800-22 statistical tests**: Run periodic self-tests on RNG output to detect degradation.
3. **Remove or clearly mark the weak LCG**: The trezor-crypto `rand.c` should be excluded from production builds via build flags, not just relied upon to be overridden.
4. **Add entropy health monitoring**: Periodically verify that all three RNG sources are producing valid entropy.
5. **Improve dice roll validation**: Add a proper statistical test (chi-squared, runs test) rather than just frequency checks.
---
## Conclusion
**The Keystone3 firmware does NOT suffer from the Coldcard RNG vulnerability.** Its triple-source hardware RNG design is fundamentally different and more secure. The primary RNG path in production always uses hardware entropy from three independent sources. The known weak RNG code (trezor-crypto LCG) is only used in simulator/test builds and is overridden in production.
The main remaining concerns are:
- TRNG attack detection not enforced in the production path
- No periodic self-testing of RNG health
- Heuristic-only dice roll validation
These are **defense-in-depth improvements** rather than critical vulnerabilities.

Yeah these people hanging on to morals should sit out of investing lol. Or idk invest in a CSR index or smn

As I use Keystone, I got AI to review the actual code, it looks good:

# Keystone3 Firmware RNG Security Analysis
## Executive Summary
The Keystone3 firmware has a **robust, multi-source RNG architecture** that is **significantly more secure** than the Coldcard RNG vulnerability (which affected Coldcard Mk2/Mk3 v4, Mk4, Q, and Mk5 devices). The Keystone implementation uses **three independent hardware RNG sources XORed together**, making it resistant to the class of vulnerabilities that affected Coldcard.
However, there are **several security concerns** worth noting:
---
## 1. RNG Architecture (Good)
The Keystone firmware implements a strong `random_buffer()` in `src/managers/keystore.c`:
```c
void random_buffer(uint8_t *buf, size_t len) {
TrngGet(buf, len); // MCU hardware TRNG
SE_GetDS28S60Rng(tempBuf1, len); // DS28C50 secure element
SE_GetAtecc608bRng(tempBuf2, len); // ATECC608B secure element
for (size_t i = 0; i < len; i++) {
buf[i] ^= tempBuf1[i] ^ tempBuf2[i]; // XOR all three
}
}
```
This is a **defense-in-depth** approach: even if one source is compromised, the XOR with the other two maintains entropy.
### RNG Sources Used Across the Firmware:
| Location | RNG Used | Purpose |
|----------|----------|---------|
| `keystore.c::random_buffer()` | TRNG ⊕ DS28C50 ⊕ ATECC608B | Wallet entropy, key generation |
| `drv_trng.c::TrngGet()` | MCU hardware TRNG | Nonces, AES IVs, encryption keys |
| `drv_atecc608b.c::Atecc608bGetRng()` | ATECC608B hardware RNG | SE operations, encrypted reads/writes |
| `slip39.c` | `random_buffer()` (overridden) | Shamir secret splitting |
| `data_parser_task.c` | `TrngGet()` | ECDH private keys for USB pairing |
---
## 2. Critical Difference from Coldcard Vulnerability
The **Coldcard vulnerability** (Block/Coinkite, July 2026) was caused by:
- `MICROPY_HW_ENABLE_RNG` defined as `0`, disabling hardware RNG
- Libngu's `#ifndef` check passed (macro exists, but value is 0)
- Fell back to a **deterministic Yasmarang PRNG** seeded from UID + timer
- Secure-element reseed only updated 32 bits of state
**Keystone does NOT have this vulnerability** because:
- It does not use MicroPython or libngu
- It directly calls hardware TRNG peripherals
- It never has a software PRNG fallback path
- The `mh_rand.c` LCG is explicitly guarded by `#ifndef RAND_PLATFORM_INDEPENDENT` and is only for testing
---
## 3. Security Concerns Found
### 3.1 Trezor Crypto RNG Comment (Low Risk — Mitigated)
The file `src/crypto/slip39/trezor-crypto/rand.c` contains:
```c
#pragma message("NOT SUITABLE FOR PRODUCTION USE! Replace random32() function with your own secure code.")
static uint32_t seed = 0; // LCG with zero initial seed
```
**However**, Keystone overrides the weak `random_buffer()` via the `__attribute__((weak))` mechanism in `keystore.c`. In production builds (`#ifndef COMPILE_SIMULATOR`), the strong triple-RNG version is used. **This is a documentation/code hygiene issue, not an active vulnerability.**
### 3.2 MCU TRNG: No Health Checks
The `TrngGet()` function in `drv_trng.c` simply reads from the TRNG data register:
```c
void TrngGet(void *buf, uint32_t len) {
for (uint32_t i = 0; i < len; i += 16) {
TRNG_Start(TRNG0);
while (0 != TRNG_Get(buf4, TRNG0)); // Wait for S128
memcpy((uint8_t *)buf + i, buf4, 16);
}
}
```
- The TRNG does have an **attack detection flag** (`RNG_CSR_ATTACK`), but it is **not checked** in the production `TrngGet()` path
- If the TRNG detects an attack, the data may be invalid but is still returned
- The `mh_rand.c` does have `mh_trand_buf_attack_get()` but it's not wired into the main entropy flow
**Risk**: If the MCU TRNG is under attack (e.g., voltage glitching), corrupted random data could be used.
### 3.3 Dice Roll Validation is Heuristic
The dice roll feature validates entropy quality with:
- Minimum length check (50 for 128-bit, 100 for 256-bit)
- Maximum frequency check: no single digit > 30% of total rolls
This is a **statistical heuristic**, not cryptographic validation. A user who deliberately inputs biased rolls (e.g., "111111...") would be caught, but the validation is not rigorous (e.g., no chi-squared test, no NIST SP 800-22 compliance).
### 3.4 Slip39 Uses `random_buffer()` for Shamir Shares
`slip39.c` calls `random_buffer()` for Shamir secret splitting:
```c
random_buffer(tempShare[i], enMasterSecretLen);
```
This is OK because Keystone overrides the weak RNG. But if a build configuration accidentally uses the platform-independent (weak) version, Shamir shares would be predictable.
### 3.5 No Periodic Re-seeding
The RNG does not periodically re-seed. Once initialized, the TRNG continues producing data, but there's no mechanism to detect TRNG degradation over the device's lifetime.
---
## 4. Comparison: Keystone vs Coldcard RNG
| Aspect | Keystone3 | Coldcard (vulnerable) |
|--------|-----------|----------------------|
| Primary RNG | MCU TRNG + 2 SE chips | STM32 hardware RNG (disabled in fallback) |
| Fallback | None | Deterministic Yasmarang PRNG |
| Entropy sources | 3 independent hardware sources | 1 (when working) |
| RNG composition | XOR of 3 sources | Single source or fallback |
| Re-seed mechanism | Not needed (always hardware) | 32-bit reseed (weak) |
| Attack detection | Present but not enforced | None in fallback path |
| Software PRNG risk | None (overridden) | **Critical** (deterministic) |
---
## 5. Recommendations
1. **Enforce TRNG attack detection**: Check the `RNG_CSR_ATTACK` flag in `TrngGet()` and refuse to return data if an attack is detected.
2. **Add NIST SP 800-22 statistical tests**: Run periodic self-tests on RNG output to detect degradation.
3. **Remove or clearly mark the weak LCG**: The trezor-crypto `rand.c` should be excluded from production builds via build flags, not just relied upon to be overridden.
4. **Add entropy health monitoring**: Periodically verify that all three RNG sources are producing valid entropy.
5. **Improve dice roll validation**: Add a proper statistical test (chi-squared, runs test) rather than just frequency checks.
---
## Conclusion
**The Keystone3 firmware does NOT suffer from the Coldcard RNG vulnerability.** Its triple-source hardware RNG design is fundamentally different and more secure. The primary RNG path in production always uses hardware entropy from three independent sources. The known weak RNG code (trezor-crypto LCG) is only used in simulator/test builds and is overridden in production.
The main remaining concerns are:
- TRNG attack detection not enforced in the production path
- No periodic self-testing of RNG health
- Heuristic-only dice roll validation
These are **defense-in-depth improvements** rather than critical vulnerabilities.

Yeah these people hanging on to morals should sit out of investing lol. Or idk invest in a CSR index or smn

you can be banned by your brokerage and forcibly evicted ( yes, that can happen - you can for example be rude with CSR on the phone and get kicked out for life ) ... having non-portable proprietary mutual funds in taxable account will result in forced sell ... if you are so paranoid about expense rations , then FXAIX is portable and has 0.015% ...

# Today is Monday, the 3rd of August
## Upcoming events for Monday, August 3rd
- Stock splits:
- KWM @ **1:30**
- LEXX @ **1:15**
- LBGJ @ **1:200**
- MVIS @ **1:15**
- PMI @ **1:50**
- SEGG @ **1:7**
- TOP @ **1:5**
- WETO @ **1:100**
- Expected earnings:
ABTC, ADEA, ADTN, ADUS, AEIS, AESI, AHRT, ALG, ALSN, ALX, AMRC, ANDE, ARE, ARTNA, ATLX, AVA, BCBP, BCC, BLZE, BRCC, BSM, BWXT, CBT, CGEN, CHRN, CLLS, CLPT, CLX, CNA, CNH, CRD.A, CRD.B, CRGY, CRSP, CSR, CSWC, CTNT, CTOS, CURR, CVGI, DAC, DDD, DEA, DHC, DORM, EC, ECHO, ELOX, EVER, FANG, GBDC, GECC, GLRE, GPOR, GRAB, GRFS, HESM, HIT, HLMN, HSTM, IBTA, ICHR, IIPR, INHD, INSP, INVX, IRT, IVT, JAZZ, JBTM, JELD, JRVR, JXN, KOS, KRYS, L, LIFE, LIND, MAR, MATX, MED, MMYT, MTUS, MUFG, MYPS, NJR, NMFC, NSPR, OKE, ON, OPAD, OTTR, PAY, PLOW, PLTR, POWL, PPLI, PRAX, PRTA, RAIL, SBAC, SBH, SBRA, SIBN, SITC, SNAP, SOHU, SRAD, STOK, STRL, TDW, TGTX, TKO, TSN, TTI, TWST, UCTT, UFCS, UFPT, UTL, VERX, VMD, VNO, VNOM, VOYG, VRTX, VTS, VVX, WGS, WHR, WMB, ZEPP
- Ex-div:
AMUN, ANGL, ASRV, BALQ, BCLO, BEDY, BGRN, BKMI, BKMS, BMOP, BND, BNDP, BNDW, BNDX, BREM, BRHY, BRTR, BSRR, CAIQ, CALI, CANQ, CLOA, CPIX, CPLS, CZNC, DMLP, EFSI, EMB, EWBC, EYEG, FALN, FIMU, FSBC, FSTB, GGAL, GNMA, GPIQ, GPIX, GPRF, HAFC, HBCP, HIFS, HYXF, IBGA, IBGB, IBGC, IBGK, IBGL, IBGM, IBTG, IBTH, IBTI, IBTJ, IBTK, IBTL, IBTM, IBTO, IBTP, IBTQ, IBTR, IEF, IEI, IGIB, IGSB, IQQQ, ISTB, IUSB, JEPQ, LSBK, MBB, MPB, MULT, MYCF, MYCG, MYCH, MYCI, MYCJ, MYCK, MYCL, MYCM, MYCN, MYCO, MYHA, MYHB, MYHC, MYHD, MYHE, MYMF, MYMG, MYMH, MYMI, MYMJ, MYMK, NCPB, NPFI, NUSB, NVEC, OVLY, OZKAP, PCMM, PCPI, PEBO, PFF, PLBC, PMBS, QQQT, ROCQ, ROCY, SATA, SHY, SKOR, SLQD, SUSB, SUSC, TAXI, TAXS, TAXT, TLT, USFI, USIG, VBCA, VBCB, VBCC, VBCD, VBCE, VBCF, VBCG, VBCH, VBCI, VBCJ, VBIL, VCIT, VCLT, VCRB, VCSH, VGIT, VGLT, VGSH, VGUS, VMBS, VPLS, VTC, VWOB, WABC, WABF, YBST, YBTY, YLDE
- Economic events and announcements:
- OPEC Meeting
## Upcoming events for Tuesday, August 4th
- Stock splits:
- AEMD @ **1:5**
- SBLRF @ **1:10**
- SUTNY @ **8:5**
- Expected earnings:
ACAD, ACEL, ACIU, ACNT, ACRE, ADM, AFG, AGNT, AHCO, AIN, AISP, AIZ, ALAB, ALGT, ALIT, AMBO, AMD, AME, AMGN, AMWL, ANET, ANGI, ANGX, ANY, AOMR, APO, APPS, APTV, AQB, ARDT, ARI, AROC, ARVN, ARWR, ASST, ATEC, ATKR, ATOM, AUDC, AZTA, BALL, BBBY, BBIO, BEAM, BIO, BIO.B, BKNG, BL, BMEA, BNTX, BOLD, BOW, BP, BR, BRBR, BRKR, BRSL, BV, BXC, BXDC, BZFD, CACC, CALY, CAT, CBC, CC, CCEP, CCO, CE, CERT, CHCT, CHT, CIFR, CIX, CLDT, CMI, CMT, COGT, COMP, CPIX, CPNG, CRBG, CRBP, CRCT, CRDF, CRIS, CRNX, CTRI, CXDO, CYCN, DBRG, DD, DEI, DEO, DMRA, DOC, DOCN, DRCT, DRVN, DUK, DVA, DVN, EA, ECG, ECO, EGHT, EHTH, ELME, EMBJ, EMR, ENIC, ENLT, ENR, ENTG, EOG, EQH, ET, EVTC, EXPD, FBIN, FHTX, FIS, FLYW, FMS, FOA, FRPH, FRSH, FTEK, FTH, FTK, FULC, FWRG, GBTG, GGB, GIC, GILD, GLAD, GOSS, GPK, GPRK, GSM, GTE, GWW, GXO, HCKT, HL, HLNE, HNGE, HQ, HRMY, HRZN, HSIC, HUT, HVT, HVT.A, HY, IBRX, IDXX, IDYA, IE, IFF, IGIC, IMNN, INDV, INFU, INGR, INTA, IOSP, IPAR, IPGP, IPI, IQMX, IT, J, JAN, JBGS, KAI, KIDS, KIM, KMB, KNF, KODK, KPLT, LCID, LDI, LDOS, LGIH, LIME, LMAT, LMB, LPCN, LRN, LSCC, LTM, LUMN, MAC, MAT, MBC, MCD, MCY, MD, MEC, METC, METCB, MLAB, MLTX, MNTN, MOS, MPC, MPLX, MQ, MRK, MRP, MTCH, NAGE, NAKA, NCMI, NGL, NPO, NRG, NVCT, NVGS, NXDR, NXE, NXRT, OCUL, OGN, OGS, OLP, OPEN, OPLN, OR, OSPN, OZ, PACS, PAM, PARR, PCRX, PCTY, PEG, PFE, PGEN, PINS, PLMR, PLUS, PNW, PRCT, PRIM, PRKS, PRU, PSKY, PSNL, PSTL, PVLA, PW, Q, QLYS, RARE, RBA, RIGL, ROK, RRR, RSVR, RVLV, RVTY, RYAM, RYTM, SACH, SEAT, SEB, SGC, SGHC, SHLS, SKT, SKWD, SKY, SLAB, SLDP, SLRC, SMP, SNDX, SOPH, SPCX, SPOT, SQNS, SRTA, SSRM, STKS, STVN, SU, SUJA, SUN, SUNC, SUPN, SWIM, SYRE, SYY, TALK, TALO, TBI, TDC, TDG, THRY, TKR, TMDX, TNGX, TOST, TPB, TPG, TREX, TRNS, TRVG, TSEM, TSLX, TVTX, TX, TXO, TYGO, ULS, UONE, UONEK, UP, UPST, URG, USAC, USAU, USNA, VATE, VERA, VGNT, VOYA, VSAT, VTOL, W, WAT, WATT, WEYS, WHLR, WIX, WK, WLFC, WLK, WLKP, WOLF, WTRG, WTTR, WYNN, XGN, XMTR, ZBRA, ZETA
- Ex-div:
AMAL, BANR, CCEC, CIVB, FCCO, FIBK, IBCP, MNSB, ORRF, SATA, SRCE
- Economic events and announcements:
- 3-Month Bill Auction (previous: 3.815%)
- 6-Month Bill Auction (previous: 3.945%)
- Atlanta Fed GDPNow
- Construction Spending (consensus: 0.2%, previous: 0.1%)
- ISM Manufacturing Employment (previous: 49.7)
- ISM Manufacturing New Orders Index (previous: 56.0)
- ISM Manufacturing PMI (consensus: 54.0, previous: 53.3)
- ISM Manufacturing Prices (consensus: 70.0, previous: 73.0)
- Loan Officer Survey
- S&P Global Manufacturing PMI (consensus: 53.8, previous: 53.8)
## Upcoming events for Wednesday, August 5th
- Expected earnings:
AACG, AAUC, ABCL, ABUS, ACA, ACB, ACIC, ACT, ACTG, ADMA, ADNT, ADV, AEVA, AGBK, AGL, AIRG, AKA, AKBA, ALB, ALL, ALNT, ALTO, AMPL, AMPX, AMPY, ANAB, APA, APLE, APP, ARQT, ARRY, ARTV, ASMB, ASTE, ASYS, ATEN, ATNI, ATO, AUGO, AUST, AVT, AWR, AXON, BAM, BATRA, BATRK, BBD, BBDC, BBDO, BBSI, BCO, BCRX, BDSX, BGSF, BHR, BIOA, BKH, BLBD, BLLN, BLMN, BMBL, BROS, BTMD, BVS, BWA, BYND, CACI, CAI, CAPL, CARL, CCU, CDE, CDLX, CDRE, CDW, CENT, CENTA, CF, CG, CGNX, CHH, CHRD, CHRS, CHYM, CIM, CLFD, CLOV, CMP, CMPS, CNTX, COKE, COOK, COR, CPA, CPAY, CPRI, CPS, CRCL, CRL, CRTO, CRUS, CRVL, CSTE, CSV, CTKB, CVS, CW, CWEN, CWK, CXT, CXW, CYN, DASH, DAVE, DEC, DGII, DHT, DHX, DIBS, DIN, DIOD, DIS, DK, DKL, DLX, DOX, DT, DUOL, DXPE, EBAY, EBS, ECPG, ECVT, EE, EHC, ELA, ELAN, ELF, ELPC, EOLS, EOSE, EPC, ERII, ERO, ETSY, EVCM, EVEX, EVGO, EXEL, EXPE, EXTR, EYPT, EZPW, FG, FIG, FIP, FLNC, FLUT, FNF, FRPT, FSLY, FSM, FTCI, FUBO, FWRD, GBLI, GDRX, GENK, GERN, GFF, GFR, GFS, GILT, GLXY, GNK, GNL, GNW, GOOD, GPCR, GPMT, GPN, GRAL, GROY, GSL, GT, GTM, HBB, HCC, HDSN, HGTY, HHH, HLF, HLLY, HLX, HMC, HMH, HMN, HNNA, HNST, HONA, HP, HPP, HRTG, HST, HUBS, ICL, IEP, III, IMNM, INMD, INN, INSE, INSG, INTR, INTT, INVA, INVZ, IONQ, IRM, ITIC, JJSF, JOBY, KD, KHC, KLIC, KLTR, KLXE, KMPR, KMT, KNTK, KRMD, KRO, KROS, KVYO, KYMR, LAB, LAW, LB, LCII, LESL, LEU, LFCR, LFMD, LILA, LILAK, LINE, LIVN, LLY, LPG, LPX, LSF, LTBR, LTC, LZ, MATV, MBI, MCK, MCRB, MDLN, MELI, MET, MFA, MFC, MGEE, MGNI, MGY, MIAX, MIRM, MKSI, MLR, MNKD, MNTK, MRAM, MSI, MTDR, MTRN, MUR, MUSA, MUX, MWA, MYO, NAMS, NATL, NC, NEXA, NHP, NI, NICE, NINE, NL, NLOP, NMRA, NNBR, NNN, NOVT, NRP, NSLR, NTR, NVO, NVST, NWN, NWS, NWSA, NXL, NYT, NYXH, O, OBDC, OC, OCSL, OEC, OESX, OFIX, OGC, ONC, ONT, OPI, OPRT, ORA, OSS, OSUR, OTF, OUT, OXY, PACB, PAYC, PAYS, PCVX, PFX, PKOH, PNTG, PODD, POWI, PPBT, PR, PRGO, PRI, PRMB, PRSU, PSBD, PSX, PTGX, PTLO, PTRN, PULM, QGEN, QNTM, QTTB, RAMP, RAND, RCMT, RCUS, RDN, RDW, REI, RELY, REPX, RGLD, RIG, RIOT, RMR, ROCK, ROOT, RPC, RPRX, RRX, RUN, RVMD, RXRX, RXST, RYDE, RYN, SAFT, SATL, SBGI, SBLK, SCM, SD, SDGR, SEDG, SEER, SEG, SEI, SGHT, SGU, SHAK, SHOP, SII, SITM, SKM, SKYT, SM, SMA, SMR, SMRT, SMSI, SN, SNDK, SNES, SNEX, SOBO, SOLV, SOUN, SR, SRI, SRPT, SST, STAA, STE, SVC, SWX, SYM, TACT, TARS, TASK, TATT, TBLA, TDUP, TECH, TFPM, TGB, TKNO, TLN, TNC, TNYA, TPC, TPL, TPVG, TRDA, TRI, TRIN, TRMB, TRNO, TROX, TRUP, TS, TSAT, TTMI, TWFG, UBER, UGI, UHAL, UHAL.B, UMH, UPB, URGN, USPH, UTHR, UTI, UUUU, UVV, VAL, VCTR, VECO, VEL, VIAV, VIR, VNDA, VPG, VRDN, VRRM, VSEC, VSH, VVV, VYGR, VYX, WBI, WDC, WES, WMK, WTI, WTS, WULF, WW, XNCR, XNDU, XPEL, XPER, XPL, XRN, XYZ, YOU, Z, ZBH, ZG, ZIP, ZNTL, ZVIA, ZVRA
- Ex-div:
BPRN, HBANZ, HFWA, JMSB, NBBK, ONBPO, ONBPP, SATA, UVSP, WTBA
- Economic events and announcements:
- 52-Week Bill Auction (previous: 3.860%)
- API Weekly Crude Oil Stock (previous: 3.296M)
- Atlanta Fed GDPNow
- Durables Excluding Defense (consensus: 0.3%, previous: 0.3%)
- Durables Excluding Transport (previous: 0.6%)
- Exports (previous: 317.70B)
- Factory Orders (consensus: 0.0%, previous: -1.3%)
- Factory orders ex transportation (previous: 1.9%)
- IBD/TIPP Economic Optimism (consensus: 47.5, previous: 45.5)
- Imports (previous: 395.30B)
- JOLTS Job Openings (consensus: 7.420M, previous: 7.594M)
- Redbook (previous: 8.3%)
- Total Vehicle Sales (previous: 16.50M)
- Trade Balance (consensus: -73.00B, previous: -77.60B)
^^^^2026-08-03