louneskmt

BIP-32 based seed generation for auth protocol, hardware wallet compatible version

Context

There exists currently two ways of generating the seed for the LUD-04 auth protocol (LNURL-auth, key-auth):

• LUD-05: BIP32-based seed generation, for regular BIP32 hot wallets
• LUD-13: signmessage-based seed generation, mainly dedicated for Lightning nodes that offer a signmessage API. This is the most used seed generation.

Both are not suitable for hardware wallets (HW) for several reasons:

• HW don't expose the device private keys, necessary for LUD-05

louneskmt

#!/bin/bash

ORG_NAME=$1
REPO_NAME=$2

if [[ -z REPO_NAME || -z ORG_NAME ]]; then
  echo "Usage: bash remove_failed_workflows.sh <USER/ORG NAME> <REPO NAME>"
  exit 1
fi

louneskmt

Umbrel Recommanded Hardware

Get Started instructions.

Amazon Global / US

• Raspberry Pi 4 - 4GB or Raspberry Pi 4 - 8GB
• 1TB SSD
• SSD Enclosure
• 16GB+ microSD

louneskmt

Umbrel - Recommanded Hardware List for Amazon UK

• Raspberry Pi 4 - 4GB or Raspberry Pi 4 - 8GB
• 1TB SSD
• SSD Enclosure
• 16GB+ microSD
• Official power supply
• Ethernet cable
• Case

louneskmt

#!/bin/bash -e

if [ "$EUID" -ne 0 ]
  then echo "Please run as root"
  exit
fi

check_dependencies () {
  for cmd in "$@"; do
    if ! command -v $cmd >/dev/null 2>&1; then

louneskmt

#!/bin/bash -e

if [ "$EUID" -ne 0 ]
  then echo "Please run as root"
  exit
fi

while [[ "$#" -gt 0 ]]; do
    case $1 in
        -h|--help) 

louneskmt

### Keybase proof

I hereby claim:

  * I am louneskmt on github.
  * I am lounes_kmt (https://keybase.io/lounes_kmt) on keybase.
  * I have a public key ASAJYOFao4Yq3F0BH-cibf9pyocKyfwQiW1jiNMMePqCgwo

To claim this, I am signing this object:

louneskmt

Keybase proof

I hereby claim:

• I am lounes-kmt on github.
• I am lounes_kmt (https://keybase.io/lounes_kmt) on keybase.
• I have a public key ASAJYOFao4Yq3F0BH-cibf9pyocKyfwQiW1jiNMMePqCgwo

To claim this, I am signing this object: