Summary
This proposal requests a continuing mandate for the designated Neverland team to evaluate, configure, deploy, operate, expand, and contain tokenized stock reserves and markets across chains selected for Neverland deployment.
The mandate covers risk analysis, preparation of supporting reports, reserve admission, oracle and market configuration, launch tokenomics, incentives, and the complete deployment and integration process. It is intended to cover the current rollout and future additions without a separate governance proposal for every chain, reserve, market, or routine operational decision.
The team would act only after its internal risk and readiness gates are satisfied. A later governance proposal could narrow, replace, or extend this mandate.
Problem Statement
Tokenized stock markets combine issuer contracts, wrappers, price sources, liquidity, risk limits, chain infrastructure, and ongoing operating controls. Readiness can change between a proposal and execution, while market and infrastructure conditions can require action quickly.
Requiring a separate vote for every chain, reserve, oracle choice, parameter update, expansion, pause, or freeze creates delay and repeats the same approval process. It also divides responsibility across several governance steps instead of assigning one accountable team to the complete path from analysis through deployment, monitoring, and containment.
A continuing mandate would preserve governance authority over the boundary while allowing the team to make the operational decisions needed to protect the protocol and its users.
Low Level Details
Scope of the mandate
If approved, the team would be authorized to:
- Select chains for tokenized stock deployments and determine the appropriate market topology for each deployment.
- Run risk analysis, prepare risk and deployment reports, and pass or reject reserves for listing, expansion, or continued operation.
- Choose and configure oracle paths, wrappers, adapters, risk settings, caps, collateral and debt permissions, isolation settings, and other market controls.
- Deploy or coordinate the required contracts and supporting systems, complete role handoffs, verify the resulting configuration, and integrate monitoring and user-facing systems.
- Set the initial tokenomics and incentive design required for a new chain or market, and maintain or adjust those choices until governance changes them.
- List additional tokenized stocks, expand existing reserves and markets, or leave any proposed reserve unlisted when its requirements are not met.
- Freeze, pause, disable, cap, delist, unwind, or otherwise adjust a reserve or market when risk, liquidity, oracle quality, issuer conditions, chain conditions, or operational readiness require it.
This authority applies to the full operational lifecycle of tokenized stock markets on existing and new chains selected by the team. It includes the decisions needed to complete a multi-chain deployment end to end.
Operating process
For each deployment or material expansion, the team would use a common sequence:
- Confirm the chain, issuer, wrapper, oracle, liquidity, dependencies, and accountable operators.
- Run the risk analysis and record the assumptions, evidence, proposed controls, and unresolved items.
- Decide whether each reserve and market is ready, and pass or reject it for activation.
- Execute and verify the deployment, configuration, ownership and role handoffs, monitoring, and user-facing integration.
- Open the market in a controlled manner, monitor it, and change or contain it when conditions require.
The team would prepare a concise record for material launches, expansions, and containment decisions. Each record should state the decision, principal risks, controls, and unresolved dependencies. Sensitive deployment details may be omitted where publishing them would increase operational risk.
Risk and governance boundaries
The mandate is limited to tokenized stock markets and the systems directly required to support them. It does not authorize unrelated asset classes, a change to governance powers, or a new protocol mechanism outside this scope.
The team is expected to favor conservative limits, observable evidence, and reversible actions where possible. Existing security review, access control, emergency control, and timelock requirements remain applicable unless a later governance decision changes them.
The mandate remains effective until governance changes it. A new proposal would be required to define, alter, or introduce a material mechanism outside the team’s delegated decisions.
Closing Statement
This proposal asks governance to authorize the Neverland team to manage tokenized stock markets across chains from risk analysis and reserve admission through deployment, incentives, monitoring, expansion, and emergency containment.
The intended result is a single accountable team that can execute the current rollout and future multi-chain additions without a new proposal for each routine market decision, while governance retains the power to revise the mandate or require a new vote for decisions outside its scope.
If governance agrees that this balance provides sufficient protection for the protocol and its users, the RFC can proceed toward a Governance Vote.
- Robinhood Chain, Stock Tokens.
Stock-token system documentation, asset behavior, oracle inputs, and integration constraints. - Neverland Documentation, Lending Model.
Lending markets, risk parameters, oracles, incentives, and governance-directed controls.