the M-address is invalid in both litecoin and bitcoin.
yes I know all âMâ address should beâŚthey are P2SH addressâ âŚI meant the public âLâ address belonging to the private key you just importedâŚis it valid in litecoin? and if so are there coins in that L address on block cypher?
I didnât save that L-address. but the litecoins still are on the 3-address. again, this 3-address is bitcoin segwit address, but on blockcypher it shows itself as a litecoin address, with the coins.
â2. Copy your private key into the Wallet Details tab on BitAddress.org. Scroll to the bottom and copy the âPrivate Key Hexadecimal Format (64 characters [0-9A-F]):â value.â
I was thinking maybe at this step 2 of the guide you provided, I should have copied my private key into LiteAddress.org. but again, I donât know anything about this whole thing and I am just being manipulative. what do you think I should do? should I repeat the process?
that is where segwit comes inâŚold wallet private keys need to be converted to a newer formatâŚso thats why you take the private key the coins are suppose to be in and paste it into liteaddressâŚthen import that key and run addwitness on the âNewâ âLâ address for the âNew private keyâ you just importedâŚrunning addwitness on the old key/address pair wont do anythingâŚ
that 3 address will show up as a valid bitcoin address because of the way the math works out through hashingâŚit will also be valid on litecoin as wellâŚ
I would try againâŚhell Iâve been trying to crack a wallet for a friend of mine everyday for the past 2 weeksâŚonly difference here is I am looking for lost change in an old wallet and have a lot of transactions to convert and tryâŚI refuse to give upâŚI have the keys I just have to figure out the exact order to convert them in Litecoin as all the guides out there are only for bitcoin address
If you try again you should get the exact same WIF keyâŚif you doâŚthen there is your âLâ address belonging to that keyâŚ
the way address are created you should get the same key every time when converting / hashing, etcâŚbecause addressâ are created as âdeterministicâ meaning the answer to the math problem is the same every timeâŚwhere ecdsa (I think it is) give a different result every timeâŚbut that is only used in signatures on Non âHDâ wallets (âhierarchical deterministicâ)
LTC Rises 5% as Market Returns to Common Sense
on my second attempt, I got everything same. when i run importprivkey ââ with the compressed wif, then the litcoin core says ânull.â basically it doesnât do anything. when i gun addwitnessaddress with the compressed litecoin address, then it gives me the same M-address. P2SH converter also confirms that the M-address returns the original 3-address. so everything checks out, but still no funds. blockcypher.com shows the 3-address has the coins. and the new L-address got nothing.
So after you import your private key run addwitness (followed by the public key belonging to the private key)âŚ
Null means task completeâŚso u imported the keyâŚnow run( addwitness âL address belonging to private key you just importedâ ) to the transaction and only the public key that is paired with that private key u just imported will do what your trying to doâŚany other public key will addwitness yes but until u run addwitness on the key u just imported it will do nothing
I run addwitnessaddress with Litecoin Address Compressed and the console returns an M-address. is there also another step involving a public key?
It should retun a 3 addressâŚan m address is a P2SH for multisig and segregated witnessâŚu should try doing a google search for P2SH address converterâŚthen convert the âMâ address to a 3 addressâŚthen try import address (â3â address)
This may only give u a watch only but its worth a shot Iâd sayâŚ
Make a separate backup before u do itâŚ
I am pretty sure all you are having to do with this is make the verification using scriptPubhash and scriptPub key match when hashed
Or try running addwitness on that M address
your suppose to get a key that starts with 3 when you run addwitnessâŚ
how many signatures does it say it needs when you run this command in console:
validateaddress (âLâ address)
and does it say it is yours?
if it says you need more than 1 signature then you need to sign the transaction with you key in order to redeem the coinsâŚ
running addwitness on the correct address should ldo this but you need to make sure you have the correct address to run it on firstâŚlike if u need 2 signatures you need to run it once on the âLâ address and then again on the âMâ address
because the â3â key you get from the M address is not an addressâŚit is a signature verification hashâŚ
addwitnessaddress M-address returns the same M-address.
âisvalidâ: true,
âaddressâ: âL-addressâ,
âismineâ: true,
âiswatchonlyâ: false,
âisscriptâ: false,
âiscompressedâ: true,
âaccountâ: ââ,
âtimestampâ: 1
this returns the M-address. then I use a P2SH converter and run this M-address. it returns the same 3-address.
I feel like I am in a loop.
the 3-address is originally a bitcoin segwit address. I accidentally sent some litecoins to this address. the transaction was confirmed. now, blockcypher thinks that this 3-address originally bitcoin is a litecoin address and it shows the litecoins are in this 3-address.
if addwitness is not returning a â3â address then that is a problemâŚ
have you tried signing the transaction yet?
how many signatures are needed for this transactionâŚ
type getrawtransaciton (txid)
in console and it should tell you or give you back a hexâŚif it give back a hex copy that and type:
decoderawtransaction (hex)
since addwitness is returning a âMâ address this tells me that it is a multisig transaction more than likelyâŚ
your not redeeming the coins correctly for some reasonâŚyou need another signature in your wallet that hashes to a matching scriptPubkey in order to redeem the coins
what is the transaction id so I can see what your doing?
what does it say when you validateaddress (âMâ address before converting)?
it should say it is a script address and that it is NOT yoursâŚ
youâll need to get the transaction history for the M address and make sure that only 1 Signature is needed to redeem the funds first
if it is a P2SH (multisig) transaction or a SEGWIT transaction then redeeming is different than a regular transactionâŚ
I am not sure what you mean by that. can you explain how i can that please?
where do i find this âtxidâ and âhexâ?
it returns this:
{
âisvalidâ: true,
âaddressâ: âM-addressâ,
âscriptPubKeyâ: ââ,
âismineâ: true,
âiswatchonlyâ: false,
âisscriptâ: true,
âscriptâ: âwitness_v0_keyhashâ,
âhexâ: ââ,
âaddressesâ: [
],
âaccountâ: ââ
}
I got the hex code from above and run