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:
89
dev/env/node_modules/ethers/lib.esm/wallet/json-keystore.d.ts
generated
vendored
Executable file
89
dev/env/node_modules/ethers/lib.esm/wallet/json-keystore.d.ts
generated
vendored
Executable file
@@ -0,0 +1,89 @@
|
||||
/**
|
||||
* The JSON Wallet formats allow a simple way to store the private
|
||||
* keys needed in Ethereum along with related information and allows
|
||||
* for extensible forms of encryption.
|
||||
*
|
||||
* These utilities facilitate decrypting and encrypting the most common
|
||||
* JSON Wallet formats.
|
||||
*
|
||||
* @_subsection: api/wallet:JSON Wallets [json-wallets]
|
||||
*/
|
||||
import type { ProgressCallback } from "../crypto/index.js";
|
||||
import type { BytesLike } from "../utils/index.js";
|
||||
/**
|
||||
* The contents of a JSON Keystore Wallet.
|
||||
*/
|
||||
export type KeystoreAccount = {
|
||||
address: string;
|
||||
privateKey: string;
|
||||
mnemonic?: {
|
||||
path?: string;
|
||||
locale?: string;
|
||||
entropy: string;
|
||||
};
|
||||
};
|
||||
/**
|
||||
* The parameters to use when encrypting a JSON Keystore Wallet.
|
||||
*/
|
||||
export type EncryptOptions = {
|
||||
progressCallback?: ProgressCallback;
|
||||
iv?: BytesLike;
|
||||
entropy?: BytesLike;
|
||||
client?: string;
|
||||
salt?: BytesLike;
|
||||
uuid?: string;
|
||||
scrypt?: {
|
||||
N?: number;
|
||||
r?: number;
|
||||
p?: number;
|
||||
};
|
||||
};
|
||||
/**
|
||||
* Returns true if %%json%% is a valid JSON Keystore Wallet.
|
||||
*/
|
||||
export declare function isKeystoreJson(json: string): boolean;
|
||||
/**
|
||||
* Returns the account details for the JSON Keystore Wallet %%json%%
|
||||
* using %%password%%.
|
||||
*
|
||||
* It is preferred to use the [async version](decryptKeystoreJson)
|
||||
* instead, which allows a [[ProgressCallback]] to keep the user informed
|
||||
* as to the decryption status.
|
||||
*
|
||||
* This method will block the event loop (freezing all UI) until decryption
|
||||
* is complete, which can take quite some time, depending on the wallet
|
||||
* paramters and platform.
|
||||
*/
|
||||
export declare function decryptKeystoreJsonSync(json: string, _password: string | Uint8Array): KeystoreAccount;
|
||||
/**
|
||||
* Resolves to the decrypted JSON Keystore Wallet %%json%% using the
|
||||
* %%password%%.
|
||||
*
|
||||
* If provided, %%progress%% will be called periodically during the
|
||||
* decrpytion to provide feedback, and if the function returns
|
||||
* ``false`` will halt decryption.
|
||||
*
|
||||
* The %%progressCallback%% will **always** receive ``0`` before
|
||||
* decryption begins and ``1`` when complete.
|
||||
*/
|
||||
export declare function decryptKeystoreJson(json: string, _password: string | Uint8Array, progress?: ProgressCallback): Promise<KeystoreAccount>;
|
||||
/**
|
||||
* Return the JSON Keystore Wallet for %%account%% encrypted with
|
||||
* %%password%%.
|
||||
*
|
||||
* The %%options%% can be used to tune the password-based key
|
||||
* derivation function parameters, explicitly set the random values
|
||||
* used. Any provided [[ProgressCallback]] is ignord.
|
||||
*/
|
||||
export declare function encryptKeystoreJsonSync(account: KeystoreAccount, password: string | Uint8Array, options?: EncryptOptions): string;
|
||||
/**
|
||||
* Resolved to the JSON Keystore Wallet for %%account%% encrypted
|
||||
* with %%password%%.
|
||||
*
|
||||
* The %%options%% can be used to tune the password-based key
|
||||
* derivation function parameters, explicitly set the random values
|
||||
* used and provide a [[ProgressCallback]] to receive periodic updates
|
||||
* on the completion status..
|
||||
*/
|
||||
export declare function encryptKeystoreJson(account: KeystoreAccount, password: string | Uint8Array, options?: EncryptOptions): Promise<string>;
|
||||
//# sourceMappingURL=json-keystore.d.ts.map
|
||||
Reference in New Issue
Block a user