Skip to content

Update komet version#40

Open
bbyalcinkaya wants to merge 3 commits into
mainfrom
update-komet
Open

Update komet version#40
bbyalcinkaya wants to merge 3 commits into
mainfrom
update-komet

Conversation

@bbyalcinkaya

@bbyalcinkaya bbyalcinkaya commented Jul 9, 2026

Copy link
Copy Markdown
Member
  • Bump the komet dependency from v0.1.79 to v0.1.85.
  • Update the README's traceTransaction example and its accompanying documentation to reflect that the upgraded semantics now emit callContract and endWasm records bracketing the contract call.
  • Document all five trace record kinds (callContract, WebAssembly instruction records, hostCall, contractData, endWasm)
  • Add examples of hostCall and contractData records that the walkthrough's example transaction doesn't itself produce.

Comment thread README.md
```

Each trace record captures the VM state at instruction entry: `pos` is the instruction's byte offset in the binary (`null` for synthetic instructions), `instr` is the instruction and its operands, and `stack`/`locals` are the value stack and locals as `[type, value]` pairs. See [docs/interpreter.md](docs/interpreter.md) for the full trace format.
A trace can contain five kinds of records:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, we must look at the shape of each record to determine its kind. I think it would make it easier for consumers of this format to have a descrimnator field, e.g. kind: 'callContrct' | 'instr' | 'contractData' | 'endWasm' on each record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants