Bitmessage Wiki - User contributions [en]

User:Erkan Yilmaz

2017-06-13T17:10:51Z

Erkan Yilmaz: stats about BM network

view uptodate stats of the BitMessage network in the TZAG group:

=== BitMessage network heartbeat (how long does it take to receive a message) ===

last 60 mins:
* 99 sec (avg); 58 sec (median)

last 2h:
* 124 sec (121 sec)

last 6h:
* 153 sec (135 sec)

last 24h:
* 147 sec (140 sec)

===processed===

* 3540 person-2-person messages
* 0224 broadcast messages
* 0409 public keys

see [https://www.reddit.com/r/bitmessage/comments/6gvrrf/tzag_group_news_stats_oracle_bot/ here]

FAQ

2017-06-11T08:32:09Z

Erkan Yilmaz: /* I have not received a reply from the Echo Server */ new echo server

==Installation and configuration==
===How do I install Bitmessage===
Bitmessage does not needs to be "installed". it is simply downloaded and executed. You can find instructions to download and run bitmessage from the [[Main Page]].
A great write up for setting up and using Bitmessage on Windows can be found [http://cryptojunky.com/blog/2013/03/09/setting-up-and-using-bitmessage-an-encrypted-communications-platform-based-on-bitcoin/ Here.]

Bitmessage should run on any OS though it is only lightly tested on OSX. The start-on-boot and minimize-to-tray features are only implemented for Windows thus far. Several examples of how to install Bitmessage on *nix and OSX platforms can be found [https://bitmessage.org/forum/index.php in the forums.]

===How do I become a node to help the network===
If your connection indicator is green then you are already accepting incoming connections and helping the Bitmessage network.

If your connection indicator is yellow, check your firewall settings and port forwarding to make sure incoming connections are allowed to your machine on the correct TCP port (Default: 8444), the port can be found in the Bitmessage settings.

You can click on the indicator for more information about each color.

===Why is my Connection Indicator Yellow===
Bitmessage will work normally with a yellow indicator. If your indicator is yellow, you can have up to 8 connections. To make your indicator green, please forward the required TCP port (usually 8444). You can find the Port in the Bitmessage settings.

===How do I setup Bitmessage to work with Tor===
If you need a TOR client, more complete instructions can be found on the [[TOR]] page.
If you already have a client, follow the instructions below.

'''Tor'''

If you are using the Tor Browser Bundle skip to the next section. In order for Bitmessage to use Tor as a proxy follow these steps.
*Navigate to Settings > Network Settings and select SOCKS5 from the Type: drop down under the Proxy server / Tor section.
*Next to 'Server hostname:' enter 'localhost' and next to 'Port:' enter '9050'.
*Select ok.
*Restart Bitmessage.

'''Tor Browser Bundle'''
*Navigate to Settings > Network Settings and select SOCKS5 from the Type: drop down under the Proxy server / Tor section.
*Next to 'Server hostname:' enter 'localhost' and next to 'Port:' enter '9150'.
*Select ok.
*Restart Bitmessage.

===How do I setup Bitmessage as a hidden service on Tor===

Bitmessage can accept incoming connections as a Tor hidden service. This feature is supported since https://github.com/Bitmessage/PyBitmessage/commit/1a40c29d221f036e82a87444ace331afbb8e80c6. In order to use it you have to manually add a new hidden service in your tor configuration. The following table explains the settings combination for Bitmessage's keys.dat. IP addresses and port number are just examples, adjust them if you have a different setup:

{| class="wikitable"
|-
! Outgoing connections !! Incoming connections only through clearnet !! Incoming connections only through Tor !! Incoming connections from both clearnet and Tor
|-
| Over clearnet || <code>socksproxytype = none</code>
<code>onionhostname = none</code>
|| <code>socksproxytype = none</code>

<code>onionhostname = abcdefgh.onion</code>

<code>onionbindip = 127.0.0.1</code>

<code>onionport = 8444</code>

<code>sockslisten = false</code>
|| <code>socksproxytype = none</code>
<code>onionhostname = abcdefgh.onion</code>

<code>onionport = 8444</code>

<code>sockslisten = true</code>
|-
| Over Tor || <code>socksproxytype = SOCKS5</code>
<code>onionhostname = none</code>

<code>sockslisten = true</code>
|| <code>socksproxytype = SOCKS5</code>
<code>onionhostname = abcdefgh.onion</code>

<code>onionbindip = 127.0.0.1</code>

<code>onionport = 8444</code>

<code>sockslisten = false</code>
|| <code>socksproxytype = SOCKS5</code>
<code>onionhostname = abcdefgh.onion</code>

<code>onionport = 8444</code>

<code>sockslisten = true</code>
|}

==Usage==
===How can I run Bitmessage in daemon mode===
Refer to the [[Daemon|Daemon Mode Page]].

===How many connections should I have===
As long as you have at least one connection, you can communicate with the network. If your connection indicator is yellow, you can have a maximum of 8 connections.

===Can I send a message to someone that is offline===
Yes. However, if you go offline then they must come back online within 2 days of the message being sent. Nodes delete data, and do not accept data, older than 2 days.

===How do I format my messages===
Here is [https://qt-project.org/doc/qt-4.8/richtext-html-subset.html the list of supported HTML tags].

===What are subscriptions?===

A [[Subscriptions|subscription]] allows you to receive messages, that were broadcasted by the address you subscribe too.
Since [[broadcast]] messages are encrypted with a key, that can be created by everyone who knows the address, you must be subscribed to an address to actually read the messages.

Subscriptions are also required to use a [[Mailing List]].

===What are "chans"?===
Chan is another word for DML. Please refer to [[DML|this article]] for a complete documentation of this rather complex feature.

==How does Bitmessage work==
'''Startup'''

When you first start Bitmessage, your client connects itself to the network and starts downloading a list of known nodes. Each new node that you connect to shares its list of known nodes. In addition to the known nodes, you will also start receiving person-to-person messages, broadcasts, and public keys. If any of these messages are bound for you, they will be shown in your inbox. All of this data is exchanged between all of your connections to make sure that everyone has a copy.

'''Sending a Message'''

When you send a message, your client must first compute a Proof of Work (POW). This POW helps mitigate spam on the network. Nodes and other clients will not process your message if it does not show sufficient POW. After the POW is complete, your message is shared to all of your connections which in turn share it with all of their connections.

===Where can I find more documentation about Bitmessage===
* [https://bitmessage.org/bitmessage.pdf Overview White Paper (PDF)]
* [[Protocol specification]]
* Detail about the [[Proof of work]]

==How does Bitmessage compare to other messaging methods==
Here is a table comparing Bitmessage to other common messaging services.

"Fully Distributed" means that after bootstrapping, the service will no longer depend on any central authority and will have no single point of failure.

"Voice calls" and "Video Calls" are irrelevant to clients which do not support "Instant Messaging".

{| border="1" class="wikitable"
|+ Comparison of Messaging Services
!  
! Trustless
! P2P
! Open Source
! Requires Proof of Work
! Hide Sender?
! Hide Receiver?
! Mobile Version
! Application or Web Based
! Attachments or File Transfers
! Acknowledge delivery
! Fully Distributed
! Instant messaging
! Voice calls
! Video calls
! Offline messages
|-
! Bitmessage
| {{Yes}}
| {{Yes}}
| [http://opensource.org/licenses/mit-license.php MIT]
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes|Beta, requires server}}
| Application
| {{Yes|220KB}}
| {{Yes}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes|Up to 28 days}}
|-
! Standard Email
| {{No}}
| {{No}}
| {{Partial|Depends}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Both
| {{Yes}}
| {{Partial}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
|-
! Email + GPG
| {{Yes}}
| {{No}}
| {{Partial|Depends}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Both
| {{Yes}}
| {{Partial}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
|-
! [http://xmpp.org/ XMPP] + [https://en.wikipedia.org/wiki/Off-the-Record_Messaging OTR]
| {{Yes}}
| {{No}}
| {{Yes|GPL V2.1}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Application
| {{Partial|No OTR, not trustless}}
| {{Partial|Depends}}
| {{No}}
| {{Yes}}
| {{Partial|Depends}}
| {{Partial|Depends}}
| {{Yes}}
|-
! [https://en.wikipedia.org/wiki/TorChat TorChat]
| {{Yes}}
| {{Yes}}
| {{Yes|GPL}}
| {{No}}
| {{Yes}}
| {{Yes}}
| {{No}}
| Application
| {{Yes}}
|
| {{No}}
| {{Yes}}
| {{No}}
| {{No}}
| {{Partial|Queued}}
|-
! [http://www.skype.com/en/ Skype]
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Application
| {{Yes}}
|
| {{No}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
|-
! [https://www.tox.im/ Tox]
| {{Yes}}
| {{Yes}}
| {{Yes|GPL}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Application
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Partial|Queued}}
|-
! [http://www.scayl.com/ Scayl]
| {{No}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes|Alpha}}
| Application
| {{Yes}}
|
|
|
|
|
|
|-
! [https://en.wikipedia.org/wiki/I2P#E-mail I2P Bote]
| {{Yes}}
| {{Yes}}
| {{Yes|GPL V3}}
| {{No}}
| {{Yes}}
| {{Yes}}
| {{Yes}}
| Application
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes|Up to 100 days}}
|-
! [https://crypto.cat/ CryptoCat]
| {{No}}
| {{No}}
| {{Yes|GPL}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Both
| {{No}}
|
| {{No}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
|-
! [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC]
| {{No}}
| {{No}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Both
| {{No}}
|
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
| {{Partial|Depends}}
|-
! SMS
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes}}
| Application
| {{Yes}}
| {{No}}
| {{No}}
| {{Yes}}
| {{No}}
| {{No}}
| {{Yes}}
|-
! [http://retroshare.sourceforge.net/ RetroShare]
| {{No}}
| {{Yes}}
|
| {{No}}
| {{No}}
| {{No}}
|
|
| {{Yes}}
|
|
|
|
|
|
|-
! [https://en.wikipedia.org/wiki/Freenet#Tools_and_applications Freenet + Frost]
| {{Yes}}
| {{Yes}}
| {{Yes|GPL}}
| {{No}}
| {{Yes}}
| {{Yes}}
| {{No}}
| Application
| {{Yes}}
|
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
|
|-
! [https://mirror4.freenetproject.org/tools.html Freenet + FMS]
| {{No}}
| {{Yes}}
|
| {{No}}
| {{No}}
| {{Yes}}
| {{No}}
| Application
| {{No}}
|
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
|
|-
! [https://mirror4.freenetproject.org/tools.html Freenet + Freemail] 0.2
| {{No}}
| {{Yes}}
| {{Yes|GPL}}
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| Application
| {{Yes}}
| {{No}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
|
|-
! [https://wiki.freenetproject.org/FLIP Freenet + FLIP]
| {{Yes}}
| {{Yes}}
|
| {{No}}
| {{No}}
| {{No}}
| {{No}}
| Application
| {{No}}
|
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
|
|-
! [http://emp.jar.st/ EMP]
| {{Yes}}
| {{Yes}}
| {{Yes|BSD}}
| {{No}}
| {{Yes}}
| {{No}}
| {{Yes}}
| Application
| {{No}}
| {{Yes}}
| {{Yes}}
| {{No}}
| {{No}}
| {{No}}
| {{Yes|Up to 30 days}}
|}

==Troubleshooting==
===My Connection Indicator is Red===
Check your connection settings.
Check if you can access the internet. In case you have a firewall with outgoing restrictions (not Windoes firewall) allow unrestricted access for Bitmessage through your firewall.
Sometimes Bitmessage takes time to connect to the network, especially if [[knownnodes.dat]] is large. Please allow at least 30 minutes for it to connect before posting to the forum.
You can also try deleting [[knownnodes.dat]].

If none of that works, [https://bitmessage.org/forum/index.php please visit the forum here.]

===I have not received a reply from the Echo Server===
*Your connection indicator should be yellow or green.
*Make sure that your POW is complete and the message has been sent. You should see an acknowledgement under "Status" on the "Sent" tab.
*On average it should take 8 minutes from the time you click the send button to the time you receive a response.
*Be sure to allow extra time in the event that the server is under heavy traffic (Example: An article about Bitmessage was posted on a popular website).
*You can always send a message to another echo server. Here are echo addresses:
** BM-2cWoG7fKafmVbfeMh8U2mRgix6eTuGSQCK
** these seem to not work anymore: BM-orkCbppXWSqPpAxnz6jnfTZ2djb5pJKDb / BM-omXeTjutKWmYgQJjmoZjAG3u3NmaLEdZK
*You may subscribe to the [[Timeservice Broadcast]] to receive network heartbeats.
*You can send messages to a [[Mailing List]] in case it still does not works
If you still do not receive a response, [https://bitmessage.org/forum/index.php visit the forum] to see if there is a current technical issue or to submit a new request for assistance.

===Other===
Here is a list of average times for different parts of Bitmessage. [[PyBitmessage Help]]

Please [https://bitmessage.org/forum/index.php visit the forum] for all other issues.

PyBitmessage Help

2014-07-21T12:02:37Z

Erkan Yilmaz: /* Database cleanup */

Welcome to the help page for PyBitmessage.

== Clarification ==
PyBitmessage is the official client, used as protocol reference. It is usually abbreviated "Bitmessage", causing confusion between the protocol and the client.

== Initial setup ==
PyBitmessage can be downloaded from the [[Main Page]], either as Windows binary or as source from github. Other builds (for example for Mac OS X) can be found in the forum.
The client sets up itself completely automatic. It can be launched and the required files for its operation are created if they do not exist.

== Daily usage ==
[[File:PyBitmessage-Sent.png|300px|thumb|right|Main window with sent tab open]]
PyBitmessage will automatically connect to other clients on start up, the user does not needs to wait for this to complete and can instantly send messages. [[POW]] can be made if offline.
The Main interface contains the following tabs:

=== Inbox ===
The inbox contains all your received messages (top part) and displays the currently selected message (bottom part). The bottom window allows copying and editing the message but it will not be saved. The context menu in the message list provides additional features, such as [[HTML view]], save as text file and a reply option. Using the HTML view renders some HTML tags from the message, for example images.
Messages that are no longer needed can be sent to the trash with the [DEL] key.

=== Send ===
The "Send" tab is used to compose new private or [[Broadcast]] messages. A message can be dedicated to multiple people but the protocol supports only one receiving address per message. Example: Sending a message to 8 people will generate the exact same message 8 times in the "Sent" tab.

=== Sent ===
The sent tab displays messages sent by the user, including messages that are in the process of [[POW|proof of work]]. The status column displays the current status of the message.
Table with the most common messages:
{| class="wikitable" border="1"
|-
! Status
! Description
|-
| Doing work necessary to send <type>...
| [[POW]] is being done
|-
| <type> sent on <date/time>
| The message has been sent
|-
| Waiting on Acknowledgement
| The message has been sent but the receiver has not received it yet. Not applicable for broadcasts
|-
| Acknowledgement received on <date+time>
| The receiver got the message. Not applicable for broadcasts
|}
Messages can be sent to the trash with the [DEL] key however, this will not stop POW from being made if it has already started.

=== Your Identities ===
Contains a list of all addresses stored in [[keys.dat]] and allows to generate new ones. The context menu allows to enable/disable addresses. Addresses can be labeled, this label is then displayed instead of the address. Labels are not sent over the network and are only visible to the client. Addresses cannot be deleted directly in this tab, but removing the [[Address Block]] from keys.dat removes it. Editing the keys.dat file requires the user to shut down the client first.

=== [[Subscriptions]] ===
Contains a list of all [[Broadcast|broadcasts]], that the client will receive. To receive broadcasts its address must be added first to the list. The context menu allows enabling, disabling and deletation of addresses.

=== Address Book ===
Can be used to associate addresses with labels for easier recognition.
The context menu allows the user to add a subscription to the address.

=== Blacklist/Whitelist ===
Addresses can be blacklisted or whitelisted. The Operation mode of the list (whitelist or blacklist) ban be set too. The context menu allows entries to be enabled, disabled or deleted.

=== Network Status ===
Shows the [[Stream]] number and the number of connected nodes in a list. Displays when it was started and how much information has been processed yet.
Detailed information about the icon color and how to get a green icon can be found [[Network Status|here]]

== [[DML]] Addresses ==
A DML Address can be either created or joined in the '''File > Join / Create chan''' menu.
These addresses are written with orange color in the identities tab.

To learn more about how to use a DML Address / chan, visit [[DML|this article]].
You need to either create the address or join it to send messages to it, else the client gets stuck when waiting for the public key. To resolve this issue, without joining or creating an address see, the DML article.

=== Join ===
To Join a DML, the address and the passphrase is required. The passphrase is used to generate the private keys, that the client needs to send and receive messages. The address is used so the user does not needs to know the stream number and address version. If the address is not known, a DML can be created, even if it actually exists, in the hope, that the resulting address is correct.

=== Create ===
Creating a DML/chan only requires a passphrase. It will create the address and mark it as such.

=== Notes ===
There is no technical difference between creation and joining. Joining requires the address to make sure, you actually get the correct private keys, because they depend on stream number and address version, which are both included in the address.
Creating an address however will always use the newest address version and stream number and thus may create a different address, which is not compatible with the one intended to join.

== Configuration ==
Bitmessage can be configured by editing [[keys.dat]] or by using the menu '''Settings > Settings''' in the GUI.

=== Settings Menu ===
The settings menu has the folowing tabs:

==== User Interface ====
Allows customization how bitmessage is started and if it should run in portable mode or not.

===== Willingly include... =====
'''Willingly include unencrypted destination address when sending to a mobile device'''

This option must be enabled, when using [[DML]] addresses and is a work in progress feature for mobile app support and has nothing to do with the user interface.

===== Interface language =====
This option is currently (at least in the compiled windows version) not fully working but allows to set the language of the client.

==== Network Settings ====
Allows setting of the TCP port used for incomming connections. This can be left at default value for most users.
A proxy server can be defined if the user wishes to do so. Supports SOCKS4a and SOCKS5 with Authentication support.
The option to allow incoming connections can be enabled if the user wishes to help the network, even when using a proxy. Incoming connections '''are not''' routed over the socks proxy!

==== Demanded Difficulty ====
The demanded difficulty allows to increase the amount of POW to be done for other clients to send messages to the user.
POW for users in the address book is always 1. Doubling the number doubles the amount of time required.

The value for small difficulty defaults to 1.0, rthe value for large difficulty to 2.0 (since version 0.4.0)

==== Max acceptable difficulty ====
Similar to the "demanded difficulty" tab, this tab has the exact same textboxes, however, they are used to limit the amount of POW the user is willing to do. If he sends a message and the destination address wants him to do more POW than he set as maximum, the message will not be processed. The user can click with the right mouse button on the message and force it to be sent or he can delete the message.

== Database cleanup ==
The database ([[messages.dat]]) can be cleaned and shrinked manually with the menu '''File > Delete all trashed messages'''.
The database is compacted once every month automatically without deletion of trashed messages.

== Statistics ==
=== Time ===
On an average computer, different processes take different amounts of time.
{| class="wikitable"
|-
! Action !! Time required
|-
| Generate an address || 1 second*
|-
| Generate an address (1 or 2 characters shorter) || 5 minutes*
|-
| Sender do work necessary to send broadcast|| 2 minutes
|-
| Sender do work necessary to send person-to-person message|| 4 minutes
|-
| message (or acknowledgement data) propagate through the network|| 10 seconds
|}
Note that on Linux and OSX systems, Bitmessage can often do work much faster as it is able to use all available cores and a faster hashing module.

<nowiki>*</nowiki> After this step is done, the client will silently do work to send out the public key over the network which will take about 2 minutes.

PyBitmessage Help

2014-07-21T11:59:21Z

Erkan Yilmaz: typo

Welcome to the help page for PyBitmessage.

== Clarification ==
PyBitmessage is the official client, used as protocol reference. It is usually abbreviated "Bitmessage", causing confusion between the protocol and the client.

== Initial setup ==
PyBitmessage can be downloaded from the [[Main Page]], either as Windows binary or as source from github. Other builds (for example for Mac OS X) can be found in the forum.
The client sets up itself completely automatic. It can be launched and the required files for its operation are created if they do not exist.

== Daily usage ==
[[File:PyBitmessage-Sent.png|300px|thumb|right|Main window with sent tab open]]
PyBitmessage will automatically connect to other clients on start up, the user does not needs to wait for this to complete and can instantly send messages. [[POW]] can be made if offline.
The Main interface contains the following tabs:

=== Inbox ===
The inbox contains all your received messages (top part) and displays the currently selected message (bottom part). The bottom window allows copying and editing the message but it will not be saved. The context menu in the message list provides additional features, such as [[HTML view]], save as text file and a reply option. Using the HTML view renders some HTML tags from the message, for example images.
Messages that are no longer needed can be sent to the trash with the [DEL] key.

=== Send ===
The "Send" tab is used to compose new private or [[Broadcast]] messages. A message can be dedicated to multiple people but the protocol supports only one receiving address per message. Example: Sending a message to 8 people will generate the exact same message 8 times in the "Sent" tab.

=== Sent ===
The sent tab displays messages sent by the user, including messages that are in the process of [[POW|proof of work]]. The status column displays the current status of the message.
Table with the most common messages:
{| class="wikitable" border="1"
|-
! Status
! Description
|-
| Doing work necessary to send <type>...
| [[POW]] is being done
|-
| <type> sent on <date/time>
| The message has been sent
|-
| Waiting on Acknowledgement
| The message has been sent but the receiver has not received it yet. Not applicable for broadcasts
|-
| Acknowledgement received on <date+time>
| The receiver got the message. Not applicable for broadcasts
|}
Messages can be sent to the trash with the [DEL] key however, this will not stop POW from being made if it has already started.

=== Your Identities ===
Contains a list of all addresses stored in [[keys.dat]] and allows to generate new ones. The context menu allows to enable/disable addresses. Addresses can be labeled, this label is then displayed instead of the address. Labels are not sent over the network and are only visible to the client. Addresses cannot be deleted directly in this tab, but removing the [[Address Block]] from keys.dat removes it. Editing the keys.dat file requires the user to shut down the client first.

=== [[Subscriptions]] ===
Contains a list of all [[Broadcast|broadcasts]], that the client will receive. To receive broadcasts its address must be added first to the list. The context menu allows enabling, disabling and deletation of addresses.

=== Address Book ===
Can be used to associate addresses with labels for easier recognition.
The context menu allows the user to add a subscription to the address.

=== Blacklist/Whitelist ===
Addresses can be blacklisted or whitelisted. The Operation mode of the list (whitelist or blacklist) ban be set too. The context menu allows entries to be enabled, disabled or deleted.

=== Network Status ===
Shows the [[Stream]] number and the number of connected nodes in a list. Displays when it was started and how much information has been processed yet.
Detailed information about the icon color and how to get a green icon can be found [[Network Status|here]]

== [[DML]] Addresses ==
A DML Address can be either created or joined in the '''File > Join / Create chan''' menu.
These addresses are written with orange color in the identities tab.

To learn more about how to use a DML Address / chan, visit [[DML|this article]].
You need to either create the address or join it to send messages to it, else the client gets stuck when waiting for the public key. To resolve this issue, without joining or creating an address see, the DML article.

=== Join ===
To Join a DML, the address and the passphrase is required. The passphrase is used to generate the private keys, that the client needs to send and receive messages. The address is used so the user does not needs to know the stream number and address version. If the address is not known, a DML can be created, even if it actually exists, in the hope, that the resulting address is correct.

=== Create ===
Creating a DML/chan only requires a passphrase. It will create the address and mark it as such.

=== Notes ===
There is no technical difference between creation and joining. Joining requires the address to make sure, you actually get the correct private keys, because they depend on stream number and address version, which are both included in the address.
Creating an address however will always use the newest address version and stream number and thus may create a different address, which is not compatible with the one intended to join.

== Configuration ==
Bitmessage can be configured by editing [[keys.dat]] or by using the menu '''Settings > Settings''' in the GUI.

=== Settings Menu ===
The settings menu has the folowing tabs:

==== User Interface ====
Allows customization how bitmessage is started and if it should run in portable mode or not.

===== Willingly include... =====
'''Willingly include unencrypted destination address when sending to a mobile device'''

This option must be enabled, when using [[DML]] addresses and is a work in progress feature for mobile app support and has nothing to do with the user interface.

===== Interface language =====
This option is currently (at least in the compiled windows version) not fully working but allows to set the language of the client.

==== Network Settings ====
Allows setting of the TCP port used for incomming connections. This can be left at default value for most users.
A proxy server can be defined if the user wishes to do so. Supports SOCKS4a and SOCKS5 with Authentication support.
The option to allow incoming connections can be enabled if the user wishes to help the network, even when using a proxy. Incoming connections '''are not''' routed over the socks proxy!

==== Demanded Difficulty ====
The demanded difficulty allows to increase the amount of POW to be done for other clients to send messages to the user.
POW for users in the address book is always 1. Doubling the number doubles the amount of time required.

The value for small difficulty defaults to 1.0, rthe value for large difficulty to 2.0 (since version 0.4.0)

==== Max acceptable difficulty ====
Similar to the "demanded difficulty" tab, this tab has the exact same textboxes, however, they are used to limit the amount of POW the user is willing to do. If he sends a message and the destination address wants him to do more POW than he set as maximum, the message will not be processed. The user can click with the right mouse button on the message and force it to be sent or he can delete the message.

== Database cleanup ==
The database ([[messages.dat]]) can be cleaned and shrinked manually with the menu '''File > Delete all trashed messages'''.
The database is compacted once every month automatically without deletation of trashed messages.

== Statistics ==
=== Time ===
On an average computer, different processes take different amounts of time.
{| class="wikitable"
|-
! Action !! Time required
|-
| Generate an address || 1 second*
|-
| Generate an address (1 or 2 characters shorter) || 5 minutes*
|-
| Sender do work necessary to send broadcast|| 2 minutes
|-
| Sender do work necessary to send person-to-person message|| 4 minutes
|-
| message (or acknowledgement data) propagate through the network|| 10 seconds
|}
Note that on Linux and OSX systems, Bitmessage can often do work much faster as it is able to use all available cores and a faster hashing module.

<nowiki>*</nowiki> After this step is done, the client will silently do work to send out the public key over the network which will take about 2 minutes.