EikHub · Guide
Signed receipts on EikHub
For each person an issue is sent to, EikHub can give the building a signed receipt of what they received, opened and printed.
Why a receipt
An issue releases revisions of drawings to people for a purpose: for review, for tender, for construction. Later someone may say "we never got revision B". A portal can show its own log, but that log lives in the portal. A receipt is that record as a file in the building, signed so that it can be checked by anyone, years later, without EikHub.
For someone the issue record does not name, such as a subcontractor a consultant passed it on to, the receipt is the building's only record that they received it at all, and it says who sent it to them.
A receipt is EikHub's word about what it saw. A contract that rests on receipt may also ask for the recipient's own signed word; EikHub's receipt does not replace that.
Sending an issue
The issue itself is written by the drawing tool, such as Stomra, when it issues: it names the revisions, the purpose and the recipients. EikHub sends it.
- Open the issue. On the building's Drawings tab, show the drawings as Issues and open one. The page shows what it released, its checks and sign-offs, and every sending of it so far.
- Choose the recipients. Pick the people the issue names and give each an address, or add someone else by name and organisation. The address stays on EikHub, for the email only; the receipt names the person, never the address.
- Add a note if you want, and press Send.
- Keep the links. Each recipient gets an email that says what changed since the revision they last received, with a link that opens without an account for 30 days. The links are shown to you once, under "The links, shown this once."
A sending can be withdrawn per recipient: the link stops at once. A version that holds no issue record can still be sent, but its recipients will have no receipt, and the page says so.
Planning comes before sending: Plan an issue on the Drawings tab chooses the drawings the model has moved on from, with status, purpose, clouds and recipients. EikHub records the plan; the drawing tool issues it.
What EikHub records
For each recipient the issue page shows what has happened, with the time of each:
| Event | On the page | What happened |
|---|---|---|
| sent | Sent | EikHub sent the issue to the recipient. |
| delivered | Delivered to their mail | The recipient's mail system took the message. |
| opened | Opened the link | The recipient opened the issue for the first time. |
| viewed | Looked at … | They looked at a revision the issue releases; the event says which. |
| downloaded | Printed … as PDF, or Took … | They took a file, such as a print, named by its digest and what it was printed from. |
| withdrawn | Link withdrawn | The sender withdrew the issue from them. |
| superseded | Told that … is replaced | A later issue released a newer revision of a drawing they had received, and they were told. |
EikHub's prints are the same bytes every time they are made from the same revision, so a print's digest can be checked by anyone who prints it again.
What a receipt holds
Press Receipt beside a recipient to get theirs. It holds:
- the issue, by its id and the hash of its record;
- the host: EikHub;
- the recipient, as the issue names them, or by name and organisation for someone added;
- for someone added, who sent it to them and in which sending;
- every event, oldest first, with what each was about.
EikHub signs it with a key it uses for receipts and nothing else, and an independent time-stamp authority dates the signature. A later receipt for the same person holds all the earlier events too; until something new happens, EikHub offers the same file again.
The format is OpenEik's (Part XVIII, Review and issue), so any tool that reads OpenEik can read and check it.
Saving receipts into the building
Receipts go into the building only when the project asks, issue by issue. On an issue's page, press Save the receipts into the building. From then on, the drawing tool saves each recipient's newest receipt beside the issue, at drawings/issues/<issue>/receipts/, when it next publishes the building. EikHub never writes the building itself.
Checking a receipt
A receipt is checked offline, with two things:
- EikHub's published keys, at
https://api.eikhub.com/.well-known/openeik/host-keys.json, each with the dates it is valid between. A retired key keeps its place in the list with an end date, so a receipt signed while it was valid stays valid; - the time-stamp authority's certificate.
Any tool that implements OpenEik can check a receipt, given the host's keys. A receipt changed after signing, or signed outside its key's dates, fails.
Paper on site: the QR check
Every print EikHub makes carries a QR code with its revision's digest. Scan it, or type the digest at eikhub.com/check, and you learn whether that sheet is still current, which revision replaced it, or that the drawing was withdrawn ("Do not build from it"). Whoever holds the sheet learns that and no more; a member of the building who signs in sees when it was issued and what changed.
Personal data
A receipt says when a named person looked at what, so it is personal data. That is why it enters the building only when the project asks for it, why it names people and never their addresses, and why each transmittal email tells the recipient what EikHub records and that the sender may save it into the building.