faq.html

---
layout: default
title: Frequently Asked Questions
---

<article class="faq">
  <h1>Frequently Asked Questions</h1>
  <style>
    details summary {
      cursor: pointer;
    }

    details summary>* {
      display: inline;
    }

    section {
      padding-bottom: 20px;
      border-bottom: 1px solid #2a2a2a;
    }

    section>h3 {
      padding-top: 12px;
      color: var(--secondary);
    }
  </style>
  <p><a href="/faq_es">Versión en Español aqui</a></p>
  <section id="toc">
    <h2>Table of Contents</h2>
    <ul>
      <li><a href="#what-is-ln">What is the Bitcoin Lightning Network?</a></li>
      <li><a href="#no-sync">Blixt doesn't sync. Why is this and what can I do?</a></li>
      <li><a href="#fees">What fees are used? Is there a cost to use LN channels?</a></li>
      <li><a href="#balance">Why my Blixt balance sometimes is variable?</a></li>
      <li><a href="#reserve">What is the "channel reserve"?</a></li>
      <li><a href="#blixt-peers">With which nodes can I open lightning channels?</a></li>
      <li><a href="#blixt-node">How is it possible to have a node on a mobile device?</a></li>
      <li><a href="#routing">Can I route payments with Blixt Wallet?</a></li>
      <li><a href="#keysend">Can I receive sats through keysend?</a></li>
      <li><a href="#connect-bitcoin-node">How do I connect Blixt Wallet to my own full node?</a></li>
      <li><a href="#umbrel-control">Can I remotely control an Umbrel from Blixt Wallet?</a></li>
      <li><a href="#blixt-restore">I lost my mobile phone (dead, stolen) or simply want to migrate to a new phone, what
          is the procedure?</a></li>
      <li><a href="#restored-funds">I restored my old node using SCB file, but funds are not back to my onchain
          wallet</a></li>
      <li><a href="#home-node-settings">I have one channel with my home node, but I get "no route found"</a></li>
      <li><a href="#closing-channels">What would be the procedure to close channels with a peer node?</a></li>
      <li><a href="#restore-external">Can I restore my Blixt wallet into another app?</a></li>
      <li><a href="#pruned-zombies">Payments with Blixt not working. What can I do?</a></li>
      <li><a href="#blixt-migrate">If I reinstall Blixt wallet or switch devices, can I keep my previous channels?</a></li>
      <li><a href="#blixt-lnaddress">Does Blixt Wallet have a Lightning Address I can receive with?</a></li>
      <li><a href="#blixt-dunder-channels">Channels opened with Dunder are max 200k sats capacity. How can I have larger Dunder channels opened?</a></li>
      <li><a href="#blixt-data">I notice that my Blixt occupy a lot of space on my mobile device. How can I reduce it?</a></li>
      <li><a href="#blixt-taproot">Does Blixt support Taproot channels?</a></li>
    </ul>
  </section>
  <section id="what-is-ln">
    <h3>What is the Lightning Network?</h3>
    <p>Before you start using Blixt Wallet, it's important to get familiarized with terms, procedures, features, etc.
    </p>
    <p>It's a good idea to start reading and get some basic knowledge about LN and how to use it, otherwise it will be
      difficult for you, as a new user, to understand what you are doing with Blixt Wallet as a node LN wallet.</p>
    <p>Here are some resources to start learning:</p>
    <h4>A. General information and documentation about the Bitcoin Lightning Network</h4>
    <ol>
      <li>
        <a href="https://darth-coin.github.io/beginner/ln-airport-analogy-en.html"
          target="_blank" rel="noopener noreferrer">The Lightning Network and the airport analogy</a>
      </li>
      <li>
        <a href="https://medium.com/@fulgur.ventures/an-overview-of-lightning-network-implementations-d670255a6cfa"
          target="_blank" rel="noopener noreferrer">An Overview of Lightning Network Implementations</a>
      </li>
      <li>
        <a href="https://lightning.how" target="_blank" rel="noopener noreferrer">
          Lightning Network Resources, complete library about LN - by Jamesson Lopp
        </a>
      </li>
      <li>
        <a href="https://bitcoin.design/guide/daily-spending-wallet/" target="_blank" rel="noopener noreferrer">
          Daily spending wallet, guide about using a Bitcoin and LN wallet - by Bitcoin Design
        </a>
      </li>
      <li>
        <a href="https://docs.lightning.engineering/" target="_blank" rel="noopener noreferrer">
          LND Documentation - by Lightning Engineering
        </a>
      </li>
      <li>
        <a href="https://www.lightningnode.info/" target="_blank" rel="noopener noreferrer">
          Lightning Node Management – by openoms
        </a>
      </li>
      <li>
        <a href="https://www.lightningnode.info/v/es/" target="_blank" rel="noopener noreferrer">
          Lightning Node Management in Español – by openoms
        </a>
      </li>
      <li>
        <a href="https://bitcoiner.guide/lightning/" target="_blank" rel="noopener noreferrer">
          Beginners LN Guide – by Bitcoin Q&amp;A
        </a>
      </li>
      <li>
        <a href="https://github.com/chaincodelabs/lightning-curriculum/" target="_blank" rel="noopener noreferrer">
          Lightning Network Dev Curriculum – by Chaincode Labs
        </a>
      </li>
      <li>
        <a href="https://github.com/lnbook/lnbook" target="_blank" rel="noopener noreferrer">
          The Lightning Book – by Rene Pickhardt, Olaoluwa Osuntokun and Andreas M. Antonopoulos
        </a>
      </li>
      <li>
        <a href="https://darthcoin.substack.com/p/lightning-network-is-awesome" target="_blank" rel="noopener noreferrer">
          ⚡️ Lightning Network is awesome ⚡️ - collection of all kind of things you can do with LN
        </a>
      </li>
    </ol>
    <h4>B. Video tutorials about the Lightning Network and Bitcoin nodes</h4>
    <ol>
      <li>
        <a href="https://youtu.be/sVeolsQ3cvU" target="_blank" rel="noopener noreferrer">
          What is a Bitcoin node
        </a>
      </li>
      <li>
        <a href="https://youtu.be/z9n8WRfMw8M" target="_blank" rel="noopener noreferrer">
          The Lightning Network: The most efficient payment system in the world
        </a>
      </li>
      <li>
        <a href="https://youtu.be/pOZaLbUUZUs" target="_blank" rel="noopener noreferrer">
          How LN channels work – by Decentralized Thought
        </a>
      </li>
      <li>
        <a href="https://www.youtube.com/user/renepickhardt/videos" target="_blank" rel="noopener noreferrer">
          LN explained – by René Pickhardt
        </a>
      </li>
      <li>
        <a href="https://youtu.be/HlPIB6jt6ww" target="_blank" rel="noopener noreferrer">
          LN Channels Management – by Alex Bosworth
        </a>
      </li>
      <li>
        <a href="https://youtu.be/bW7hvvjum9o" target="_blank" rel="noopener noreferrer">
          Everything you need to know about LN – Till Musshoff
        </a>
      </li>
    </ol>
  </section>

  <section id="no-sync">
    <h3>Blixt doesn't sync. Why is this and what can I do?</h3>
    <p>First of all, let's explain some reasons for WHY it is not syncing, so the user can understand the situation:</p>
    <ul>
      <li>The Blixt app needs to be online (connected to the internet) in order to connect to the Neutrino node and sync
        the block headers and filters. If your device, for some reason, is not connected to a stable internet
        connection, Blixt will stall the sync until it is restarted.</li>
      <li>If you use the Tor network, the connection is quite unstable sometimes, not because of your device but because
        of poor or congested Tor relays in your area.</li>
      <li>Keep in mind that Blixt uses quite a good amount of storage on your device, up to 2GB, so be
        sure to have enough free space, otherwise the app will stop the sync.</li>
      <li>Sometimes the sync was not done properly and the app didn't scan all your BTC addresses.</li>
      <li>If you switched to sync with your own home node, maybe your node was not prepared for this or connection with
        your node was interrupted.</li>
    </ul>
    <p>So what you can do?</p>
    <ul>
      <li>Put your Blixt in "Persistent Mode". Go to Options - Experimental - Persistent Mode. Will restart the app and the LND service will stay active. Video demo: <a href="/assets/images/blixt-persistent.mp4">How to set Blixt LND service in Persistent Mode</a></li>
      <li>Restart the Blixt app (try force close for closing bad connections).</li>
      <li>Remove Tor connection (if is possible and you want it) and restart Blixt.</li>
      <li>Switch between your internet connections (Wifi <-> 4G). That could trigger a refresh of DNS providers in your device.</li>
      <li>Switch back to default sync server node.blixtwallet.com, or just leave it blank. See below more details about neutrino peers.</li>
      <li>Go to <i>Settings -> Rescan wallet</i>, then restart the app. Once restarted, go to <i>Settings -> Read lnd
          log</i>, or go to <i>Settings -> Copy lnd log to local storage</i> to save a copy of the lnd log.</li>
      <li>Check if you have enough space on your device. Move apps, photos, and videos to your mSD card, and leave more
        space on the local disk. Blixt needs up to 1.5GB for its data (block headers, LN graph, channels.db, etc).</li>
      <li>Restart the app, then go to <i>Settings -> LndMobile Help Center</i>, and run a diagnostics test. Get in
        contact with Blixt support on <a href="https://t.me/BlixtWallet" target="_blank">Telegram</a> for further
        instructions or to share logs.</li>
      </ul>
    <p style="color:yellow;">More details about syncing problems.</p>
    <p>All these issues start because YOUR DEVICE IS NOT SYNCING PROPERLY. Please understand this important aspect: Blixt is a mobile LND node, that uses Neutrino for syncing / reading the blocks.</p>
      <ul>
      <li>Here's a less technical explanation from <a href="https://bitcoinmagazine.com/technical/why-bitcoin-wallets-need-block-filters">Bitcoin Magazine</a></li>
      <li>Here are more technical resources from <a href="https://bitcoinops.org/en/topics/compact-block-filters/">Bitcoin Optech</a></li>
      <li>Here is how you can activate Neutrino on your own home node and serve blocks filters for your mobile node, from <a href="https://docs.lightning.engineering/lightning-network-tools/lnd/enable-neutrino-mode-in-bitcoin-core">Docs Lightning Engineering</a></li>
      </ul>
    <p><span style="color:yellow;">REMINDER:</span> Using Neutrino over clearnet is totally safe, your IP or xpub are not leaked. You are just reading blocks from a remote node with neutrino. That's all. All the rest is done on your local device.</p>
    <p>So there's NO NEED to use it with Tor. Tor will add a huge latency on your syncing process and will make your Blixt very unstable. If you really want to use over Tor, be sure what are you doing and have a good connection and patience. Same case for using a VPN. Be careful what latency is given to you from that VPN.</p>
    <p>You can test the latency of a neutrino server by simply ping it, from a PC or from your mobile.</p>
    <center>
    <p><img src="/assets/images/blixt.ping-peer.jpg" class="center"></p>
    </center>
    <p>This is an usual ping to the neutrino server europe.blixtwallet.com, this shows that the connection is very good with a response time of avg 50ms and a TTL of 51. The response time can vary but not too much. TTL must be stable.</p>
    <p>If these values are higher than 100-150ms then your syncing process will stale or even worse, it could cause closed channels by peers ! Do not ignore this aspect.</p>
    <p>Without a proper sync, you also cannot see the correct balance or your LN channels will not get online and operational. No matter how many giga ultra terra mbps you have the download speed IT DOESN'T MATTER. It matter the time response and TTL (time to live).</p>
    <p>This is like a general case for LATAM users. I don't know what happen down there but you guys have a terrible connection with pings of over 200ms that can disrupt any sync.</p>
    <p style="color:yellow;">So what is the solution for these desperate users?</p>
    <ul>
    <li>stop using Blixt with Tor. Is totally useless</li>
    <li>you can use a VPN but choose it wisely and monitor all the time the ping. Use one that is closer to your geographical location. Distance means more ms response time, remember.</li>
    <li>select wisely your neutrino peers, here is a list of well known public neutrino servers:</li>
    </ul>
    <p style="color:yellow;">For US region</p>
    <pre>
    btcd1.lnolymp.us | btcd2.lnolymp.us
    btcd-mainnet.lightning.computer
    swest.blixtwallet.com (Seattle)
    node.eldamar.icu
    noad.sathoarder.com
    bb1.breez.technology | bb2.breez.technology
    neutrino.shock.network
    </pre>
    <p style="color:yellow;">For EU region</p>
    <pre>
    europe.blixtwallet.com (Germany)
    </pre>
    <p style="color:yellow;">For Asia region</p>
    <pre>
    sg.lnolymp.us
    asia.blixtwallet.com
    </pre>
    <p>Another way is to select one from this list of nodes announcing the "compact filters" (BIP157 / neutrino) - <a href="https://bitnodes.io/nodes/?q=NODE_COMPACT_FILTERS">Bitnodes Page Neutrino filter</a>. Choose one that is closer to your geographical location.</p>
    <p>Another way (the best way) is to connect to a local community node, run by a friend or group that you know them, and is offering neutrino connection. <a href="https://docs.lightning.engineering/lightning-network-tools/lnd/enable-neutrino-mode-in-bitcoin-core">Here are the instructions how to do it.</a> Their node will not be affected in any way, they just need a stable and public connection.</p>
    <p>There is a need for more neutrino servers in the LATAM region, for a better and fast sync. So please organize yourself, with your local Bitcoin community and decide who and where is running a Bitcoin Core + Neutrino for your own use. With just a public IP is enough. If you do not have access to a public IP, you can use a VPS IP and make wireguard tunnel to your home node. That way you redirect all the traffic to your local VPS IP, without revealing any private information about your home node.</p>
    <p>Some other "quick fixes" you could do:</p>
    <h4 style="color:yellow;">Time Server</h4>
    <p>Sometimes people use various old devices or are not properly connected to a time server. Neutrino is syncing ok until reached the actual blocks that do not correspond to real local time. You will see in Blixt lnd logs an error saying that "block time stamp is far from future" or something related with "header don't pass sanity check".</p>
    <p><span style="color:yellow;">Quick fix:</span> set the correct time and date for your device and restart Blixt.</p>
    <h4 style="color:yellow;">Low space on device</h4>
    <p>Sometimes using an old device, with low space, it can reach a threshold limit and stuck. Indeed for more you are using this mobile LND node, the neutrino files get bigger and also the channel.db file.</p>
    <p><span style="color:yellow;">Quick fix:</span> Go to Blixt Options - Debug section - Select "stop LND and delete neutrino files". It will restart the app and start a new fresh sync. Sometimes this quick fix can repair also corrupted data. Keep in mind that will take some time, between 1 and 3 min to fully resync. It is NOT deleting existing funds or channels, but yes, after resync it could trigger a re-scan of your bitcoin addresses and that could take more time.</p>
    <p>Next step is to check how much data is still occupied. You can see this in Android App info - data. If is still bigger than 400-500MB, you can compact the lnd files. So go to Blixt Options - Debug section - Select "Compact DB LND". Restart Blixt app if is not doing automatically. The compaction is taking place at startup and is only once. Now you will see that Blixt data is more less occupied.</p>
    <h4 style="color:yellow;">Persistent mode</h4>
    <p>Sometimes people do not open Blixt for long time, so is way too old the sync. But they expect to be synced instantly when they open it.</p>
    <p>Please have patience, and look at the top spinning wheel. Optional you can go to Options - See Node Info and see if is synced to chain and synced to graph marked as "true". Without that "true" mention you cannot use properly Blixt, you cannot see correctly the balance, you cannot see the LN channels online, you cannot do payments.</p>
    <p><span style="color:yellow;">Quick fix:</span> There's a powerful option to "keep alive" your Blixt node. Go to Options - Experiments - Select "Activate Persistent Mode". That will restart your Blixt and will put the lnd service in persistent mode, aka will always be active and keep online your sync, even if you switch to another app or simply close Blixt (not force close or kill the task). You can keep it like that all day if you are in a stable connection and you need to use Blixt several times. It will not consume too much the battery.</p>
    <p>Here is a video demonstration how "Persitent Mode works on Android with Blixt</p>
    <center>
      <video width="320" height="640" controls>
        <source src="/assets/images/blixt-persistent.mp4" type="video/mp4">
      </video>
    </center>
  </section>

  <section id="fees">
    <h3>What are the fees? Is there a cost to use LN channels?</h3>
    <p>1. Blixt Wallet itself does not charge any fees for usage of the app.</p>
    <p>2. Use of the Lightning Network (LN) is <i>not free</i>! This is a myth. Even if the cost of using LN is really
      small, there is a cost, and some users will look at that cost too.</p>
    <p>3. Opening and closing channels on LN <i>has a cost</i>, and sometimes it's not cheap. It also depends on the
      current miner fees when opening a LN channel. Sometimes it can be really high, sometimes it can be really low.
      Users should first learn about how fees work. To learn more about mempool, users can read <a
        href="https://mempool.space/docs/faq" target="_blank" rel="noopener noreferrer">What is
        Mempool?</a>. To learn more about LN fees, users can read <a
        href="https://suredbits.com/lightning-101-lightning-network-fees/" target="_blank"
        rel="noopener noreferrer">Lightning 101: Lightning Network Fees</a>.</p>

    <h4>USE CASE SCENARIO:</h4>
    <p>You are a new Blixt Wallet user, and you have just installed the app. You have no funds deposited into the
      wallet.</p>
    <p>
      Let's say you choose to use the Dunder LSP service (<a href="#blixt-lsp">see down below how Dunder LSP works and
        what is LSP</a>) to deposit 100k sats into your Blixt LN wallet.</p>
    <p>The moment the LSP service receives your 100k deposit, it will use those 100k sats to open a 400k sats channel
      (amount can vary, <a href="https://dunder.blixtwallet.com/ondemand-channel/service-status" target="_blank"
        rel="noopener noreferrer">see here for more details</a>) towards your wallet. You will have 100k sats as
      outbound liquidity and 300k sats as inbound liquidity, but that opening comes at a cost: on-chain fees for the tx
      as well as a commit fee (reserve held for channel closure).

    </p>
  </section>

  <section id="balance">
    <h3>Why my Blixt balance sometimes is variable?</h3>
    <p>The LN balance (spendable) fluctuates because commit fees for channels get renegotiated as the cost to publish to the bitcoin blockchain changes. 
      When the commit fees rise (btc fees become more expensive) some of your local balance is reserved to meet those fees, 
      resulting in your local balance dropping. When fees drop the reverse happens.</p>
    <p>To avoid this issue what you want to do is sum all your channel local balances with the commit fees for only the channels you have opened. 
      There is currently no easy way to tell if you opened a channel or not but there was just a PR in lnd for example to make this easier on developers. 
      Right now the solution I am using is to infer whether or not I opened a channel by its sent, received, and local balance.</p>
    <center>
    <p><img src="/assets/images/blixt-ch-commit-fee.jpg" class="center" alt="Channel Commit Fees"/></p>
    </center>
    <p>Besides the 1% channel reserve you as the funder are responsible for paying onchain fees in case you need to force close the channel by spending the commitment transaction.
      Lightning nodes in general are rather overestimating onchain fees as they cannot rely on the fact that the fees that where taken when the commitment 
      transaction was signed will work in the future if force closing of the channel takes place.</p>
    <p>Things you can do:</p>
    <ul>
      <li>Don't force close channels (fees will be much smaller with mutual closes, since the fee is more accurate and only one tx is needed)</li>
      <li>Have bigger channels then the relative fee. When you have a channel size of 20-30k sats your "spendable" balance could be even 0 in a high fee enviornment.
        But when you have let's say a 300-500k sats channel, those commit fees are almost negligible.</li>
      <li>You cannot even do too much as the fees being used are negotiated between you and your channel partner. 
        If the channel partner starts out with a really high fee there is hardly anything you can do to defend against this.</li>
    </ul>
    <p>The reason for commit_fee to exist is to prepare if the channel ends up in a force closing.</p>
    <p>If your channel has a cooperative closing you can choose how much fee you want to pay with --sat_per_byte.</p>
    <p>If your channel has a force closing the tx fee can't be manually set, but it's set by the LND system based on bitcoin node's estimated fee at the time the channel is closed.</p>
    <p>And most of the time a force closure creates a higher closing tx fee than a co-operative closure, because of this a commit fee is set aside in such a high amount, 
      but if the channel is not closed by force you won't have to spend that much money in fee.</p>
    <p>Currently LND has 20k sat as the channel minimum by default but it's too low. I think it will be changed to a higher number.</p>
  </section>

  <section id="reserve">
    <h3>What is the channel reserve?</h3>
    <p>"I have opened a 500k sats channel, but I can't use more than 495k sats, it says insuficient balance. Why is that?"</p>
    <p>Another aspect to take in consideration is the "channel reserve". If you go to your Blixt - top drawer - Lightning Channels
       you will see in the channel details that is mentioned how much is the channel reserve.
    </p>
    <center>
    <p><img src="/assets/images/blixt-ch-reserve.jpg" class="center" alt="Blixt Channel Reserve"/></p>
    </center>
    <p>A channel reserve is an amount that is set aside by each channel participant which ensures neither have "nothing at stake" 
      if a cheating attempt occurs.</p>
    <p>This reserve (usually 1% of the total amount of the channel) cannot be spent, and is held aside for the entirety of the channels lifetime. 
       Channel reserves make cheating attempts less economical. When one channel party attempts to cheat the other and they are caught, 
       a penalty transaction can be used to steal all the cheating parties bitcoin as punishment. 
       Channel reserves makes it so cheating attempts always have something at stake making this less likely to occur.
     </p>
     <p><a href="https://bitcoin.design/guide/how-it-works/liquidity/#channel-reserve">Read more about LN channel reserve here.</a></p>
     <p>Another aspect to keep in mind is that LND (Blixt LN node backend) is using also "channel buffer fees". 
      <a href="https://github.com/lightningnetwork/lnd/blob/6dea86428d031171af30119e3f6599820dc5454a/lnwallet/channel.go#L3803-L3815">See more technical details here.</a> 
      Practically, when you try to send all sats you see "spendable" in your channel, in fact only 95-99% you can actually send out. 
      But after you send that amount you can continue sending again 95-99% and so on until depletion.</p>
  </section>

  <section id="blixt-peers">
    <h3>With which nodes can I open lightning channels?</h3>
    <p>REMEMBER:</p>
    <ul>
      <li>Blixt Wallet uses private channels, not routing channels.</li>
      <li>You can open channels with whatever node peer you choose, but choose wisely.</li>
      <li>Blixt Wallet is a private node wallet and mostly for quick payments. You will need to find the best routes:
        cheap, fast, reliable, and well connected peers.</li>
      <li>You can connect to your own home node, but keep in mind that at that moment, your home node will be the
        liquidity provider for your wallet, so make sure it's reliable and you have good routes and good fees.</li>
      <li>Not every LN node wants or agrees with private channels. If it is a dedicated routing node, they usually do
        not want private channels because for them it is like "locked" liquidity. It is better if you can first ask the
        node operator if they will agree to a private channel. You can open directly, but be aware that some of them can
        close the channel because they do not want private channels.</li>
    </ul>
    <p>Blixt Wallet itself offers two optional methods for opening channels with the <a
        href="https://amboss.space/node/0230a5bca558e6741460c13dd34e636da28e52afd91cf93db87ed1b0392a7466eb"
        target="_blank" rel="noopener noreferrer">Blixt Node Server</a>:
    </p>
    <ul>
      <li><a href="/guides#guide-autopilot" target="_blank">Autopilot</a>: at the moment, it works only for the first
        on-chain deposit in Blixt and will open a channel with the Blixt Node for the amount you deposited.</li>
      <li><a id="blixt-lsp" href="/guides#guide-lsp" target="_blank">Dunder LSP</a>: Blixt Node Server will provide you
        with an inbound channel until 400k sats, on top of your deposit amount, to start with your first deposit on
        Lightning (if you do not have any other channel). You will need to activate it in the Settings menu.</li>
    </ul>
    <p>Inbound liquidity providers - Blixt also offers a direct link, in the wallet, to LNBig and Bitrefill (Thor). Go
      to <i>Settings -> Inbound channel services</i>. Select the desired one, and follow the instructions provided.
      Those are used only when you need more "INBOUND" liquidity.</p>
    <p>Open channels with any other good nodes - 
        <a href="https://github.com/hsjoberg/blixt-wallet/issues/1033" target="_blank">Blixt Community recommended peers</a>
        is a good source to inspire from other Blixt users. As we've pointed out, we recommend choosing your peers wisely. 
        Blixt is a quick-spending LN wallet. We recommend finding one with low fees or even zero fees. Also, look at <a
         href="https://amboss.space/community/fa2a3e5a-769c-4cbf-ab9d-7ed8680a9ec6" target="_blank">this Amboss Community
         of Zero Base Fee</a> or any other node community. Your Blixt Wallet needs good peers and low fees, so your
         payments will be fast and cheap.
    </p>
    <p>It is very good practice to open channels with merchants or services you pay frequently. Opening a channel with
      your favorite merchant can bring you 0 fees since it is a direct channel and it is like a "line of credit." You
      can also use that channel to pay other merchants or services. Just be aware of their fees for routing your
      payment, because if there isn't a direct payment route, their node will have to route your payment to the next hop
      until it reaches the destination, and that comes at a cost.</p>
  </section>

  <section id="blixt-node">
    <h3>How is it possible to have a node on a mobile device?</h3>
    <p>Blixt Wallet uses the lightning node implementation <a href="https://github.com/lightningnetwork/lnd"
        target="_blank" rel="noopener noreferrer">lnd</a> and the<a
        href="https://suredbits.com/neutrino-what-is-it-and-why-we-need-it/" target="_blank" rel="noopener noreferrer">
        Bitcoin SPV client Neutrino</a> directly on the phone. Lnd has been configured to work well on mobile devices.
    </p>
    <p>Keep in mind that Blixt Wallet is a Lightning node, with LN channels as any other node. That means that in order
      to be able to transact on LN, you need to be online and connected at the moment of the transaction. If you do not
      transact, it's not necessary to stay online. Blixt. Once Blixt is open, it will take a few moments to re-sync the
      latest blocks through SPV Neutrino, and you will be back online. On the other hand, for transacting on-chain (not
      LN), it's not necessary to be online.</p>
  </section>

  <section id="routing">
    <h3>Can I route payments with Blixt Wallet?</h3>
    <p>Blixt is not a routing node, it is more like a private LN node.</p>
    <p>All channels on Blixt are private, which means they are not "visible" to the other routing nodes in the
      network. These so-called "unannounced" channels are used only for private payments.</p>
    <p>Your Blixt LN node can send and receive payments using other nodes as hops, but can not route other payments
      through your Blixt node.</p>
    <p>That's why Blixt is so special ... nobody knows about your payments. <a
        href="https://www.youtube.com/watch?v=toarjBSPFqI" target="_blank" rel="noopener noreferrer">Check out this
        short tutorial about LN onion routing</a>.</p>
  </section>

  <section id="keysend">
    <h3>Can I receive sats through keysend?</h3>
    <p>Yes, always when your Blixt Wallet is online.</p>
    <p>To display your nodeURI/QR code, go to <i> Menu -> Advanced -> Keysend Experiment</i>. Have the payer scan that
      QR code and pay.</p>
    <p>Aspects to keep in mind:
    <p>
    <ul>
      <li>If you want to share your nodeID on a website or send it to someone so they can pay you via keysend, your
        Blixt Wallet must be online at the time of the payment.</li>
      <li>If you, as receiver, are using a Tor connection, the payer also has to use a Tor connection, otherwise they
        cannot "see" your Blixt node and connect with it.</li>
    </ul>
  </section>

  <section id="connect-bitcoin-node">
    <h3>How do I connect Blixt Wallet to my own full node?</h3>
    <p>Under <i>Settings -> Bitcoin Node</i>, you can enter a Bitcoin node to connect to.</p>
    <p>BIP157 compact filter indexing must be enabled for your node. Add this to your bitcoin.conf if it isn't already set:</p>
    <pre>
      blockfilterindex=1
      peerblockfilters=1
    </pre>
    <p>Also your Bitcoin node's port 8333 should be forwarded into your internet router.</p>
  </section>

  <section id="umbrel-control">
    <h3>Can I remotely control an Umbrel node from Blixt Wallet?</h3>
    <p><strong>Blixt Wallet</strong> is a fully fledged lightning node in and of itself. It's not possible to connect to
      and control a remote node like Umbrel, myNode, RaspiBlitz, etc. For that management task, you would need to use
      apps like Zeus, Zap, Thunderhub, Ride The Lightning, or Fully Noded.</p>
    <p>Instead of controlling your node from home, enable Tor and open a channel to it. That way, you could use your
      Blixt Node Wallet as a companion for your home routing node. See more details on the <a href="/guides"
        target="_blank">Guides</a> page.</p>
  </section>

  <section id="blixt-restore">
    <h3>I lost my mobile phone (dead, stolen) or simply want to migrate to a new phone. What is the procedure?</h3>
    </summary>
    <p>
      RULE NO.1 - You should always have a channel backup and keep it in a safe place (e.g., password manager). If you
      did that, the procedure is simple and you have two ways (fast and slow) and also two situations to take into
      consideration (whether you had funds in on-chain or not).
    </p>
    <p>
      RULE NO.2 - Never use a full backup of a device as a restored backup for BTC/LN wallets. This can result in
      losing funds by broadcasting the wrong state of channels.
    </p>
    <p>
      NOTE NO.1 - Migration (or funds restore procedure) means creating a new Node ID and moving the restored funds to
      it. This is a better procedure for privacy, safety of funds, and overall ease of use.
    </p>
    <p>
      NOTE NO.2 - If you have the ORIGINAL DEVICE still working and online with funds in LN channels, NEVER do
      the restore procedure on a new device with the channels restore options. This action will force close the existing
      channels and you could get a penalty for that (broadcasting twice the status of channels). You can ONLY restore
      the on-chain wallet/seed on another device, keeping the original still open, but never restore the channels
      backup.
    </p>
    <p>
      NOTE NO.3 - If, after starting the restore process, you do not see in the "Lightning Channels" menu that the old
      channels have entered the status "closing," or if they are not there at all, it is safe to restart the restore
      process from the backup file. There is no need to start over from zero with an on-chain restore. If your on-chain
      wallet is restored and funds are back, it is OK to continue with LN channel restore.
    </p>
    <p>
      NOTE NO.4 - If you restore LN channels that were open using the Tor network, then BEFORE starting the restore
      process, go to <i>Settings -> Enable Tor</i>. That way, your Blixt node can "see" the Tor peers and start the
      closing procedure in the normal way.
    </p>
    <h4>Scenario A - migrate Blixt to a new device (fast way)</h4>
    <p>Conditions:</p>
    <ol>
      <li>You still have the old device functional</li>
      <li>You have a new device ready with Blixt Wallet already installed (but not started yet)</li>
      <li>You have funds ONLY in LN channels, the on-chain is empty</li>
    </ol>
    <p>Procedure:</p>
    <ul>
      <li>
        Create a new Blixt wallet instance on the new device (new seed) and save that seed into a safe place (e.g.,
        password
        manager).
      </li>
      <li>
        Wait for Blixt to sync (takes just a few minutes), you will see the sync icon on the top right disappear.
      </li>
      <li>
        On the new device <i>Settings -> Enable Dunder LSP</i>.
      </li>
      <li>
        On the new device, go to main screen and click on the <i>Receive</i> button to create a new LN invoice to open a
        Dunder LSP channel.
      </li>
      <li>
        Put the amount of total balance available displayed on the old device Blixt (main screen), then press
        <i>CREATE INVOICE</i>.
      </li>
      <li>
        With the old Blixt device, scan the LN invoice QR code and pay it. The old wallet will send all available funds
        to the new one, and Dunder will open a new channel for you with that amount.
      </li>
      <li>
        It will take a few minutes until the tx is confirmed and the channel is opened on the new device. Be patient.
      </li>
      <li>
        Once you see the funds in the new device available, it is recommended to close those old empty channels. If
        there are some residual satoshis, they will go back to the on-chain wallet and can be sent later to the new
        device using an on-chain tx.
      </li>
      <li>
        DONE! Blixt can now be deleted from the old device, and the funds are safe in the new one.
      </li>
    </ul>
    <h4>Scenario B - old device is lost, non-functional, or non-recoverable (slow way)</h4>
    <p>Conditions:</p>
    <ol>
      <li>You do not have the old device anymore</li>
      <li>You have a new device ready with Blixt Wallet already installed (but not started yet)</li>
      <li>You have funds in the LN channels but also in the on-chain wallet</li>
    </ol>
    <p>Procedure:</p>
    <ul>
      <li>
        Install Blixt Wallet on a new phone.
      </li>
      <li>
        On the first screen to create or restore a wallet, go to <i>Settings -> Enable Tor</i> (if you previously
        opened channels with Tor nodes). You have funds in the LN channels but also in the on-chain wallet.
      </li>
      <li>
        Blixt will restart in Tor mode. Then click on "restore." Fill in your 24 word seed from your old wallet, space
        delimited. You can also add the channels.backup file you saved previously and copy it onto your new phone.
        Optionally, you can use Google Drive, if you have it there.
      </li>
      <li>
        Click "restore" and wait for the app to perform the standard procedure for recovering the funds.
      </li>
      <li>
        Blixt will close the existing channels and, after a few blocks, funds will be recovered and visible in
        your on-chain wallet. Be patient.
      </li>
      <li>
        To check the funds, go to <i> Menu -> On-chain</i>. Click the top right menu to see the Transaction Log. After
        channels are closed and txs are confirmed, locktime expires. The funds are displayed here.
      </li>
    </ul>
  </section>

  <section id="restored-funds">
    <h3>I restored my old node using the SCB file, but funds are not back in my on-chain wallet.</h3>
    </summary>
    <p>OK, I had a previous dead node and I used the restore procedure, using the SCB backup channels file into Blixt. I
      wait for the channels to be closed, but funds are not back in my on-chain wallet. What can I do?</p>
    <p>Usually, there are a few possible scenarios for closing channels:</p>
    <ul>
      <li>
        A normal "cooperative close" channel usually takes a few blocks if both peers are online. Then everything goes
        smooth and fast.
      </li>
      <li>
        If the other channel peer is not online, the closure task takes effect. This could take at least 144 blocks
        until funds are released from the lock time. Check the locktime for the closing tx on mempool.
      </li>
      <li>
        A normal closure can be for many reasons, but mostly because of lost connectivity. If a normal closure gets
        stuck, then once the rest of the channels have entered into a "waiting to close" state, you could repeat the
        process to once again push the closure of the remaining stuck channels.
      </li>
      <li>
        Another way to "push" the connection with your lost peers is to add them manually. Go to <a
          href="https://mempool.space/lightning" target="_blank" rel="noopener noreferrer">mempool.space/lightning</a>, search for your peer,
        copy or scan the QR URI of your peer, and go to <i>Settings -> Show Lightning Peers -> +</i> .
      </li>
      <li>
        To try a force closing action again, go to <i>Menu -> Lightning Channels</i>. Select the channel you want to
        push, and swipe on activity view to start the process again.
      </li>
    </ul>
    <p>Once all the channels are initiated into "closing", wait patiently. This process takes time.
      If you see that on mempool the tx has released the funds, check your on-chain wallet. If funds are still
      not there, it means that the lnd wallet has to rescan previous addresses and refresh the wallet history. Some
      UTXOs are linked to "anchor outputs," so they are more complicated to get back on-chain.</p>
    <p>When you see that all channels are closed, go to <i>Settings -> Rescan wallet</i>. Activate it and restart the
      app if it does not do so automatically.</p>
    <p>Only when the lnd is initiated, can the rescan take place. Be patient and check the lnd logs (see <i>Settings ->
        Read lnd log</i>). You will read in there how it is scanning many blocks at once for your restored addresses.
      Once the process is finished, you should see the funds in the on-chain wallet.</p>
    <p>Try to keep the Blixt app active during this process. If it is interrupted, you will have to restart again to
      trigger it.</p>
    <p>IMPORTANT NOTES TO CONSIDER (in regards of how LN funds are moved):</p>
    <ul>
      <li>When you open a channel of 2M sats with a peer, in the beginning, all the sats will be on YOUR side.</li>
      <li>You start moving these sats by making payments and/or routing others' payments through this channel.</li>
      <li>If you do not make your own payments out of your node, your balance will always be the same, but some channels
        will move sats in and out.</li>
      <li>By routing others' payments, the dynamic of your channel's balances is changing. That is, if you started with
        2M sats and routed 1M sats, your channel balance will be 1M sats. When you close that channel, you will get back
        1M sats and NOT 2M sats that you had initially.</li>
      <li>Before you begin to close your channels, remember the total balance you had in your node on YOUR side of the
        channels. That is the amount you will get back. Some channels will be empty on your side, so don't expect to get
        sats from those closed channels.</li>
    </ul>
  </section>

  <section id="home-node-settings">
    <h3>I have one channel with my home node, but I get "no route found". What can I do?</h3>
    <p>In this case, having only one channel open with your own node, you will need to tweak a bit your node.</p>
    <p>And we've found these options that will help your Blixt to "communicate" better with your home node.</p>
    <p>Go to your home node lnd.conf file and add these lines:
    <p>at the end of [Application Options] section</p>
      <pre>numgraphsyncpeers=9</pre>
      <pre>ignore-historical-gossip-filters=false</pre>
    <p>under [Routing] section</p>
      <pre>routing.strictgraphpruning=false</pre>
    <p>under [gossip] section (create it at the end if you do not have it)</p>
      <pre>gossip.max-channel-update-burst=20</pre>
      <pre>gossip.channel-update-interval=1m</pre>
    <p>We always recommend to have more than one channel open and not just with the same peer, but with different peer nodes. 
      <a href="#blixt-peers">As we explain it in this section.</a></p>
  </section>

  <section id="closing-channels">
    <h3>What would be the procedure to close channels with a peer node?</h3>
    <p>I have a channel with a peer node that I want to close it / peer announced that will shut down his node.</p>
    <p>I would like to have the minimum impact possible over my remaining balance and pay minimum fees.</p>
    <p>The simple answer is to have a "collaborative closing", so follow this procedure:</p>
    <ul>
      <li>Wait for Blixt to sync and also bring online your LN channels.</li>
      <li>Eventually check Blixt lnd logs in settings if all the sync is done.</li>
      <li>Check if your peer is connected. Go to Settings - Lightning peers and check if the peer with which one you want to close is online. 
          If is not, try to add it, by scanning his node URI.</li>
      <li>Go to Blixt top drawer - Lightning channels</li>
      <li>Select the channel you want to close and click on the red button "Close channel".</li>
      <li>Confirm the closing and wait with Blixt app active until you see the confirmation tx of the closing channel.</li>
      <li>It will take few moments to be closed, depending on the status of the <a href="https://mempool.space">mempool</a></li>
      <li>Once the closing tx will have 3 confirmations in the mempool, your remaining funds will be displayed in the on-chain wallet.</li>
    </ul>
    <p>Done. This will close the channel with minimum costs in fees and also the channel reserve is returned to your onchain address.</p>
    <p>If you want a "force close" of the channel, in case that the peer is already shut down, non-responsive, 
       then instead of a simple click on the red button, use a long press on the same button and then the popup message will contain the words
       "Do you want to FORCE CLOSE this channel?" and will push the closure with a higher fee.</p>
    <p>REMEMBER: this procedure will take more time to be confirmed, due to a lock time of the closing tx, in case are penalties to apply.
       It could take up to 144 blocks, aproximately 2 weeks, but no more.</p>
    <p>If for some reasons, the coop close is not done well (see if your txid is not broadcast in the mempool after long time),
       then you could try to push a "force close" of the "waiting to close" status. This could happen sometimes, for various reasons.
    </p>
    <p>Here is an example:</p>
    <center>
    <p><img src="/assets/images/blixt-force-close-channel.jpg" class="center" alt="Blixt Force Close Channel"/></p>
    </center>
    <p>Once you hit the button "Force close pending channel" you will be asked if you are sure and then a message that it will start force close.</p>
    <p>Be patient, after few moments, you will see in the lnd logs the message that the force close was inititated:</p>
    <pre>[INF] PEER: Waiting for confirmation of cooperative close of 
      ChannelPoint(6659e11bd3fc6f266c2e057545a7b4c8ec6e6dbc3579167e4346889af602b485:1) 
      with txid: ce3ed9c8396c8dda4085be8aef4eff4207562f7fdfb79413ab27b828789170ac
    </pre>
    <p>When the txid is taken in a block and you have the 1st confirmation, you will hear a jingle from Blixt app.
      The closing is on the way, but be aware of the indicated maturity block height, is when actually you will receive the funds in onchain.
      Usually are 144 blocks for force closing. That means aprox. 1 day.
    </p>
  </section>

  <section id="restore-external">
    <h3>Can I restore my Blixt wallet into another app?</h3>
    <p>Yes. Remember that Blixt is a full vanilla LND node wallet (aezeed).</p>
    <p>What does it means that? Means that you can restore it in any other wallet app that support <a href="https://coldbit.com/what-types-of-mnemonic-seeds-are-used-in-bitcoin/">LND/aezeed type mnemonic seed</a>.</p>
    <p>IMPORTANT NOTE:</p>
    <p>There is a limitation anyways. Blixt now is using also Taproot type of addresses. Is not by default, but if you activated that option
       in Settings, your Blixt wallet will generate Taproot format addresses.
       Keep in mind that not all other apps that can import xpub or full Blixt aezeed wallet could also display / read those adddresses.
       That means, you will miss some sats in your balance displayed because those taproot addresses will be ignored. That doesn't means you lost your sats.
       It just that are not displayed, not shown, not "readable" by the app you use to import the wallet.</p>
    <p>Let's say you cannot install anymore Blixt app on your device. You could use the following procedures, to restore your funds from a Blixt wallet:</p>
    <h4>A. Using <a href="https://zeusln.com">Zeus LN</a>.</h4>
    <p>There are two ways/methods to restore your Blixt node into Zeus: only onchain wallet and / or full recovery with LN channels.</p>
    <ul>
      <li>Only onchain recovery - Simply put your Blixt 24 words aezeed seed into <a href="https://docs.zeusln.app/for-users/embedded-node/backup-and-recovery">Zeus restore procedure</a>
        wait few moments to restore old UTXOs and done. Wait for Zeus to rescan all UYXOs and all your onchain balance will appear into the onchain wallet.</li>
      <li>Full recovery with channels funds - Take the SCB file exported previously from your Blixt node and copy the encrypted Basde64 code into 
        <a href="https://docs.zeusln.app/for-users/embedded-node/backup-and-recovery">Zeus restore procedure</a>. Remember also to insert the 24 words seed.</li>
    </ul>
    <h4>B. Using <a href="https://bluewallet.io">Bluewallet</a>.</h4>
    <p>Simply put your Blixt 24 words seed into restore procedure, wait few moment to restore old UTXOs and done.</p> 
    <p>REMINDER: this is restoring ONLY onchain wallet, not also the LN channels! And also will not read your taproot addresses from your wallet.</p>
    <h4>C. Using <a href="https://electrum.org">Electrum Wallet</a>.</h4>
    <p>This procedure is very well described <a href="https://www.lightningnode.info/technicals/restorelndonchainfundsinelectrum">in this excellent guide</a> by openoms.</p>
    <p>REMINDER: this is restoring ONLY onchain wallet, not also the LN channels! And also will not read your taproot addresses from your wallet.</p>
    <h4>D. Using <a href="https://sparrowwallet.com/">Sparrow Wallet</a>.</h4> 
    <p>REMINDER: this is restoring ONLY onchain wallet, not also the LN channels! And also will not read your taproot addresses from your wallet.</p>
    <p>The procedure is not complicated but require some steps:</p>
    <ul>
      <li>Go to <a href="https://guggero.github.io/cryptography-toolkit/#!/aezeed">Cryptography Toolkit</a> and download the page as HTML file onto your computer.</li>
      <li>Open that HTML file in "offline mode" (no internet) and select "aezeed Cipher Seed Scheme" from Tools. Then go to the 2nd tab "Decode Mnemonic".</li>
      <li>Paste your 24 words into the "Mnemonic" field.</li>
      <li>Select format BIP84 native segwit and wait a bit to be decoded.</li>
      <li>Copy the zprv displayed into the field "HD node root base 58".</li>
      <li>Open (already downloaded) Sparrow wallet app and select "new wallet".</li>
      <li>In the "Keystores" select "new imported software wallet".</li>
      <li>In the next window that will open, select "Master Private Key BIP32" and paste that "zprv" key you get it from the cryptography tool and click "import". It will show you that is a m/84'/0'/0 derivation path. That will import only the segwit P2WPKH type of addresses. But if you used Taproot P2TR addresses, then you should change it into "m/86'/0'/0".</li>
      <li>Click on "Import Keystore" and it will go back to main window of the wallet app where you can see all the wallet config. Click on "apply" and will prompt you to set a password to encrypt your local wallet file.</li>
      <li>If you used both types of addresses in Blixt, we suggest to import them as two wallets in Sparrow, using the same "xprv" key but each one with a different derivation path. In this way you can avoid confusions.</li>
      <li>You can also change between segwit and taproot an already imported wallet, by going to wallet Settings and switch the "Scrypt Type" ("bc1q" (<a href="https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki">BIP84</a>) segwit P2WPKH or "bc1p" <a href="https://github.com/bitcoin/bips/blob/master/bip-0086.mediawiki">BIP86</a> taproot P2TR) and then re-import the BIP32 xprv keys to make the switch.</li>
      <center>
      <p><img src="/assets/images/shtf-sparrow-p2tr.png" class="center" alt="Sparrow wallet settings"/></p>
      </center>
      <li>Sparrow app will start scanning all your keys and txs and it will be displayed after
          a while in the "Transactions" tab. Patience, it will take some time.</li>
    </ul>
    <p>REMINDER: this is restoring ONLY onchain wallet, not also the LN channels! And also will not read your taproot addresses from your wallet.</p>
    <p>And done! You've just restore your Blixt onchain wallet in Sparrow.</p>
    <h4>D. Using another LND node instance.</h4>
    <p>Yes, is fully compatible with any desktop LND node, as myNode, Raspiblitz, Umbrel, Nodl, Citadel etc.</p>
    <p>You could even restore your funds from LN channels if you have the SCB file (static channels backup) from Blixt.</p>
    <p>Simply follow the regular procedure of restoring a LND node using the seed + scb file: 
       <a href="https://www.lightningnode.info/recovery/lndrecovery">LND nodes procedures</a></p>
    <p>This procedure could also read/restore your taproot addresses from your wallet, if you are using a LND version higher than 0.15.4.</p>
  </section>

  <section id="pruned-zombies">
    <h3>Payments with Blixt not working. What can I do?</h3>
    <p>During the Blixt v0.6.2 our team did a lot of testing in regards of pruned zombie channels 
       that were affecting the normal activity of LN users and especially Blixt users.</p>
    <p>To fix this annoying issue (payments stuck or mostly failed) it was released the Blixt v0.6.3 
       with a special flag for prunning all these zombie channels. 
       Unfortunately, to get rid totally of this issue, Blixt users must close old existing channels, 
       create from scratch a new Blixt wallet / nodeID using the new v0.6.3 or next ones.</p>
    <p>Procedure A - keep the same Blixt nodeID/ wallet seed:</p>
    <ul>
      <li>Open your Blixt Wallet, wait to be fully synced (onchain and LN graph).</li>
      <li>Go to top drawer and select "Lightning Channels".</li>
      <li>Select "close channel" for each channel you already have open.</li>
      <li>Keep your Blixt app online / active until you see the closing transaction done and your funds are back in your onchain wallet.</li>
      <li>Go to "Settings" and from "Show mnemonic" write down your 24 words seed words (if you didn't saved them before).</li>
      <li>Now, you can go and uninstall the existing Blixt app (v 0.6.2). It will wipe all Blixt data from your device.</li>
      <li>Install the latest Blixt version (<a href="https://github.com/hsjoberg/blixt-wallet/releases">See here the github releases page</a>)</li>
      <li>When you start the new Blixt app, select "Restore" and put your previous 24 words seed.</li>
      <li>Wait until is recovered and all the old addresses are rescaned and your funds will appear in the Blixt onchain wallet. Have patience.</li>
      <li>Now you are ready to open new LN channels as usual with the balance you already have restored.</li>
    </ul>
    <p>Procedure B - create a new Blixt nodeID / wallet seed:</p>
    <ul>
      <li>Open your Blixt Wallet, wait to be fully synced (onchain and LN graph).</li>
      <li>Go to top drawer and select "Lightning Channels".</li>
      <li>Select "close channel" for each channel you already have open.</li>
      <li>Keep your Blixt app online / active until you see the closing transaction done and your funds are back in your onchain wallet.</li>
      <li>Go to top drawer - "Onchain wallet" and send all funds to other external onchain wallet (temporary).</li>
      <li>Now, you can go and uninstall the existing Blixt app (v 0.6.2). It will wipe all Blixt data from your device.</li>
      <li>Install the latest Blixt version (<a href="https://github.com/hsjoberg/blixt-wallet/releases">See here the github releases page</a>)</li>
      <li>When you start the new Blixt app, select "New wallet" and follow all the instructions for a new Blixt wallet.</li>
      <li>Wait until is synced and then send back all the sats you had in that temporary onchain wallet to this new Blixt wallet.</li>
      <li>Once you get back the sats, you are ready to open new LN channels as usual with the balance you already have restored.</li>
    </ul>
  </section>

  <section id="blixt-migrate">
    <h3>If I reinstall Blixt Wallet or switch devices, can I keep my previous channels?</h3>
    <p>Blixt follows the LND standard procedure of restoring funds using the SCB file (SCB = static channels backup) previously saved</p>
    <p>Please make your usual SCB backups and follow the instructions described in the chapter <a href="#blixt-restore">Restore Blixt funds</a></p>
    <p>REMINDER: do the SCB backup each time you open or close a LN channel. There's NO need after each payment.</p>
    <p>Nevertheless, recently it was implemented a new Blixt feature for migrating an old node with existing channels into a new device,
      but is not recommended for inexperienced users and we want to be done ONLY under close supervision of Blixt devs/support.</p>
    <p>So in order to do this step, please contact Hampus or support team in the <a href="https://t.me/blixtwallet/411466">Blixt Telegram group chat</a> for asssitance</p>
  </section>

  <section id="blixt-lnaddress">
    <h3>Does Blixt Wallet have a Lightning Address I can receive with?</h3>
    <p>Yes, starting with <a href="https://github.com/hsjoberg/blixt-wallet/releases/tag/v0.6.9-420">Blixt v0.6.9-420</a> you can have a Lightning Address of your own.</p>
    <p><a href="https://github.com/hsjoberg/lightning-box">Lightning Box</a> is a Lightning Address provider for mobile nodes like Blixt Wallet, letting you receive Lightning Address payments directly to your phone.</p>
    <p>This works in conjunction with the Persistent Mode released in v0.6.9, which allows Blixt Wallet to stay active in the background in order to receive payments. Keep in mind that this feature is available only for Android users.</p>
    <p>You can also use this for <a href="https://nostr.com">NOSTR</a> tipping and with <a href="/guides#guide-sn">Stacker News</a> too.</p>
    <p>Register your own Lightning Address from the left menu -> Advanced -> Lightning Box.</p>
    <p>Lightning Box is open-source software and you can run your own instance, working seamlessly with Blixt Wallet.
      A draft specification for the protocol can be found <a href="https://github.com/hsjoberg/blips/blob/lnurl-forwarding/blip-lnurlforward.md">here.</a></p>
    <p>The Blixt Project hosts a Lightning Box service for @blixtwallet.com Lightning Addresses. In the future we will look at Lightning Box support without using Persistent mode and for other platforms than Android.</p>
    <p><strong>Important note:</strong> If battery drain for Persistent Mode is high, try "Compact lnd's databases" from Settings -> Debug.</p>
  </section>

  <section id="blixt-dunder-channels">
    <h3>Channels opened with Dunder are max 200k sats capacity. How can I have larger Dunder channels opened?</h3>
    <p>Yes, the current limit for opening Dunder channels with Blixt node is max 200k sats.</p>
    <p>And that is for some reasons:</p>
      <ul>
      <li>Blixt node MUST put from its own pocket the amount of sats as remote balance.</li>
      <li>Blixt node, is offering this service for free now, but this could not stay forever. It is just a courtesy for a easy onboarding new users.</li>
      <li>Blixt developers are encouraging more node operators to run <a href="https://github.com/hsjoberg/dunder-lsp">Dunder server</a> 
          and offer themselves these kind of services, with larger size of the channels and including charging fees. If you will run such Dunder service,
          your Dunder server could be listed in Blixt app as optional provider too. Like this one (from another Blixt developer): dunder.eldamar.icu,
          offering even smaller channels as 200k sats max for testing purposes.</li>
      <li>Do NOT consider Dunder channels as inbound channels! These are designed to be used as quick onboarding method,
          when the new user do not have any sats in his new Blixt wallet onchain, to be able to open channels. Yes, you can open multiple dunder channels,
          but please do not abuse this option and also having multiple channels with same peer is NOT recommended and could end up in failed payments.</li>
      </ul>
      <p>We encourage other node operators to start using our open source code for Dunder LSP. <a href="/guides#guide-dunder-lsp">Read here a mini guide.</a> 
        That will decentralize more the offers for LSP channels and also could offer larger channels, by demand.</p>
      <p>To change the default Dunder provider, go to Settings -> Set Dunder server and put the name of server. 
       Then go to Debug Section -> Test Dunder server and see if is responding correctly. After that you can open a new Dunder channel.</p>
    <p>If the user need more inbound liquidity, please use the specific method with Inbound LSP, that you can find it in Settings.</p>
  </section>

  <section id="blixt-data">
    <h3>I notice that my Blixt occupy a lot of space on my mobile device. How can I reduce it?</h3>
    <p>Yes, that could happen due to Neutrino sync that is keeping the old sync temporary data on the device. 
      Also a part of that data is from LN Graph sync, but is not too much and that data is re-synced every time you open Blixt, 
      overwritting the old one.</p>
    <p>Until new developements on Neutrino server code, we advice to do the following steps to clear up that old data.</p>
      <ul>
      <li>DO NOT clear data from Android app storage details!</li>
      <li>Open Blixt and go to "Settings". Scroll way down to the "Debug" section and click on "Stop LND and delete Neutrino files".</li>
      <li>This will restart Blixt and at the startup will erase the old neutrino data and resync the new ones, freeing up the storage.</li>
      <li>Next step is to compact the LND database. Again, go to Blixt "Settings", way down to "Debug" section and click on "compact lnd database"
        Blixt will restart again and in few moments will compact the database. This compaction will have a serious good effect and will improve battery life.</li>
      <li>Now you can go back to Android Blixt app storage details and check the occupied space.</li>
      </ul>
    <p>This procedure is also good to do it, when you se your Blixt in persistent mode. We've notice that by deleting this old data the device is not working
      so intensively and heating up the battery. Also is noticed an improved less utilization of the battery.</p>
  </section>

  <section id="blixt-taproot">
    <h3>Does Blixt support Taproot Channels?</h3>
    <p>Yes, starting with v0.6.9 Blixt support Simple Taproot Channels. 
      For the moment are available only for opening normal LN channels. Soon will be available for Dunder LSP channels too.</p>
    <p>Important aspects about Simple Taproot Channels:</p>
    <ul>
      <li>Allow users to open unannounced (private) channels with Taproot transactions improving on-chain privacy and cost efficiency.</li>
      <li>Closing these channels, less fees are incurred and are given more privacy as they appear to like any other 
        Taproot spend when examining their on-chain footprint.</li>
      <li>the integration of Schnorr signatures with Taproot enhances on-chain efficiency by enabling signature aggregation. 
        This development ensures that on-chain cooperative operations become more space- and cost-efficient.</li>
    <p><a href="https://lightning.engineering/posts/2023-10-03-lnd-0.17-launch/">Read more about Taproot Channels here.</a></p>
    </ul>
  </section>
</article>