diff --git a/117.md b/117.md
index 26317450..dea77fa0 100644
--- a/117.md
+++ b/117.md
@@ -42,6 +42,8 @@ The following tags MAY be present:
 
 - A `context` tag to provide a link to a website or other resource that provides more information about the bounty.
 
+- An arbitrary amount of `t` tags to provide a list of tags that can be used as categories to filter bounties.
+
 The following tags MUST be present when the bounty is updated to `assigned` status:
 
 - A `p` tag of the applicant public key to track who is currently assigned to the bounty.
@@ -50,8 +52,6 @@ The following tags MUST be present when the bounty is updated to `assigned` stat
 
 - An `application` tag with the stringified **Bounty Application Event**.
 
-- An arbitrary amount of `t` tags to provide a list of tags that can be used as categories to filter bounties.
-
 ## Bounty Application Event
 
 The `.content` of these events should be a simple plain text string explaining why the creator should choose the applicant.
@@ -80,6 +80,10 @@ The following is a description of the lifecycle of a bounty:
 
 4: **Canceled:** The bounty has been canceled by the creator. The bounty MUST be updated with an `s` tag of `canceled`.
 
+## Solution Submission
+
+Solutions to bounties may be submitted via a nip-04 encrypted message to the creator of the bounty. Or however the client chooses.
+
 ## Motivation
 
 Bounties will provide social incentive to complete tasks related to the development of Nostr and allow developers to get paid and build a reputation across the network.