Project history

PadReset's repository is private, so there is no log you can read for yourself. This is the history that can be published: the milestones with their dates, in order, and with each one's proof a click away, so you do not have to take them on faith.

First public build

The site starts with the home, the guide and the download table in Spanish, English and Portuguese, and the model catalogue refreshing on every build. The sitemap, the llms.txt and the Imprímelo 247 credit ship the same day.

Check: Downloadllms.txtsitemap.xml

No more trust on faith

The download table adds each file's VirusTotal analysis, linked to its exact SHA-256: whoever downloads a binary can check for themselves what was scanned.

Check: Download

Privacy and headers

CSP, HSTS and our own security headers, and the privacy policy rewritten to explain Cloudflare's cookieless analytics. Privacy stops being a promise and becomes a description.

Check: Privacyrobots.txt

When software is not enough

The site stops assuming a reset fixes everything: a maintenance box with a chip keeps its own counter, and this software does not touch it. That is stated on Models, in the guide and in the FAQ, instead of being left for whoever already paid for the printer to discover.

Check: ModelsFAQGuide

Four languages

French arrives, with its own URLs and translated slugs, and the site goes from ES/EN/PT to the four languages it has today, with a complete hreflang cluster on every page.

Check: sitemap.xml

Downloads pinned to a version

The buttons stop pointing at “latest”: every link is pinned to the version that was scanned, tag included, so the file you download is the file that was checked.

Check: Download

Model index by letter

Alongside the search, the Models page publishes the whole database by letter, so the catalogue can be browsed with Ctrl+F even when the exact spelling of a model is unknown.

Check: Models

Gates and a verifiable deploy

The deploy aborts if headers, sitemap, structured data or meta descriptions drift from what is expected, CI runs the same command Cloudflare runs, and the site starts publishing the served commit in a header: since then the live deploy can be checked from outside.

Check: sitemap.xml

The read-only harness

ewr-safe.mjs ships: it identifies the printer, reads the counters, backs up the EEPROM and simulates the write, with the real write left to a person. It is served with its .sha256 and the build checks that the served copy is byte for byte the one that passed the tests.

Check: ewr-safe.mjsewr-safe.mjs.sha256Guide

Who answers, and what was reviewed

The site publishes the name and profile of the person who operates it, the date each link was last checked, the build stamp that verifies this evidence, and its terms of use. This is the reliability piece that had been missing from day one.

Check: AboutTerms of use

The report, not the number

The VirusTotal chips stop publishing an engine count and become a link to the public report for each file, looked up by its SHA-256. VirusTotal's public API is for non-commercial use only, and this site is published as a product of Imprímelo 247: rather than keep asserting someone else's drifting datum, the site publishes the hash —which does not change— and sends the reader to the source.

Check: Download

Binary verification, one step further

EWR v1.4.1 publishes a build-provenance attestation per archive: a signed statement (GitHub Artifact Attestations) that each file is byte for byte what its release workflow built, from the tag it names. The site checks it, pins EWR to v1.4.1 with the three hashes cross-checked against their attestation, and documents how to verify it with the GitHub CLI. v1.4.1 also fixes a bug that left the printer in firmware-update mode when resetting with v1.3.x and v1.4.0, and the warning goes in the table for anyone who already downloaded those versions.

Check: Download

The recommended app signs too

Epson Reset v1.0.3 signs and notarizes its macOS .dmg and, like EWR, publishes a build-provenance attestation: a signed statement that its seven files are byte for byte what the release workflow built from the v1.0.3 tag. The site checks the attestation before pinning the version, cross-checks the three pinned hashes —exe, dmg and AppImage— against the attestation subjects, and the download page documents gh attestation verify for both projects.

Check: Download

Step 2, with photos

The guide embeds the photo walkthrough of the pad and the counter, in each language of the site: this is the step text alone cannot carry —opening the printer, finding the pad, washing or replacing it. The walkthrough was written by the author of this site and is published on iFixit; the credit names him, not the platform.

Check: Guide

The first full reset on the bench

With an L365 at 100% pad usage the whole cycle ran, write included: EWR v1.4.1 wrote under the printer's foreign-error warning, the power cycle held it, and the harness's verification —counters and a byte-for-byte dump against the backup— came back applied. Until today the project had tested the read, backup and check halves, but never the final write.

Check: Guidellms.txt

What is still missing

Phase 2, a tool that unifies protocols and databases; better coverage of the maintenance box with a chip; and our own issue tracker once the repository can be opened. In the meantime, the linked tools have their own issue trackers.

Check: Download