Chapter 10 — Web3, blockchain and cryptoasset security: quality and troubleshooting
Lesson map
Lesson 10 published. Map, example, EX046.
flowchart TD
N0["Learning outcomes"]
N1["10.1 Monitoring quality"]
N2["10.2 Methodical troubleshooting"]
N3["10.3 Improving from evidence"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX046"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["10.1 Monitoring quality"]
N2["10.2 Methodical troubleshooting"]
N3["10.3 Improving from evidence"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX046"]
[Learning outcomes]
|
v
[10.1 Monitoring quality]
|
v
[10.2 Methodical troubleshooting]
|
v
[10.3 Improving from evidence]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX046]
Learning outcomes
You will (1) monitor workflow quality; (2) troubleshoot problems methodically; (3) improve the process from evidence.
10.1 Monitoring quality
Marcus tracks simple quality measures for the donation workflow: percentage of donations reconciled within five days, number of discrepancies per month and their causes, time from proposal to approval, and any approvals outside the documented steps. After three months, reconciliation within five days rises from 70 to 95 percent, and discrepancies fall from six to two a month after receipts were generated from ledger references. Measures show whether controls are working in practice, and trends help catch slippage early before it becomes a habit.
10.2 Methodical troubleshooting
One month, a transfer to the exchange shows as executed on the ledger, but the exchange account shows no credit after a day. Marcus follows a method: confirm the transaction reference and destination on a block explorer, check that it matches the allow-listed address, check the exchange's status page and contact the exchange's support through the documented channel. The transaction and address are correct; the exchange reports a delay in crediting deposits from that network. The funds are credited the next day. He records the timeline and evidence.
10.3 Improving from evidence
From the delay, Marcus adds a step to the workflow: check the exchange's status page before initiating a transfer, and avoid transfers during announced maintenance. He also records the expected crediting time for the network. From the quality measures, he finds approvals sometimes take four days, mostly when the trustee travels, and proposes scheduling approvals around trustees' calendars. Ms Holm notes that continuous improvement based on measured evidence is what keeps controls usable over time, rather than letting them become burdens people work around.
Worked example
Reconciliation within five days rises from 70 to 95 percent, a delayed exchange credit is traced to the exchange, and a status-page check is added.
Synthetic case. The measures, delay and improvements are synthetic.
Errors and limits
Assuming funds are lost when a credit is delayed, without checking, causes needless alarm.
Exercises
- EX046 — Reconciliation improvement. How did on-time reconciliation change? Rubric: 3 = from 70 to 95 percent;; 2 = 95 percent;; 1 = unchanged;; 0 = none.
- EX047 — Discrepancy trend. How did monthly discrepancies change? Rubric: 3 = from six to two;; 2 = fell;; 1 = rose;; 0 = none.
- EX048 — Delay cause. What caused the missing exchange credit? Rubric: 3 = an exchange delay crediting that network;; 2 = exchange delay;; 1 = wrong address;; 0 = none.
- EX049 — Added step. What step is added before transfers? Rubric: 3 = check the exchange's status page;; 2 = status check;; 1 = vague;; 0 = none.
- EX050 — Approval delay cause. Why did approvals sometimes take four days? Rubric: 3 = the trustee was travelling;; 2 = travel;; 1 = no reason;; 0 = none.
Synthesis
Quality measures and methodical troubleshooting drive evidence-based improvements.
Continue studying — chapter 10 of 12
← Chapter 09 (draft) · Course chapter index · Chapter 11 (draft) →