> For the complete documentation index, see [llms.txt](https://docs.topledger.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.topledger.xyz/data-tables/decoded-instructions-data/switchboard-v2.md).

# Switchboard V2

#### switchboard**.txns**

This table has similar schema as of Solana [transactions](/data-tables/solana-data/transactions.md) table

#### switchboard**.parsed**

The table contains the parsed instructions data for [Switchboard](https://docs.switchboard.xyz/solana/program/mainnet). Data related to instruction type, executing account, account arguments, arguments, etc. is available here.

| Column Name               | Column Type    | Description                                                                                            |
| ------------------------- | -------------- | ------------------------------------------------------------------------------------------------------ |
| block\_date               | date           | Event date                                                                                             |
| block\_time               | timestamp      | The (estimated) time this block was produced                                                           |
| block\_slot               | bigint         | This block’s slot index in the ledger                                                                  |
| dapp                      | string         | Solana program address                                                                                 |
| inner\_instruction\_index | int            | The order of inner instruction of an instruction in a txns                                             |
| input\_accounts           | array\<string> | Ordered list of accounts to pass to the program                                                        |
| instruction\_index        | int            | The order of the instruction in a txns                                                                 |
| instruction\_type         | string         | Name of the function of a Solana program invoked via an instruction                                    |
| is\_inner\_instruction    | boolean        | Whether the respective instruction of a txns has an inner instruction                                  |
| tx\_id                    | string         | The first signature in the transaction                                                                 |
| args                      | \<STRUCT>      | The arguments passed to the invoked function. Generated after decoding the instructions data parameter |

Some columns in the above table needs to be explained a bit for better understanding. Let's go into what each one of them contains.

#### **input accounts**

<table><thead><tr><th width="374.3333333333333">Field</th><th>Column Type</th></tr></thead><tbody><tr><td>aggregator</td><td>string</td></tr><tr><td>authority</td><td>string</td></tr><tr><td>callbackPid</td><td>string</td></tr><tr><td>crank</td><td>string</td></tr><tr><td>crankDataBuffer</td><td>string</td></tr><tr><td>dataBuffer</td><td>string</td></tr><tr><td>escrow</td><td>string</td></tr><tr><td>feedPermission</td><td>string</td></tr><tr><td>funder</td><td>string</td></tr><tr><td>gcOracle</td><td>string</td></tr><tr><td>historyBuffer</td><td>string</td></tr><tr><td>instructionsSysvar</td><td>string</td></tr><tr><td>lease</td><td>string</td></tr><tr><td>mint</td><td>string</td></tr><tr><td>oracle</td><td>string</td></tr><tr><td>oracleAuthority</td><td>string</td></tr><tr><td>oraclePermission</td><td>string</td></tr><tr><td>oracleQueue</td><td>string</td></tr><tr><td>oracleWallet</td><td>string</td></tr><tr><td>owner</td><td>string</td></tr><tr><td>payerAuthority</td><td>string</td></tr><tr><td>payerWallet</td><td>string</td></tr><tr><td>payoutWallet</td><td>string</td></tr><tr><td>permission</td><td>string</td></tr><tr><td>programState</td><td>string</td></tr><tr><td>queue</td><td>string</td></tr><tr><td>queueAuthority</td><td>string</td></tr><tr><td>queueDataBuffer</td><td>string</td></tr><tr><td>recentBlockhashes</td><td>string</td></tr><tr><td>tokenAccount</td><td>string</td></tr><tr><td>tokenProgram</td><td>string</td></tr><tr><td>vrf</td><td>string</td></tr></tbody></table>

#### args

| Field                     | Data Type |
| ------------------------- | --------- |
| counter                   | int       |
| failOpenOnAccountMismatch | bool      |
| leaseBump                 | int       |
| leaseBumps                | string    |
| loadAmount                | float     |
| mantissa                  | float     |
| nonce                     | int       |
| permissionBump            | int       |
| permissionBumps           | string    |
| proofEncoded              | string    |
| scale                     | int       |
| stateBump                 | int       |

#### switchboar&#x64;**.events**

This table has all the switchboard v2 historically parsed events.

| Field           | Column Type | Description                                  |
| --------------- | ----------- | -------------------------------------------- |
| block\_date     | date        | Event date                                   |
| block\_time     | timestamp   | The (estimated) time this block was produced |
| block\_slot     | bigint      | This block’s slot index in the ledger        |
| tx\_id          | string      | The first signature in the transaction       |
| dapp            | string      | Solana program address                       |
| event\_type     |             | The name of the event emitted                |
| [args](#args-1) | \<STRUCT>   | The arguments of the respective event        |

#### args

| Field                         | Data Type      |
| ----------------------------- | -------------- |
| alpha                         | string         |
| amount                        | bigint         |
| authorityPubkey               | string         |
| counter                       | bigint         |
| existingAmount                | bigint         |
| feedPubkey                    | string         |
| funder                        | string         |
| jobPubkeys                    | array\<string> |
| leasePubkey                   | string         |
| loadAmount                    | bigint         |
| oraclePubkey                  | string         |
| oraclePubkeys                 | array\<string> |
| [oracleValues](#oraclevalues) | array\<STRUCT> |
| queueAuthority                | string         |
| queuePubkey                   | string         |
| remainingFunds                | bigint         |
| roundSlot                     | bigint         |
| slot                          | bigint         |
| timestamp                     | timestamp      |
| [val](#val)                   | \<STRUCT>      |
| vrfPubkey                     | string         |
| walletPubkey                  | string         |

#### oracleValues

| Field    | Data Type |
| -------- | --------- |
| mantissa | double    |
| scale    | int       |

#### val

| Field    | Data Type |
| -------- | --------- |
| mantissa | double    |
| scale    | int       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.topledger.xyz/data-tables/decoded-instructions-data/switchboard-v2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.