> For the complete documentation index, see [llms.txt](https://docs.selcier.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.selcier.xyz/reference/further-reading.md). # Further reading Where Selcier's external foundations are documented, from standards to network docs and infrastructure. Open standards and public infrastructure underpin Selcier. The sources below are where the conventions used throughout these docs come from. ## Chain documentation | Resource | Topics | | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Connecting to Robinhood Chain](https://docs.robinhood.com/chain/connecting) | For mainnet and testnet: chain IDs, RPC endpoints, sequencer feeds and the block explorer | | [Add network to your wallet](https://docs.robinhood.com/chain/add-network-to-wallet) | Setting up a wallet for either network | | [Stock Tokens](https://docs.robinhood.com/chain/stock-tokens/) | Reference conventions for stock tokens on the chain, namely trading status checks, per-asset price feeds, the `uiMultiplier` for corporate actions, and one ERC-20 per asset | | [Robinhood Chain explorer](https://robinhoodchain.blockscout.com) | Mainnet transactions and contracts, viewed in Blockscout | Wallets, oracles and DeFi integrations can expect predictable behavior from Selcier Share Tokens because they adhere to the stock token conventions of Robinhood Chain. Network specifics are in [The network underneath](/under-the-hood/network-foundation.md). ## Standards behind the token | Standard | Role in Selcier | | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [ERC-20](https://eips.ethereum.org/EIPS/eip-20) | The interface all Selcier Share Tokens build on | | [ERC-3643 (T-REX)](https://www.quicknode.com/guides/real-world-assets/erc-3643) | Standard for permissioned tokens, covering an identity registry, eligibility based on claims, and modular transfer rules. The [T-REX whitepaper](https://tokeny.com/wp-content/uploads/2023/05/ERC3643-Whitepaper-T-REX-v4.pdf) is a useful companion. | | ERC-8056 (Scaled UI Amount Extension) | Source of the `uiMultiplier()` interface that Robinhood Chain stock tokens use for splits and other corporate actions. The [Robinhood Chain Stock Tokens docs](https://docs.robinhood.com/chain/stock-tokens/) describe it. | | [EIP-712](https://eips.ethereum.org/EIPS/eip-712) | Signing of typed structured data. RFQ quotes rely on it, with domain name `Selcier` and version `1`. | | [ERC-1967 and UUPS (ERC-1822)](https://eips.ethereum.org/EIPS/eip-1822) | Share tokens sit behind this proxy pattern, and `IssuerTimelock` gates their upgrades | ## Price data | Resource | Topics | | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | [Chainlink: Robinhood Tokenized Equity Feeds](https://docs.chain.link/data-feeds/tokenized-equity-feeds/robinhood) | Price feeds per asset on Robinhood Chain, including how the multiplier feeds into them and what happens during a token pause | | [Chainlink Data Feeds API](https://docs.chain.link/data-feeds/api-reference) | Home of `AggregatorV3Interface`, the interface compatible consumers can call on the `ValuationOracle` | ## Rollup, explorers and RPC | Resource | Topics | | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | [Arbitrum documentation](https://docs.arbitrum.io) | Robinhood Chain's underlying rollup stack, with sequencing and force inclusion via Ethereum | | [Blockscout documentation](https://docs.blockscout.com) | Explorer APIs relied on for indexing and contract verification | | [Alchemy: Robinhood Chain RPC](https://www.alchemy.com/rpc/robinhood) | Mainnet archive, WebSocket and production RPC access | | [Alchemy: Robinhood Chain testnet RPC](https://www.alchemy.com/rpc/robinhood-testnet) | Connecting to the test network, chain ID `46630`, over RPC | | [Chainstack: Robinhood Chain](https://docs.chainstack.com/reference/robinhood-getting-started) | Used for failover, as an alternative source of RPC | ## Developer tooling | Library | Purpose | | ----------------------------------------------------------------- | -------------------------------------------------------------- | | [OpenZeppelin Contracts](https://docs.openzeppelin.com/contracts) | The ERC-20, access control and proxy code Selcier starts from | | [Foundry](https://book.getfoundry.sh) | Writing, testing and deploying contracts | | [viem](https://viem.sh) | Compatible with the on-chain helpers in `@selcier/sdk/onchain` | --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.selcier.xyz/reference/further-reading.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.