So you're saying the burn ledger handles 999 blocks no problem, so I gotta ask - when you're running 10k+ profiles through this thing, how much does that 30 min cooldown actually tank your wall-clock time? Like, are we talking negligible or are users waiting forever? And here's the thing that's bugging me - does that JSON-LD schema ever fall out of sync with the live profile, like after someone switches jobs? Because if it does, how stale is too stale? Google's crawler can be days or even months behind, so you could end up shoving outdated employer data at your users, which is kinda sketchy. And the Go TLS client is fire, but it sounds like you're manually babysitting it every time linkedIn pushes new cipher suites to their edge. So you got some auto-detect magic under the hood, or have you just accepted that this is gonna be a maintenance headache you gotta deal with?