Development Announcements

There is one thing that can't be faked: a long, public, technically coherent development history.

That is why public GitHub provenance matters.

The public sporeproject GitHub organization currently shows three repositories: spore-frontend, spore-api, and spore-ipfs. The frontend alone shows 727 commits and 12 forks. The API shows 54 commits. The IPFS repo shows 10 commits. Taken together, that is at least 791 visible commits spread across app, backend, and infrastructure work.

This is not the footprint of a last-minute edition. The visible frontend history goes back at 19th March, 2021, then continues through 2022, 2023, 2024, and into 2025 (and soon 2026 will be updated). The commit log also shows merge activity and multiple contributor accounts, including florez-alberto, ismae147, and juslin03. That kind of multi-year, multi-contributor trail is exactly what real software provenance looks like in public.

Here is the core reason that matters. GitHub explains that every commit receives a unique SHA, or hash, identifying the specific changes, when they were made, and who created them. The Git manual is even more direct: because the object name is computed from the contents of the commit, a commit cannot change without its name changing too.

In plain English, that means a public commit history is not just a story someone tells. It is a chain of cryptographic identifiers tied to actual repository state. Once a project has accumulated years of commits, merges, and references, nobody can quietly swap in a different history and still claim it is the same one. A new history can be created, but it will be a different history, because the commit IDs change. GitHub’s documentation explicitly states that even changing a commit message creates a new commit ID.

Never forget "crypto" is for cryptography, those beautiful hashes that secure the provenance of the world.

In the following weeks we will be rolling out an updated website code, using modern infraestructure. We have moved the servers to a local development using a proxy VPS server so our services stay online reliably for decades to come.

The database is currently being populated to finally ship our burn analytics. Things are in motion on the background again.

Kind regards,

THE SPORE SURVIVORS