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.
113 lines
4.7 KiB
Solidity
Executable File
113 lines
4.7 KiB
Solidity
Executable File
// SPDX-License-Identifier: MIT
|
|
// OpenZeppelin Contracts (last updated v5.4.0) (interfaces/IERC1820Registry.sol)
|
|
|
|
pragma solidity >=0.5.0;
|
|
|
|
/**
|
|
* @dev Interface of the global ERC-1820 Registry, as defined in the
|
|
* https://eips.ethereum.org/EIPS/eip-1820[ERC]. Accounts may register
|
|
* implementers for interfaces in this registry, as well as query support.
|
|
*
|
|
* Implementers may be shared by multiple accounts, and can also implement more
|
|
* than a single interface for each account. Contracts can implement interfaces
|
|
* for themselves, but externally-owned accounts (EOA) must delegate this to a
|
|
* contract.
|
|
*
|
|
* {IERC165} interfaces can also be queried via the registry.
|
|
*
|
|
* For an in-depth explanation and source code analysis, see the ERC text.
|
|
*/
|
|
interface IERC1820Registry {
|
|
event InterfaceImplementerSet(address indexed account, bytes32 indexed interfaceHash, address indexed implementer);
|
|
|
|
event ManagerChanged(address indexed account, address indexed newManager);
|
|
|
|
/**
|
|
* @dev Sets `newManager` as the manager for `account`. A manager of an
|
|
* account is able to set interface implementers for it.
|
|
*
|
|
* By default, each account is its own manager. Passing a value of `0x0` in
|
|
* `newManager` will reset the manager to this initial state.
|
|
*
|
|
* Emits a {ManagerChanged} event.
|
|
*
|
|
* Requirements:
|
|
*
|
|
* - the caller must be the current manager for `account`.
|
|
*/
|
|
function setManager(address account, address newManager) external;
|
|
|
|
/**
|
|
* @dev Returns the manager for `account`.
|
|
*
|
|
* See {setManager}.
|
|
*/
|
|
function getManager(address account) external view returns (address);
|
|
|
|
/**
|
|
* @dev Sets the `implementer` contract as ``account``'s implementer for
|
|
* `interfaceHash`.
|
|
*
|
|
* `account` being the zero address is an alias for the caller's address.
|
|
* The zero address can also be used in `implementer` to remove an old one.
|
|
*
|
|
* See {interfaceHash} to learn how these are created.
|
|
*
|
|
* Emits an {InterfaceImplementerSet} event.
|
|
*
|
|
* Requirements:
|
|
*
|
|
* - the caller must be the current manager for `account`.
|
|
* - `interfaceHash` must not be an {IERC165} interface id (i.e. it must not
|
|
* end in 28 zeroes).
|
|
* - `implementer` must implement {IERC1820Implementer} and return true when
|
|
* queried for support, unless `implementer` is the caller. See
|
|
* {IERC1820Implementer-canImplementInterfaceForAddress}.
|
|
*/
|
|
function setInterfaceImplementer(address account, bytes32 _interfaceHash, address implementer) external;
|
|
|
|
/**
|
|
* @dev Returns the implementer of `interfaceHash` for `account`. If no such
|
|
* implementer is registered, returns the zero address.
|
|
*
|
|
* If `interfaceHash` is an {IERC165} interface id (i.e. it ends with 28
|
|
* zeroes), `account` will be queried for support of it.
|
|
*
|
|
* `account` being the zero address is an alias for the caller's address.
|
|
*/
|
|
function getInterfaceImplementer(address account, bytes32 _interfaceHash) external view returns (address);
|
|
|
|
/**
|
|
* @dev Returns the interface hash for an `interfaceName`, as defined in the
|
|
* corresponding
|
|
* https://eips.ethereum.org/EIPS/eip-1820#interface-name[section of the ERC].
|
|
*/
|
|
function interfaceHash(string calldata interfaceName) external pure returns (bytes32);
|
|
|
|
/**
|
|
* @notice Updates the cache with whether the contract implements an ERC-165 interface or not.
|
|
* @param account Address of the contract for which to update the cache.
|
|
* @param interfaceId ERC-165 interface for which to update the cache.
|
|
*/
|
|
function updateERC165Cache(address account, bytes4 interfaceId) external;
|
|
|
|
/**
|
|
* @notice Checks whether a contract implements an ERC-165 interface or not.
|
|
* If the result is not cached a direct lookup on the contract address is performed.
|
|
* If the result is not cached or the cached value is out-of-date, the cache MUST be updated manually by calling
|
|
* {updateERC165Cache} with the contract address.
|
|
* @param account Address of the contract to check.
|
|
* @param interfaceId ERC-165 interface to check.
|
|
* @return True if `account` implements `interfaceId`, false otherwise.
|
|
*/
|
|
function implementsERC165Interface(address account, bytes4 interfaceId) external view returns (bool);
|
|
|
|
/**
|
|
* @notice Checks whether a contract implements an ERC-165 interface or not without using or updating the cache.
|
|
* @param account Address of the contract to check.
|
|
* @param interfaceId ERC-165 interface to check.
|
|
* @return True if `account` implements `interfaceId`, false otherwise.
|
|
*/
|
|
function implementsERC165InterfaceNoCache(address account, bytes4 interfaceId) external view returns (bool);
|
|
}
|