Developer documentation
Technical reference for integrating, deploying, and operating the Robipad EVM launch infrastructure on Robinhood Chain.
Quick start
A Robipad launch packages token creation, initial allocation, pool initialization, liquidity locking, fee routing, and optional holder rewards into one atomic workflow.
# Install the future SDK
npm install @robipad/sdk ethers
# Target Robinhood Chain
ROBIPAD_CHAIN_ID=<pending network release>
ROBIPAD_FACTORY=<deployed factory address>- 1Connect an EVM wallet
Use an EIP-1193 provider and validate the active Robinhood Chain ID.
- 2Build a launch configuration
Define immutable token metadata, supply, quote asset, fees, and treasury.
- 3Simulate before signing
Estimate gas and validate factory constraints before broadcasting.
Architecture
The protocol separates immutable token deployment from upgradeable launch coordination and fee distribution.
| Component | Pattern | Upgrade policy |
|---|---|---|
| RobipadFactory | UUPS proxy | Timelock + multisig |
| RobipadToken | Minimal immutable | Non-upgradeable |
| LiquidityManager | UUPS proxy | Timelock + multisig |
| RewardDistributor | Beacon proxy | Per-market isolation |
EVM contract suite
Reference Solidity interfaces target Solidity 0.8.28 and OpenZeppelin Contracts 5.x. Production source code must be implemented, tested, verified, and independently audited.
interface IRobipadFactory {
struct LaunchConfig {
string name;
string symbol;
uint256 totalSupply;
address quoteToken;
uint24 poolFee;
uint16 rewardShareBps;
address treasury;
}
event TokenLaunched(
address indexed token,
address indexed creator,
address pool,
bytes32 configHash
);
function launch(LaunchConfig calldata config)
external payable returns (address token, address pool);
}Token implementation
Each launch receives a fixed-supply ERC-20 with permit support. Administrative permissions should be renounced or transferred according to the published launch policy.
contract RobipadToken is ERC20, ERC20Permit, AccessControl {
bytes32 public constant MINTER_ROLE = keccak256("MINTER_ROLE");
constructor(
string memory name_,
string memory symbol_,
uint256 supply_,
address owner_
) ERC20(name_, symbol_) ERC20Permit(name_) {
_grantRole(DEFAULT_ADMIN_ROLE, owner_);
_mint(owner_, supply_);
}
}Allowlisted implementations, deterministic addresses, configuration validation, and launch registry.
Pool creation, initial price bounds, LP NFT custody, lock expiry, and emergency recovery.
Index-based USDC accrual, claim accounting, dust handling, and treasury routing.
Role separation for pauser, upgrader, fee manager, and approved launch operators.
Launch lifecycle
Check symbol, supply, fees, quote asset, and creator permissions.
Create the token deterministically and register it with the factory.
Create the DEX pool, set initial price, and seed both assets.
Transfer LP position custody to the configured lock contract.
Enable swaps, fee accounting, indexing, and discovery metadata.
Fee routing
Every market defines a bounded swap fee. The distributor accounts for each destination before transfers, following checks-effects-interactions.
| Parameter | Recommended | Hard limit |
|---|---|---|
| Total swap fee | 1.00% | 3.00% |
| Protocol share | 0.15% | 0.50% |
| Holder rewards | 0.35% | 1.00% |
Holder rewards
Rewards use a cumulative reward-per-token index, avoiding holder iteration. Balances are checkpointed on transfer and claims settle only the caller’s accrued amount.
interface IRewardDistributor {
event RewardsDeposited(address indexed token, uint256 amount);
event RewardsClaimed(address indexed account, uint256 amount);
function checkpoint(address account) external;
function claim(address receiver) external returns (uint256 amount);
function claimable(address account) external view returns (uint256);
}Security model
Deployment, upgrades, pausing, fee changes, and treasury actions use distinct roles.
Upgrades require multisig approval and a public delay before execution.
Supply, accounting, pool ownership, and claim solvency invariants run continuously.
Factory, proxy, pool, and fee events feed real-time alerting and incident response.
Do not deploy contracts represented by this interface without complete tests, external audits, verified deployment bytecode, multisig governance, monitoring, and a funded incident response process.