---
# System prepended metadata

title: Prosze Nakarm Kot

---

# Prosze Nakarm Kot


## Renting the house

```plantuml
actor owner as o
participant home as h
actor locator as l
actor neighbor as n
l -> o: Ask for house rental
o -> l: accept rental and provide credential with perrmission to open the house,
l -> h: Provide crenential that you get from owner
h -> h: Verify provided credential. If it verifies, let locator in

```
## Renting the house, diagram with external actors



```plantuml
actor locator as l
actor owner as o
participant home as h
actor neighbor as n
actor mesaĝkesto as msg
actor watcher as wat
actor witness as wit

l -> o: (owner oobi, owner mesaĝkesto)
    note right 
        Scan qr code to get to know house owner
    end note
l -> msg: rental request
msg -> o: rental request
o -> wat: resolve locator identifier
wat -> wit: find locator KEL
wat -> o: Get KEL, verify request
o -> o: generate ACDC
o -> l: ACDC
l -> h: ACDC
o -> wat: resolve locator identifier
wat -> wit: find locator KEL
wat -> o: Get KEL, verify request
h -> h: verify ACDC

```

### Remarks

Key Event Log(KEL) is KERI term, that associates Identifier and its private key. It let's user change current keys, without changing Identifier.
Watcher and witness are KERI specyfic actoras. Witness role is to verify, sign and keep events associated with identifier. Watcher role is retreiving Identifiers KEL that witnesses keeps, and provide it to Verifier.
When verifier has KEL of Identifeir's KEL it can verify, if data are really from him.