Merge branch 'master' into library

README.md

@@ -588,11 +588,11 @@ The [Ecosystem Helper](https://mvw4g-yiaaa-aaaam-abnva-cai.icp0.io/) is an oncha
 
 ### Asset guidelines
 
-| Asset       |          | Requirements | Format       | Notes                                                                             |
-|-------------|----------|--------------|--------------|-----------------------------------------------------------------------------------|
-| logo        | required | 112x112px    | webp/svg/png | Currently displayed 56x56px                                                       |
-| screenshots | optional | 1024x576px   | webp/jpg     | The schema supports multiple files, but only the first one will be displayed      |
-| video       | optional | max 10MB     | webm/mp4     | If there is a video file specified, it will be displayed instead of a screenshot. |
+| Asset       |          | Requirements                    | Format                    | Notes                                                                                  |
+|-------------|----------|---------------------------------|---------------------------|----------------------------------------------------------------------------------------|
+| logo        | required | 112x112px (1:1 aspect ratio)    | svg(recommended)/png/webp | Optimize file size with [SVGOMG](https://svgomg.net) or [TinyPNG](https://tinypng.com) |
+| screenshots | optional | 1024x576px                      | webp/jpg                  | The schema supports multiple files, but only the first one will be displayed           |
+| video       | optional | max 10MB                        | webm/mp4                  | If there is a video file specified, it will be displayed instead of a screenshot.      |
 
 ### Tags
 

blog/features/vetkey-primer.md

@@ -63,7 +63,7 @@ Considering that blockchains are very public places where transparency has been
 Note that we care most about the secret ***key derivation*** here, as that is the most sensitive part which we want to protect from one central (potentially untrusted, unauthorized, or compromised) party, and hence the **KD** in VETKD. To deal with the centralization point, we need to move into the distributed setting.  Assuming there is no one trusted party, we distribute trust amongst multiple parties, and require that some *threshold* of them collaborate on shares of the master secret key to derive decryption keys.
 
 How do parties **get shares** of the master secret key? This is done by leveraging a distributed key generation (DKG) protocol, where a threshold of honest parties (or nodes) work together to obtain a set of master key shares. Assuming no collusion between nodes, at no point does any one node hold the full private key.
-Click around to learn more about [threshold cryptography]( https://en.wikipedia.org/wiki/Threshold_cryptosystem), [DKG](https://en.wikipedia.org/wiki/Distributed_key_generation) and chapter 22 in the [Boneh-Shoup book](http://toc.cryptobook.us/).
+Click around to learn more about [threshold cryptography]( https://en.wikipedia.org/wiki/Threshold_cryptosystem), [DKG](https://en.wikipedia.org/wiki/Distributed_key_generation) and chapter 22 in the [Boneh-Shoup book](https://toc.cryptobook.us/).
 
 It’s clear from above that we don't want a centralised key derivation process and this is why we need the **T** for the KD process, but what about **V** and **E**? Perhaps this is best highlighted by a scenario.
 
@@ -100,7 +100,7 @@ At a first glance, we could guess that we will need a distributed key generation
 Crucially, An observation buried in [BF01] gives us the answer. Moni Naor noted that an IBE scheme can be directly converted into a signature scheme. Considering the key derivation of Boneh-Franklin IBE specifically, the resulting signature scheme happens to be BLS.
 
 ### BLS signatures
-Digital signatures are used everywhere in cryptography and in the blockchain world to attest to the authenticity of a message, transaction, or other pieces of information. As they are so prevalent, it’s really worth spending time getting to know them. You can get a high level view on wikipedia ([Digital Signatures](https://en.wikipedia.org/wiki/Digital_signature) and [BLS](https://en.wikipedia.org/wiki/BLS_digital_signature)), and dive into the [Boneh-Shoup book](http://toc.cryptobook.us/) when you want more formal details.
+Digital signatures are used everywhere in cryptography and in the blockchain world to attest to the authenticity of a message, transaction, or other pieces of information. As they are so prevalent, it’s really worth spending time getting to know them. You can get a high level view on wikipedia ([Digital Signatures](https://en.wikipedia.org/wiki/Digital_signature) and [BLS](https://en.wikipedia.org/wiki/BLS_digital_signature)), and dive into the [Boneh-Shoup book](https://toc.cryptobook.us/) when you want more formal details.
 
 BLS signatures are a particular type of digital signature introduced in by Dan Boneh, Ben Lynn, and Hovav Shacham in 2001. 
 
@@ -132,7 +132,7 @@ This page contains a high level view and description of VETKD and its building b
 It also shows one possible way of building VETKD, there are others, some with fancy features, that are described more in the paper. There are many use cases and motivations for building VETKD, these are discussed in [the video](https://youtu.be/baM6jHnmMq8) and can be written up if you like. There are also extensions that could be built depending on what is needed in the community. Finally, note that this page is hosted onchain.
 
 ## References
-* [BS23](http://toc.cryptobook.us/) - The Boneh-Shoup Book.
+* [BS23](https://toc.cryptobook.us/) - The Boneh-Shoup Book.
 * [BF01](https://crypto.stanford.edu/~dabo/papers/bfibe.pdf) - The IBE paper.
 * [BLS01](https://www.iacr.org/archive/asiacrypt2001/22480516.pdf) - The BLS paper.
 * [DH76](https://ee.stanford.edu/~hellman/publications/24.pdf) - Diffie and Hellman's New Directions paper.

blog/news-and-updates/2023-12-06-update.mdx

@@ -15,7 +15,7 @@ Hello developers and welcome back to developer weekly! This week, we have some v
 
 On Friday, December 1st, the NNS proposals to enable ckETH on ICP went live. We're excited to announce that all proposals were passed by the NNS, and ckETH is now live on the mainnet! 
 
-ckETH has been added to the ICP dashboard, which you can view [here](http://dashboard.internetcomputer.org/ethereum). You can learn how to interact with ckETH by reviewing the ckETH minter documentation [here](https://github.com/dfinity/ic/blob/master/rs/ethereum/cketh/minter/README.adoc).
+ckETH has been added to the ICP dashboard, which you can view [here](https://dashboard.internetcomputer.org/ethereum). You can learn how to interact with ckETH by reviewing the ckETH minter documentation [here](https://github.com/dfinity/ic/blob/master/rs/ethereum/cketh/minter/README.adoc).
 
 ckETH support is also live in the ICRC-1 wallet, which includes ckETH has a pre-defined token. The index canister has been integrated, allowing you to mint directly to your principal. The ICRC-1 wallet canister can be found [here](https://e4hv6-7yaaa-aaaao-a2ida-cai.icp0.io/)
 

blog/news-and-updates/2024-08-14-update.mdx

@@ -27,7 +27,7 @@ The digital assets section of the developer docs has gotten an overhaul! Before,
 
 - [Token standards](/docs/current/developer-docs/defi/tokens/token-standards)
 
-- [Asset flow](/docs/current/developer-docs/defi/tokens/asset_flow/)
+- [Asset flow](/docs/current/developer-docs/defi/overview)
 
 - [Ledger integration options](/docs/current/developer-docs/defi/tokens/advanced/direct_integration)
 

blog/news-and-updates/2024-10-09-update.mdx

@@ -40,7 +40,7 @@ Developer office hours are back in the ICP developer Discord server! Every Wedne
 
 Be sure to drop in to the session and ask questions, share your project, or simply listen in on the discussion.
 
-[Join the ICP developer Discord server](https://discord.gg/RMZNkGMp8N).
+[Join the ICP developer Discord server](https://discord.internetcomputer.org).
 
 ## Community spotlight: KongSwap
 
@@ -50,4 +50,4 @@ You can [try KongSwap yourself](https://www.kongswap.io/?viewtab=swap&pool=ICP_c
 
 That'll wrap up this week. Tune back in next week for more developer updates!
 
--DFINITY
+-DFINITY

blog/news-and-updates/2024-12-04-update.mdx

@@ -0,0 +1,42 @@
+---
+title: Developer weekly update December 4, 2024
+description: This week we have a new release of dfx, an important update about the Bitcoin integration, and an update from the community project Juno.
+tags: [Devs]
+image: /img/blog/dev-update-blog-dec-4.jpg
+---
+
+# Developer weekly update December 4, 2024
+
+![December 4 2024](../../static/img/blog/dev-update-blog-dec-4.jpg)
+
+Hello developers, and welcome to this week's developer weekly update! This week we have a new release of `dfx`, an important update about the Bitcoin integration, and an update from the community project Juno. Let's get started!
+
+## dfx v0.24.3
+
+The latest version of `dfx` is now promoted! This latest update includes new features such as:
+
+- PocketIC now supports Bitcoin through the `--enable-bitcoin` and `--bitcoin-node` flags.
+
+- The canisters for the ICP, ckBTC, and ckETH ledger canisters can now be pulled.
+
+- The frontend canister now supports setting canister permissions in the init arguments.
+
+- Output for `dfx start` and `dfx cycles` have been improved. 
+
+[Read the full release notes](https://github.com/dfinity/sdk/releases/tag/0.24.3).
+
+## Bitcoin integration updates
+
+The Bitcoin Testnet API is being migrated from Testnet v3 to Testnet v4. To support this work, the ckTestBTC minter has been stopped and the Bitcoin Testnet API has been disabled. Once the migration has finished, these features will be re-enabled.
+
+You can stay up to date on the status via the [forum](https://forum.dfinity.org/t/direct-integration-with-bitcoin/6147/743?u=cryptoschindler).
+
+## Juno v0.0.39
+
+A new version of Juno has been released! This latest version introduces backups to Juno through the new ICP canister snapshot feature. Backups are available through both the Juno API and the Juno CLI tool.
+
+[Learn more in the Juno release notes](https://github.com/junobuild/juno/releases/tag/v0.0.39).
+
+That'll wrap up this week. Tune back in next week for more developer updates!
+
+-DFINITY

blog/news-and-updates/team-spotlight-sdk.mdx

@@ -67,7 +67,7 @@ Hey devs and welcome to this edition of ICP team spotlight! In this issue, we sa
 
 **The SDK team is pretty involved with the dev community on the forum and Discord server, which I'm sure has lead to features derived as a result of community feedback. What are some of the improvements made as a direct result of developer feedback?**
 
-*Lots! We built the [developer feedback board](http://dx.internetcomputer.org) a while back, and every two weeks, our internal focus group meets to go over the latest items and check-in on the progress we’ve made addressing others. One thing that's come as a result of the feedback received is the `dfx` version manager. Developers expressed that they want a way to switch `dfx` versions easily. We spent some time working out how best to accomplish that, and the `dfx` version manager was born. Another example is the Cycles Ledger - we heard feedback that the Cycles Wallet was a pain to use and developers wanted a better solution. We are continuously looking for ways to improve our tooling, so keep the feedback coming!*
+*Lots! We built the [developer feedback board](https://dx.internetcomputer.org) a while back, and every two weeks, our internal focus group meets to go over the latest items and check-in on the progress we’ve made addressing others. One thing that's come as a result of the feedback received is the `dfx` version manager. Developers expressed that they want a way to switch `dfx` versions easily. We spent some time working out how best to accomplish that, and the `dfx` version manager was born. Another example is the Cycles Ledger - we heard feedback that the Cycles Wallet was a pain to use and developers wanted a better solution. We are continuously looking for ways to improve our tooling, so keep the feedback coming!*
 
 **Where should developers look for the latest SDK updates?**