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.
48 lines
1.3 KiB
TypeScript
Executable File
48 lines
1.3 KiB
TypeScript
Executable File
/**
|
|
* When interacting with Ethereum, it is necessary to use a private
|
|
* key authenticate actions by signing a payload.
|
|
*
|
|
* Wallets are the simplest way to expose the concept of an
|
|
* //Externally Owner Account// (EOA) as it wraps a private key
|
|
* and supports high-level methods to sign common types of interaction
|
|
* and send transactions.
|
|
*
|
|
* The class most developers will want to use is [[Wallet]], which
|
|
* can load a private key directly or from any common wallet format.
|
|
*
|
|
* The [[HDNodeWallet]] can be used when it is necessary to access
|
|
* low-level details of how an HD wallets are derived, exported
|
|
* or imported.
|
|
*
|
|
* @_section: api/wallet:Wallets [about-wallets]
|
|
*/
|
|
|
|
export { BaseWallet } from "./base-wallet.js";
|
|
|
|
export {
|
|
defaultPath,
|
|
|
|
getAccountPath, getIndexedAccountPath,
|
|
|
|
HDNodeWallet,
|
|
HDNodeVoidWallet,
|
|
} from "./hdwallet.js";
|
|
|
|
export { isCrowdsaleJson, decryptCrowdsaleJson } from "./json-crowdsale.js";
|
|
|
|
export {
|
|
isKeystoreJson,
|
|
decryptKeystoreJsonSync, decryptKeystoreJson,
|
|
encryptKeystoreJson, encryptKeystoreJsonSync
|
|
} from "./json-keystore.js";
|
|
|
|
export { Mnemonic } from "./mnemonic.js";
|
|
|
|
export { Wallet } from "./wallet.js";
|
|
|
|
|
|
export type { CrowdsaleAccount } from "./json-crowdsale.js";
|
|
export type {
|
|
KeystoreAccount, EncryptOptions
|
|
} from "./json-keystore.js"
|