diff --git a/.github/workflows/calibreapp-image.yml b/.github/workflows/calibreapp-image.yml
index 60d10b5..45291f0 100644
--- a/.github/workflows/calibreapp-image.yml
+++ b/.github/workflows/calibreapp-image.yml
@@ -1,5 +1,6 @@
 name: Compress Images
 on:
+  workflow_dispatch:
   pull_request:
     paths:
       - '**.jpg'
@@ -24,3 +25,12 @@ jobs:
           jpegProgressive: true
           pngQuality: '100'
           webpQuality: '100'
+
+      - name: Create New Pull Request If Needed
+        if: steps.calibre.outputs.markdown != ''
+        uses: peter-evans/create-pull-request@v4
+        with:
+          title: Compressed Images Nightly
+          branch-suffix: timestamp
+          commit-message: Compressed Images
+          body: ${{ steps.calibre.outputs.markdown }}
diff --git a/docs/developer/README.md b/docs/developer/README.md
index 4d89ffe..240ad60 100644
--- a/docs/developer/README.md
+++ b/docs/developer/README.md
@@ -27,7 +27,7 @@ There are two networks on mainnet:
 `quicknet` network chain hash: 
 ```52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971```
 
-Note that [the `fastnet` network has been deprecated.](/blog/2023/07/03/fastnet-sunset-quicknet-new/)
+Note that [the `fastnet` network has been deprecated.](/blog/2023/07/03/fastnet-sunset-quicknet-new/).
 
 In order to retrieve randomness from a drand network you should **preferentially use the [drand client libraries](/developer/clients/) or the [drand-client CLI](/developer/drand-client/)**, which support the different mechanisms and perform verification for every value obtained.
 
diff --git a/docs/developer/http-api.md b/docs/developer/http-api.md
index d7262c2..f7b599e 100644
--- a/docs/developer/http-api.md
+++ b/docs/developer/http-api.md
@@ -19,7 +19,7 @@ The public [League of Entropy](https://blog.cloudflare.com/league-of-entropy/) H
 
 The League of Entropy currently runs two networks in mainnet: `default` and `fastnet`. They are chained and unchained networks respectively, the details of which can be found in the [cryptography specification](https://drand.love/docs/cryptography/#randomness).
 
-The chain hash for the League of Entropy `default` drand group is:
+The chain hash for the League of Entropy `default` chain running at a 30s frequency in chained mode on Mainnet is:
 
 ```
 8990e7a9aaed2ffed73dbd7092123d6f289930540d7651336225dc172e51b2ce
@@ -27,12 +27,14 @@ The chain hash for the League of Entropy `default` drand group is:
 
 It also available at the default context, i.e. omitting the `/{chain-hash}` in the API specification below.
 
-The chain has for the League of Entropy `fastnet` drand group is:
+The chain hash for the League of Entropy `quicknet` network running at a 3s frequency in unchained mode on Mainnet is:
 
 ```
-dbd506d6ef76e5f386f41c651dcb808c5bcbd75471cc4eafa3f4df7ad4e4c493
+52db9ba70e0cc0f6eaf7803dd07447a1f5477735fd3f661792ba94600c84e971
 ```
 
+Note that [the `fastnet` network has been deprecated.](/blog/2023/07/03/fastnet-sunset-quicknet-new/).
+
 ## `/chains`
 
 Retrieves the _chain hash_ of every running network a user can interact with. It returns a JSON object with the following structure:
diff --git a/docs/docs/timelock-encryption.md b/docs/docs/timelock-encryption.md
index e370feb..fa02aba 100644
--- a/docs/docs/timelock-encryption.md
+++ b/docs/docs/timelock-encryption.md
@@ -22,6 +22,7 @@ Additionally, this means that users can decrypt their timelock ciphertext *offli
 - [here is our blog post announcing the new network and timelock encryption](https://drand.love/blog/2023/03/28/timelock-on-fastnet/)
 - [here is Yolan's talk at Real World Crypto](https://www.youtube.com/watch?v=Xh849Ij3lhU) on timelock encryption
 - [here is the paper on eprint](https://eprint.iacr.org/2023/189)
+- [here is our post about deprecating `fastnet` in favor of the RFC-compliant `quicknet`](https://drand.love/blog/2023/07/03/fastnet-sunset-quicknet-new/)
 
 
 ## ⚠️ Security assumptions ⚠️
@@ -31,7 +32,7 @@ While our timelock scheme has been assessed for security issues by renowned secu
 - **there have never been a threshold of malicious nodes in the drand network**
 
 If there were, at any time, a threshold number of malicious nodes in the network, they could cooperatively generate all future random values and use them to decrypt arbitrary future timelock ciphertexts. Drand randomness, while unpredictable, is entirely deterministic, even after the resharing of keys.
-That said, `fastnet` (our new network for timelock encryption) was started with 16 different participants running 23 nodes, so we're confident a threshold number of them have not been compromised!
+That said, `quicknet` (our latest network compatible with timelock encryption) was started with 18 different organisations running in total 22 nodes for a threshold of 12, effectively eliminating any trusted third party and diluting trust in independent organisations that have no reason to collude with one another!
 
 - **neither the scheme, nor drand are quantum resistant**