smartsanctions has left #bitcoin-core-dev [#bitcoin-core-dev]
bairen has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
bairen has quit [Ping timeout: 240 seconds]
sipsorcery has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
sudoforge has joined #bitcoin-core-dev
pink_sarco is now known as shiza
mikehu44 has quit [Ping timeout: 256 seconds]
shiza is now known as pink_sarco
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
shesek has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
vysn has quit [Remote host closed the connection]
kexkey_ has joined #bitcoin-core-dev
kexkey has quit [Ping timeout: 272 seconds]
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
kexkey_ has quit [Quit: kexkey_]
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
kexkey has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
kexkey has quit [Quit: kexkey]
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43_ has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
kexkey has joined #bitcoin-core-dev
ghost43_ has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
kexkey has quit [Quit: kexkey]
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
bitdex has quit [Ping timeout: 240 seconds]
bitdex has joined #bitcoin-core-dev
roconnor has quit [Ping timeout: 256 seconds]
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
bitdex has quit [Ping timeout: 240 seconds]
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
meshcollider has quit [Changing host]
meshcollider has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
bitdex has joined #bitcoin-core-dev
flooded has joined #bitcoin-core-dev
flooded is now known as _flood
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
kexkey has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
kexkey has quit [Quit: kexkey]
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
<jeremyrubin>
bitcoin core doesn't have an API for getting a valid pubkey for taproot does it?
<jeremyrubin>
trying to figure out if it's something worth having
<jeremyrubin>
the way i can think of doing it is getnewaddress and getaddressinfo
<jeremyrubin>
but that's not guaranteed to be a TR address
<jeremyrubin>
and the top-level key in theory could be NUMS
<sipa>
any public key is valid for tr()
roconnor has joined #bitcoin-core-dev
<jeremyrubin>
that's not true
<jeremyrubin>
i want a valid spendable one
<jeremyrubin>
e.g. if i do getaddressinfo the top-level key i can see might be NUMs
<sipa>
i mean any public key you generate
<jeremyrubin>
yes
<jeremyrubin>
i would like core to generate a a public key and give it to me
<jeremyrubin>
since it does hardened derivation i cant do it my own
<jeremyrubin>
but i'd want the key and maybe the path?
<sipa>
what do you want this for?
<jeremyrubin>
e.g. if i want to create a multisig address let's say
<sipa>
yeah, there isn't a good interface for that
<jeremyrubin>
i want to input the key into Miniscript and have my core wallet be able to sign a psbt
<sipa>
though i think generating pubkeys manually is too low level
<jeremyrubin>
are there any reasons not to expose that?
<sipa>
you generally want xpubs or xpub paths for using in a descriptir
<jeremyrubin>
sipa: it's not manually, it's done through software
<jeremyrubin>
sipa: but core does hardened derivation
<jeremyrubin>
i would like core to give me a hardened key
<sipa>
sure, i mean: not per individual key
<sipa>
@jeremyrubin Only if you use hardened derivation paths
kexkey has joined #bitcoin-core-dev
<sipa>
You can construct descriptors with unhardened paths too
<jeremyrubin>
but wrt miniscript, i still need to send a deriv path to core and get the actual key back
<jeremyrubin>
i cant otherwise create the address from third party software
<jeremyrubin>
since it's a hardened path...
<jeremyrubin>
theres also not a way to dump XPUB right now AFAIU
shesek has quit [Remote host closed the connection]
<sipa>
All keys are linked to a descriptor in descriptor wallets, I believe. So you can't really ask to generate a key without risking having that key being reused in an address.
kexkey has quit [Client Quit]
shesek has joined #bitcoin-core-dev
shesek has quit [Remote host closed the connection]
shesek has joined #bitcoin-core-dev
<sipa>
You can export xpubs or xprvs.
<jeremyrubin>
hmm isn't there an application prefix?
<jeremyrubin>
(for context, hit up on this in Sapio studio where i want to input keys for spend paths into a vault contract, but don't really have any clear way to actually get a key a core node would be able to sign for)
<sipa>
Or rather, descriptors with or without private key data.
<sipa>
Yes, but you can choose them freely when importing, and they're also part of exported descriptors.
kexkey has joined #bitcoin-core-dev
<sipa>
You could try to export an existing descriptor, use its key expression with a slightly or non-hardened different path or so, and re-import that.
<jeremyrubin>
Ok it sounds like the flow might be:
<sipa>
Not sure if that works; the private key may be tied to the descriptor it came from.
<sipa>
Certainly easier to just generate a new xprv externally and import that.
<jeremyrubin>
sipa: yes but in theory i want to prefer cores rng lol
<jeremyrubin>
and then i need to backup a new thing
<sipa>
maybe there could be a feature to generating a fresh xpub (whose private key gets stored in the wallet)?
<jeremyrubin>
listdescript => filter for tr => getdescriptorinfo => check if isSolvable => deriveaddresses? but then the issue there is reuse...
<sipa>
so you can construct descriptor key expressions from that
<jeremyrubin>
still need ot back up a new thing
<jeremyrubin>
prefer to have 1 seed backup
<sipa>
that's not how core works
<sipa>
if you're going to be importing a descriptor anyway, you'll need a new backup regardless
<jeremyrubin>
I thought you can rebuild most wallet state with a reindex
<jeremyrubin>
and just a seed backup
<sipa>
for bitcoin core you need a backup of the wallet.dat
<jeremyrubin>
when?
<sipa>
or since recently, a dump of the private descriptors will also work
<sipa>
since descriptor wallets
<jeremyrubin>
i mean "after which events"
<jeremyrubin>
i just made a backup
<jeremyrubin>
when do i backup again
<sipa>
after importing anything
<jeremyrubin>
so the difference is that
<jeremyrubin>
for the seed it's the _private_ materials
<jeremyrubin>
which the backup procedures are different for IMO
<sipa>
they can be, in theory
ghost43 has quit [Remote host closed the connection]
<sipa>
but that's not how it works in bitcoin core's wallet
<jeremyrubin>
for a non-priv bearing descriptor, i can back it up to e.g. cloud storage
<sipa>
yes, i'm aware
ghost43 has joined #bitcoin-core-dev
<sipa>
but again, that's not how it works; the supported procedure is backing up your wallet.dat
<jeremyrubin>
i dont think for the thing im doing you need to backup anything in core
<jeremyrubin>
the descriptors arent being kept in core
<jeremyrubin>
theyre kept externally
<sipa>
yes they are
<jeremyrubin>
i just need core to spit out a derivation path and key?
<sipa>
if you want bitcoin core to use them you need to import them
<jeremyrubin>
yes, but they dont need to be backed up
<jeremyrubin>
because this application layer can always re-import them
<jeremyrubin>
it will "own" them afterwards
<jeremyrubin>
but core still has the signing authority
<sipa>
achow101 probably has a better idea how something like that could be supported
<sipa>
it wasn't clear to me you just wanted the ability to sign
<jeremyrubin>
yeah
<jeremyrubin>
im happy to treat all the other data as responsibility of client
<sipa>
i'm not sure it's possible to do something like that currently
<jeremyrubin>
it's a pretty straighforward architecture that you treat core as your 'key enclave' and then it will give you data out that it could later sign for
<jeremyrubin>
maybe it's a separate software project for a virtual key enclave...
<jeremyrubin>
but it'd be nice if it's core because it's good to have like all the wallet and descriptor stuff working in that, as well as other things core can do
<jeremyrubin>
thanks for your time!
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
shesek has quit [Read error: Connection reset by peer]
shesek has joined #bitcoin-core-dev
shesek has quit [Read error: Connection reset by peer]
shesek has joined #bitcoin-core-dev
javi404 has quit [Ping timeout: 256 seconds]
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
szkl has joined #bitcoin-core-dev
shesek has quit [Read error: Connection reset by peer]