Problem
Grant programmes require periodic progress reports, and hackathon judges want
evidence of sustained work rather than a weekend push. There is nowhere to
publish either, so progress currently lives only in commit history — which
nobody outside the project reads.
What to do
- A
/changelog route rendering markdown from the repository, so writing a
release note is part of shipping rather than a separate chore.
- Longer-form posts for the decisions worth explaining: why attestation and
settlement are separate contracts, what the threat model found, what the
first testnet fee measurements showed.
- Tag entries against milestones so a grant report can be assembled from them
rather than written from scratch.
- RSS, so people can follow without an account.
- Publish the awkward things too — a postmortem for a bug found in audit is
more credible than an unbroken run of feature announcements.
Acceptance criteria
Notes
The milestone tagging is what makes this pay for itself: writing the report at
the end of a grant period is much harder than assembling entries written as the
work happened.
Problem
Grant programmes require periodic progress reports, and hackathon judges want
evidence of sustained work rather than a weekend push. There is nowhere to
publish either, so progress currently lives only in commit history — which
nobody outside the project reads.
What to do
/changelogroute rendering markdown from the repository, so writing arelease note is part of shipping rather than a separate chore.
settlement are separate contracts, what the threat model found, what the
first testnet fee measurements showed.
rather than written from scratch.
more credible than an unbroken run of feature announcements.
Acceptance criteria
Notes
The milestone tagging is what makes this pay for itself: writing the report at
the end of a grant period is much harder than assembling entries written as the
work happened.