Data Flow

1. User submits feedback on nodosdeconocimiento.es/feedback
2. Browser POSTs to nodosdeconocimiento.es/hm/api/feedback
3. The nodosdeconocimiento web server reads /opt/seed/web/config.json
4. Config says:
   - destination account = seed-surveys account
   - signer account = nodosdeconocimiento server signer
   - capability = grant from seed-surveys to that signer
5. Server asks its local daemon to sign the document change
6. The signed change says:
   - account: seed-surveys
   - path: random private path
   - visibility: PRIVATE
   - capability: capability CID
7. Server publishes blobs to the network
8. Seed validates:
   - signer matches the delegate in the capability
   - capability was issued by seed-surveys
   - capability grants WRITER
   - account matches seed-surveys
9. If valid, the private doc belongs to seed-surveys

Concrete values from your current setup

Current site:
nodosdeconocimiento.es

Current site account:
z6MkhGQJc96o3UNQ3JyUbCKfQo2bvaQ9KDNa9xxYHJFWWTwg

Feedback destination:
seed-surveys.hyper.media

Feedback destination account:
z6MkkeXDXo4p5y483NqxnMjZKbE4VAv8GPXp3kQ5JGYbTTsR

Server signer:
z6MkmYhMohZM7agevqQdejj56Y6ZQNVVMw2Mq3LUmER4jNtf

Correct capability:
bafy2bzacedh3rr5ew5nvy4exly2zietju3dkqawyqzciyjkevtqewwp7kdq7k

Verification gap

Right now the flow ends with:

Server returns success

But it does not return:

documentId

So the user sees success, but we cannot directly inspect the created private document.

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime