blocks|key|164846|text|[%5EOIl]可以匹配任何不是O、I或l的字符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|164847|164848|你的末尾没有$，所以它会匹配任何以BC地址开头的字符串。|unordered-list-item|164849|你没有计算{27,34}中的第一个字符-那应该是{26,33}|164850|164851|然而，正如评论中提到的，正则表达式不是验证比特币地址的好方法。|164852|entityMap^0|0|6|0|0|6|1|0|5|7|O|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|J|3|K|5|I|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|12|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|P|$]]

<code>[^OIl]</code> matches any character that's not O, I or l. The problems in your regex are:

<ul>
<li>You don't have a <code>$</code> at the end, so it'd match any string beginning with a BC address.</li>
<li>You didn't count the first character in your <code>{27,34}</code> - that should be <code>{26,33}</code></li>
</ul>

However, as mentioned in a comment, a regex is not a good way to validate a bitcoin address.

blocks|key|2968651|text|%5E[13][a-km-zA-HJ-NP-Z1-9]{25,34}$|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2968652|将匹配以1或3开头的字符串，然后匹配a-z、A-Z或0-9组成的25到34个字符，不包括l、I、O和0+(不是比特币地址中的有效字符)。|unstyled|offset|length|style|CODE|2968653|entityMap^0|0|4|1|6|1|18|1|1A|1|1C|1|1E|1|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@$G|O|H|P|I|J]|$G|Q|H|R|I|J]|$G|S|H|T|I|J]|$G|U|H|V|I|J]|$G|W|H|X|I|J]|$G|Y|H|Z|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|F|7|10|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
</code></pre>

will match a string that starts with either <code>1</code> or <code>3</code> and, after that, 25 to 34 characters of either a-z, A-Z, or 0-9, excluding <code>l</code>, <code>I</code>, <code>O</code> and <code>0</code> (not valid characters in a Bitcoin address).

blocks|key|2968669|text|%5E[13][a-km-zA-HJ-NP-Z1-9]{25,34}$|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2968670|比特币地址是|unstyled|2968671|2968672|+26-35字母数字字符|unordered-list-item|offset|length|style|BOLD|2968673|的标识符，以数字1或3+|2968674|开始H110随机数字|2968675|大写字母|2968676|小写字母|2968677|，但大写字母O、小写字母l和数字0从不用于防止视觉歧义。|CODE|2968678|2968679|entityMap^0|0|0|0|1|5|0|8|3|0|0|0|0|6|1|C|1|G|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|13|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|15|8|@$K|16|L|17|M|N]]|9|@]|A|$]]|$1|O|3|P|5|J|7|18|8|@$K|19|L|1A|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1C|8|@]|9|@]|A|$]]|$1|U|3|V|5|J|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|J|7|1E|8|@$K|1F|L|1G|M|Y]|$K|1H|L|1I|M|Y]|$K|1J|L|1K|M|Y]]|9|@]|A|$]]|$1|Z|3|-4|5|F|7|1L|8|@]|9|@]|A|$]]|$1|10|3|-4|5|F|7|1M|8|@]|9|@]|A|$]]]|11|$]]

<pre><code>^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
</code></pre>

bitcoin address is

<ul>
<li>an identifier of 26-35 alphanumeric characters </li>
<li>beginning with the number 1 or 3 </li>
<li>random digits </li>
<li>uppercase </li>
<li>lowercase letters </li>
<li>with the exception that the uppercase letter <code>O</code>, uppercase letter <code>I</code>, lowercase letter <code>l</code>, and the number <code>0</code> are never used to prevent visual ambiguity.</li>
</ul>

blocks|key|162081|text|%5E(bc1%7C[13])[a-zA-HJ-NP-Z0-9]{25,39}$|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|162082|基于新的地址类型Bech32|unstyled|offset|length|162083|entityMap|0|LINK|mutability|MUTABLE|url|https://en.bitcoin.it/wiki/Bech32^0|0|8|6|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code>^(bc1|[13])[a-zA-HJ-NP-Z0-9]{25,39}$
</code></pre>

Based on the new address type <a href="https://en.bitcoin.it/wiki/Bech32" rel="noreferrer">Bech32</a>

blocks|key|2756273|text|基于runeks和Erhard+Dinhobl的回答，我得到了这样一个接受bech32和遗留的：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2756274|\b(bc(0([ac-hj-np-z02-9]{39}%7C[ac-hj-np-z02-9]{59})%7C1[ac-hj-np-z02-9]{8,87})%7C[13][a-km-zA-HJ-NP-Z1-9]{25,35})\b|code-block|syntax|javascript|2756275|包含testnet地址：|2756276|\b((bc%7Ctb)(0([ac-hj-np-z02-9]{39}%7C[ac-hj-np-z02-9]{59})%7C1[ac-hj-np-z02-9]{8,87})%7C([13]%7C[mn2])[a-km-zA-HJ-NP-Z1-9]{25,39})\b|2756277|只有testnet：|2756278|\b(tb(0([ac-hj-np-z02-9]{39}%7C[ac-hj-np-z02-9]{59})%7C1[ac-hj-np-z02-9]{8,87})%7C[mn2][a-km-zA-HJ-NP-Z1-9]{25,39})\b|2756279|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/24205650/450148|1|https://stackoverflow.com/a/50391800/450148^0|2|6|0|9|E|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]|$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|18|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1A|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|1B|8|@]|9|@]|C|$G|H]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]]]

Based on answer of <a href="https://stackoverflow.com/a/24205650/450148">runeks</a> and <a href="https://stackoverflow.com/a/50391800/450148">Erhard Dinhobl</a> I got this that accepts bech32 and legacy:

<pre><code>\b(bc(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})|[13][a-km-zA-HJ-NP-Z1-9]{25,35})\b
</code></pre>

Including testnet address:

<pre><code>\b((bc|tb)(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})|([13]|[mn2])[a-km-zA-HJ-NP-Z1-9]{25,39})\b
</code></pre>

Only testnet:

<pre><code>\b(tb(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})|[mn2][a-km-zA-HJ-NP-Z1-9]{25,39})\b
</code></pre>

blocks|key|2968693|text|基于这里的描述：https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki我认为版本1和版本0的Bech32比特币地址的正则表达式是：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2968694|\bbc(0([ac-hj-np-z02-9]{39}%7C[ac-hj-np-z02-9]{59})%7C1[ac-hj-np-z02-9]{8,87})\b|style|CODE|2968695|以下是我找到信息的其他一些链接：|2968696|2968697|https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki|unordered-list-item|2968698|http://r6.ca/blog/20180106T164028Z.html|2968699|2968700|entityMap|0|LINK|mutability|MUTABLE|url|1|2^0|8|1Q|0|0|0|24|0|0|0|0|1Q|1|0|0|13|2|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@$A|14|B|15|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|17|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|N|3|O|5|M|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|P|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|L]]|X|$5|T|U|V|C|$W|L]]|Y|$5|T|U|V|C|$W|O]]]]

Based on the description here: <a href="https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki" rel="nofollow noreferrer">https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki</a> I would say the regex for a Bech32 bitcoin address for Version 1 and Version 0 (only for mainnet) is:

<code>\bbc(0([ac-hj-np-z02-9]{39}|[ac-hj-np-z02-9]{59})|1[ac-hj-np-z02-9]{8,87})\b</code>

Here are some other links where I found infos:

<ul>
<li><a href="https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki" rel="nofollow noreferrer">https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki</a></li>
<li><a href="http://r6.ca/blog/20180106T164028Z.html" rel="nofollow noreferrer">http://r6.ca/blog/20180106T164028Z.html</a></li>
</ul>

blocks|key|162106|text|由于OP没有提供具体的用例(只提供匹配标准)，而我在研究检测BitCoin地址的方法时遇到了这一点，我想发回并与社区分享。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|162107|提供的这些RegEx将在行首和/或行尾查找BitCoin地址。我的用例是在电子邮件正文中查找BitCoin地址，因为勒索/性勒索的增加(参考：https://krebsonsecurity.com/2018/07/sextortion-scam-uses-recipients-hacked-passwords/)+-所以这些都不是有效的解决方案(如后面所述)。由于URL中的文件名和其他标识符，建议的RegEx将在电子邮件中捕获许多FP。我不是在抨击解决方案，因为它们适用于某些用例，但它们根本不适用于我的用例。一种变体在被动警报的短时间内捕获了许多垃圾邮件(示例如下)。|offset|length|162108|以下是我的测试用例：|162109|--------------------------------------------------------
BitCoin+blackmail+formats+observed+(my+org+and+online):
--------------------------------------------------------
BTC+Address:+1JHwenDp9A98XdjfYkHKyiE3R99Q72K9X4+
BTC+Address:+1Unoc4af6gCq3xzdDFmGLpq18jbTW1nZD
BTC+Address:+1A8Ad7VbWDqwmRY6nSHtFcTqfW2XioXNmj
BTC+Address:+12CZYvgNZ2ze3fGPFzgbSCELBJ6zzp2cWc
BTC+Address:+17drmHLZMsCRWz48RchWfrz9Chx1osLe67

Receiving+Bitcoin+Address:+15LZALXitpbkK6m2QcbeQp6McqMvgeTnY8
Receiving+Bitcoin+Address:+1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5

--------------------------------------------------------
Other+possible+BitCoin+test+cases+I+added:
--------------------------------------------------------
-+What+if+text+comes+before+and/or+after+on+same+line?++Or+doesn't+contain+BitCoin/BTC/etc.+anywhere+(or+anywhere+close+to+the+address)?
++++Send+BitCoin+payments+here+1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5
++++1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5+to+keep+your+secrets+safe.
++++Send+payments+here+1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5+to+keep+your+secrets+safe.

-+Standalone+address:
++++1Dvd7Wb72JBTbAcfTrxSJCZZuf4tsT8V72

--------------------------------------------------------
Redacted+Body+content+generating+FPs+from+spam+emails:
--------------------------------------------------------
src=3D"https://example.com/blah=3D2159024400&amp;t=3DXWP9YVkAYwkmif9RgKeoPhw2b1zdMnMzXZSGRD_Oxkk"

"cursor:pointer;color:#6A6C6D;-webkit-text-size-blahutm_campaign%25253Drdboards%252526e_t%25253Dd5c2deeaae5c4a8b8d2bff4d0f87ecdd%252526utm_cont=blah

src=3D"https://example.com/blah/74/328e74997261d5228886aab1a2da6874.jpg"+

src=3D"https://example.com/blah-1c779f59948fc5be8a461a4da8d938aa.jpg"

href=3D"https://example.com/blah-0ff3169b28a6e17ae8a369a3161734c1?alert_=id=blah|code-block|syntax|javascript|162110|我测试过的一些RegEx样本(不会列出那些我认为是贪婪的、带有回溯的)：|162111|%5E[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
++++(Too+narrow+and+misses+BitCoin+addresses+within+a+paragraph)

(bc1%7C[13])[a-zA-HJ-NP-Z0-9]{25,39}$
++++(Still+misses+text+after+BTC+on+same+line+and+triples+execution+time)

\W[13][a-km-zA-HJ-NP-Z1-9]{25,34}\W
++++(Too+broad+and+catches+URL+formats)|162112|我正在评估的当前RegEx捕获了我所有已知的/精心设计的示例案例，并消除了已知的FP(特别是避免了URL文件名FP的句点结束)：|162113|[13][a-km-zA-HJ-NP-Z1-9]{25,34}\s|162114|执行时间的一个参考点(以步骤和时间显示成本)：https://regex101.com/|162115|请随时发表意见或提供改进建议(我绝不是RegEx专家)。当我进一步检查它对正文内容的电子邮件检测时，如果观察到其他FP案例或获得更有效的RegEx，我将更新。|162116|赛斯|162117|entityMap|0|LINK|mutability|MUTABLE|url|https://krebsonsecurity.com/2018/07/sextortion-scam-uses-recipients-hacked-passwords/|1|https://regex101.com/^0|0|1Z|2D|0|0|0|0|0|0|0|0|N|L|1|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|F|3|G|5|6|7|1F|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1I|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1K|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1L|8|@]|9|@$D|1M|E|1N|1|1O]]|A|$]]|$1|W|3|X|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]|18|$5|13|14|15|A|$16|19]]]]

As the OP didn't provide a specific use case (only matching criteria) and I came across this in researching methods to detect BitCoin addresses, wanted to post back and share with the community.

These RegEx provided will find BitCoin addresses either at the start of a line and/or end of the line. My use case was to find BitCoin addresses in the body of an email given the rise of blackmail/sextortion (Reference: <a href="https://krebsonsecurity.com/2018/07/sextortion-scam-uses-recipients-hacked-passwords/" rel="nofollow noreferrer">https://krebsonsecurity.com/2018/07/sextortion-scam-uses-recipients-hacked-passwords/</a>) - so these weren't effective solutions (as outlined later). The proposed RegEx will catch many FPs in email, due to filenames and other identifiers within URLs. I am not knocking the solutions, as they work for certain use cases, but they simply don't work for mine. One variation caught many spam emails within a short timeframe of passive alerting (examples follow).

Here are my test cases:

<pre><code>--------------------------------------------------------
BitCoin blackmail formats observed (my org and online):
--------------------------------------------------------
BTC Address: 1JHwenDp9A98XdjfYkHKyiE3R99Q72K9X4 
BTC Address: 1Unoc4af6gCq3xzdDFmGLpq18jbTW1nZD
BTC Address: 1A8Ad7VbWDqwmRY6nSHtFcTqfW2XioXNmj
BTC Address: 12CZYvgNZ2ze3fGPFzgbSCELBJ6zzp2cWc
BTC Address: 17drmHLZMsCRWz48RchWfrz9Chx1osLe67

Receiving Bitcoin Address: 15LZALXitpbkK6m2QcbeQp6McqMvgeTnY8
Receiving Bitcoin Address: 1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5

--------------------------------------------------------
Other possible BitCoin test cases I added:
--------------------------------------------------------
- What if text comes before and/or after on same line? Or doesn't contain BitCoin/BTC/etc. anywhere (or anywhere close to the address)?
 Send BitCoin payments here 1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5
 1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5 to keep your secrets safe.
 Send payments here 1MAFzYQhm6msF2Dxo3Nbox7i61XvgQ7og5 to keep your secrets safe.

- Standalone address:
 1Dvd7Wb72JBTbAcfTrxSJCZZuf4tsT8V72

--------------------------------------------------------
Redacted Body content generating FPs from spam emails:
--------------------------------------------------------
src=3D"https://example.com/blah=3D2159024400&amp;amp;t=3DXWP9YVkAYwkmif9RgKeoPhw2b1zdMnMzXZSGRD_Oxkk"

"cursor:pointer;color:#6A6C6D;-webkit-text-size-blahutm_campaign%253Drdboards%2526e_t%253Dd5c2deeaae5c4a8b8d2bff4d0f87ecdd%2526utm_cont=blah

src=3D"https://example.com/blah/74/328e74997261d5228886aab1a2da6874.jpg" 

src=3D"https://example.com/blah-1c779f59948fc5be8a461a4da8d938aa.jpg"

href=3D"https://example.com/blah-0ff3169b28a6e17ae8a369a3161734c1?alert_=id=blah
</code></pre>

Some RegEx samples I tested (won't list those I'd knock for greedy globbing with backtraces):

<pre><code>^[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
[13][a-km-zA-HJ-NP-Z1-9]{25,34}$
 (Too narrow and misses BitCoin addresses within a paragraph)

(bc1|[13])[a-zA-HJ-NP-Z0-9]{25,39}$
 (Still misses text after BTC on same line and triples execution time)

\W[13][a-km-zA-HJ-NP-Z1-9]{25,34}\W
 (Too broad and catches URL formats)
</code></pre>

The current RegEx I am evaluating which catches all my known/crafted sample cases and eliminates known FPs (specifically avoiding end of sentence period for URL filename FPs):

<pre><code>[13][a-km-zA-HJ-NP-Z1-9]{25,34}\s
</code></pre>

One reference point for execution times (shows cost in steps and time): <a href="https://regex101.com/" rel="nofollow noreferrer">https://regex101.com/</a>

Please feel free to weigh in or provide suggestions on improvements (I am by no means a RegEx master). As I further vet it against email detection of Body content, I will update if other FP cases are observed or more efficient RegEx is derived.

Seth

blocks|key|2756293|text|我不喜欢复杂的解决方案，当您不想收到完全胡言乱语时，这个正则表达式用于最简单的验证。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2756294|\w{25,}|code-block|syntax|javascript|2756295|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I am not into complicated solutions and this regex served the purpose for the most simplest validation, when you just don't want to receive complete nonsense.
<pre><code>\w{25,}
</code></pre>

blocks|key|2968846|text|mainnet比特币|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2968847|/%5E([13]{1}[a-km-zA-HJ-NP-Z1-9]{26,33}%7Cbc1[a-z0-9]{39,59})$/|code-block|syntax|javascript|2968848|如果您不想了解上面的正则表达式，可以跳过下面的细节|2968849|拆分一下|2968850|对于常规地址|2968851|/[13]{1}/|2968852|地址将以1或3开头，{1}个定义仅与方括号中的一个字符匹配|2968853|/[13]{1}[a-km-zA-HJ-NP-Z1-9]/|2968854|不能有l(小写el)、i(大写字母)、O(大写O)和0(零)|2968855|/[13]{1}[a-km-zA-HJ-NP-Z1-9]{26,33}/|2968856|长度可以是27到34个字符，记住我们已经检查了第一个字符是1或3，因此剩余的地址长度将是26到33个字符|2968857|对于segwit|2968858|/bc1/|2968859|从bc1开始|2968860|/bc1[a-z0-9]/|2968861|只能包含小写字母和数字|2968862|/bc1[a-z0-9]{39,59}/|2968863|长度可以是42到62个字符，我们已经检查了前三个字符是否为bc1，因此剩余的地址长度将为39到59个字符|2968864|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1F|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1G|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1H|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1I|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1L|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1M|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1N|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1P|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|1Q|8|@]|9|@]|A|$E|F]]|$1|12|3|13|5|6|7|1R|8|@]|9|@]|A|$]]|$1|14|3|15|5|D|7|1S|8|@]|9|@]|A|$E|F]]|$1|16|3|17|5|6|7|1T|8|@]|9|@]|A|$]]|$1|18|3|19|5|D|7|1U|8|@]|9|@]|A|$E|F]]|$1|1A|3|1B|5|6|7|1V|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|1D|$]]

for mainnet bitcoin
<pre><code>/^([13]{1}[a-km-zA-HJ-NP-Z1-9]{26,33}|bc1[a-z0-9]{39,59})$/
</code></pre>
if you don't want to understand the above regex you can skip the detail below
breaking it down
For regular addresses
<pre><code>/[13]{1}/
</code></pre>
address will start with 1 or 3, {1} defines that only match one character in square bracket
<pre><code>/[13]{1}[a-km-zA-HJ-NP-Z1-9]/
</code></pre>
cannot have l (small el), I (capital eye), O (capital O) and 0 (zero)
<pre><code>/[13]{1}[a-km-zA-HJ-NP-Z1-9]{26,33}/
</code></pre>
can be 27 to 34 characters long, remember we already checked the first character to be 1 or 3, so remaining address will be 26 to 33 characters long
For segwit
<pre><code>/bc1/
</code></pre>
starts with bc1
<pre><code>/bc1[a-z0-9]/
</code></pre>
can only contain lower case letters and numbers
<pre><code>/bc1[a-z0-9]{39,59}/
</code></pre>
can be 42 to 62 characters long, we already checked first three characters to be bc1, so remaining address will be 39 to 59 characters long

blocks|key|2756297|text|对于匹配传统、嵌套SegWit和本征SegWit地址：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2756298|/%5E(?:[13]{1}[a-km-zA-HJ-NP-Z1-9]{26,33}%7Cbc1[a-z0-9]{39,59})$/|offset|length|style|CODE|2756299|来源：Regex+for+Bitcoin+Addresses。|2756300|entityMap|0|LINK|mutability|MUTABLE|url|https://regexland.com/regex-bitcoin-addresses/^0|0|0|1P|0|3|R|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

For matching legacy, nested SegWit, and native SegWit addresses:
<code>/^(?:[13]{1}[a-km-zA-HJ-NP-Z1-9]{26,33}|bc1[a-z0-9]{39,59})$/</code>
Source: <a href="https://regexland.com/regex-bitcoin-addresses/" rel="nofollow noreferrer">Regex for Bitcoin Addresses</a>.

I am trying to come up with a regular expression to match Bitcoin addresses according to <a href="https://en.bitcoin.it/wiki/Address">these specs</a>:

<blockquote>
 A Bitcoin address, or simply address, is an identifier of 27-34
 alphanumeric characters, beginning with the number 1 or 3 [...]
</blockquote>

I figured it would look something like this

<pre><code>/^[13][a-zA-Z0-9]{27,34}/
</code></pre>

Thing is, I'm not good with regular expressions and I haven't found a single source to confirm this would not create false negatives.

I've found one online that's <code>^1[1-9A-Za-z][^OIl]{20,40}</code>, but I don't even know what the <code>[^OIl]</code> part means and it doesn't seem to match the <code>3</code> a Bitcoin address could start with.

RegEx to match Bitcoin addresses?

根据，我正在尝试想出一个正则表达式来匹配比特币地址比特币地址，或简称地址，是由27-34个字母数字字符组成的标识符，从数字1或3开始...我想它应该是这样的/^[13][a-zA-Z0-9]{27,34}/问题是，我不擅长使用正则表达式，而且我还没有找到一个单一的来源来确认这不会产生假阴性。我在网上找到了一个^1[1-9A-Za-z][^OIl]{20,40}，但我甚至不知道[^OIl]部分是什么

问匹配比特币地址的RegEx？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问匹配比特币地址的RegEx？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问匹配比特币地址的RegEx？
EN