You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bridge RPC readers, primary receipt refused by PublicNode. PublicNode changed the text of its keyless historical-read refusal to Archive requests require a personal token. Get one at: https://www.allnodes.com/publicnode, and APN matched only the earlier text. A refused primary receipt on Base or Ethereum therefore stopped falling back to the configured APN_<CHAIN>_ARCHIVE_RPC_URL, and APN had never recognized the refusal on BSC or Arbitrum. QA's resume of a BSC operation hit this and needed a separate APN_BNB_RECEIPT_RPC_URL. APN now accepts both texts exactly from the keyless Ethereum, Base, BSC and Arbitrum roots. In a batch the receipt fails as a sub-error and APN reads it again on its own, so a receipt after either refusal now reaches the archive. Any other text or origin still fails without a fallback.
Bridge RPC readers, status hint. When an unresolved bridge operation stores an RPC refusal as its observation_rpc_failure (an HTTP status, or a history the endpoint does not serve), its status, bridge approve and operation resume output get one more next_actions entry. The entry names the refusing endpoint role, the method and the status, plus the one variable to set. A refusal on the receipt route names the chain's receipt reader: the receipt reader itself, a receipt read, or an archive batch, which is how keyless Tatum's 402 shows up. Any other archive read, or a trace or native-fill balance the primary refused, names the archive. Anything else names the primary RPC. A proof that needed a missing archive names the archive. Receipts keep the plain next actions, so receipts stored by earlier versions still verify.
Docs: which reader reads in JSON-RPC batches. On 2026-11-08 the keyless Tatum gateway refused batches with HTTP 402, which is what QA saw; it can serve as an archive only beside a receipt reader that accepts batches. The docs also list when a primary receipt falls back, and how daily caps count holds whose outcome is unproved: per UTC day, including what abandonment does to them in each family.