RusStocks

Existing tokenized-stock issuers are built primarily for exchanges and institutions; self-custody holders are accommodated, not designed for. RusStocks starts from the opposite direction: built for the person who holds their own keys and wants to verify the backing themselves, not delegate trust to a brand.

1. User mints a token; USDC enters the protocol vault.
2. The multisig withdraws collateral. Every withdrawal carries a mandatory on-chain memo (e.g. "buy 12 SBER shares") and emits an event.
3. Real MOEX shares are purchased and held in brokerage custody.
4. A configurable burn buffer stays in the vault so redemptions clear instantly. When burns draw it down, shares are sold and USDC is returned.
5. Proof of Reserves publishes the cumulative mint/burn counter, the withdrawal log, and current share holdings, so shares-held ≥ tokens-outstanding is independently checkable, not asserted.

Russian equities pay dividends to the custody account in rubles. There is no native on-chain dividend, so RusStocks reconstructs one. At a published block height tied to the issuer's record date, a snapshot fixes every wallet's balance and total supply. The ruble dividend is converted to a ruble stablecoin and deposited into a dividend vault tied to that snapshot.

Payout is pull-based: (balance at snapshot ÷ supply at snapshot) × pool, claimed on demand rather than pushed to every holder. This also means a token held in a liquidity pool or lent out on a money market at snapshot time still earns the dividend, credited to whoever held it then, not whoever holds the LP position now.

• Reserve solvency at /reserves: an on-chain counter cross-checked against custodied share holdings, published via API.
• Every collateral withdrawal carries a human-readable on-chain memo naming the exact trade. The full purchase history is public, not summarized after the fact.
• Price oracle runs on a dedicated price_updater key, separate from the admin key, pushing MOEX ISS price ÷ USD/RUB every 10 minutes during market hours.
• A circuit breaker bounds each oracle update to 30% movement within 30 seconds, limiting the damage a bad feed or compromised updater key can do before it's caught.