> 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/readme.md).

# Welcome to Selcier

With Selcier, private companies put their shares on Robinhood Chain as stock tokens, and each issuance, transfer and corporate action settles in the open, on-chain.

Private companies run their equity on Selcier. On this infrastructure a company turns its shares into stock tokens on Robinhood Chain, keeps its cap table on-chain, brings in capital from eligible investors, and offers shareholders liquidity under conditions it chooses.

No Selcier token exists apart from its company, which is why we call them **issuer-sponsored**: the company behind a token issues it, sets its rules, and retains control over who may hold it. Robinhood Chain records each issuance, transfer, corporate action and rule decision, and that record settles to Ethereum. The events are open to verification by anyone, yet the identities behind them are kept private.

## The platform in six verbs

|                |                                                                                                                                                                                                                 |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Tokenize**   | Each share class becomes a Selcier Share Token: an ERC-20 built to Robinhood Chain's stock token conventions.                                                                                                   |
| **Enforce**    | Rules hold by construction. On-chain checks test each transfer against holder identities and the company's settings for regions, eligibility, holding periods, holder caps, vesting and right of first refusal. |
| **Raise**      | Primary offerings run from a vault on-chain. Subscriptions sit in USDG escrow, and a single transaction both mints shares to investors and releases the money.                                                  |
| **Administer** | Corporate administration moves on-chain, with a transaction for each split, dividend, conversion, shareholder vote or disclosure.                                                                               |
| **Trade**      | A company can open Liquidity Windows for a fixed period, turn on RFQ trading among eligible holders, or opt into permissioned pools.                                                                            |
| **Verify**     | Supply, holder count, transfers and corporate actions for each company appear in the Selcier Explorer, and every figure can be confirmed on-chain.                                                              |

## The pieces and who uses them

```
 Company ─► Console ──┐
 Investor ─► Portfolio ┼─► Selcier platform ─► Robinhood Chain (4663) ─► Ethereum
 Developer ─► API/SDK ─┘        │                     │
                                └──── Explorer ◄──────┘
```

Four front doors lead to one platform. Companies operate from the [Console](/the-platform/issuer-console.md), while investors and employees use [Portfolio](/the-platform/holder-portfolio.md) to hold, buy and sell. Venues and developers connect through the [API and SDK](/the-platform/developer-tools.md), and the [Explorer](/the-platform/public-explorer.md) opens the public record to everyone.

## Pick a path

* **Learning what Selcier is.** Begin with [The case for Selcier](/start-here/the-case-for-selcier.md) and [Tokenized equity, explained](/start-here/tokenized-equity-explained.md), and move on to [Tokenized share classes](/fundamentals/tokenized-share-classes.md), the central concept.
* **Putting a company on-chain.** Work through [Bring a company on-chain](/walkthroughs/onboard-a-company.md), and continue with [Launch a raise](/walkthroughs/launch-a-raise.md) or [Put a Liquidity Window on the calendar](/walkthroughs/schedule-a-window.md).
* **Holding or buying shares.** Two walkthroughs apply here: [Subscribe to a raise](/walkthroughs/subscribe-to-a-raise.md) and [Sell your shares in a window](/walkthroughs/sell-your-shares.md).
* **Writing code against Selcier.** Your starting point is [Your first integration](/build-on-selcier/first-integration.md). The [Smart contract map](/build-on-selcier/smart-contracts.md) and [Supporting Selcier tokens](/build-on-selcier/supporting-selcier-tokens.md) come after it.

{% hint style="info" %}
Selcier is built on Robinhood Chain and is an independent company. The [Explorer](https://explorer.selcier.xyz) lists contract addresses for all networks, and `GET /v1/contracts` returns them too. Be cautious with an address that comes from any other source.
{% endhint %}


---

# 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/readme.md?ask=<question>&goal=<user_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.
