You can't solve provenance with a database. A database has an owner, and an owner can be asked — or paid — to change a record. That's not a bug in someone's implementation. It's the entire category.

A chain changes the question. The ledger is append-only and public, so the receipt either exists or it doesn't, and no single party gets to rewrite it. When the stakes are "is this video real," that's the only kind of record worth trusting.

database:  "trust us, this record is intact"
chain:     "verify it yourself, it's all public"

the anchor is the point

Each day's receipts fold into one merkle root that anchors on chain. That one number is all it takes to verify every receipt from that day — cheap, permanent, and checkable by anyone.

Provenance isn't a storage problem. It's a trust problem. And trust, once you need it to survive an adversary, is a chain problem.