+
diff --git a/404.md b/404.md new file mode 100644 index 0000000..5c5dd77 --- /dev/null +++ b/404.md @@ -0,0 +1,12 @@ +--- +layout: 404 +title: 404 not found +permalink: /404.html +section: 404 +--- + +## 404 + +Sorry, the requested page could not be found. + +Please visit the [Home Page](/) instead. diff --git a/CNAME b/CNAME index 0ebae2f..64a5de7 100644 --- a/CNAME +++ b/CNAME @@ -1 +1 @@ -bluewallet.io \ No newline at end of file +hungry-pare-adf179.netlify.com \ No newline at end of file diff --git a/Gemfile b/Gemfile new file mode 100644 index 0000000..b71047c --- /dev/null +++ b/Gemfile @@ -0,0 +1,30 @@ +source "https://rubygems.org" + +# Hello! This is where you manage which Jekyll version is used to run. +# When you want to use a different version, change it below, save the +# file and run `bundle install`. Run Jekyll with `bundle exec`, like so: +# +# bundle exec jekyll serve +# +# This will help ensure the proper Jekyll version is running. +# Happy Jekylling! +gem "jekyll", "~> 3.8" +gem 'jekyll-seo-tag' +gem 'jekyll-paginate' +gem 'jekyll-github-metadata' +gem 'jekyll-get-json' + +# If you want to use GitHub Pages, remove the "gem "jekyll"" above and +# uncomment the line below. To upgrade, run `bundle update github-pages`. +# gem "github-pages", group: :jekyll_plugins + +# If you have any plugins, put them here! +group :jekyll_plugins do + # +end + +# Windows does not include zoneinfo files, so bundle the tzinfo-data gem +gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby] + +# Performance-booster for watching directories on Windows +gem "wdm", "~> 0.1.0" if Gem.win_platform? diff --git a/Gemfile.lock b/Gemfile.lock new file mode 100644 index 0000000..4778acc --- /dev/null +++ b/Gemfile.lock @@ -0,0 +1,84 @@ +GEM + remote: https://rubygems.org/ + specs: + addressable (2.7.0) + public_suffix (>= 2.0.2, < 5.0) + colorator (1.1.0) + concurrent-ruby (1.1.5) + deep_merge (1.2.1) + em-websocket (0.5.1) + eventmachine (>= 0.12.9) + http_parser.rb (~> 0.6.0) + eventmachine (1.2.7) + faraday (0.17.1) + multipart-post (>= 1.2, < 3) + ffi (1.11.3) + forwardable-extended (2.6.0) + http_parser.rb (0.6.0) + i18n (0.9.5) + concurrent-ruby (~> 1.0) + jekyll (3.8.6) + addressable (~> 2.4) + colorator (~> 1.0) + em-websocket (~> 0.5) + i18n (~> 0.7) + jekyll-sass-converter (~> 1.0) + jekyll-watch (~> 2.0) + kramdown (~> 1.14) + liquid (~> 4.0) + mercenary (~> 0.3.3) + pathutil (~> 0.9) + rouge (>= 1.7, < 4) + safe_yaml (~> 1.0) + jekyll-get-json (0.0.1) + deep_merge (~> 1.2) + jekyll (~> 3.0) + jekyll-github-metadata (2.12.1) + jekyll (~> 3.4) + octokit (~> 4.0, != 4.4.0) + jekyll-paginate (1.1.0) + jekyll-sass-converter (1.5.2) + sass (~> 3.4) + jekyll-seo-tag (2.6.1) + jekyll (>= 3.3, < 5.0) + jekyll-watch (2.2.1) + listen (~> 3.0) + kramdown (1.17.0) + liquid (4.0.3) + listen (3.2.1) + rb-fsevent (~> 0.10, >= 0.10.3) + rb-inotify (~> 0.9, >= 0.9.10) + mercenary (0.3.6) + multipart-post (2.1.1) + octokit (4.14.0) + sawyer (~> 0.8.0, >= 0.5.3) + pathutil (0.16.2) + forwardable-extended (~> 2.6) + public_suffix (4.0.1) + rb-fsevent (0.10.3) + rb-inotify (0.10.0) + ffi (~> 1.0) + rouge (3.14.0) + safe_yaml (1.0.5) + sass (3.7.4) + sass-listen (~> 4.0.0) + sass-listen (4.0.0) + rb-fsevent (~> 0.9, >= 0.9.4) + rb-inotify (~> 0.9, >= 0.9.7) + sawyer (0.8.2) + addressable (>= 2.3.5) + faraday (> 0.8, < 2.0) + +PLATFORMS + ruby + +DEPENDENCIES + jekyll (~> 3.8) + jekyll-get-json + jekyll-github-metadata + jekyll-paginate + jekyll-seo-tag + tzinfo-data + +BUNDLED WITH + 2.0.2 diff --git a/LICENSE b/LICENSE index 77afa5b..883a4d5 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ -The MIT License (MIT) +MIT License -Copyright (c) 2013-2018 Blackrock Digital LLC +Copyright (c) 2018 Dan Urbanowicz Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal @@ -9,13 +9,13 @@ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: -The above copyright notice and this permission notice shall be included in -all copies or substantial portions of the Software. +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -THE SOFTWARE. +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/_changelogs/changelog-1.md b/_changelogs/changelog-1.md new file mode 100644 index 0000000..b705f9e --- /dev/null +++ b/_changelogs/changelog-1.md @@ -0,0 +1,15 @@ +--- +title: November Update +date: 2018-11-11 +--- + +{% include tag.html tag="fixed" %} + +```html +
+ + + + + +``` diff --git a/_changelogs/changelog-2.md b/_changelogs/changelog-2.md new file mode 100644 index 0000000..0eda2f6 --- /dev/null +++ b/_changelogs/changelog-2.md @@ -0,0 +1,14 @@ +--- +title: 🚧 January Updates v1.0.5 +date: 2019-01-17 +--- + +Create your own labels, set text and color: + +{% include tag.html tag="added" %} +{% include tag.html tag="changed" %} +{% include tag.html tag="deprecated" %} +{% include tag.html tag="removed" %} +{% include tag.html tag="fixed" %} +{% include tag.html tag="security" %} +{% include tag.html tag="unreleased" %} diff --git a/_changelogs/changelog-3.md b/_changelogs/changelog-3.md new file mode 100644 index 0000000..7eb5707 --- /dev/null +++ b/_changelogs/changelog-3.md @@ -0,0 +1,21 @@ +--- +title: February Updates +date: 2019-02-02 +--- + +February updates across our stack, the main focus for this month in regards to what was released is around: + +Migrating all companies to new access control +Migrating all companies using ticket deflection to the new system +Further improving system, and allowing you to compare your results against wide averages for deflection rates + +{% include tag.html tag="changed" %} +- Better support for using applying additional filters to posts_tax_query for categories for custom WordPress syncs +- Reporting fine-tuning for speed improvements (up to 60% improvement in latency) +- Search engine upgraded. Bringing with it enhancements and bug fixes. +- Replaced login / registration pre-app screens with a cleaner design + +{% include tag.html tag="fixed" %} +- Fixed an issue with the sync autolinker only interlinking selectively. +- Fixed up an issue with prematurely logging out users + diff --git a/_changelogs/changelog-4.md b/_changelogs/changelog-4.md new file mode 100644 index 0000000..ebacb51 --- /dev/null +++ b/_changelogs/changelog-4.md @@ -0,0 +1,20 @@ +--- +title: 🚀 April Updates +date: 2019-04-22 +--- + +April comes with a whole bunch of updates across our stack, the main focus for this month in regards to what was released is around: + +Further improving system, and allowing you to compare your results against wide averages for deflection rates +Improvements to our tool to give you and your team more control +And various other new features, updates, and bug fixes along the way. + +{% include tag.html tag="added" %} +- Some scheduled changelogs, tweets, and slack messages queued up this weekend and were not published on time. We fixed the issue and all delayed publications should be out. +- We now prioritize keywords over title and body so customers can more effectively influence search results +- Support form in the Assistant is now protected with reCaptcha to reduce spam reinitializeOnUrlChange added to the JavaScript API to improve support for pages with turbolinks + +{% include tag.html tag="fixed" %} +- Fixed an issue with the sync autolinker only interlinking selectively. +- Fixed up an issue with prematurely logging out users + diff --git a/_config.yml b/_config.yml new file mode 100644 index 0000000..478a856 --- /dev/null +++ b/_config.yml @@ -0,0 +1,182 @@ +# Welcome to Jekyll! +# +# This config file is meant for settings that affect your whole blog, values +# which you are expected to set up once and rarely edit after that. If you find +# yourself editing this file very often, consider using Jekyll's data files +# feature for the data you need to update frequently. +# +# For technical reasons, this file is *NOT* reloaded automatically when you use +# 'bundle exec jekyll serve'. If you change this file, please restart the server process. + +# Site settings +# These are used to personalize your new site. If you look in the HTML files, +# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on. +# You can create any custom variable you would like, and they will be accessible +# in the templates via {{ site.myvariable }}. +title: BlueWallet - Bitcoin Wallet for iOS and Android +email: your-email@example.com +description: >- # this means to ignore newlines until "baseurl:" + Bitcoin wallet and Lightning wallet for iOS and Android extremely simple and powerful. Open source, Segwit and HD wallets, lightning network, plausible deniability, replace by fee and full encryption +baseurl: "" # the subpath of your site if applicable, e.g. /blog +url: "https://jekyll-netlify-boilerplate.netlify.com" # the base hostname & protocol for your site, e.g. https://example.com + + +# Enable section IDs in frontmatter, useful for identifying current page +# (used as a hook for styling etc) +section: true + +# set to 'true' to enable Netlify CMS (/admin) in production builds +netlifycms: true + +# set to 'true' to enable Google Analytics tracking code in production builds +analytics: true + +# Google analytics code, get your code here https://www.google.com/analytics/ +google_analytics: UA-120614437-1 + + +# Compress HTML (in liquid via layouts/compress.html) +compress_html: + clippings: all + +# Kramdown options +kramdown: + # Prevent IDs from being added to h1-h6 tags + auto_ids: false + +plugins: + - 'jekyll-seo-tag' + - 'jekyll-paginate' + + +# Include in processing (e.g. Netlify directives) +# Uncomment before use + +#include: +# - _redirects +# - _headers + +# Exclude from processing. +# The following items will not be processed. +exclude: + - README.md + - LICENSE.txt + - netlify.toml + - feed.xml + - Gemfile + - Gemfile.lock + - node_modules + - vendor/bundle/ + - vendor/cache/ + - vendor/gems/ + - vendor/ruby/ + +# Site subpath, e.g. /blog +baseurl: "" + +# Permalink URLs structure, for permalink style options see: https://jekyllrb.com/docs/permalinks/ +permalink: /:title/ + +# Site base hostname & protocol, e.g. http://example.com +url: "https://ncoelho.github.io/jekyll-netlify-boilerplate/" + +# Site logo # e.g. logo.png, upload logo image file to /uploads/ folder +logo: logo-bluewallet.svg + +navbar: + sticky: false + search: false + +# Default author settings +author: + name: Nuno Coelho + title: Product & UX + avatar: nuno.png + +# Author settings, displayed on post and doc pages if front matter references author name e.g. author: peter +authors: + nuno: + name: Nuno Coelho + title: Product & UX + avatar: nuno.png + igor: + name: Igor Korsakov + title: Engineering + avatar: igor.png + marcos: + name: Marcos Rodriguez + title: Engineering + avatar: marcos.png + + +# Social icons displayed in footer +social: + email: + website: + facebook: + flickr: + dribbble: + github: https://github.com/bluewallet/bluewallet + googleplus: + instagram: + linkedin: + pinterest: + twitter: https://twitter.com/@bluewalletio + vimeo: + youtube: + telegram: https://t.me/bluewallet + +# Share button +share: + post: false # Display share buttons on a post page + doc: false # Display share buttons on a doc page + twitter: false # Enable by adding Twitter handle + facebook: false # Enable by setting true (Facebook handle not required) + +# Default footer image settings +footer: + copyright: Made somewhere on the planet earth. + +# Disqus comments shortname, requires Disqus account https://disqus.com/ +disqus: + shortname: # 1234 + + +# Number of posts displayed on blog page +paginate: 10 + +# Blog path +paginate_path: "/blog/:num/" + +# Path to post content assets directory i.e post images, pdfs etc +uploads: /uploads/ + +# Build settings +markdown: kramdown +highlighter: rouge + +sass: + style: compressed + +collections: + docs: + output: true + faqs: + output: false + changelogs: + output: false + +# Defaults +defaults: + # _posts + - scope: + path: "" + type: posts + values: + layout: post + # _docs + - scope: + path: "" + type: docs + values: + layout: doc \ No newline at end of file diff --git a/_data/all_features.yml b/_data/all_features.yml new file mode 100644 index 0000000..2c67fdc --- /dev/null +++ b/_data/all_features.yml @@ -0,0 +1,63 @@ +- title: Payjoin + desc: Payjoin or Pay-to-endpoint, it's a feature that allows to break common chain analysis heuristics, where to participants build a transaction together. + +- title: Plug-in your Bitcoin node + desc: Ability to plug-in your own Bitcoin Full node through Electrum Personal Server (EPS), ElectrumX or Electrs. Don't trust, verify for a maximum sovereignty. + +- title: Offline mode + desc: In case you don't have internet connection, BlueWallet will allow you to generate wallets or addresses to be able to receive offline. + +- title: Custom entropy + desc: Ability to manually generate entropy for wallet creation with Coins and Dices. This is an advanced feature, use with caution. + +- title: Coldcard support + desc: Connect to your Coldcard wallet with ease. Support for PSBT and Watch-only wallets. Allows for receiving and sending transactions by signing them offline. + +- title: CoboVault support + desc: Support for Cobo Vault hardware wallet. With one of the first of its kind Air-gapped, PSBT with animated QR codes support. + +- title: Hardware Wallets + desc: Ability to connect and work with Hardware Wallets that support PSBT. After importing your wallet on watch-only mode, go to the wallet options and turn on "hardware wallet" mode. + +- title: PSBT + desc: Support for PSBT - Partially Signed Bitcoin Transactions, BIP 174. Under the hood transactions on BlueWallet are using and constructed by the PSBT standard. + +- title: Broadcast Transaction + desc: Ability to broadcast a transaction that was previsously signed on BlueWallet or elsewhere. + +- title: Multiple Storage + desc: Besides having one storage for all your wallets, you can have multiple encrypted storages, that can be accessed by different passwords. This is useful in case you don't want to have all your wallets in the same storage, or you have other family members or employees accessing or using the app. + +- title: Full encryption + desc: On top of the phone multi-layer encryption, blue wallet can encrypt everything with an added password. Biometric security (touch ID, Face ID) is not safe, so you will have an additional password to encrypt your wallet instead. + +- title: Your keys (bip39) + desc: On your Bitcoin wallet your Private keys (Seed) never leave your device. You can at any moment generate backups and export/import your wallets, with full control of what to do with your private keys. + +- title: HD wallets + desc: The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), allows creating child keys from parent keys in a hierarchy. The HD Wallets will generate for you a different address for each transactions. + +- title: SegWit + desc: SegWit supported in P2SH-compatibility mode and bech32 Native mode. Segwit was a massive upgrade to the Bitcoin Protocol released in 2017. You will find all wallets with SegWit enabled by default. Find more about SegWit here. + +- title: Export TXHEX + desc: You can get your transaction HEX (TXHEX) without broadcasting it, and only do it with the relay of your choice. + +- title: Dark mode + desc: BlueWallet is now available in Dark mode for iOS and android. + +- title: LNurl + desc: Support for the LNurl protocol with LNurl-pay and LNurl-withdraw. This features allows you to have an easier interaction with the Lightning Network and services that support LNurl. + +- title: Marketplace + desc: Support for the LNurl protocol with LNurl-pay and LNurl-withdraw. This features allows you to have an easier interaction with the Lightning Network and services that support LNurl. + +- title: Lightning Browser + desc: A Lightning browser supporting the webLN standard to help you use and discover new services. + +- title: Multi-currency + desc: BlueWallet supports more than 30 currencies, including USD, AUD, BRL, CAD, CHF, CZK, CNY, EUR, GDP, HRK, INR, JPY, MXN, MYR, RUB, and more. + +- title: Open Source + desc: BlueWallet is built on a public repo, up-to-date and available on the BlueWallet GitHub. This means that any user can build it and run it on his own, without any custodial dependencies. Verify the code and contribute to the wallet development. + diff --git a/_data/authors.yml b/_data/authors.yml new file mode 100644 index 0000000..e067171 --- /dev/null +++ b/_data/authors.yml @@ -0,0 +1,11 @@ +# specify site authors in this file +# you can add .yml files for any other global data in this folder + +dan_urbanowicz: + name: Dan Urbanowicz + email: dan.urbanowicz@gmail.com + web: https://www.danurbanowicz.com +john_doe: + name: John Doe + email: johndoe@email.com + web: http://twitter.com/johndoe diff --git a/_data/backup-wallet.md b/_data/backup-wallet.md new file mode 100644 index 0000000..8406c59 --- /dev/null +++ b/_data/backup-wallet.md @@ -0,0 +1,21 @@ +--- +title: How to backup/export a wallet +subtitle: Access to private keys and recover of wallets +tags: [usage] +--- + +To backup or export your wallet is pretty simple. This backup is the "key", usually a mnemonic (set of 24 words) or just a "text" that will give you access to your wallet if you lose your device, uninstall the app, etc. In short, if something wrong happens and you want/need to get access to your wallet again. + +### Things to know +On bluewallet every wallet has its own backup and there's no global backup for all wallets that you can create, this is something you need to do individually for each wallet. We advise to backup all wallets. + +### Where to do it +Inside your wallet you are going to find on the top right an options menu. Usually with the 3 dots icon. After you tap there you will be taken to the wallet options screen, where you will find the "backup/export" option. + +Send to multiple recipients
+Contact support for any doubts bluewallet@bluewallet.io
+ +{% include faqs.html multiple="true" title="Frequently asked questions" category="problems" subtitle="Find quick answers to frequent questions asked by customers" %} diff --git a/_docs/lndhub-macos.md b/_docs/lndhub-macos.md new file mode 100644 index 0000000..e47ca78 --- /dev/null +++ b/_docs/lndhub-macos.md @@ -0,0 +1,156 @@ +--- +title: LNDHub on Mac OSX +subtitle: Coldcard with Bluewallet - Lightning SD card +tags: + - lndhub +--- +**Requirements:** + +* [NodeLauncher](https://github.com/lightning-power-users/node-launcher) +* Mac Terminal +* Homebrew installed — [https://brew.sh](https://brew.sh/) +* [LndHub](https://github.com/BlueWallet/LndHub) +* [BlueWallet](http://bluewallet.io/) + +Let’s create a self-sovereign mobile lightning wallet using nothing but a Mac, a mobile phone and some software supplied by the fantastic open source community! + + + +Step 1 — LND + +1A — Download and set up Pierre Rochard’s NodeLauncher. + +**[lightning-power-users/node-launcher](https://github.com/lightning-power-users/node-launcher/releases)** + +Setup guide here: + +**[Easiest Bitcoin Lightning Guide](https://medium.com/lightning-power-users/windows-macos-lightning-network-284bd5034340)** + + + +Launch Bitcoin and LND + +1B— “**Launch Bitcoin**” to begin syncing with Bitcoin (12–72 hours). + +1C — “**Launch LND**” to start syncing LND (2–6 hours) + +1D — “**Create**” LND Wallet + +Step 2— LndHub + +LndHub is the open-source wrapper for LND provided by BlueWallet. + +[**BlueWallet/LndHub***Wrapper* ](https://github.com/BlueWallet/LndHub) + +2A — Set up the LNDHub + +git clone [git@github.com](mailto:git@github.com):BlueWallet/LndHub.git\ +cd LndHub + +2B— Copy in the LND Macaroon `admin.macaroon`to the LndHub directory. Quick find from NodeLauncher, “**Show Macroons**”: + + + +Click “Show Macaroons” + +2C — Copy in the `tls.cert` file. Quick find by Nodelauncher “**Advanced**” menu, then “S**how lnd.conf**” + + + +Click “Show lnd.conf” + + + +Copy this file into LndHub folder + +2D — Edit the LndHub `config.js` file to add bitcoin RPC credentials + +sudo nano config.js + +* Change bitcoind.rpc login:password to match the rpcuser & rpcpassword in your bitcoin.conf (use Nodelauncher Advanced menu to locate this file, and then a text editor to open) +* Change all the IP addresses from 1.1.1.1 to 127.0.0.1 +* Change
+
+The BlueWallet project born out of the ashes of the 2017 bull-run. With the frustration of not finding a wallet for our Bitcoin needs. Where we could have a Bitcoin only wallet and full control of the transactions. At the time, there wasn't a single Bitcoin wallet available for iOS that was bitcoin-only, supported Segwit and where we could have fee control. So we decided to build it.
+Our commitment is to build the best Bitcoin wallet we can. With strong focus on open source fundations, self-sovereign principles, decentralization and the Cypherpunk's Manifesto. We will iterate slowly, we will not build it in one day, but we will get there.
+We are a collective of developers and designers focused on bringing tools to self-sovereignity, personal property security and privacy.
Reach out, we will appreciate your feedback.
+ + +{{ include.text }}
+
+
+ {{ include.subtitle | escape }}
{% endif %} + +{{ include.subtitle | escape }}
{% endif %} + {{ include.button_text }} +Easily connect to your hardware wallet through watch-only and PSBTs support.
+Create multiple storages or fake ones in case of a forced disclosure.
+Support for different wallet types. Like Bip84/49/44, electrum, legacy, etc.
+Full node connection through ElectrumX, Electrs or Electrum Personal Server.
+Easily Bump, Cancel or do Batch transactions. With RBF and CPFP.
+With push notifications for pending and confirmed transactions.
+{{ include.subtitle | escape }}
+ {% endif %} + + {% if include.category %} + {% assign faqs = site.faqs | where: "categories", include.category %} + {% else %} + {% assign faqs = site.faqs %} + {% endif %} + +{{ include.subtitle | escape }}
+ {% endif %} + +
+
+
+
+
+ Allows you to refill your Lightning wallet with Bitcoin. It needs 3 confirmations to validate.
+Make payments after scanning a QR code or through an invoice.
+Receive instant payments. Generate invoices that can be easily shared.
+Allows you to have an easier interaction with services that support LNurl. Pay and Withdraw.
+Access and Explore Lightning ready services and start participating on the new layer for payments.
+Directly access your favourite lightning ready apps from our browser.
+Once you have created your Lightning Wallet, you will find the option "manage funds" inside your wallet. This is where you can refill new Wallet.
+Choose your favourite refill option and send a transaction with the desired amount. Keep the amount low, Lightning is experimental.
+Once you send your transaction, it will require 3 comfirmations before your balance appears on your Lightning wallet. Welcome to Lighting.
+
+ The user sends a transaction to a dedicated top-up address, and this balance is added to his account on LNDhub. Then, the user can use this balance to pay Lightning invoices. But under the hood, it’s actually LNDhub who pays the invoice, deducting user’s account balance. It works the same way when the user wants to receive a Lightning payment - it’s LNDhub who creates the Lightning invoice and actually receives coins on one of it’s channels.
+Accept offers from sellers and buy directly from fellow users.
+You can search by location, payment method, currency and offer type.
+Once an offer is accepted a “contract” is created and can be viewed in the app.
+Step 1 - Accept an offer and a secure multisig escrow contract is created
+Step 2 - Seller deposits Bitcoin in the escrow directly from their wallet
+Step 3 - Buyer pays the seller according to the agreed upon payment method
+Step 4 - Seller releases Bitcoin from multisig escrow directly to the buyer’s wallet
+Total flexibility to choose the number os keys and address types.
+Easily import or recover any setup. Compatible with most wallets.
+Safely backup your signing keys simultaneously with all pubkeys.
+Easily backup and spread your coordination setup (pubkeys) for better protection.
+Support for PSBTs and QR codes for maximum security.
+Easily change your setup to allow key rotation or fast signing for emergency situations.
+Provides better protection or safety on...
+In this demo of the Multisig Vaults you can see 2 BlueWallet apps signing transactions offline and airgapped.
++ {{ page.intro_paragraph | markdownify | remove: '
' | remove: '
' }} + +{% endif %} diff --git a/_includes/paginate-blog.html b/_includes/paginate-blog.html new file mode 100644 index 0000000..a1b3815 --- /dev/null +++ b/_includes/paginate-blog.html @@ -0,0 +1,8 @@ + +Individual wallet details and basic functionality.
+Receive or Send payments directly on your wirst.
+See latest transactions from your wallets.
+A x/y/zpub or master public key address can be passed to generate receiving addresses.
+Monitor individual addresses you want to keep an eye on.
+Generate adresses and QR codes for receiving.
+Send transactions by signing them offline or with another wallet.
+To facilitate the experience for big transactons.
+Support for your cold storage solution and hardware devices.
+
+
+
+ Use your wallets with ease on your mobile app while leaving your keys in cold storage. Ability to create, send and receive transactions.
+
+ System Font CSS is set of @font-face rules that let you use the native system font of the OS running the browser.
+
+body { + font-family: system; +} ++ +
+ system-font.css offers eight variations of the system font family; light (300) light italic, normal (400), normal italic, medium (500), medium italic, bold (700), and bold italic.
+
+blockquote { + font: italic 300 system; +} + +p { + font: 400 system; +} ++ +
+ OSX has used three system typefaces. Since El Capitan it has used San Fransisco. In Yosemite it used Helvetica Neue. From Mavericks back to Kodiak it used Lucida Grande. +
+ ++ Windows has used four system typefaces. Since Vista it has used Segoe UI. In XP, it used Tahoma, which oddly enough lacks an italic variation. From Windows ME back to Windows 3.1 it used Microsoft Sans Serif. Finally, from Windows 2.0 back to Windows 1.0 it used Fixedsys. Neither Microsoft Sans Serif or Fixedsys are included in this set, with apologies. +
+ +
+ Also, for those of opposed to joy, remember that Internet Explorer 8 does not support local @font-face rules. Therefore, should you need to reference system fonts in that browser then you will need to do so from the font declaration.
+
+body { + font-family: system, "Segoe UI", Tahoma; +} ++ +
+ Android has used two system typefaces. Since Ice Cream Sandwich it has used Roboto. From Jelly Bean back to Cupcake it used Droid Sans, which also lacks an italic variation. Do you suppose OS developers dislike emphasis? +
+ ++ Ubuntu has always used one system typeface, apty named Ubuntu. That part was easy. +
+ +system going to be a thing?
+
+ Maybe. There are discussions in the W3C to standardize a generic system family.
+
Hi there, I’m Nuno from Bluewallet, a Bitcoin wallet. I’m a UX and Product Designer. And for the last couple of years Bitcoin has been a daily passion, an obsession, and the most exciting thing I’ve come across, since I first connected to the internet.
+ +Usually when I start talking about Bitcoin with my friends, the conversation always goes along the lines of:
+ +Them: “ohh, you are on that shit, have you made some money yet? What about Ripple…?” (lol…).
+ +Me: “It’s not about that, you see, bitcoin is a protocol where you can build things on top of.”
+ +Them: “Really…!? I’m not following”
+ +Me: “Heya, imagine the internet, and services like gmail, facebook and so on. But the internet of money!”
+ +… Crickets***…!
+ +Explaining Bitcoin to your friends is not that simple. The tech is at a very early stage and still has flawed concepts all over the place.
+ +For example:
+ +Early this year, after some time of studying Bitcoin daily, I started looking for open source projects to collaborate on. Long story short, Igor Korsakov, an experienced bitcoin developer found me. After some discussions we were a team building what we think will be the next generation of a bitcoin wallet. Later this year, Marcos Rodriguez found our project on Github and immediately joined the team.
+ +Ok, fu** we are a team of 3 people, how amazing is that??!!
+ +It is pretty cool, but trying to build a wallet with a remote team that has never worked together is not easier than explaining what bitcoin is to your friends. Truth is, most wallets suck and the best examples out there are not really there yet or even close to what the technology allows. For sure what the user experience should be, or will be in the future, doesn’t exist yet, and there’s no one who can tell you what it will look like.
+ +The amount of uncertainty, questions without answers, flawed concepts on the protocol, for sure, don’t help. But having an idea of the direction we should go to, certainly helps. That is what I’m going to try to write about, a glimpse on how I see the UX on Bitcoin will go in the future.
+ +We just started, and after hacking our wallet in React Native (props to Igor), we are now redesigning the main experience and trying to step up the game on what the basic expectations from a user should be for a Bitcoin wallet.
+ +Our first Prototype in Production
+ +
I remember that Igor was not really happy when we were talking about it, and I said something like “looks like a prototype, it’s not there yet…” :D
+ +After the first iteration and having something working in production that we can get feedback and learn from, we are working on the UI and what the main navigation should be.
+ +Wallets need to step up their game on basic things: like GUI quality, navigation that falls in what users expect from an app and their mental models, etc.
+ +Here’s a little preview on how we plan to do just that.
+ +

So pretty much, a lot of catching up is going on a the moment. But we are slowly working on this every day. We will get there!
+ +Also, our lightning solution is right around the corner. Stay tuned for some awesomeness!
+ +After showing you a bit of the short term future, I’m going to ramble about where can we go from here. Most likely in some years I’m going to be so ashamed of this article that I may find myself crying alone in the dark. Nevertheless the future belongs to the dreamers :D
+ +There was this sentence I read somewhere that completely changed the way I understood Bitcoin. Someone saying “the wallet is the interface, it’s where the users will interact with the network. The wallet is the browser!”.
+ +This completely changed my perspective of Bitcoin. If there’s an interface for the users, then people will be able to build services on top of it. People will build banks, mortgage services, loans services. You can pay for your bills, top up your phone, send money to your friends. This is a game changer.
+ +The way we transfer, keep and secure our personal value will never be the same.
+ +So let’s see how can a first, next generation wallet do that…
+ +
In this concept (just a concept) we are seeing a wallet that features a marketplace. Imagine an app (a wallet) that provides the ability for other services to live and be built on top of it. Think about Messenger apps or wechat mini-programs. Where developers have APIs and pre-made Interfaces to create their services on.
+ +A kind of eco-system like this would also solve the common question for wallet builders, “how will you make money from a wallet?”.
+ +Now we have an answer. No problem, you can thank me later :)
+ +At this point you also may be asking yourself. “But this already exists out there?!” Well kind of… There are literally billions of people without access to a bank. Bitcoin brings that access to everyone on the planet. Imagine having a bank account on your pocket, now you (and the rest of people) can have an entire bank!
+ +Another inherent problem of the Bitcoin protocol concerns identity. For sure privacy will be the next big thing, and many projects are working on that. But people are not numbers, Bitcoin will be more social than ever! It’s a network in the end of the day…
+ +The ability to send money to your friends, pay for your food delivery to your local restaurant, or buy from your favourite shop needs to be easy to do. And, most probably it will be conversational too.
+ +QR codes will die, and addresses will be something users won’t interact with.
+ +
At the end of the day, it’s about people and not about the tech. This example aims to exemplify that. Users, services, brands and humans will directly interact with Bitcoin everyday.
+ +This won’t be built in a few days or even in a couple of years. This is a long journey, and the opportunity of a lifetime to build products that will change the future as we know it. Personal and business interactions with value, personal sovereignty and money education are the next revolution!
+ +The most exciting thing since the internet.
+ +We are a team of 3, trying to bring Bitcoin to the people. How can you help?
+ +Thank you for reading and any feedback, comments, thoughts and violent reactions. I’m all yours, see you around!
+ + +It’s here! It took us a while. But the Android version of Blue Wallet is live on play store. With full featured and more exciting new things ahead.
+ +
+undefined
Blue Wallet is an open source project. A Bitcoin wallet built by bitcoiners, by community members, by hodlers, by bitcoin maximalists, and by hodlers of last resort. Call us whatever you want. 😎
+ +But quite simply just by 3 guys who deeply care about bringing bitcoin to the masses. Hi there! We are Igor Korsakov, Marcos Rodriguez and Nuno Coelho. 👋
+ +We were deeply frustrated with the current status of mobile wallet development on Bitcoin. Most of the wallets out there became a shitcoin horror show. Onboarding users to pure speculative useless tokens, where the creators are making money while the normal user is being introduced to scams, frauds on top of being directed to the least interesting aspect of the technology. Wasting time, creating frustration, and thereby resulting to a slow adoption.
+ +We are on a mission to fix that.
+ +We want to bring to the community a wallet focused on the users and their usage. Notice the overuse of the use word…
+ +We plan to do that by focusing our efforts on two main pillars: Security and User Experience.
+ +Let’s take a look on what our MVP (minimum viable product) looks like.
+ +Open Source
+Blue Wallet is built on a public repo, up-to-date, and available on the Blue Wallet GitHub. This means that any user can build it and run it on his own, without any custodial dependencies. Verify the code and contribute to the wallet development. Blue Wallet is made with ReactNative and Distributed under MIT licensed.
Plausible deniability +A custom made feature thinking about your personal security. Blue Wallet allows you to define a different password which will decrypt a fake wallet set up for any situation you are forced to disclose your access or when you don’t want to or you can’t show your real wallet.
+ +Full encryption +Blue Wallet can encrypt everything with an additional password. Biometric security (touch ID, Face ID) is not secure enough, and because this we’ve given you the option to have an additional password to protect and encrypt your wallet instead.
+ +SegWit
+SegWit supported in P2SH-compatibility mode. Segwit was a massive upgrade to the Bitcoin Protocol released in 2017. You will find all wallets with SegWit enabled by default. Find more about SegWit here.
HD wallets +The Hierarchical Deterministic (HD) key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy. The HD Wallets will generate you different public keys for each transactions.
+ +Be in control +Your private keys never leave your device**. You are in full control of your private keys. You can, at any moment, generate backups and export/import your wallets, with full control of what to do with your private keys.
+ +Watch-only wallets +Watch-only wallets allow you to keep an eye on your cold storage without touching your private key. Easily import your address or xpub and watch it from your app without ever touching it.
+ +Flexible fees +Starting from 1 Satoshi. You define, with full flexibility, the amount you want to add to your transaction. Blue Wallet also provides you a fee estimation to give you an idea how much to add to your transaction to be included on the next block.
+ +Replace-By-Fee +If you would like to speed up a transaction, Blue Wallet allows to do just that by supporting RBF. Speed-up transactions by increasing the fee (BIP125).
+ +Export TXHEX +You can get your transaction HEX (TXHEX) without broadcasting it, and only do it with the relay of your choice.
+ +Multiple wallet support +Blue Wallet aims to support maximum wallet standards. Currently supported: BIP44 (HD), BIP49 (HD SegWit), BIP39 Breadwallet-compatible (m/0’/0/0), Legacy single-address, SegWit single-address (P2SH). You can have as many wallets in a single app at the same time.
+ +Ok, all of that is cool. But the future is cooler. Let’s take a look at what is coming next.
+ +So we compiled a list of 4 main focus areas that we are working on at the moment and for the near future. And of course, our backlog and our roadmap are all open for everyone to see and contribute to if anybody should want to do just that.
+ +Lightning Wallets +Wallets with support for the Lightning Network Protocol. It will bring you unfairly cheap and fast transactions.
+ +Batch TX +Ability to pay multiple addresses with a single transaction. Save on fees and optimize blockspace usage.
+ +MultiSig TX +Add security to your funds. Each transactions requires M of N signatures (with keys stored on different physical devices with Blue Wallet).
+ +Plug your node +Plug your own Bitcoin Core node for a maximum sovereignty.
+ +We are a team of 3, trying to bring Bitcoin to the people. Do you want to help?
+ +Thank you for reading and for any feedback, comments, thoughts and even violent reactions you might want to share with us. I’m all yours… See you around!
+ +Check out our previous article on the future of Bitcoin UX
+ + +
BlueWallet for Desktop is out on the mac store
+ +This is the first Bitcoin-only wallet available on the mac store for millions of users. And, a huge effort from the team to bring to the Bitcoin community our first desktop product.
+ +It is kind of a big deal. With a desktop product, we can start to think about things mobile doesn’t really allow us to do, like shipping a wallet with a full bitcoin node, and all the privacy gains that comes with it. Which I bet some of you will appreciate.
+ +For now it is only available for macOS, but we expect to increase the compatibility with other platforms as we go.
+ +HWW integration Easily connect to your hardware wallet through watch-only and PSBTs support.
+ +Plausible Deniability Create multiple storages or fake ones in case of a forced disclosure.
+ +Multiple Wallets Support for different wallet types. Like Bip84/49/44, electrum, legacy, etc.
+ +
Full node Full node connection through ElectrumX, Electrs or Electrum Personal Server.
+ +Transactions control Easily Batch, Bump or Cancel transactions. With RBF and CPFP.
+ +Notifications With push notifications for pending and confirmed transactions.
+ +
And many other features available right from the start.
+ +Give it a try, send feedback. Let’s build the revolution together :)
+ +We are a Bitcoin collective of developers and designers trying to help on how to bring Bitcoin to the people and the people to Bitcoin. Through beautifully crafted open source software.
+ +How can you help?
+ +Thank you for reading and any feedback, comments, thoughts and violent reactions, I’m all yours. See you around!
+ + +BlueWallet has just released support for the Lightning Network. Being a 2nd layer scaling solution, Lightning promises low-fees and instant payments. But as a drawback brings a lot of complexities and unfamiliarities to unsuspecting users.
+ +Completely aligned with Bitcoin’s “be your own bank” for sovereign individuals, Lightning requires users to run their own Lightning nodes (besides their own Bitcoin node), open and manage state channels with other nodes (this is what makes a network), maintain liquidity (both incoming and outgoing) in channels, and basically, do a hard ‘node operator’ work. This is the cost of independence from financial institutions.
+ +Our approach to Lightning is different.
+ +We decided to hide the complexity of running a node under the hood and take over the work of hub operator.
+ +This makes the user experience smooth, bringing Lightning payments to anyone who is at least remotely acquainted with cryptocurrencies and mobile wallets.
+ +We called it LndHub, an opensource wrapper around LND. This is “3rd layer solution” (as we jokingly call it; of course this is not real 3rd layer).
+ +
This is how it works: the user sends his bitcoins to a dedicated top-up address, and this balance is added to his account on LndHub. Then, the user can use this balance to pay Lightning invoices. But under the hood, it’s actually LndHub who pays the invoice, deducting the user’s account balance. It works the same way when the user wants to receive a Lightning payment — it’s LndHub who creates Lightning invoice and actually receives coins on one of its channels.
+ +
This has its drawbacks. Basically, user transfers his funds in custody to a 3rd party (and we all know that trusted 3rd parties are security holes, thanks to Nick Szabo). But how much of a problem is that? Let’s think a bit about it. Trust is minimized to an absolute minimum required to carry its duties. On the other hand, Lightning is expected for day-to-day use, and how much the average user usually has in his pocket for daily expenses? Probably, $50 for groceries and coffee? A fair tradeoff risking those for an exchange of usability.
+ +Of course, on-chain Bitcoins private keys should be in full user’s control. Not your keys — not your coins, as they say. We are thinking of it as “savings” account (as opposed to Lightning — “current” account).
+ +Other drawbacks include centralisation of the network. Given lots of users start using LndHub, amount of funds and liquidity it holds will also grow, turning LndHub into a major Hub on the network. This was anticipated in the dawn of Lightning development, and we don’t see a problem with that. Network still remains open, and is free to morph and mutate as per current economic reality.
+ +Luckily, LndHub is completely opensource, which means any tech-savvy user can deploy his own instance of LndHub and use it with his wallet. This instance can even be shared with the party, such as friends and family: each member will have his own independent balance and transaction history. Should be pretty convenient for someone to onboard more people to the Lightning party. Just install lnd, bitcoind, lndhub and in your wallet settings put a link to your hub. Share the link with your friends and help them config their wallets. Done!
+ +
This also mitigates effects of hub centralization, letting the user maintain control over his on-chain and off-chain funds.
+ +To sum this up, here’s a quick pros and cons list:
+ +Pros:
+ +Cons:
+ +You can give it a try with BlueWallet mobile app (iOS and Android), check out code for LndHub or BlueWallet (both are opensource and MIT licensed), and let us know what you think! Of course, there might be bugs, so be careful and please report them. LndHub API spec is also open, so you can build your own product on top of it.
+ +For bonus cypherpunk points you can build wallet binaries yourself and plugnplay your own bitcoind/lnd/lndhub!
+ +

What is Lightning-powered App (Lapp)? In general, this is any application which works with Lightning network. In our case, this is any web-page that can receive payments or pay you back (not only that but more on that later).
+ +Since BlueWallet added Lightning integration, our users made thousands of payments, and we have some stats and insights to share (which we will in further blog posts), but for now, we want to bring closer users and real business. We want to make it easier for regular people to discover great goods and services, allow them to interact with Lapps, pay and get paid easily.
+ +
Its been one year since Lightning network mainnet launch, and it’s time to take it seriously.
+ +Thus, the very first thing to meet & greet users on the Lapp Browser will be a Lapp Marketplace — a simple collection of Lapps worth of your attention.
+ +In the essence, Lapp Browser is a webview that navigates to Lightning-enabled webpages. The webview has javascript code injected, which bridges user’s Lightning wallet with the Lapp, allowing a more smooth interaction. The interaction part itself can evolve a lot in the future to be and feel more native, more integrated, etc.
+ +BlueWallet partially conforms to webln specification (which is still in early alpha), so any Lapp that implements that spec will integrate with the wallet more naturally. Ideally, paying and getting paid in Lapp will be within one button tap (not a hustle of switching between apps and copypasting bolt11 strings).
+ +
There’s no way to know what the future of wallets will be.
+ +Imagine a world where you have full control of your money. Bitcoin is the main currency online and offline. You open your wallet app where you are able to easily pay your bills, send money to your family, buy stuff online, topup your phone, etc.
+ +This is the world we want to live in. And this experiment is a first step to start learning how can we build this on top of the Lightning Network.
+ +
Lots of work to be done. At the moment very few Lapps implement webln spec. Although this spec is still in alpha stage, it feels like a way to go. For example, every Dapp supports web3 specs, so developers might want to build their next Lapp considering webln compatibility. Except for frictionless send and receive, this spec also drafts providing identity to Lapp (so Lapp can seamlessly create an account and authorize you; no personal information leaked though, only anonymous public key is shared), and also mechanisms to sign messages with your identity, and verify other people signatures. Please, give this spec some love.
+ +BlueWallet’s Lightning integration is custodial by default, but you can easily connect it with your own LND instance for the same experience (everything we do is opensource).
+ +Be warned, there might be bugs (please report them). Actually, with this release we’ve hit a sort of “beta” jackpot: Lapp browser is in beta, Lightning integration is in beta, and BlueWallet itself is still in beta. Don’t use it for large amounts! Be reckless, but not too reckless.
+ +4.2.0 is out for iOS and android. With a massive update! 🤯
+ +New
+
+undefined
Fixed
+Keep your apps updated! Thank you 🙏
+ + + + +Bluewallet v.4.4.1, mobile Bitcoin wallet for iOS and android is out and there are some cool new features that you should know about. Mainly the ability to send all funds, the ability to have a bit more privacy by allow you to hide your balances and the super cool “Scan to receive”, a new functionality available for Lightning based on lnurl spec.
+ +The ability to Send MAX, one of the most requested features appears when you tap on the amount. The keyboard goes up, you can see your total balance and you can tap on it to select the total amount. That simple.
+ +Particularly useful if you want to migrate your wallets to Bech32 wallets ;)
+ +
+undefined
lnurl is a protocol for communication between Lightning wallets and third-party services. It simplifies complicated common flows into standard subprotocols carried on between the user wallet and the service over simple HTTP JSON calls.
+ +Basically it goes like this:
+ +
+undefined
Supported by: BlueWallet, Bitcoin Lightning Wallet and @lntxbot
+ +Can be used on: Kriptode, Lightning Gifts and @lntxbot
+ +The ability to hide your balance is a small privacy improvement. With it you now don’t need to be afraid of opening your wallet in public or over the shoulder kind of situations for instance.
+ +
+undefined
What was fixed
+ +Keep Building! And keep that feedback coming. Free Open Source Software! Thank you all :)
+ +We are always available by email bluewallet@bluewallet.io or on the usual channels.
+ +
Last week we got a call from an Apple employee. That call was about removing our “marketplace” feature.
+ +Apparently it is not permitted to have 3rd party not embedded code for payments in the Apple app store when presented in form of store or store-like interface. This is point 4.7 on the review guidelines for the other teams this issue may concern.
+ +This is obviously terrible news 😢
+ +Terrible news for all the indie devs that we are supporting, promoting, and sending traffic to. Now will have one less source of traffic to count on.
+ +And, it means Apple doesn’t have or provide a solution for wallets to work with lapps/dapps. Which, taking into consideration their monopoly, is something they should provide solutions on. It also reveals a lack of adaptation to new trends and making it difficult for innovation to happen in their eco-system.
+ +A wallet is, at the end-of-day, more like a browser or a gateway type of interface than a “wallet itself”. It is a way for users to interact with the Bitcoin network and with Bitcoin related services. Bitcoin is here to stay. Bitcoin won’t change. Apple should adapt and provide solutions for wallet developers to work with Bitcoin services.
+ +The “Marketplace” feature consists of two elements, a Lightning and Bitcoin enabled services directory and a “Lapp Browser”, that interacts and understands Bitcoin features through protocols like the WebLN.
+ +For all the developers using Bluewallet Lapp browser, the Lapp Browser will still be available and can be easily deeplinked to provide a better experience for direct send/receive.
+ +Example:
+lapp://openlappbrowser?url=your_urlencoded_link_here
We will think of something else and find new solutions. Any suggestion is very welcome. For now, we are extremely sad to announce that the Marketplace feature was removed from the iOS (not on android) version.
+ +Big thanks for all the support we have received. Keep the feedback and ideas coming. We will keep building!
+ +If you wanna hangout here is our group. ✌️
+ + +We have been busy building, that’s a good way to be busy and we haven’t update the blog in awhile, so here it is, an update on the latest releases 😃
+ +We’ve release to production versions 4.5.2, 4.6.0, 4.7.0, 4.7.1 and 4.8.0. These versions include minor new features, bug fixes and user experience improvements. Lots of polishing and small tweaks to make bluewallet more solid and a better free open source product for the community.
+ +

With the feedback sometimes features got to go, which is fine. See you! 👋
+ +A huge amount of bugs squashed, thanks to all the feedback and issues opened!
+ +We are a small team of Bitcoin users trying to help on how to bring Bitcoin to the people and the people to Bitcoin, through beautifully crafted open source software. How can you help?
+ +Thank you for reading and any feedback, comments, thoughts and violent reactions, I’m all yours. See you around!
+ + +Preparing for war — how was 2019 and a glimpse of the future
+ +2019 was a great year for BlueWallet. Although it is a new wallet and still in its infancy, we did get some some media coverage, we did get some recognition from industry experts and we did get some users to remind us how much we suck and how much better it can still be. All that, working on the project on our free time in a pure open source fashion.
+ +This year blew away our wildest expectations on what we thought we could achieve. To give you a bit of perspective, at this time last year we were releasing the android version of the app and our Lightning wallets feature right before Christmas. And probably, at that time, most of you hadn’t really heard about Blue.
+ +Talking about Lightning. While the Lightning Network slowly matures, and after doing our part to put it on the spotlight and bringing the attention it actually deserved. We decided to take a step back and work on the layer that really matters. The base layer.
+ +In the core, BlueWallet is (and always was) a non-custodial on-chain bitcoin wallet, born out of the frustration and ashes of the 2017 Bull market. When fees were high and the majority of wallets still had not implemented segwit and flexible fees. Paying $20 in fees for a transaction because your wallet’s fee estimation was broken? That was a real deal back then.
+ +The very first release of BlueWallet fixed exactly that: segwit, flexible fees (starting from 1 sat/byte), and RBF (replace-by-fee).
+ +During the next cycle of adoption (this is how I like to call the bull-run) I expect to see exactly the same thing we saw in 2017: with that many people discovering the advantages of Bitcoin and making their first happy transactions. The block space will again be an extremely scarce commodity.
+ +After another block reward halving, a more mature fee market will develop, and we will witness a natural competition for block space. This is why I think it is important to prepare for that in advance: your bitcoin wallet app (as a customer-facing software) should be the one to act in your best interests, trying to save as much pennies on transactions as possible and, at the same time, give you the full control you need and should have.
+ +In preparation for that, at BlueWallet we implemented:
+ +I like to repeat that BlueWallet is preparing for war, and this war will be for block space. Once another billion of Earth inhabitants realize the benefits of hard, censorship-resistant and non-confiscatable money.
+ +If this is the kind of fight you want to be part of, protecting the Bitcoin user interests over miners and corporate players, you know where to go. And you are much welcomed!
+ +
That was not the only features we were busy with. Among many, some new and also remarkable features:
+ +We still have a lot of work to do:
+ +And some other more experimental consumer ideas that we are already sharing with the community and putting it out there. The list doesn’t end there, but one needs to keep some secrets as well :) Feel free to bring your ideas on!
+ +Just some statistics of the year:
+ +A special thanks to all the contributors, you guys rock! 🤘
+ +To summarize, we are preparing for war! It will be a war about block space, it will be a war about providing the users with the right tools to fight against corporate interests trying to take advantage of Bitcoin. Join us, we promise it won’t be a boring one!
+ +https://github.com/bluewallet/bluewallet
+ +Cheers!
+ + +Olá! 👋
+ +Thought it would be cool to share what people are working on at the Bluewallet project.
+ +Usually there’s not much visibility on open source projects, unless, of course, you are part of the mailing list, IRC channels or chat groups of the project. So a WIP (work in progress) Post seems like a nice idea. It’s a way to have the community aware, updated, and given a chance to say something. Best to have feelings and violent reactions shared now, than after something is done.😃
+ +We will approach this as a “Now” and “Next.
+ +Now being what we are working on now and should be hitting production at any moment.
+ +Next being what we will be working on and will come sooner than later.
+ +
Bluewallet supports many address types. During 2019, we invested most of our time improving and testing our Bech32 wallets. They are now a powerful open financial systems available to anyone for free. And here’s what you can do with them:
+ +It seems that the time has come, and as Bitcoin Core also made bech32 the default type on the latest release, there’s no reason for us to not do so as well.
+ +
+undefined
BTCPay has become the Swiss Army knife of the Bitcoin tech stack. From developing applications, running nodes, to integrating with hardware wallets, etc.
+ +It seems obvious to us that bringing this eco-system to Bluewallet, where BTCPay users can have an open source native mobile app to interact with their applications, can be the cherry on top of the proverbial cake.
+ +It solves a real problem - where today, users have their wallets on web frontends, which is something not that secure to do. At the same time, we can work on a native experience to improve the User Experience for the end user, who are, in this case, the merchants and store payees.
+ +This opens interesting scenarios, where people would be able to hack cool things. For instance, it could be to explore NFC (Near Field Communication) solutions to develop open source cards/points-of-sale, and so much more on top of BTCPay and native mobile environments and everything they can bring.
+ +How and where can you help or know more?
+ +
+undefined
There’s this saying on the wallets world, “You either die a hero or you live long enough to become an exchange” 😆
+ +Bluewallet doesn’t really want to be an exchange. So integrating with Hold Hodl, where they focus on the exchange technology, so Blue can just focus on the wallet technology, seems like the perfect plan.
+ +Only the future will tell, but I’m super excited about this one. P2P marketplaces definitely bring a lot of value and they are a huge escape tunnel from the regulated world.
+ +Why Hodl Hodl?
+ +No-KYC exchange, non-custodial, P2P transactions, kick-ass multi-sig tech, Lightning on exchanges pioneers, bad-ass group of people. Organizers of the arguably best Bitcoin conference :)
+ +Still at a very early stage, so this is what we can show at the moment. But pretty sure this one will blow many people’s minds.
+ +
+undefined
+undefined
We are a small team of Bitcoin users trying to help on bringing Bitcoin to the people and the people to Bitcoin — through beautifully crafted open source software.
+ +Thank you for reading and any feedback, comments, thoughts and violent reactions, I’m all yours. See you around!
+ + +The BlueWallet project born out of the ashes of the 2017 bull-run. With the frustration of not finding a wallet for our Bitcoin needs. Where we could have a Bitcoin only wallet and full control of the transactions. At the time, there wasn't a single Bitcoin wallet available for iOS that was bitcoin-only, supported Segwit and where we could have fee control. So we decided to build it.
+Our commitment is to build the best Bitcoin wallet we can. With strong focus on open source fundations, self-sovereign principles, decentralization and the Cypherpunk's Manifesto. We will iterate slowly, we will not build it in one day, but we will get there.
+We are a collective of developers and designers focused on bringing tools to self-sovereignity, personal property security and privacy.
Reach out, we will appreciate your feedback.
+ + +