@@ -300,9 +300,11 @@ pokes are actually coming from - our example agents would accept data from
300anywhere, including random foreign ships. We'll now have a look at how to handle
300anywhere, including random foreign ships. We'll now have a look at how to handle
301such permission checks.
301such permission checks.
303+Back in [lesson 2](/docs/userspace/gall-guide/2-agent#bowl) we discussed the
303−The `bowl` includes a couple of useful fields: `our` and `src`. The `our` field
304+[bowl](/docs/arvo/gall/data-types#bowl). The `bowl` includes a couple of useful
304−just contains the `@p` of the local ship. The `src` field contains the `@p` of
305+fields: `our` and `src`. The `our` field just contains the `@p` of the local
305−the ship from which the event originated.
306+ship. The `src` field contains the `@p` of the ship from which the event
307+originated, and is updated for every new event.
307When messages come in over Ames from other ships on the network, they're
309When messages come in over Ames from other ships on the network, they're
308[encrypted](/docs/arvo/ames/cryptography) with our ship's public keys and signed by the ship which sent them.
310[encrypted](/docs/arvo/ames/cryptography) with our ship's public keys and signed by the ship which sent them.