Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nexfi.robert.dpdns.org/llms.txt

Use this file to discover all available pages before exploring further.

​
Staking Admin Products

​
Product Config Fields

FieldDescription
product_keyUnique product key
display_nameFrontend display name
modeaggregated / vault
product_typenative / lst / stable_yield / liquidity
chain_idChain ID
asset_symbolDeposit asset
receipt_symbolReceipt asset
protocol_keyUnderlying protocol
risk_levellow / medium / high
statusactive / paused / disabled
reward_sourceYield source description
lock_ruleLock rule description
exit_ruleExit rule description
warning_textProduct warning
apy_sourceAPY source
sort_orderFrontend order
is_featuredHomepage recommendation
vault_addressVault contract address for vault mode
whitelist_requiredWhitelist flag

​
Admin APIs

​
GET /api/admin/v1/staking/products

Query fields:
  • status
  • productType
Example request: 
GET /api/admin/v1/staking/products?status=active&productType=lst

​
POST /api/admin/v1/staking/products

Typical body fields:
  • id
  • name
  • productType
  • chainId
  • riskLevel
  • status
Example request: 
{
  "name": "Lido stETH",
  "productType": "lst",
  "chainId": 1,
  "riskLevel": "medium",
  "status": "active"
}

​
POST /api/admin/v1/staking/products/{id}/status

Body fields:
  • status
  • reason
Example request: 
{
  "status": "paused",
  "reason": "protocol maintenance"
}

​
Rules

  • User-visible products must define reward_source, lock_rule, and exit_rule.
  • vault products must define vault_address before activation.
  • High-risk products should require stronger release review and audit tracking.