Session
Written Transaction Annotation
You send one mainnet signature. The desk returns a written reading: a field list, plain sentences for each instruction, and the questions the page leaves open.
Who it is for
Someone who needs a page they can hand to a colleague, a supervisor, or their later self, and who cannot sit the ninety minutes in Jeongeup.
What you leave with
A written reading of one signature that names the fee payer, the account flags, each outer instruction, and any inner instructions the explorer shows.
Scope
One mainnet signature. Devnet pages are declined for this commission because the note is meant to be cited later. Address lookup tables are quoted as an extra sheet before that work starts.
Included
- A look at the public page and a fee reply before writing begins
- A field list and plain-language lines for each instruction
- A short section on what the page does not show
- One round of clarification by email
Outside this arrangement
- A live sitting or a call
- More than one signature
- A second clarification round, unless you commission it
- Translation of program source, and any promise about what a closed-source program intended
How the time is spent
- Send the signature and say who will read the note.
- The desk counts instructions and replies with the fee before opening a markup.
- The note is written at the desk and emailed within four working days of agreement.
- You may send one list of lines that are still unclear. The desk answers that list once.
Before you begin
Send the full signature, the explorer you were looking at, and whether the reader needs Korean field names beside the English.
Limits
Work starts only after you accept the quoted fee. Pages with a very long inner-instruction list may be declined if they cannot be read honestly in the usual time.