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.
58 lines
1.7 KiB
TypeScript
Executable File
58 lines
1.7 KiB
TypeScript
Executable File
/**
|
|
* Addresses are a fundamental part of interacting with Ethereum. They
|
|
* represent the global identity of Externally Owned Accounts (accounts
|
|
* backed by a private key) and contracts.
|
|
*
|
|
* The Ethereum Naming Service (ENS) provides an interconnected ecosystem
|
|
* of contracts, standards and libraries which enable looking up an
|
|
* address for an ENS name.
|
|
*
|
|
* These functions help convert between various formats, validate
|
|
* addresses and safely resolve ENS names.
|
|
*
|
|
* @_section: api/address:Addresses [about-addresses]
|
|
*/
|
|
|
|
null;
|
|
|
|
/**
|
|
* An interface for objects which have an address, and can
|
|
* resolve it asyncronously.
|
|
*
|
|
* This allows objects such as [[Signer]] or [[Contract]] to
|
|
* be used most places an address can be, for example getting
|
|
* the [balance](Provider-getBalance).
|
|
*/
|
|
export interface Addressable {
|
|
/**
|
|
* Get the object address.
|
|
*/
|
|
getAddress(): Promise<string>;
|
|
}
|
|
|
|
/**
|
|
* Anything that can be used to return or resolve an address.
|
|
*/
|
|
export type AddressLike = string | Promise<string> | Addressable;
|
|
|
|
/**
|
|
* An interface for any object which can resolve an ENS name.
|
|
*/
|
|
export interface NameResolver {
|
|
/**
|
|
* Resolve to the address for the ENS %%name%%.
|
|
*
|
|
* Resolves to ``null`` if the name is unconfigued. Use
|
|
* [[resolveAddress]] (passing this object as %%resolver%%) to
|
|
* throw for names that are unconfigured.
|
|
*/
|
|
resolveName(name: string): Promise<null | string>;
|
|
}
|
|
|
|
export { getAddress, getIcapAddress } from "./address.js";
|
|
|
|
export { getCreateAddress, getCreate2Address } from "./contract-address.js";
|
|
|
|
|
|
export { isAddressable, isAddress, resolveAddress } from "./checks.js";
|