Update eip-1577.md

EIPS/eip-1577.md

@@ -42,6 +42,8 @@ When resolving a `contenthash`, applications MUST use the protocol code to deter
 
 ### Example
 
+#### IPFS
+
 Input data:
 
 ```
@@ -65,6 +67,35 @@ Text format:
 ipfs://QmRAQB6YaCyidP37UdDnjFY5vQuiBrcqdyoW1CuDgwxkD4
 ```
 
+### Swarm
+
+Input data:
+
+```
+storage system: Swarm (0xe4)
+CID version: 1 (0x01)
+content type: swarm-manifest (0xfa)
+hash function: keccak256 (0x1b)
+hash length: 32 bytes (0x20)
+hash: d1de9994b4d039f6548d191eb26786769f580809256b4685ef316805265ea162
+```
+
+Binary format:
+```
+0xe40101fa011b20d1de9994b4d039f6548d191eb26786769f580809256b4685ef316805265ea162
+```
+
+Text format:
+```
+bzz://d1de9994b4d039f6548d191eb26786769f580809256b4685ef316805265ea162
+```
+
+Example usage with swarm hash:
+```
+$ swarm hash ens contenthash d1de9994b4d039f6548d191eb26786769f580809256b4685ef316805265ea162                                 
+> e40101fa011b20d1de9994b4d039f6548d191eb26786769f580809256b4685ef316805265ea162
+```
+
 ### Fallback
 
 In order to support names that have an IPFS or Swarm hash in their `content` field, a grace period MUST be implemented offering those name holders time to update their names. If a resolver does not support the `multihash` interface, it MUST be checked whether they support the `content` interface. If they do, the value of that field SHOULD be treated in a context dependent fashion and resolved. This condition MUST be enforced until at least March 31st, 2019.