Custom Tracer Authoring Guide

Sei exposes the standard debug_trace* RPC suite and accepts the same JavaScript tracer scripts as upstream go-ethereum. This guide captures the runtime expectations introduced in v1.15.7-sei-6 and v1.15.7-sei-7, plus Sei-specific conventions for panic handling.

Runtime Expectations

Authoring Patterns

const tracer = {
  result: {
    steps: [],
    gasUsed: 0,
    errors: []
  },
  step(log, db) {
    try {
      this.result.steps.push({
        pc: log.getPC(),
        op: log.op.toString(),
        gasCost: log.getCost()
      });
      this.result.gasUsed += log.getCost();
    } catch (err) {
      this.result.errors.push(String(err));
      throw err; // bubble up so Sei surfaces it in error.data.trace
    }
  },
  fault(log, db) {
    this.result.errors.push(`fault: ${log.getError()}`);
  },
  result() {
    return this.result;
  }
};
 
module.exports = tracer;

Recommendations

• Wrap logic in try/catch to append diagnostic context before re-throwing.
• Keep returned objects shallow; avoid large arrays or deeply nested state.
• Include a version identifier in the result to track script revisions.
• Use db.getBalance, db.getCode, etc., sparingly; each call hits execution state.

Validation Checklist

Troubleshooting