Skip to content

Commit

Permalink
another pass and fix tables
Browse files Browse the repository at this point in the history
  • Loading branch information
joaniefromtheblock committed Jul 13, 2024
1 parent bfb9324 commit 79aaf57
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 2 deletions.
18 changes: 17 additions & 1 deletion services/reference/linea/json-rpc-methods/trace-methods/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,4 +44,20 @@ smart contract transaction. Excludes precompiled contracts.
]
```

<table><thead><tr><th width="242">Key</th><th>Value</th></tr></thead><tbody><tr><td><code>action</code> </td><td>Transaction details.</td></tr><tr><td><code>callType</code></td><td> Whether the transaction is <code>call</code> or <code>create</code>.</td></tr><tr><td><code>from</code></td><td>Address of the transaction sender.</td></tr><tr><td><code>gas</code></td><td>Gas provided by sender.</td></tr><tr><td><code>input</code></td><td>Transaction data.</td></tr><tr><td><code>to</code></td><td>Target of the transaction.</td></tr><tr><td><code>value</code></td><td>Value transferred in the transaction.</td></tr><tr><td><code>result</code></td><td>Transaction result.</td></tr><tr><td><code>gasUsed</code></td><td>Gas used by the transaction. Includes any refunds of unused gas.</td></tr><tr><td><code>output</code></td><td>Return value of the contract call. Contains only the actual value sent by a <code>RETURN</code> operation. If a <code>RETURN</code> was not executed, the output is empty bytes.</td></tr><tr><td><code>subTraces</code></td><td>Traces of contract calls made by the transaction.</td></tr><tr><td><code>traceAddress</code></td><td>Tree list address of where the call occurred, address of the parents, and order of the current sub call.</td></tr><tr><td><code>transactionHash</code></td><td>Hash of the transaction.</td></tr><tr><td><code>transactionPosition</code></td><td>Transaction position.</td></tr><tr><td><code>type</code></td><td>Whether the transaction is a <code>CALL</code> or <code>CREATE</code> series operation.</td></tr></tbody></table>
| Key |Value |
|---------------------|-----------------------------------------------------------------------------------------------------------|
| `action` | Transaction details. |
| `callType` | Whether the transaction is `call` or `create`. |
| `from` | Address of the transaction sender. |
| `gas` | Gas provided by sender. |
| `input` | Transaction data. |
| `to` | Target of the transaction. |
| `value` | Value transferred in the transaction. |
| `result` | Transaction result. |
| `gasUsed` | Gas used by the transaction. Includes any refunds of unused gas. |
| `output` | Return value of the contract call. Contains only the actual value sent by a `RETURN` operation. If a `RETURN` was not executed, the output is empty bytes. |
| `subTraces` | Traces of contract calls made by the transaction. |
| `traceAddress` | Tree list address of where the call occurred, address of the parents, and order of the current sub call. |
| `transactionHash` | Hash of the transaction. |
| `transactionPosition`| Transaction position. |
| `type` | Whether the transaction is a `CALL` or `CREATE` series operation. |
4 changes: 3 additions & 1 deletion snaps/how-to/request-permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,13 +28,15 @@ following to the manifest file:
```

:::note

All Snaps API methods except the following interactive UI methods require requesting permission in
the manifest file:

- [`snap_createInterface`](../reference/snaps-api.md#snap_createinterface)
- [`snap_getInterfaceState`](../reference/snaps-api.md#snap_getinterfacestate)
- [`snap_updateInterface`](../reference/snaps-api.md#snap_updateInterface)
:::

:::

### Endowments

Expand Down

0 comments on commit 79aaf57

Please sign in to comment.