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.
36 lines
1.2 KiB
Solidity
Executable File
36 lines
1.2 KiB
Solidity
Executable File
// SPDX-License-Identifier: MIT
|
|
// OpenZeppelin Contracts (last updated v5.4.0) (interfaces/IERC777Sender.sol)
|
|
|
|
pragma solidity >=0.5.0;
|
|
|
|
/**
|
|
* @dev Interface of the ERC-777 Tokens Sender standard as defined in the ERC.
|
|
*
|
|
* {IERC777} Token holders can be notified of operations performed on their
|
|
* tokens by having a contract implement this interface (contract holders can be
|
|
* their own implementer) and registering it on the
|
|
* https://eips.ethereum.org/EIPS/eip-1820[ERC-1820 global registry].
|
|
*
|
|
* See {IERC1820Registry} and {IERC1820Implementer}.
|
|
*/
|
|
interface IERC777Sender {
|
|
/**
|
|
* @dev Called by an {IERC777} token contract whenever a registered holder's
|
|
* (`from`) tokens are about to be moved or destroyed. The type of operation
|
|
* is conveyed by `to` being the zero address or not.
|
|
*
|
|
* This call occurs _before_ the token contract's state is updated, so
|
|
* {IERC777-balanceOf}, etc., can be used to query the pre-operation state.
|
|
*
|
|
* This function may revert to prevent the operation from being executed.
|
|
*/
|
|
function tokensToSend(
|
|
address operator,
|
|
address from,
|
|
address to,
|
|
uint256 amount,
|
|
bytes calldata userData,
|
|
bytes calldata operatorData
|
|
) external;
|
|
}
|