Remove optional ecash

4A.md

@@ -28,7 +28,6 @@ The event MUST include a `p` tag specifying the router to route the event. The `
     "content": nip44_encrypt("[
         [ "event", "<event-as-json-string>" ],  // required event to publish
         [ "relay", "wss://example1.com" ]       // required relay to target
-        [ "ecash", "<token-uri>" ],             // optional ecash incentive with ecash proof and mint info
     ]")
     "tags": [
         [ "p", "<pubkey-of-router>" ]
@@ -38,24 +37,18 @@ The event MUST include a `p` tag specifying the router to route the event. The `
 
 Multiple `event`s and `relays` MAY be provided. Every given `event` SHOULD be published to every given `relay`.
 
-An OPTIONAL `ecash` tag containing a token proof and mint information may be provided as incentive for the router.
-
 The routing event could use a [NIP-59](59.md) gift wrap to hide that it is a routing request, but the effectiveness would vary depending on if a router's pubkey is well known as an onion router.
 
 ## Router Announcement
 
 Kind `10690` are replaceable router announcement events which allow routers to be discovered by senders. The `relay` tag is a relay where the router listens for onion routing requests. The event MUST include at least one `relay`.
 
-The event MAY include fee requirements. The `ecash` tag contains a supported ecash protocol. The `fee` tag gives the amount and denomination per event per relay. For example, if a one sat fee is set and a routing request contains two events and three relays, the total fee required is six sats.
-
 ```
 {
     "kind": 10690,
     "tags": [
         [ "relay", "wss://example1.com" ],
         [ "relay", "wss://example2.com" ],
-        [ "fee", "1", "sat" ],
-        [ "ecash", "cashu" ]
     ],
     "pubkey": <pubkey-of-router>
 }