If anybody will help me resolve this i’d be most greatful….
Difficulty is CORE IS USING A DIFFERENT DERIVATION PATH….
So i’ve damaged this all the way down to the X/Y pair scalar and might validate key 123 which corrlates to handle ABC ….. that is on regular technology factors and might stroll the important thing displaying each comp and uncomp outcomes which is appropriate… its the one worth in a position to take action.
When i’m going to import this WIF into core it shows one other deal with. import 123 involves DEF… however this isn’t appropriate as the maths and libs present the ABC consequence. I dont know why its utilizing one other derivation path at present, when again years years years in the past it labored effective as there are ship txns and so on and so on.. .
Attempting to determine methods to make this work, i can change the Technology factors to replicate the keys gen factors after which it’s going to map it out accurately additionally however modifying this isn’t allowed in core consensus guidelines so i’m not certain methods to apply that repair… the XY does change on that side however comes out appropriate.
It doesn’t matter what i do that confirmed legitimate 100% appropriate scalar wif uncooked hex no matter stage you need to use is imported as DEF … and its not appropriate when it must be ABC. The kind is p2pkh-p2sh and was created previous to compression being adopted.
I dont know the comamnds purse to import a key in early core anymore because it was toggles on the exe string. Would this resolve the importing problem? … ive tried electrum and possibly there’s a particular script by way of console to drive it to see the right deal with?
So 123 IS appropriate and maps to ABC 1xxx umcomp
123 IS appropriate and maps to ABC 1xxx comp
Non-public key mathematically gens the general public Q that maps to the corrlated addys…
THE CONTRACICTION
Core says importing 123 provides deal with DEF BUT as per math ought to give ABC
The one resolution i’ve is that in some unspecified time in the future Bitcoin Core descriptor wallets use completely different deal with derivation than easy WIF imports. Once you use importdescriptorsBitcoin Core could be deriving addresses in another way.
Since its not the right addy i cant dump the right values if i attempted…
There was a importdesc bug and i believe this is likely one of the victims ..
i can attempt too importing with wpkh (Witness PKH) as a substitute of pkh (doubt it’s going to work)
i can attempt Use Uncooked Public Key Descriptor .. no concept how as i havent accomplished that earlier than
Emergecy resolution is to try to use py solely to create a txn instantly … however it’s going to wont see the right worth when uploaded i really feel…
IS there any working resolution anybody can present? This could be a dev problem or at this level i actually dont know what to do … please advise or recommend choices if there’s a model of software program or approach to go about this… thanks!! ugh…
ps – the one work round i’ve discovered is the next process bypasses the WIF import ambiguity and instantly instructs Bitcoin Core on the precise P2PKH rule to make use of for the identified public key, which is the one approach to remedy this particular configuration battle. — ugh my cli by no means works so i suppose sick attempt that except there may be one other method in one other software program … if anybody has come throughout this ever…
