@forgezero/providers 0.1.23 → 0.1.24

package/dist/chain.d.ts

@@ -1,99 +0,0 @@
-/**
- * A blockchain node, behind the same failover every other service gets.
- *
- * Reading a chain is a PROVIDER problem, not a runtime one, and the distinction
- * is not bookkeeping. A node needs a credential, it rate-limits, it goes down,
- * and the answer when it does is to ask a different one — which is precisely
- * what the registry already does for email and storage. Deriving an address
- * needs none of that and lives in `runtime/finance/custody`.
- *
- * ## Why several nodes is the normal case, not a luxury
- *
- * Public RPC endpoints are rate-limited and unreliable, and paid ones have
- * outages like anything else. A deposit scanner that stops when one endpoint is
- * down stops CREDITING DEPOSITS, and the user's money is on the chain the whole
- * time. Priority and health belong here so a scanner never has to know which
- * node answered.
- *
- * ## The classification is the load-bearing part
- *
- *   terminal   our request is malformed, or the chain rejected the transaction
- *              on its merits. Every node will say the same thing, and asking
- *              three of them buries the real reason under two duplicates.
- *   backoff    rate limited. The node is healthy and we are asking too fast;
- *              striking it would punish the one that is working.
- *   retryable  this node is behind, broken, or its key is bad. The next may
- *              be fine.
- *
- * "Already known" and "nonce too low" are the interesting cases. Both mean the
- * transaction is ALREADY IN FLIGHT, so they are terminal rather than retryable:
- * rebroadcasting through another node cannot help, and treating them as failure
- * is how a sweep gets sent twice.
- */
-export type ChainCall = {
-    op: 'head';
-} | {
-    op: 'balance';
-    address: string;
-    block?: string;
-} | {
-    op: 'call';
-    to: string;
-    data: string;
-    block?: string;
-} | {
-    op: 'logs';
-    fromBlock: number;
-    toBlock: number;
-    address?: string;
-    topics?: (string | string[] | null)[];
-} | {
-    op: 'nonce';
-    address: string;
-    block?: 'pending' | 'latest';
-} | {
-    op: 'send';
-    raw: string;
-} | {
-    op: 'receipt';
-    hash: string;
-};
-export interface ChainLog {
-    transactionHash: string;
-    logIndex: number;
-    blockNumber: number;
-    address: string;
-    topics: string[];
-    data: string;
-}
-export interface ChainReceipt {
-    hash: string;
-    blockNumber: number;
-    /** True only when the chain executed it successfully. */
-    success: boolean;
-}
-export type ChainResult = {
-    op: 'head';
-    block: number;
-} | {
-    op: 'balance';
-    wei: bigint;
-} | {
-    op: 'call';
-    data: string;
-} | {
-    op: 'logs';
-    logs: ChainLog[];
-} | {
-    op: 'nonce';
-    nonce: bigint;
-} | {
-    op: 'send';
-    hash: string;
-}
-/** `null` when the transaction has not mined yet — not an error. */
- | {
-    op: 'receipt';
-    receipt: ChainReceipt | null;
-};
-export declare const evmRpc: import("./index").ProviderDefinition<Record<"request", import("./index").ProviderMethodSpec<ChainCall, ChainResult>>>;