refactor: move brother_node development artifact to dev/test-nodes subdirectory
Development Artifact Cleanup: ✅ BROTHER_NODE REORGANIZATION: Moved development test node to appropriate location - dev/test-nodes/brother_node/: Moved from root directory for better organization - Contains development configuration, test logs, and test chain data - No impact on production systems - purely development/testing artifact ✅ DEVELOPMENT ARTIFACTS IDENTIFIED: - Chain ID: aitbc-brother-chain (test/development chain) - Ports: 8010 (P2P) and 8011 (RPC) - different from production - Environment: .env file with test configuration - Logs: rpc.log and node.log from development testing session (March 15, 2026) ✅ ROOT DIRECTORY CLEANUP: Removed development clutter from production directory - brother_node/ moved to dev/test-nodes/brother_node/ - Root directory now contains only production-ready components - Development artifacts properly organized in dev/ subdirectory DIRECTORY STRUCTURE IMPROVEMENT: 📁 dev/test-nodes/: Development and testing node configurations 🏗️ Root Directory: Clean production structure with only essential components 🧪 Development Isolation: Test environments separated from production BENEFITS: ✅ Clean Production Directory: No development artifacts in root ✅ Better Organization: Development nodes grouped in dev/ subdirectory ✅ Clear Separation: Production vs development environments clearly distinguished ✅ Maintainability: Easier to identify and manage development components RESULT: Successfully moved brother_node development artifact to dev/test-nodes/ subdirectory, cleaning up the root directory while preserving development testing environment for future use.
This commit is contained in:
49
dev/env/node_modules/ethers/lib.commonjs/providers/default-provider.d.ts
generated
vendored
Executable file
49
dev/env/node_modules/ethers/lib.commonjs/providers/default-provider.d.ts
generated
vendored
Executable file
@@ -0,0 +1,49 @@
|
||||
import type { AbstractProvider } from "./abstract-provider.js";
|
||||
import type { Networkish } from "./network.js";
|
||||
import { WebSocketLike } from "./provider-websocket.js";
|
||||
/**
|
||||
* Returns a default provider for %%network%%.
|
||||
*
|
||||
* If %%network%% is a [[WebSocketLike]] or string that begins with
|
||||
* ``"ws:"`` or ``"wss:"``, a [[WebSocketProvider]] is returned backed
|
||||
* by that WebSocket or URL.
|
||||
*
|
||||
* If %%network%% is a string that begins with ``"HTTP:"`` or ``"HTTPS:"``,
|
||||
* a [[JsonRpcProvider]] is returned connected to that URL.
|
||||
*
|
||||
* Otherwise, a default provider is created backed by well-known public
|
||||
* Web3 backends (such as [[link-infura]]) using community-provided API
|
||||
* keys.
|
||||
*
|
||||
* The %%options%% allows specifying custom API keys per backend (setting
|
||||
* an API key to ``"-"`` will omit that provider) and ``options.exclusive``
|
||||
* can be set to either a backend name or and array of backend names, which
|
||||
* will whitelist **only** those backends.
|
||||
*
|
||||
* Current backend strings supported are:
|
||||
* - ``"alchemy"``
|
||||
* - ``"ankr"``
|
||||
* - ``"cloudflare"``
|
||||
* - ``"chainstack"``
|
||||
* - ``"etherscan"``
|
||||
* - ``"infura"``
|
||||
* - ``"publicPolygon"``
|
||||
* - ``"quicknode"``
|
||||
*
|
||||
* @example:
|
||||
* // Connect to a local Geth node
|
||||
* provider = getDefaultProvider("http://localhost:8545/");
|
||||
*
|
||||
* // Connect to Ethereum mainnet with any current and future
|
||||
* // third-party services available
|
||||
* provider = getDefaultProvider("mainnet");
|
||||
*
|
||||
* // Connect to Polygon, but only allow Etherscan and
|
||||
* // INFURA and use "MY_API_KEY" in calls to Etherscan.
|
||||
* provider = getDefaultProvider("matic", {
|
||||
* etherscan: "MY_API_KEY",
|
||||
* exclusive: [ "etherscan", "infura" ]
|
||||
* });
|
||||
*/
|
||||
export declare function getDefaultProvider(network?: string | Networkish | WebSocketLike, options?: any): AbstractProvider;
|
||||
//# sourceMappingURL=default-provider.d.ts.map
|
||||
Reference in New Issue
Block a user