现实世界资产

存在什么

通俗版文档描述了三层。其中正好有一层在本仓库里有代码，而本参考记录的就是那一层。

所以：有价格，也有持有并提供这些价格的合约。没有保证金引擎，没有抵押品注册表，也没有可以调用 的头寸合约。当它们存在时，它们会作为调用表面被记录在这里，而不是作为意图。

是一个价格，不是那个资产

这是一句关于这条链做了什么的陈述，而不是硬贴上去的免责声明。注册表里没有任何东西引用发行方、 托管方或储备，因为根本没有：Pickle 不发行任何现实世界资产，也不持有任何现实世界资产。一个名为 AAPL/USD 的价格源，是一个描述那只股票在别处的市场上成交于什么价位的数字，发布在 这条链上，仅此而已。

拿到资产列表

三种方式，而第一种几乎总是对的那一种。它不需要 ABI，不需要地址，也不需要密钥。

# Every feed the chain carries, with its adapter, decimals, answer and age.
curl -s $RPC_URL \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"pickle_prices","params":[]}' \
  | jq '.result.feeds[] | {symbol, feedId, adapter, decimals, price, statusName, staleOnchain}'

# The count alone, when you only want to know whether the catalog changed.
curl -s $RPC_URL \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"pickle_prices","params":[]}' \
  | jq '.result.feeds | length'

$RPC_URL 就是网络参数上的那个接入点。答案里还带着 blockNumber、timestamp，以及注册表点名的 publisher 和 owner：如果你想知道谁本可以写下你刚读到的东西，就去读它们。

33 个价格源

33 个里有 19 个是现实世界资产。在运维上要紧 的是另一种划分：13 个价格源由现货交易所支撑， 而 20 个只来自 Pyth，也就是每一个现实世界价格源， 外加 XMR/USD，那个唯一没有交易所腿的加密资产交易对。

• 5 个交易所 + Pyth。 five spot venues, with a Pyth feed alongside as a cross-check and a stand-in
• 仅 Pyth。 Pyth only - no venue is listed for this feed, so an absent Pyth credential leaves it unpublished

市场这一列：始终开盘，open every day, all day；NYSE 交易时段，09:30-16:00 New York, Monday to Friday, with the exchange holiday list；外汇周，continuous Monday to Friday afternoon New York, closed Saturday, reopening Sunday evening；含每日休市的交易时段，a nearly-continuous session with a daily break and a closed Saturday。这些时间表是市场时段那一节的主题，而处理它们不是可选的。

五种发布策略，不是三十三种

步进上限是最常被读错的那一行。在每一个加密资产价格源上它都是 0，因而是关闭的； 在每一个现实世界价格源上它都是启用的，所以一次一步走得比这个上限更远的现实世界更新，会被合约跳过而不是被写入，除非市场状态在同一次更新里发生了变化。正是那个例外 让一个周末缺口能够落地。

一条价格源记录带着什么

同样这些字段就是这个价格源在链上的配置，所以你从 pickle_prices 或从 feeds(offset, limit) 读到的，就是这条记录加上最新的一轮。今天每一个价格源的 decimals 都是 8，而这个字段允许 0 到 18：请去读它而不是假定它，因为弄错的代价 是一个差了八个数量级的价格。

价格源 id

一个价格源以它符号的哈希为键，不是以一个下标，也不是以一个地址：

bytes32 feedId = keccak256(bytes("ETH/USD"));

The canonical symbol, upper case, with a single slash - keccak256("ETH/USD"), not "ETH-USD" and not "eth/usd". The same 32 bytes key the contract's mappings, name the feed on the RPC, and appear as the indexed topic of every FeedUpdated log. You can compute it offline with any keccak-256 implementation; nothing has to be fetched to know it.

The node and the service both accept ETH/USD, ETH-USD, eth-usd or 0x<64 hex feed id and normalise before looking up, so a URL-safe spelling costs nothing.

解析地址

The price registry and one adapter per feed are predeploys: their addresses are fixed at genesis and canonical for the life of the chain. That is precisely why this reference resolves them instead of printing them.

• pickle_prices answers with the registry's address in core and each feed's adapter in feeds[].adapter, checksummed. That is the shortest path and it needs no ABI.
• pickle_price(feed) carries that feed's adapter; pickle_ethUsdPrice carries the adapter, the registry and, under contract, the adapter again, which is what a Chainlink reader should be pointed at.
• On chain, adapterOf(feedId) returns the deployed adapter and adapterAddress(feedId) recomputes it: the adapter is CREATE2 from the registry with salt = feedId, so its address is a pure function of the registry address and the symbol.
• The first-party applications resolve every address they use at runtime rather than compiling one in - shared-ui/config.js merges the deployment's address files into config.addresses at load.
• The explorer shows that address as an account, with its code and its activity, which is the human-readable cross-check that something is deployed there. It publishes no source and no ABI: the repository is not public yet, and the explorer verifies no contract.

# The registry and one feed's adapter, resolved from the chain itself.
curl -s $RPC_URL \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"pickle_price","params":["ETH-USD"]}' \
  | jq '{adapter: .result.adapter, feedId: .result.feedId}'

# Then prove the address has code before you call it.
curl -s $RPC_URL \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["<adapter>","latest"]}'

Verify a resolved address with an eth_getCode before your first call. A CALL to an account with no code succeeds and returns nothing, so a wrong address does not revert - it reads as a price of zero.