From: Steve Myers Date: Sat, 12 Sep 2020 06:31:53 +0000 (-0700) Subject: rename magical bitcoin to bitcoin dev kit, update icons, logos and github repo links X-Git-Url: http://internal-gitweb-vhost/script/%22https:/database/struct.EncoderStringWriter.html?a=commitdiff_plain;h=bdbd6171ce7a33ee08134ef5258749c930c31aa4;p=bitcoindevkit.org rename magical bitcoin to bitcoin dev kit, update icons, logos and github repo links --- diff --git a/README.md b/README.md index 862179c61e..675ed065d5 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# magicalbitcoin.org +# bitcoindevkit.org This website is built with [Hugo](https://gohugo.io). diff --git a/config.toml b/config.toml index 9ee93c330f..fa39689ae4 100644 --- a/config.toml +++ b/config.toml @@ -1,6 +1,6 @@ -baseURL = "https://magicalbitcoin.org/" +baseURL = "https://bitcoindevkit.org/" languageCode = "en-us" -title = "Magical Bitcoin" +title = "Bitcoin Dev Kit" theme = "learn" [outputs] @@ -10,11 +10,11 @@ home = [ "HTML", "RSS", "JSON"] # Prefix URL to edit current page. Will display an "Edit this page" button on top right hand corner of every page. # Useful to give opportunity to people to create merge request for your doc. # See the config.toml file from this documentation site to have an example. -editURL = "https://github.com/MagicalBitcoin/magicalbitcoin.org/edit/master/content/" +editURL = "https://github.com/bitcoindevkit/bitcoindevkit.org/edit/master/content/" # Author of the site, will be used in meta information author = "Alekos Filini - @afilini" # Description of the site, will be used in meta information -description = "The Magical Bitcoin project aims to build a collection of tools and libraries that are designed to be a solid foundation for Bitcoin wallets." +description = "The Bitcoin Dev Kit project aims to build a collection of tools and libraries that are designed to be a solid foundation for Bitcoin wallets." # A title for shortcuts in menu is set by default. Set this to true to disable it. # disableShortcutsTitle = false # Hide breadcrumbs in the header and only show the current page title @@ -32,12 +32,22 @@ custom_css = ["css/style.css", "css/jsonview.css"] [markup.goldmark.renderer] unsafe= true +[[Languages.en.menu.shortcuts]] +name = " Rust Docs" +url = "/docs-rs/magical/" +weight = 5 + [[Languages.en.menu.shortcuts]] name = " Playground" url = "/repl/playground" weight = 10 [[Languages.en.menu.shortcuts]] -name = " Rust Docs" -url = "/docs-rs/magical/" -weight = 5 +name = " Follow on Twitter" +url = "https://twitter.com/intent/follow?screen_name=bitcoindevkit" +weight = 15 + +[[Languages.en.menu.shortcuts]] +name = " Chat on Discord" +url = "https://discord.gg/yRRan6q" +weight = 20 \ No newline at end of file diff --git a/content/_index.md b/content/_index.md index 3860a5123e..124867dbee 100644 --- a/content/_index.md +++ b/content/_index.md @@ -4,33 +4,33 @@ date: 2020-04-28T09:46:18+02:00 draft: false --- -# 🧙 Magical Bitcoin 🧙 +# Bitcoin Dev Kit -The Magical Bitcoin project aims to build a collection of tools and libraries that are designed to be a solid foundation for Bitcoin wallets, along with a fully working *reference implementation* wallet. -All of its components are designed to be lightweight and modular so that they can be adapted for virtually any use-case: from the single-sig mobile wallet to the multi-billion-dollar cold storage vault. +The [Bitcoin Dev Kit (BDK)](https://github.com/bitcoindevkit) project (originally called Magical Bitcoin 🧙) aims to build a collection of tools and libraries that are designed to be a solid foundation for cross platform Bitcoin wallets, along with a fully working *reference implementation* wallet called Magical Bitcoin. +All BDK components are designed to be lightweight and modular so that they can be adapted for virtually any use-case: from single-sig mobile wallets to multi-billion-dollar cold storage vaults. The main long-term goal is to concentrate the development efforts of multiple people and companies into one open source and very well reviewed project, instead of dispersing them over multiple closed/semi-closed or poorly designed projects. {{% notice info %}} Keep in mind that this project is still in a very early phase of development. The APIs and the general architecture shouldn't be considered stable yet. At the moment most of the code is concentrated in the -[main repo](https://github.com/MagicalBitcoin/magical-bitcoin-wallet) and is slowly being refactored and taken out into separate, independent modules. +[main repo](https://github.com/bitcoindevkit/bdk) and is slowly being refactored and taken out into separate, independent modules. {{% /notice %}} ## Playground -As a way of demostrating the flexibily of this project, the minimalistic command line (also called "repl") that is currently shipped as a debugging tool in the main [`magical-bitcoin-wallet`](https://github.com/MagicalBitcoin/magical-bitcoin-wallet) -repo has been compiled to WebAssembly and can be used directly from the browser. See the [playground](/repl/playground) section to give it a try! +As a way of demonstrating the flexibly of this project, a minimalistic command line tool (also called "repl") is available as a debugging tool in the main [`bdk`](https://github.com/bitcoindevkit/bdk) +repo. It has been compiled to WebAssembly and can be used directly from the browser. See the [playground](/repl/playground) section to give it a try! -The playground relies on [Esplora](https://blockstream.info) to monitor the blockchain and is currently locked in testnet-only mode, for obvious safety reasons. The native command line can also be used in regtest mode when installed on +The playground relies on [Esplora](https://blockstream.info) to monitor the blockchain and is currently locked in testnet-only mode, for obvious safety reasons. The native command line tool can also be used in regtest mode when installed on a computer. See the [REPL](/repl) section to learn more. ## Descriptors -The name of the project refers to the fact that when its components are built into a wallet, it can "almost magically" support very complex spending policies, without having to individually translate them into code. It may sound disappointing, but there isn't, in fact, +One of the original milestones of this project was to provide wallets with "almost magically" support for very complex spending policies, without having to individually translate them into code. It may sound disappointing, but there isn't, in fact, any real magic in this wallet: the generalization is achieved thanks to *descriptors*, that are now slowly starting to see adoption in a few other Bitcoin projects as well. The author of this project strongly believes descriptors will be a big part of the future generation of Bitcoin wallets, since they provide a very flexible scripting language that can also be extended as the -technology and tooling on Bitcoin evolve and change (Schnorr signatures, Taproot, etc). +technology and tooling of Bitcoin evolves and changes (Schnorr signatures, Taproot, etc). To learn more, check out the specific [Descriptors section](/descriptors). diff --git a/content/descriptors/_index.md b/content/descriptors/_index.md index 1c1555a6c8..b0ab422a83 100644 --- a/content/descriptors/_index.md +++ b/content/descriptors/_index.md @@ -10,18 +10,18 @@ Descriptors are a compact and semi-standard way to easily encode, or "describe", more complex scripts, where the structure of the script itself is not trivial. They are a big step forward in making wallets more portable across different tools and apps, because for the first time they create a common language to describe a full bitcoin script that developers can use and integrate in their software. -The ecosystem around descriptors is still very much in its early stage, but they are starting to see some adoption in [Bitcoin Core](https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md) and other projects. Magical Bitcoin +The ecosystem around descriptors is still very much in its early stage, but they are starting to see some adoption in [Bitcoin Core](https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md) and other projects. BDK aims to produce the first "Native Descriptor" Bitcoin library that can be used by developers to build their own ["Native Descriptor Wallets"](https://www.youtube.com/watch?v=xC25NzIjzog). ### Compatibility Matrix -Below are some tables to highlight the differences between Bitcoin Core's descriptor support, rust-miniscript's one and Magical Bitcoin's. +Below are some tables to highlight the differences between Bitcoin Core's descriptor support, rust-miniscript's one and BDK's. #### Key Types
-| Key Type | Magical Bitcoin | rust-miniscript | Bitcoin Core | +| Key Type | BDK | rust-miniscript | Bitcoin Core | | -------- | --------------- | --------------- | ------------ | | Hex PublicKey | ✓ | ✓ | ✓ | | WIF PrivateKey | ✓ | ✗ | ✓ | @@ -33,7 +33,7 @@ Below are some tables to highlight the differences between Bitcoin Core's descri
-| Script Type | Magical Bitcoin | rust-miniscript | Bitcoin Core | +| Script Type | BDK | rust-miniscript | Bitcoin Core | | -------- | --------------- | --------------- | ------------ | | `pk()` | ✓ | ✓ | ✓ | | `pkh()` | ✓ | ✓ | ✓ | @@ -53,7 +53,7 @@ Below are some tables to highlight the differences between Bitcoin Core's descri
-| Operator | Magical Bitcoin | rust-miniscript | Bitcoin Core | +| Operator | BDK | rust-miniscript | Bitcoin Core | | -------- | --------------- | --------------- | ------------ | | `pk()` | ✓ | ✓ | ✓ | | `pk_h()` | ✓ | ✓ | ✓ - as `pkh()` | @@ -76,7 +76,7 @@ Below are some tables to highlight the differences between Bitcoin Core's descri
-| Script Type | Magical Bitcoin | rust-miniscript | Bitcoin Core | +| Script Type | BDK | rust-miniscript | Bitcoin Core | | -------- | --------------- | --------------- | ------------ | | `a:` | ✓ | ✓ | ✗ | | `s:` | ✓ | ✓ | ✗ | @@ -95,7 +95,7 @@ For a more thorough description of these operators and modifiers see [Sipa's Min ### Examples -Some examples of valid Magical Bitcoin descriptors are: +Some examples of valid BDK descriptors are:
@@ -110,7 +110,7 @@ Some examples of valid Magical Bitcoin descriptors are: ### Implementation Details -Magical Bitcoin extends the capabilities of [rust-miniscript](https://github.com/apoelstra/rust-miniscript) by introducing the concept of an *ExtendedDescriptor*: it represents a descriptor that contains one or more "derivable keys" like `xpubs` or `xprvs` +BDK extends the capabilities of [rust-miniscript](https://github.com/apoelstra/rust-miniscript) by introducing the concept of an *ExtendedDescriptor*: it represents a descriptor that contains one or more "derivable keys" like `xpubs` or `xprvs` and can be "derived" to a normal Descriptor by deriving every single one of its keys. It is currently called "StringDescriptor" in the code, because it's implemented as a wrapped `miniscript::Descriptor`. ExtendedDescriptors are derived using a single index instead of a full derivation path: this is because normally most of the path is fixed and can be represented right after the xpub/xprv itself, and only the diff --git a/content/repl/_index.md b/content/repl/_index.md index 07ae230c7d..9a53caf71e 100644 --- a/content/repl/_index.md +++ b/content/repl/_index.md @@ -8,5 +8,5 @@ pre = ' ' # REPL -The [magical-bitcoin-wallet](https://github.com/magicalbitcoin/magical-bitcoin-wallet) repo has a very minimalistic interactive shell that acts both as a reference implementation of a wallet and a tool to +The [bdk](https://github.com/bitcoindevkit/bdk) repo has a very minimalistic interactive shell called `repl` that acts both as a reference implementation of a wallet and a tool to quickly experiment with descriptors and transactions. diff --git a/content/repl/compiler.md b/content/repl/compiler.md index 2a9633fa39..9b717a3893 100644 --- a/content/repl/compiler.md +++ b/content/repl/compiler.md @@ -8,9 +8,9 @@ pre: "5. " ## Introduction -If you want to play around with more complicated spending policies, you'll start to find it harder and harder to manually create the descriptors. This is where the miniscript compiler comes in! `magical-bitcoin-wallet` -includes a very simple compiler that can produce a descriptor given a spending policy. The syntax used to encode the spending policiy is very well described [in this page](http://bitcoin.sipa.be/miniscript/), -specifically in the "Policy to Miniscript compiler". The compiler included in Magical Bitcoin does basically the same job, but produces a descriptors for `rust-miniscript` that has some minor differences from +If you want to play around with more complicated spending policies, you'll start to find it harder and harder to manually create the descriptors. This is where the miniscript compiler comes in! The `bdk` library +includes a very simple compiler that can produce a descriptor given a spending policy. The syntax used to encode the spending policy is very well described [in this page](http://bitcoin.sipa.be/miniscript/), +specifically in the "Policy to Miniscript compiler". The compiler included in BDK does basically the same job, but produces descriptors for `rust-miniscript` that have some minor differences from the ones made by the C++ implementation used in that website. ## Installation @@ -18,7 +18,7 @@ the ones made by the C++ implementation used in that website. To install the miniscript compiler run the following command: ```bash -cargo install --git https://github.com/magicalbitcoin/magical-bitcoin-wallet --features="compiler" --example miniscriptc +cargo install --git https://github.com/bitcoindevkit/bdk --features="compiler" --example miniscriptc ``` Once the command is done, you should have a `miniscriptc` command available. You can check if that's the case by running `miniscriptc --help`. @@ -26,7 +26,7 @@ Once the command is done, you should have a `miniscriptc` command available. You ## Usage In this case the interface is very simple: it accepts two arguments called "POLICY" and "TYPE", in this order. The first one, as the name implies, sets the spending policy to compile. The latter defines the type -of address that should be used to incapsulate the produced script, like a P2SH, P2WSH, etc. +of address that should be used to encapsulate the produced script, like a P2SH, P2WSH, etc. Optionally, the `--parsed_policy` flag can be enabled and it will make the compiler print the JSON "human-readable" version of the spending policy, as described in the [`policies subcommand`](/repl/interface/#policies) of the CLI. diff --git a/content/repl/concept.md b/content/repl/concept.md index d57f541789..8f9147d120 100644 --- a/content/repl/concept.md +++ b/content/repl/concept.md @@ -6,21 +6,21 @@ weight: 2 pre: "2. " --- -Now, in order to better grasp some of the design choiches made by Magical Bitcoin, it's important to understand the main concept driving the development of this project, and the goal that it's trying to +Now, in order to better grasp some of the design choices made by BDK, it's important to understand the main concept driving the development of this project, and the goal that it's trying to achieve. -Magical Bitcoin is aiming first of all to be a **set of libraries and tools**, all meant to be very reusable and adaptable. Developers working on their own wallets or other projects that are trying to integrate +BDK is aiming first of all to be a **set of libraries and tools**, all meant to be very reusable and adaptable. Developers working on their own wallets or other projects that are trying to integrate Bitcoin can pick the tools they need and piece them together to prototype and quickly ship a working product. This means that the REPL that we've just installed is designed to be a **very thin layer** over the APIs exposed by the various components of the library, **not a full, end-user-ready Bitcoin wallet**. This concept leads to a few design choices that are arguably very bad for the "UX" of this wallet, but that allow developers to work more directly with the underlying library. For instance: -* Magical Bitcoin has an internal database that's used to store data about received transactions, spendable UTXOs, etc. This database is stored by default in your home folder, in `~/.magical-bitcoin`. The database +* BDK has an internal database that's used to store data about received transactions, spendable UTXOs, etc. This database is stored by default in your home folder, in `~/.bdk`. The database **will never** contain any data that can't be recreated purely by looking at the blockchain. Keys, descriptors, Electrum endpoints **are not stored in there**. This explains why you'll have to specify them every time in the command line. It can be seen more like a *cache* and can be safely deleted without risking funds. -* Magical Bitcoin doesn't automatically "monitor" the blockchain, instead there's a `sync` command that has to be called by the user. -* When you create a transaction and then sign it, it's not automatically broadcasted to the network. There's a `broadcast` command that does this. Moreover, the command doesn't accept a normal Bitcoin raw transaction, +* BDK doesn't automatically "monitor" the blockchain, instead there's a `sync` command that has to be called by the user. +* When you create a transaction and then sign it, it's not automatically broadcast to the network. There's a `broadcast` command that does this. Moreover, the command doesn't accept a normal Bitcoin raw transaction, but instead a *PSBT*. That's because internally transactions are always moved as PSBTs, and again, the `broadcast` command is just a very thin wrapper over the raw library call. -There are probably more of these examples, but hopefully by this point you'll have more or less understood the gist of it. If you are not a developer, some parts of this are gonna feel weird, inefficient, hard +There are probably more of these examples, but hopefully by this point you'll have more or less understood the gist of it. If you are not a developer, some parts of this will feel weird, inefficient, hard to understand, and that's absolutely normal. Just try to survive through the pain and you'll be rewarded! diff --git a/content/repl/installation.md b/content/repl/installation.md index c1972e12a8..ca5e59355d 100644 --- a/content/repl/installation.md +++ b/content/repl/installation.md @@ -8,7 +8,7 @@ pre: "1. " ## Requirements -The only requirement is a Linux/macOS system with a fairly recent Rust toolchain installed. Since Linux distros tend to lack behind with updates, the quickest way to install the Rust compiler and Cargo is +The only requirement is a Linux/macOS system with a fairly recent Rust toolchain installed. Since Linux distros tend to lag behind with updates, the quickest way to install the Rust compiler and Cargo is [rustup.rs](https://rustup.rs/). You can head there and follow their instructions, after which you can test if everything went fine by running `cargo version`, which should print something like: ``` @@ -17,18 +17,18 @@ cargo 1.45.0 (744bd1fbb 2020-06-15) **At the time of writing, the project requires cargo >= 1.45.0, which is the latest stable as of June 2020. If you have an older version installed with rustup.rs, you can upgrade it with `rustup update`.** -If you really don't wanna pipe the output of `curl` into `sh`, you can also try using a [Docker image](https://hub.docker.com/_/rust) and working inside of it, but that's meant for more advanced +If you really don't want to pipe the output of `curl` into `sh`, you can also try using a [Docker image](https://hub.docker.com/_/rust) and working inside of it, but that's meant for more advanced users and won't be covered in this guide. -## Installing Magical Bitcoin +## Installing BDK -Once Cargo is installed, you can proceed to install the interactive Magical Bitcoin shell directly from the GitHub repository, by running: +Once Cargo is installed, you can proceed to install the interactive BDK shell directly from the GitHub repository, by running: ```bash -cargo install --git https://github.com/magicalbitcoin/magical-bitcoin-wallet --features=cli-utils --example magic +cargo install --git https://github.com/bitcoindevkit/bdk --features=cli-utils --example magic ``` -This command will probably take a while to finish, since it will fetch and compile all the dependencies and the `magical-bitcoin-wallet` itself. Once it's done, you can check if everything went fine +This command will probably take a while to finish, since it will fetch and compile all the dependencies and the `bdk` itself. Once it's done, you can check if everything went fine by running `magic --help` which should print something like this: ```text diff --git a/content/repl/interface.md b/content/repl/interface.md index 62b29d415b..9b01015daf 100644 --- a/content/repl/interface.md +++ b/content/repl/interface.md @@ -45,7 +45,7 @@ These are the global options that can be set. They are pretty much like the flag associated descriptor**. The `--change-descriptor` flag can be used to set a different descriptor for the change addresses, sometimes called "internal" addresses in Bitcoin Core. Unfortunately there isn't -[really consensus](https://freenode.irclog.whitequark.org/bitcoin-wizards/2020-01-25#26222504;) on a nice way to encode informations about the change derivation inside the standard descriptor, so we are +[really consensus](https://freenode.irclog.whitequark.org/bitcoin-wizards/2020-01-25#26222504;) on a nice way to encode information about the change derivation inside the standard descriptor, so we are stuck with having two separate ones. Keep in mind though, that even if you don't specify a change descriptor, you'll still be able to create transactions - the change address will simply be generated from the standard descriptor. @@ -58,8 +58,8 @@ Right now both plaintext and ssl servers are supported (prefix `tcp://` or no pr The `--proxy` flag can be optionally used to specify a SOCKS5 proxy to use when connecting to the Electrum server. Spawning a local Tor daemon and using it as a proxy will allow you to connect to `.onion` Electrum URLs. **Keep in mind that only plaintext server are supported over a proxy** -The `--wallet` flag can be used to select which wallet to use, if you have more than one of them. If you get a `ChecksumMismatch` error when you make some changes to your descriptor, it's because it doesn't -match anymore the one you've used to initialize the cache. One solution could be to switch to a new wallet name, or delete the cache directory at `~/.magical-bitcoin` and start from scratch. +The `--wallet` flag can be used to select which wallet to use, if you have more than one of them. If you get a `ChecksumMismatch` error when you make some changes to your descriptor, it's because it does not +match anymore the one you've used to initialize the cache. One solution could be to switch to a new wallet name, or delete the cache directory at `~/.bdk` and start from scratch. ## Subcommands @@ -153,7 +153,7 @@ Some ids have been omitted since they are not particularly relevant, in this exa {{}} graph TD; - subgraph "" + subgraph " " R["Root - qd3um656"] --> A["pk(A) - ykfuwzkl"] R["Root - qd3um656"] --> B["B - ms3xjley"] B["B - ms3xjley"] --> B_0["pk(B)"] diff --git a/content/repl/regtest.md b/content/repl/regtest.md index 684cfff85b..ce31c84ba5 100644 --- a/content/repl/regtest.md +++ b/content/repl/regtest.md @@ -7,7 +7,7 @@ pre: "4. " --- Running the REPL in regtest requires having a local Electrum server set-up. There are two main implementations, [`electrs`](https://github.com/romanz/electrs) in Rust and [`ElectrumX`](https://github.com/spesmilo/electrumx) in Python. Since the Rust toolchain is already required to -use Magical, this page will focus mostly on the former. +use BDK, this page will focus mostly on the former. Electrs can be installed by running: @@ -25,7 +25,7 @@ electrs -vv --timestamp --db-dir /tmp/electrs-db --electrum-rpc-addr="127.0.0.1: on macOS you should change the cookie-file to `$HOME/Library/Application Support/Bitcoin/regtest/.cookie`. -This will start the Electrum server on port 50001. You can then add the `-n regtest -s localhost:50001` the `magic` commands to switch to the local regtest. +This will start the Electrum server on port 50001. You can then add the `-n regtest -s localhost:50001` the `bdk` commands to switch to the local regtest. ## Troubleshooting @@ -49,4 +49,4 @@ $ nigiri start This will start electrum RPC interface on port `51401`, the REST interface on `3000` and the esplora UI on `5000` (You can visit with the browser and look for blocks, addresses and transactions) -You can then add the `-n regtest -s localhost:51401` the `magic` commands to switch to the local regtest. +You can then add the `-n regtest -s localhost:51401` to the `magic` commands to switch to the local regtest. diff --git a/static/icons/android-chrome-192x192.png b/static/icons/android-chrome-192x192.png index a2e4dad8c2..15dcea39a2 100644 Binary files a/static/icons/android-chrome-192x192.png and b/static/icons/android-chrome-192x192.png differ diff --git a/static/icons/android-chrome-512x512.png b/static/icons/android-chrome-512x512.png index 3b4b06bbba..be05e1a937 100644 Binary files a/static/icons/android-chrome-512x512.png and b/static/icons/android-chrome-512x512.png differ diff --git a/static/icons/apple-touch-icon.png b/static/icons/apple-touch-icon.png index ed9281b8ba..605cd0509a 100644 Binary files a/static/icons/apple-touch-icon.png and b/static/icons/apple-touch-icon.png differ diff --git a/static/icons/favicon-16x16.png b/static/icons/favicon-16x16.png index 678299afbe..2f4bc6f184 100644 Binary files a/static/icons/favicon-16x16.png and b/static/icons/favicon-16x16.png differ diff --git a/static/icons/favicon-32x32.png b/static/icons/favicon-32x32.png index c0a3b561c9..4beecf7e44 100644 Binary files a/static/icons/favicon-32x32.png and b/static/icons/favicon-32x32.png differ diff --git a/static/icons/favicon.ico b/static/icons/favicon.ico index b6571971cd..33555bf2da 100644 Binary files a/static/icons/favicon.ico and b/static/icons/favicon.ico differ diff --git a/static/icons/mstile-150x150.png b/static/icons/mstile-150x150.png index 17106a6aa6..b7f7b57ead 100644 Binary files a/static/icons/mstile-150x150.png and b/static/icons/mstile-150x150.png differ diff --git a/static/icons/safari-pinned-tab.svg b/static/icons/safari-pinned-tab.svg index a882dc1927..84c1abbfc2 100644 --- a/static/icons/safari-pinned-tab.svg +++ b/static/icons/safari-pinned-tab.svg @@ -1,82 +1,20 @@ - - - - -Created by potrace 1.11, written by Peter Selinger 2001-2013 - - - - - + + + + safari-pinned-tab + Created with Sketch. + + + + + + + \ No newline at end of file diff --git a/static/icons/site.webmanifest b/static/icons/site.webmanifest index ccaa826fe6..4d0a2f6570 100644 --- a/static/icons/site.webmanifest +++ b/static/icons/site.webmanifest @@ -1,6 +1,6 @@ { - "name": "MagicalBitcoin Docs", - "short_name": "MagicalBitcoin Docs", + "name": "Bitcoin Dev Kit Docs", + "short_name": "Bitcoin Dev Kit Docs", "icons": [ { "src": "/android-chrome-192x192.png", diff --git a/static/images/logo.svg b/static/images/logo.svg index b284a89c4d..6fb06d6c4f 100644 --- a/static/images/logo.svg +++ b/static/images/logo.svg @@ -1,283 +1,16 @@ - - - - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + Logo Rounded + Created with Sketch. + + + + + - - + \ No newline at end of file diff --git a/static/images/logo2.svg b/static/images/logo2.svg new file mode 100644 index 0000000000..b284a89c4d --- /dev/null +++ b/static/images/logo2.svg @@ -0,0 +1,283 @@ + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +