<p>No, this is working as intended. When litecoin first introduced segwit, they also used 3.... adresses. They were (are) generated the same way ( Using the same P2SH as bitcoin.).</p>

<p>These now start with an M.., but because of backwards compatibility these 3... adresses are still valid. (but no longer used.)</p>

<p>I guess this issue covers what you are facing pretty well - <a href="https://github.com/litecoin-project/litecoin/issues/433" rel="nofollow noreferrer">https://github.com/litecoin-project/litecoin/issues/433</a></p>

CC BY-SA 3.0
2018-02-10T18:56:17.393Z
2018-02-10T18:56:17.393Z
Jan Janssen
<p>I was messing around with litecoin-cli and found some strange behaviour. If I try to validate a segwit bitcoin address, with the litecoin-cli it returns as a valid litecoin address.</p>

<p>Is this the intended behaviour, or is this a bug?</p>

<pre><code>[user@server ~]# bitcoin-cli getnewaddress
13nKR2gooAr6MEZev2NsQ5RjQPHBs4vY8g
[user@server ~]# litecoin-cli validateaddress 13nKR2gooAr6MEZev2NsQ5RjQPHBs4vY8g
{
  "isvalid": false
}
[user@server ~]# bitcoin-cli addwitnessaddress 13nKR2gooAr6MEZev2NsQ5RjQPHBs4vY8g
39kzm57uJi8iZ9qJWGivVjf44XYJFLur9M
[user@server ~]# litecoin-cli validateaddress 39kzm57uJi8iZ9qJWGivVjf44XYJFLur9M
{
  "isvalid": true,
  "address": "39kzm57uJi8iZ9qJWGivVjf44XYJFLur9M",
  "scriptPubKey": "xxxxxxxxxxxxxxx",
  "ismine": false,
  "iswatchonly": false,
  "isscript": true
}
</code></pre>

<p>`</p>

<bitcoin-core><address><litecoin>
Litecoin-cli validates segwit bitcoin address as valid litecoin address
Adam Baranyai
# Litecoin-cli validates segwit bitcoin address as valid litecoin address

(Asked by: username_0 on 2018-02-10)

I was messing around with litecoin-cli and found some strange behaviour. If I try to validate a segwit bitcoin address, with the litecoin-cli it returns as a valid litecoin address.

Is this the intended behaviour, or is this a bug?

```
[user@server ~]# bitcoin-cli getnewaddress
13nKR2gooAr6MEZev2NsQ5RjQPHBs4vY8g
[user@server ~]# litecoin-cli validateaddress 13nKR2gooAr6MEZev2NsQ5RjQPHBs4vY8g
{
  "isvalid": false
}
[user@server ~]# bitcoin-cli addwitnessaddress 13nKR2gooAr6MEZev2NsQ5RjQPHBs4vY8g
39kzm57uJi8iZ9qJWGivVjf44XYJFLur9M
[user@server ~]# litecoin-cli validateaddress 39kzm57uJi8iZ9qJWGivVjf44XYJFLur9M
{
  "isvalid": true,
  "address": "39kzm57uJi8iZ9qJWGivVjf44XYJFLur9M",
  "scriptPubKey": "xxxxxxxxxxxxxxx",
  "ismine": false,
  "iswatchonly": false,
  "isscript": true
}

```

`

**Tags:** bitcoin-core, address, litecoin


---

## 1 answers

### Answer by username_1 on 2018-02-10. Score: 1 | Accepted answer

No, this is working as intended. When litecoin first introduced segwit, they also used 3.... adresses. They were (are) generated the same way ( Using the same P2SH as bitcoin.).

These now start with an M.., but because of backwards compatibility these 3... adresses are still valid. (but no longer used.)

I guess this issue covers what you are facing pretty well - <https://github.com/litecoin-project/litecoin/issues/433>


---

