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.
38 lines
1.5 KiB
TypeScript
Executable File
38 lines
1.5 KiB
TypeScript
Executable File
import { AbstractSigner } from "./abstract-signer.js";
|
|
import type { TypedDataDomain, TypedDataField } from "../hash/index.js";
|
|
import type { BlockTag, Provider, TransactionRequest, TransactionResponse } from "./provider.js";
|
|
import type { Signer } from "./signer.js";
|
|
/**
|
|
* A **NonceManager** wraps another [[Signer]] and automatically manages
|
|
* the nonce, ensuring serialized and sequential nonces are used during
|
|
* transaction.
|
|
*/
|
|
export declare class NonceManager extends AbstractSigner {
|
|
#private;
|
|
/**
|
|
* The Signer being managed.
|
|
*/
|
|
signer: Signer;
|
|
/**
|
|
* Creates a new **NonceManager** to manage %%signer%%.
|
|
*/
|
|
constructor(signer: Signer);
|
|
getAddress(): Promise<string>;
|
|
connect(provider: null | Provider): NonceManager;
|
|
getNonce(blockTag?: BlockTag): Promise<number>;
|
|
/**
|
|
* Manually increment the nonce. This may be useful when managng
|
|
* offline transactions.
|
|
*/
|
|
increment(): void;
|
|
/**
|
|
* Resets the nonce, causing the **NonceManager** to reload the current
|
|
* nonce from the blockchain on the next transaction.
|
|
*/
|
|
reset(): void;
|
|
sendTransaction(tx: TransactionRequest): Promise<TransactionResponse>;
|
|
signTransaction(tx: TransactionRequest): Promise<string>;
|
|
signMessage(message: string | Uint8Array): Promise<string>;
|
|
signTypedData(domain: TypedDataDomain, types: Record<string, Array<TypedDataField>>, value: Record<string, any>): Promise<string>;
|
|
}
|
|
//# sourceMappingURL=signer-noncemanager.d.ts.map
|