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.
99 lines
3.3 KiB
Solidity
Executable File
99 lines
3.3 KiB
Solidity
Executable File
// SPDX-License-Identifier: MIT
|
|
// OpenZeppelin Contracts (last updated v5.4.0) (access/IAccessControl.sol)
|
|
|
|
pragma solidity >=0.8.4;
|
|
|
|
/**
|
|
* @dev External interface of AccessControl declared to support ERC-165 detection.
|
|
*/
|
|
interface IAccessControl {
|
|
/**
|
|
* @dev The `account` is missing a role.
|
|
*/
|
|
error AccessControlUnauthorizedAccount(address account, bytes32 neededRole);
|
|
|
|
/**
|
|
* @dev The caller of a function is not the expected one.
|
|
*
|
|
* NOTE: Don't confuse with {AccessControlUnauthorizedAccount}.
|
|
*/
|
|
error AccessControlBadConfirmation();
|
|
|
|
/**
|
|
* @dev Emitted when `newAdminRole` is set as ``role``'s admin role, replacing `previousAdminRole`
|
|
*
|
|
* `DEFAULT_ADMIN_ROLE` is the starting admin for all roles, despite
|
|
* {RoleAdminChanged} not being emitted to signal this.
|
|
*/
|
|
event RoleAdminChanged(bytes32 indexed role, bytes32 indexed previousAdminRole, bytes32 indexed newAdminRole);
|
|
|
|
/**
|
|
* @dev Emitted when `account` is granted `role`.
|
|
*
|
|
* `sender` is the account that originated the contract call. This account bears the admin role (for the granted role).
|
|
* Expected in cases where the role was granted using the internal {AccessControl-_grantRole}.
|
|
*/
|
|
event RoleGranted(bytes32 indexed role, address indexed account, address indexed sender);
|
|
|
|
/**
|
|
* @dev Emitted when `account` is revoked `role`.
|
|
*
|
|
* `sender` is the account that originated the contract call:
|
|
* - if using `revokeRole`, it is the admin role bearer
|
|
* - if using `renounceRole`, it is the role bearer (i.e. `account`)
|
|
*/
|
|
event RoleRevoked(bytes32 indexed role, address indexed account, address indexed sender);
|
|
|
|
/**
|
|
* @dev Returns `true` if `account` has been granted `role`.
|
|
*/
|
|
function hasRole(bytes32 role, address account) external view returns (bool);
|
|
|
|
/**
|
|
* @dev Returns the admin role that controls `role`. See {grantRole} and
|
|
* {revokeRole}.
|
|
*
|
|
* To change a role's admin, use {AccessControl-_setRoleAdmin}.
|
|
*/
|
|
function getRoleAdmin(bytes32 role) external view returns (bytes32);
|
|
|
|
/**
|
|
* @dev Grants `role` to `account`.
|
|
*
|
|
* If `account` had not been already granted `role`, emits a {RoleGranted}
|
|
* event.
|
|
*
|
|
* Requirements:
|
|
*
|
|
* - the caller must have ``role``'s admin role.
|
|
*/
|
|
function grantRole(bytes32 role, address account) external;
|
|
|
|
/**
|
|
* @dev Revokes `role` from `account`.
|
|
*
|
|
* If `account` had been granted `role`, emits a {RoleRevoked} event.
|
|
*
|
|
* Requirements:
|
|
*
|
|
* - the caller must have ``role``'s admin role.
|
|
*/
|
|
function revokeRole(bytes32 role, address account) external;
|
|
|
|
/**
|
|
* @dev Revokes `role` from the calling account.
|
|
*
|
|
* Roles are often managed via {grantRole} and {revokeRole}: this function's
|
|
* purpose is to provide a mechanism for accounts to lose their privileges
|
|
* if they are compromised (such as when a trusted device is misplaced).
|
|
*
|
|
* If the calling account had been granted `role`, emits a {RoleRevoked}
|
|
* event.
|
|
*
|
|
* Requirements:
|
|
*
|
|
* - the caller must be `callerConfirmation`.
|
|
*/
|
|
function renounceRole(bytes32 role, address callerConfirmation) external;
|
|
}
|