doc/dep/0006: propose app identifier for version and verack messages

doc/src/SUMMARY.md

@@ -81,6 +81,7 @@
 - [DEP 0002: Smart Contract Composability (deprecated)](dep/0002.md)
 - [DEP 0003: Token Mint Authorization (accepted)](dep/0003.md)
 - [DEP 0004: Client wallet WASM modules (draft)](dep/0004.md)
+- [DEP 0006: App Identifier for Version and Verack Messages (draft)](dep/0006.md)
 
 # Specs
 

doc/src/dep/0006.md

@@ -0,0 +1,24 @@
+# DEP 0006: App Identifier for Version and Verack Messages
+
+```
+status: draft
+```
+
+## Motivation
+
+Currently we use app version in `version` and `verack` messages to
+check if two nodes can communicate during version exchange phase, but
+this is not enough we need an app identifier to make sure two nodes
+are running the same app over the p2p network.
+
+This would be in addition to the magic bytes we use to identify p2p
+networks as this human-readable info will make it easier to debug
+connection issues.
+
+## Proposal
+
+Add the following field to Version and Verack Message
+
+| Type                 | Description         | Comment        |
+|----------------------|---------------------|----------------|
+| `String`             | app_name            | App identifier |