docs: reproducible build (#35)

Also add CL entry

Please go the the `Preview` tab and select the appropriate sub-template:

* [Production code](?expand=1&template=production.md) - for types `fix`,
`feat`, and `refactor`.
* [Docs](?expand=1&template=docs.md) - for documentation changes.
* [Others](?expand=1&template=others.md) - for changes that do not
affect production code.

Author: tbruyelle

CHANGELOG.md

@@ -1,5 +1,33 @@
 # CHANGELOG
 
+## Unreleased
+
+*Release date*
+
+### API BREAKING
+
+### BUG FIXES
+
+### DEPENDENCIES
+
+### FEATURES
+
+* Add reproducible builds ([#34](https://github.com/atomone-hub/govgen/pull/34))
+
+## v1.0.1
+
+*February 26st, 2024*
+
+### API BREAKING
+
+### BUG FIXES
+
+### DEPENDENCIES
+
+### FEATURES
+
+* `InitChainer` auto stakes uniformly to validators at genesis ([#26](https://github.com/atomone-hub/govgen/pull/26)).
+
 ## v1.0.0
 
 *February 21st, 2024*
@@ -20,7 +48,5 @@
   ([#13](https://github.com/atomone-hub/govgen/pull/13)).
 * Adapt voting period to proposal type.
   ([#16](https://github.com/atomone-hub/govgen/pull/16)).
-* `InitChainer` auto stakes uniformly to validators at genesis
-  ([#26](https://github.com/atomone-hub/govgen/pull/26)).
 
 ### STATE BREAKING

README.md

@@ -25,3 +25,11 @@ The following modifications have been made to the Cosmos Hub software to create
 8. Removed community spend proposal
 9. Allowed setting different voting periods for different proposal types
 10. Stake automatically 50% of balance for accounts that have more than 25 $GOVGEN at genesis initialization. The resulting stake distribution will provide approximately the same voting power to all genesis validators. Accounts will automatically stake to a maximum of 5 validators if 50% of the balance is less than 500 $GOVGEN, a maximum of 10 validators if less than 10,000 $GOVGEN and a maximum of 20 validators if more, uniformly. The number of validators elected for the delegations is not a constant because it depends on the state of the distribution.
+
+## Reproducible builds
+
+An effort has been made to make it possible to build the exact same binary
+locally as the Github Release section. To do this, checkout to the expected
+version and then simply run `make build` (which will output the binary to the
+`build` directory) or `make install`. The resulted binary should have the same
+sha256 hash than the one from the Github Release section.