# Tables The following tables are outline in the order of a transaction starting at once chain and progressing to the opposing chain. `settings` - settings for this link library including things like the addresses and chain names `pmessages` - pending messages table, where incoming transfers go to be processed `batches` - pending messages added to batches table to be read by an oracle request from the opposing chain's bridge contract `bmessages` - pending messages added to batched messages after irreversible check, assuming was processed on opposing chain, awaiting receipt `ibatches` - inbound batches are stores here from oracle fetch on opposing chain's bridge contract `ibatch` - batches broken down 1 by 1 into individual batch and handled `fbatches` - if batch fails goes here, if not goes to `imessages` - inbound messages from each batch, fetch IPFS vRAM information `imessage` - messages broken down 1 by 1 into individual messages, if all messages in batch handled, delete batch, if not keep processing, if successful process message as receipt and send to opposing chain through `pmessages` table `fmessages` - if message fails, add to failed messages table --- # Agent Instructions: 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: ``` GET https://docs.liquidapps.io/liquidapps-documentation/introduction/dapp-network-resources/link-library/eosio-link/tables.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.