面向开发者 / 从这里开始
网络参数
那些常量,每个主题一张表。
身份
| 参数 | Value |
|---|---|
| Chain name | Pickle Chainthe brand, the chain, the token and the name service all say Pickle |
| Network | Pickle Chain Testnetthe network this reference documents. Its state may be reset without notice, and test ETH and test PKL have no monetary value |
| Chain ID | 782700x131be - a compile-time constant, enforced on every transaction: an envelope signed for another chain is rejected at admission. The whitepaper's 78271 is the mainnet figure |
| JSON-RPC over HTTPS | https://rpc.picklechain.xyzno key, no account, no header beyond a content type |
| JSON-RPC over WebSocket | wss://rpc.picklechain.xyz/ws/the /ws path is required; an upgrade at the bare origin answers 405. Both /ws and /ws/ work. eth_subscribe, pickle_subscribe and ordinary calls; see Subscriptions |
| Explorer | https://explorer.picklechain.xyzthe archive the node is not: every block, receipt, log and account, kept past the node's own window |
| Faucet | https://faucet.picklechain.xyztest ETH and test PKL against a pasted address, one claim per address every 24 hours |
| MCP server | https://mcp.picklechain.xyz/mcpfor AI agents: streamable HTTP, read-only, no key; see AI agents (MCP) |
| Gas token | ETHpermanently. PKL is never required to transact |
| Currency decimals | 18 |
chain ID 是一个编译期常量,并且在每一笔交易上都会被检查:为另一条链签名的信封会在准入处 以 chain id 被拒绝,而不是先被接受再被丢弃。
节律
这些是调度目标,不是保证
下面两个数字都是区块生产者力求达到的间隔。它们都不是延迟保证,也都不是吞吐量数字:封存者 会跳过一个迟到的节拍而不是追赶,所以一个目标描述的是节律,而不是一个承诺。本文档不发布任何 吞吐量数字。
| 阶段 | 目标 |
|---|---|
| Mini-block | ~10 ms scheduling targeta signed batch of transactions and receipts, constituting a preconfirmation. Sealed by a dedicated OS thread that skips a late tick rather than catching up. MINIBLOCK_MS |
| EVM block | ~250 ms scheduling targetan Ethereum-shaped block wrapping the mini-blocks of the interval, constituting a confirmation for wallets and explorers. EVM_BLOCK_MS, which refuses any value below 50 |
| Execution | immediateeth_sendRawTransaction blocks until the transaction has executed; it does not merely enqueue. The seals above are when the result becomes visible as a preconfirmation and then as a confirmation |
| Finality | after L1 settlementa block is final when the data needed to re-derive it has been committed to Ethereum and that commitment is itself final. One commitment per 60 s scheduling target |
执行与 gas
| 参数 | Value |
|---|---|
| Execution hardfork | Cancunpinned as revm SpecId::CANCUN, not operator-tunable - a revm upgrade cannot silently re-price gas under an already-settled chain |
| Block gas limit | 30,000,000also the per-transaction ceiling: a transaction that cannot fit a block is rejected at admission |
| Base fee | 0the EVM runs with basefee 0 and blocks report baseFeePerGas 0x0; fees are still charged through gasPrice |
| eth_gasPrice | 1 wei0x1 |
| Minimum accepted gas price | 1 weiMIN_GAS_PRICE, a consensus constant. Deliberately not an environment variable: an operator-tunable minimum would let a replica re-price a transaction the leader accepted, and derivation would halt |
| Fee beneficiary in revm | address(0)then re-split by the sequencer in the same transaction; blocks report the fee treasury as miner |
其中两个值是编译期常量而不是环境变量,这是一项正确性要求:一个可调的最低 gas 价格、或者一个 可调的硬分叉,都会让副本节点拒绝或重新定价一笔主导节点已经接受的交易,而推导会在这个分歧上 停机。把 Cancun 钉死也意味着一次 revm 升级不能在一条已经结算过的链底下悄悄改变 gas 记账。
gas 永久地以 ETH 支付。交易从不需要 PKL:PKL 是什么、不是什么,见术语表。
节点保留什么
| 数据 | 保留 |
|---|---|
| EVM block history | ~2 minuteskeep_evm_blocks() = 120,000 / EVM_BLOCK_MS - 480 blocks at the default. Older blocks return null and their logs become unqueryable |
| Mini-block history | 20,000KEEP_MINI_BLOCKS, roughly 200 seconds at the 10 ms scheduling target |
| Receipts and bodies | 200,000MAX_RECEIPTS, evicted first-in-first-out |
| Full history | not on the nodeit lives in Postgres behind the explorer, fed by the sequencer's spool. This RPC is an index, not an archive |
对任何要写索引器的人来说,这是全站后果最重的一张表,而且它有自己的一页,把各种失败模式都写清楚了。简短版是:节点是一个 RPC 索引,不是归档,而一个假定相反情况的查询模式会悄悄丢数据,而不是报错。
合约地址
解析一个地址,永远不要猜一个
本页不发布任何合约地址。对你在别处找到的任何地址都要小心:一次指向无代码账户的 EVM CALL 会成功,所以一笔被路由到什么都没部署的地址上的兑换不会 revert,它会拿走你的 ETH 并报告成功。这是这条链上唯一一个代价是钱而不是时间的错误。
第一方前端不会把地址编译进去,而是在运行时从链上解析它们需要的地址。浏览器展示一个地址上 部署了什么,但它不验证任何源码,也不发布 ABI;仓库会随着测试网逐步开放。