Private companies use Selcier to turn their shares into tokens on Robinhood Chain. The company's rules run on each transfer before it can settle, and each issuance, offering and corporate action lands on a record anyone can verify.
$SELCIER - 0xea9bdde9e1b9474da1628c6a529c0d83aaacbbba
Larkway Labs
Series B Preferred · LKW-B
Reference Valuation
22.50 USDG
Priced round · Sep 30, 2026
Series B extension
6 days remaining
canTransfer
500 LKW-B
Halted by EligibilityModule. The recipient falls short of this class's eligibility tier.
Issuer-sponsored. The company behind a Selcier token is always its issuer.
In place of spreadsheets and manual transfer review, Selcier gives each class a share token. Token balances then serve as the cap table: reconciled once at onboarding, then kept current by the chain.
A company passes verification and picks the share classes it will bring on-chain. It then names a registrar to keep the authoritative cap table, either the company itself or an administrator of its choosing.
A CSV or a cap table software export brings in the existing records, which are reconciled line by line. Holders accept an invitation, prove their identity, and either take an embedded wallet or connect one they own.
Each share class gets its rules in the Console: regions, eligibility tier, holding periods, holder cap, transfer windows, right of first refusal, maximum ownership and employee vesting. Because rules are modules, they can be changed later with no token upgrade.
The same configuration goes to Robinhood Chain testnet first. Against it the company tries sample transfers, an offering and a window, and inspects every reason code while mainnet stays untouched.
In a single transaction, SelcierFactory puts the company's full contract set on mainnet. Working from the reconciled cap table, the registrar mints to each holder, and SharesIssued records the reference for every mint.
The company now raises through offerings, opens Liquidity Windows, pays distributions, holds votes and anchors disclosures. Each of these starts in the Console and lands as an on-chain transaction.
Companies work in the Console and holders in Portfolio. The Explorer is open to anyone, and the API gives developers access to all of it. Every surface reads from the same Robinhood Chain contracts.
Console, Portfolio, Explorer and the API. Four ways in, one set of contracts.
Console
For companies
Boards and finance teams set up share classes and transfer rules, run offerings and Liquidity Windows, and sign off on sensitive actions through a multi-sig that includes the company.
Portfolio
For holders
Every position appears by lot, with locked and unlocked shares kept apart. From here holders join offerings, sell in Liquidity Windows, claim distributions, vote and read company documents, all with gas sponsored.
Explorer and API
For everyone
Supply, holder count, rules, offerings, windows, valuations and events are all visible in the Explorer for each company, with no personal data. Through the API and SDK, venues and wallets reach those records and the same transfer checks.
Each surface is covered in depth in the product documentation.
Because the token itself carries the rules, they apply across every wallet, venue and pool on a permissionless chain. Rule-breaking transfers cannot settle, and canTransfer gives the reason ahead of any signature.
Is the class paused? Does the sender have enough shares that are unlocked and unfrozen?
On the company's registry, does each wallet map to a verified identity whose claims have not expired?
The modules the company enabled run one after another. When all of them pass, the result is OK and the transfer settles.
Admits or bars holders by region, from a country allow-list or block-list.
Accepts a recipient only with a valid eligibility claim at the class's tier or higher.
Keeps every lot locked for a set period from acquisition. The oldest lots are used first.
Caps how many distinct holders the class can have.
Permits transfers solely within company-scheduled windows.
Grants the company first refusal, and the right is exercised on-chain.
Limits how much of the class one holder can own.
Holds unvested employee shares locked until the schedule releases them.
Each share class has its own module configuration, and swapping a module needs no token upgrade. Any addition or removal waits out a 24 hour timelock.
An IdentityRegistry per company links wallets to an on-chain identity. Verifiers the company trusts sign the claims on that identity, and every claim has a topic, a value and an expiry. Names, documents and contact details remain with the verifier, off-chain.
IDENTITY_VERIFIED
Shows the holder cleared identity verification. It has an expiry.
INVESTOR_ELIGIBLE
States the holder's eligibility tier, attested by a trusted verifier.
REGION
Holds the ISO 3166 country code that RegionModule reads.
EMPLOYEE_OF
Names the holder's employer, for vesting and employee windows.
SCREENED
Dates the holder's latest screening. A failed re-screen revokes it automatically.
VENUE
Identifies a pool or venue contract approved to hold shares.
Liquidity stays under the company's control instead of arriving unplanned. All four mechanisms settle delivery versus payment in USDG, so shares and stablecoins move together in one transaction or not at all.
OfferingVault
Price per share, minimum and maximum raise, minimum ticket and dates are all set by the company. Subscriptions arrive in USDG and wait in escrow. Close either mints shares and releases funds in one transaction or refunds every investor.
LiquidityWindow
These are sales for a fixed period, on dates the company picks. Shares from sellers and USDG from eligible buyers are locked, and a single uniform price clears the window. If ROFR is on, the company holds a priority bid at that price ahead of settlement. Fixed-price tenders follow the same pattern.
RFQSettlement
Between windows, eligible holders trade on signed EIP-712 quotes. Fills happen on-chain with canTransfer run on both sides, and the company may limit RFQ to its transfer windows.
PoolGate
An opted-in company can list a class on an AMM pool. Every swap and liquidity change passes through canTransfer at PoolGate, which leaves trading and liquidity provision to eligible holders alone.
Here a Liquidity Window runs on LKW-B, an illustrative Series B Preferred class for the sample company Larkway Labs. Once it closes, any caller can run clear(windowId). The contract settles on the one price that matches the most shares, resolving ties toward the last Reference Valuation, and fills by price priority with pro-rata at the margin. Whatever stays unmatched is released.
Asks
Sellers lock shares
Bids
Buyers lock USDG
Cleared
WindowCleared
24.00 USDG
Buyers and sellers alike fill at the same price
That price then becomes the latest Reference Valuation, published with source WINDOW_CLEARING.
Private company equity usually changes hands in one of two ways: by hand against off-chain records, or through tokens that third parties create without the company. Selcier offers the issuer-sponsored alternative.
Without the issuer, nothing gets tokenized on Selcier. A token's issuer is always the company behind it.
Wallets, pools and oracles on Robinhood Chain already understand the conventions it set. Selcier tokens observe all of them and layer on identity-gated transfers and issuer governance. As a company, Selcier is independent, and it is built on Robinhood Chain.
One Selcier Share Token represents each share class: an ERC-20 of 18 decimals with ERC-3643-compatible permissioned transfers and the ERC-8056 multiplier. To wallets and indexers on the chain, it reads as one more stock token.
Each Reference Valuation goes on-chain through ValuationOracle, which answers latestRoundData as an AggregatorV3 feed would. For the source, the date and the supporting document's hash, call latestValuation.
A split updates the ERC-8056 uiMultiplier once a 48 hour timelock has passed. Because raw balances stay fixed, pools and integrations run straight through the event, while the oracle pauses across it.
AMMs and stablecoin rails are already running on the chain. Any company that opts in can place a class in a pool behind PoolGate, which applies that class's rules to every swap.
Onboarding gives incoming holders an embedded wallet, and EVM wallets they already use connect unchanged. Because Selcier relays transactions, neither investors nor employees ever need ETH.
A full rule check per transfer stays economical thanks to low fees and sub-second soft confirmation, while settlement inherits Ethereum security.
The public record reaches the Explorer directly from Robinhood Chain. With personal data kept off-chain, the whole record can stay public and holders can stay private.
Supply cannot change quietly. Mints, burns, recoveries, freezes and pauses each carry a reference, and every event is indexed by the Explorer and the API with its block and transaction.
For each document the company publishes, DisclosureRegistry stores its kind, hash and location. Verified holders read the contents in Portfolio, and anyone can prove a document is unchanged since anchoring.
One integration of the rule engine serves a venue or wallet for every company on Selcier. On-chain, through the API and in the SDK, canTransfer gives the same answer.
$ npm install @selcier/sdk
import { Selcier } from "@selcier/sdk";
const selcier = new Selcier(process.env.SELCIER_SECRET_KEY);
const check = await selcier.transfers.check({
share_class: "cls_nwl_series_b",
from: "0x71c3a0d5f1b84e2c9a07d36b5e8f12c4d0a39e4a",
to: "0x4e8817b3a9c25d06e4f71b8a2d93c5e6f048c0b1",
amount: "500",
});
// {
// ok: false,
// reason_code: "NOT_ELIGIBLE",
// message: "The recipient does not meet the eligibility tier for this share class."
// }Webhook events
Endpoints cover companies, share classes, holders, offerings, windows, distributions, proposals, documents and valuations, in JSON with cursor pagination. Every POST takes an Idempotency-Key.
Each on-chain event arrives with its block number, transaction hash and confirmation depth. Deliveries are HMAC-SHA256 signed and retried for three days.
Using sk_test_ keys, you work on Robinhood Chain testnet, where contracts and reason codes match mainnet.
A browser or wallet can use pk_live_ keys directly for read-only endpoints, including transfer checks and public Explorer data.
Roles stay separate, the issuer signs on the timelocked multi-sig that sensitive actions pass through, and a pause always publishes its reason. Every deployment first runs on testnet with the identical configuration.
These are defaults. A company may adjust its timelocks inside fixed bounds.
Sets up modules, offerings, windows, distributions and votes.
Approves recoveries, and mints and burns against cap table records.
Sponsors and submits transactions, but cannot move holder tokens alone.
Can pause a share class, with an on-chain reason, and unpause it.
To report a vulnerability, write to security@selcier.xyz.
After reporting the lost wallet, the holder repeats identity verification with a trusted verifier.
The replacement wallet needs approval from two of ISSUER_ADMIN, REGISTRAR and OPERATOR. One party acting alone cannot complete it.
On-chain scheduling reveals the execution time, letting the holder and any observer see the recovery ahead of time.
By default the balance is frozen for 72 hours. During that time, a mistaken or contested recovery can be cancelled.
The replacement wallet receives the entire balance, and lots and holding periods carry over.
Share the details of your company and the classes you plan to issue. Our team will guide yours through the Console, rehearse your configuration on testnet, and deploy on your timing.
Less than four weeks to onboard · hello@selcier.xyz