Updated brand guidelines with v2 brand assets.

miscellaneous/sia-brand-guidelines.md

@@ -33,15 +33,13 @@ These Sia brand guidelines will assist those developing their project by ensurin
 
 The Sia Foundation strictly owns the trademark in the US and advises against using the Sia logo and wordmark directly in any capacity, such as third-party projects. Users can only style the original logo and wordmark to prevent confusion and misrepresentation.
 
-The following is an example of an acceptable change. The SiaStats logo resembles the Sia logo, but is styled significantly so as not to be confused with our trademarked version. Only projects with direct relevance (see below) may style their logo based on the Sia logo.
+The following is an example of an acceptable change. The SiaStats logo resembles the Sia logo, but is styled significantly so as not to be confused with our trademarked version. Only projects with direct relevance may style their logo based on the Sia logo.
 
 <div data-full-width="false">
 
-<figure><img src="../.gitbook/assets/sia_original.png" alt="" width="300"><figcaption><p>Original Sia Logo and wordmark</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/v2-brand-assets/primary_logo_dark.png" alt="" width="300"><figcaption><p>Sia Wordmark Logo</p></figcaption></figure>
 
-
-
-<figure><img src="../.gitbook/assets/siastats.png" alt="" width="375"><figcaption><p>Example of styling of the original (Siastats logo)</p></figcaption></figure>
+<figure><img src="../.gitbook/assets/v2-brand-assets/shorthand_dark.png" alt="" width="164"><figcaption><p>Sia Shorthand Logo</p></figcaption></figure>
 
 </div>
 
@@ -55,7 +53,7 @@ Sia's trademark name is pronounced _"sigh-uh,_ not _"see-ya."_
 
 ### Direct relevance
 
-If your project directly relates to the Sia ecosystem, or wouldn't exist outside of Sia, it's probably ok to use the term **Sia** in your project's name. Good examples of this are **SiaStats**, **Siasync**, **SiaWiki**, and **Siamining**. These projects all had straight-line relevance to the ecosystem and directly serviced the Sia network.
+If your project directly relates to the Sia ecosystem, or wouldn't exist outside of Sia, it's probably ok to use the term **Sia** in your project's name. Good examples of this are **Siascan**, **SiaGraph** and **Dartsia**. These projects all have straight-line relevance to the ecosystem and directly serviced the Sia network.
 
 Check with the team if you're not sure. If you do qualify, there are two restrictions:
 
@@ -66,7 +64,7 @@ Check with the team if you're not sure. If you do qualify, there are two restric
 
 If you're building a project on the Sia network, but could just as easily swap out Sia with another storage backend, don't use the term Sia in your project's name. Grant projects commonly fall into this trap.
 
-For example, if you are building a file transfer service with Sia as your storage location, don't call it SiaSend. Now would be the time to craft a unique name that reflects your project's identity and your creative efforts. Illustrative instances of such custom names include **Pixeldrain**, **Filebase**, and **Roadie**.
+For example, if you are building a file transfer service with Sia as your storage location, don't call it SiaSend. Now would be the time to craft a unique name that reflects your project's identity and your creative efforts.
 
 {% hint style="info" %}
 We're eagerly anticipating what you'll create! If you have any questions regarding our Sia branding guidelines, please don't hesitate to reach out via [email](mailto:hello@sia.tech) or [Discord](https://sia.tech/discord).

navigating-the-v2-hardfork/sia-ecosystem-fork-compliance.md

@@ -38,7 +38,7 @@ Last updated: May 27, 2025. Average daily volume may not add to 100% as some val
 | Upbit      | 4.5%                 | Committed      | February 11, 2025 | [Link](https://www.panewslab.com/en/articles/fvx2ilom)                                                                                                                              |
 | MEXC       | 2%                   | Committed      | February 19, 2025 | [Link](https://www.mexc.com/support/articles/17827791524227)                                                                                                                        |
 | OKX        | .75%                 | Committed      | February 11, 2025 |                                                                                                                                                                                     |
-| Kraken     | .25%                 | Committed      | October 23, 2024  |                                                                                                                                                                                     |
+| Kraken     | .25%                 | Committed      | October 23, 2024  | [Link](https://status.kraken.com/incidents/h0sqj1188drp)                                                                                                                            |
 | HTX        | 5%                   | Dev discussion | February 25, 2025 |                                                                                                                                                                                     |
 | Bybit      | 1%                   | Dev discussion | March 24, 2025    |                                                                                                                                                                                     |
 | Gate.io    | .75%                 | Dev discussion | April 25, 2025    |                                                                                                                                                                                     |