BM-2NB prefix ?

BM-2cWzfh4UX1GjBihaRz9gj3PNLBmV9JF6Zn
Jul 8 11:30

I noticed that one of my addresses is prefixed with BM-2NB rather than BM-2c /S/T/U/V/W/X. It was generated in the QT interface. What is the technical explanation for this?

[chan] bitmessage
Jul 8 13:11

That doesn't seem valid. Perhaps you meant BM-NB instead? NB prefix occurs when you select "spend several minutes of extra time to make address(es) 1 or 2 characters shorter" because, well, the address is 1 or 2 characters shorter.

[chan] bitmessage
Jul 8 13:30

Yes I meant BM-NB. I noticed prefixes of BM-N /A/B/C. I didn't choose the option to make the address shorter. With a particular deterministic passphrase the address just generates that way. What mean the prefixes, such as 2cS, 2cU, 2cV, 2cW, 2cX, NA, NB, NC, etc? What data do these addresses contain or represent?

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
Brute forcing BM addr's Jul 21 18:57 24
Network Size Jul 21 13:07 5
memory leak? Jul 21 06:19 3
BM bot sourcecode sample Jul 20 15:56 7
RE: BM bot sourcecode sample Jul 20 04:01 1
BitMessage need new improvements Jul 19 23:35 3
2 bugs while quitting Jul 19 19:03 1
[Feature Request/Question] Blacklist counters Jul 19 12:01 1
raspberry pi Jul 18 17:13 3
Feature request (2) Jul 17 00:44 13
Bug report (UI shows deleted messages) Jul 17 00:20 3
ECC Curves: secp256k1 versus secp521r1 -> BitMessage Secure Station Jul 16 22:18 1
PyBitmessage message save folder Jul 16 21:00 5
HELP(!) - Impossible PoW recipient address msg Jul 16 20:53 6
ECC Curves: secp256k1 versus secp521r1 Jul 16 20:44 28
Precedence of work / Priority of work Jul 16 20:43 5
I need help Jul 16 16:42 1
Pre-commitment and "open source canary" Jul 16 16:41 2
Killing impossible PoW sent items (daemon) Jul 16 16:40 1
Feature request (1) Jul 13 13:45 6
Bitmessage statistics Jul 13 09:42 13
addr command problems and plans Jul 13 06:19 7
BM client 0.6.2 (OS X) does not show images Jul 12 04:16 24
bug in latest commits Jul 11 08:46 11
Bitmessage bug in latest v0.6 branch Jul 11 06:09 1
bmwrapper broadcasts Jul 10 14:27 5
Beamstat chanlist bug? Jul 10 06:10 3
FPGA Hardware backdoors risk and counter-measures, regarding « TOR/VPN fingerprinting family anonymity breach fix » with a custom FPGA based « Single Socket » Ethernet Controller. Jul 9 11:36 1
tor socks access issues continue (0.6dEV pYbm code @ 20170706) Jul 8 23:10 3
FPGA Hardware backdoors, regarding « TOR/VPN fingerprinting family anonymity breach fix » with a custom FPGA based « Single Socket » Ethernet Controller. Jul 8 14:10 3
BM-2NB prefix ? Jul 8 13:30 3
Jabit and Abit update Jul 8 07:45 1
Peer "Ratings" Jul 7 12:54 9
How to.. Jul 6 18:01 49
Is there a quick way to export a thread, or all threads of a chan in a readable manner. Jul 6 04:00 6
Dev-talk PML status / instructions pls Jul 5 21:04 5
BM db blob questions Jul 5 07:40 11
How to connect to more nodes Jul 5 07:34 13
P.P.S. Re: BM db blob questions Jul 5 03:21 2
bitmessage API TTL Jul 5 01:08 2
Re: Re: Re: Re: Religious garbage at this point Jul 4 22:28 7
Yes it's obvious my BM private keys have been stolen.... Jul 4 22:20 34
MiNode I2P support testing Jul 2 07:04 25
To the person running /wire:0.1.0/bmd:0.0.1/ on 158.69.119.35:8444 Jul 1 12:55 9
So you think God is a myth ... Jul 1 12:14 1
How to.. (Node Conns Encrypted) Jul 1 10:17 1
Any predictions? Jun 30 12:24 2
Hello ! Jun 30 10:03 18
If I had cash Jun 30 09:56 3
"addr" commands Jun 29 22:14 2
How to.. (DNS issues and asyncore/conventional Network Access behaviour) Jun 29 13:03 3
I2P peer discovery by publishing destinations as custom objects Jun 27 03:53 4
Confused Jun 25 21:29 6
Curious Jun 25 21:23 1
Question - BM mesage model alteration idea Jun 25 18:39 4
Privacy? I don't have anything to hide. Jun 25 18:30 2
Support (connections are "stuck" when using TOR+iptables) Jun 24 21:10 7