Bitcoin Forum
December 11, 2024, 10:22:32 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Using coldcard With Armory Lockbox  (Read 116 times)
cryptoknut (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
August 27, 2019, 12:29:06 AM
 #1

Hello, I'm trying to use a Coldcard with armory for purpose of using multisig to harden my security, I'm trying to do a 2of2 Multisig lockbox. I am able to get xpub text file but when trying to enter it into the lockbox I get an error message. I'll put an example of the file I get from coldcard  below. Is what I'm trying to do possible or is this just a waste of time.

# Coldcard Wallet Summary File

## Wallet operates on blockchain: Bitcoin Testnet

For BIP44, this is coin_type '1', and internally we use symbol XTN for this blockchain.

## Top-level, 'master' extended public key ('m/'):

tpubD6NzVbkrYhZ4Y7XQkmZe9fchT8GBdsx9MSjEbnTPAhC1FPUHJLD9dcEudPWUayLGy1MtVqu73a2 QfaUv3YB54yUNesAc8dShcUTUNmMhopY

Derived public keys, as may be needed for different systems:


## For Bitcoin Core: m/{account}'/{change}'/{idx}'

m => tpubD6NzVbkrYhZ4Y7XQkmZe9fchT8GBdsx9MSjEbnTPAhC1FPUHJLD9dcEudPWUayLGy1MtVqu73a2 QfaUv3YB54yUNesAc8dShcUTUNmMhopY

... first 5 receive addresses (account=0, change=0):

m/0'/0'/0' => mwokgDX6HQREsFgevxZwKDxmVfDjEqwPuC
m/0'/0'/1' => mwGmYgnd3MDjaTXfp5dgq5YxNtGjfRyTuT
m/0'/0'/2' => mntHLuyhXr6QsVsWstRs3XFHaMXD8AKuLo
m/0'/0'/3' => msU7yGFgbqTJF9n55jYB8e3Hxh4hi7vhhF
m/0'/0'/4' => mjdKAoMcyieEwcscdvrnKzqu4r6bnfQMj1


## For Bitcoin Core (Segregated Witness, P2PKH): m/{account}'/{change}'/{idx}'

m => tpubD6NzVbkrYhZ4Y7XQkmZe9fchT8GBdsx9MSjEbnTPAhC1FPUHJLD9dcEudPWUayLGy1MtVqu73a2 QfaUv3YB54yUNesAc8dShcUTUNmMhopY
# SLIP-132 style
m => vpub5SLqN2bLY4WeZixKds1JXa6Kn4sdmFU5yb6VgScU4mgMPuB7io2wF3FoLwWX4f5CMpbNPKC7b9V GCpmBDHVob4esrb2THH9VV4jmqZ4QqHz

... first 5 receive addresses (account=0, change=0):

m/0'/0'/0' => tb1qk2hk9sdh0akzyc99nx65a2erpuftcek3v4mret
m/0'/0'/1' => tb1q4nfn0gme6yr9fezwlrdzdycfpztswal0j4l38m
m/0'/0'/2' => tb1q2rgcg659h4fte2c6dzljzskyjz5qfftrfwcyv7
m/0'/0'/3' => tb1qsvv9dv4g7uepe5pk0tf3cp7hdgnmtx5hp626ap
m/0'/0'/4' => tb1q952xefka88ep3s8htxgnw0n60a4spqwfppm5mu


## For Electrum (not BIP44): m/{change}/{idx}

m => tpubD6NzVbkrYhZ4Y7XQkmZe9fchT8GBdsx9MSjEbnTPAhC1FPUHJLD9dcEudPWUayLGy1MtVqu73a2 QfaUv3YB54yUNesAc8dShcUTUNmMhopY

... first 5 receive addresses (account=0, change=0):

m/0/0 => mu7NuiLq1PsK7ncvE5cN3YPwU89wCjz4fC
m/0/1 => mvSCNC4w9wBRksZwQsLPL4pyNMbHB8rFKy
m/0/2 => mooEuT4TzKte4yvNxk4T7Du9K9vG1ZfjyK
m/0/3 => mpuSJdR1W3WLEH1FN3KN3Mxye9dBnnJYd6
m/0/4 => miwaFWAkjmAggdFGix4SGiSxaq4zzue78B


## For BIP44 / Electrum: m/44'/1'/{account}'/{change}/{idx}

m/44'/1' => tpubDALcajyQQtb5HRLZ8jAJhVhxbGVY7vSJWfxuYUknNMQDZzjQdWtge5GDNnqw5jB8wCDuDXp1tJQ kFbZyE1YmYawBrJZiHeRWfXr7KBQoxUM

... first 5 receive addresses (account=0, change=0):

m/44'/1'/0'/0/0 => n2sEggcZ9vztixvwaEtf9aJPXTze4qcyEK
m/44'/1'/0'/0/1 => mix1rdoLEzR1n7pmfkRLJRL2eCVhoL9xD6
m/44'/1'/0'/0/2 => mwAy5FLgdKzGnjTwUbkpd7Fp97cRKNjY56
m/44'/1'/0'/0/3 => mi5RvZpkR9yKtxLiVwWqYXiHaYzjskSKgF
m/44'/1'/0'/0/4 => mujhjLQ9cpyqNjbv6NAPTUA6HWjBP64HZv


## For BIP49 (P2WPKH-nested-in-P2SH): m/49'/1'/{account}'/{change}/{idx}

m/49'/1' => tpubDBJSfnStqiS6NpVyZjTGpR27FQQG5x6nAKwycydndiNUcuexGYbc5aW5KE9bAKmTWRWQF6ihZyS oZHRLZk3hCFGfjS3nUNgkrS29K3Aa635
# SLIP-132 style
m/49'/1' => upub5CS2EYcTgPrCZ8jmcU7JzEQEQNsGGhdDsMo1vEtz9nUwiKYZSMFq4wrq1aC3e6rTVbd5P6R9etZ 7DF631nxQv6ma4pDD37a4TJEoPMWrETv

... first 5 receive addresses (account=0, change=0):

m/49'/1'/0'/0/0 => 2NFLZEZVQizq4j1RbPmrM4PDCBVBJT8yz8g
m/49'/1'/0'/0/1 => 2MtnK8YM3trNgW1SGKnHVLxUGQinHJ9gzJN
m/49'/1'/0'/0/2 => 2Muj9cwcCCm6r7qpLxUHe1mRz4D1ikmuGSu
m/49'/1'/0'/0/3 => 2NAwepU6eSdb1c6nnV13SJAqSJEYjbUeNGB
m/49'/1'/0'/0/4 => 2N7bVgw1d1jmipnFL95droVt5JgKvfw9cRr


## For BIP84 (Native Segwit P2PKH): m/84'/1'/{account}'/{change}/{idx}

m/84'/1' => tpubDAZhhJ9SaAKCt2gngU8aA2babxVAM93oBgo2wGknMUDmtLrzvLnynFuAYo4eME3MqWpcTM3DpGL 9J45nQw7CA7VroAY8e7v9Zo6r7mddUMS
# SLIP-132 style
m/84'/1' => vpub5WXYZiyvZXGnue7hZZaEXw5Cvu6cUWZjoqAJ1vusFYi82rZqLocmPgv4GM4gpunHEL46LpLEMqn zqJN3agRvgCgMztPynmcwSPP9aYGfxLs

... first 5 receive addresses (account=0, change=0):

m/84'/1'/0'/0/0 => tb1qtymulkjmx26pvq6n45sly2gmttwc4g5vtgzxez
m/84'/1'/0'/0/1 => tb1q4gcq8et9qvjy3cffzqmhr2qtchhvdy9x6v08cd
m/84'/1'/0'/0/2 => tb1qnmw70uefcns626xu4umftmqx8n7wjusxej7k32
m/84'/1'/0'/0/3 => tb1qzdtj4cn6kj3lt3uha9my2skh0a99e0u59tw45r
m/84'/1'/0'/0/4 => tb1q27ysu4ut4v3wv4xsq55wvrlyn7n4xqjfsslz4h
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3780
Merit: 1375

Armory Developer


View Profile
August 28, 2019, 12:06:55 PM
 #2

Armory doesn't support BIP44 atm, that's in for the next version. So you'd have to input the public keys manually, Armory won't be able to generate these for you from your seed. If you want so sign those coins out of multisig script with Armory, you will have to import the underlying private keys too.

After that, you have to pick your MS script type. I suggest you pick the P2WPSH.

At any rate, addresses in your case are not useful, you need the straight up public keys. You cannot create a multisig script from addresses, as you cannot yield public keys from addresses.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!