aitbc
816e258d4c
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.
50 lines
1.8 KiB
TypeScript
Executable File
50 lines
1.8 KiB
TypeScript
Executable File
/**
|
|
* There are many awesome community services that provide Ethereum
|
|
* nodes both for developers just starting out and for large-scale
|
|
* communities.
|
|
*
|
|
* @_section: api/providers/thirdparty: Community Providers [thirdparty]
|
|
*/
|
|
|
|
/**
|
|
* Providers which offer community credentials should extend this
|
|
* to notify any interested consumers whether community credentials
|
|
* are in-use.
|
|
*/
|
|
export interface CommunityResourcable {
|
|
/**
|
|
* Returns true if the instance is connected using the community
|
|
* credentials.
|
|
*/
|
|
isCommunityResource(): boolean;
|
|
}
|
|
|
|
// Show the throttle message only once per service
|
|
const shown: Set<string> = new Set();
|
|
|
|
/**
|
|
* Displays a warning in the console when the community resource is
|
|
* being used too heavily by the app, recommending the developer
|
|
* acquire their own credentials instead of using the community
|
|
* credentials.
|
|
*
|
|
* The notification will only occur once per service.
|
|
*/
|
|
export function showThrottleMessage(service: string): void {
|
|
if (shown.has(service)) { return; }
|
|
shown.add(service);
|
|
|
|
console.log("========= NOTICE =========")
|
|
console.log(`Request-Rate Exceeded for ${ service } (this message will not be repeated)`);
|
|
console.log("");
|
|
console.log("The default API keys for each service are provided as a highly-throttled,");
|
|
console.log("community resource for low-traffic projects and early prototyping.");
|
|
console.log("");
|
|
console.log("While your application will continue to function, we highly recommended");
|
|
console.log("signing up for your own API keys to improve performance, increase your");
|
|
console.log("request rate/limit and enable other perks, such as metrics and advanced APIs.");
|
|
console.log("");
|
|
console.log("For more details: https:/\/docs.ethers.org/api-keys/");
|
|
console.log("==========================");
|
|
}
|