ERC-20 tools
Explore 20lab ERC-20 Tools
Simplify ERC-20 token management with our powerful tools.ERC-20 Tools
Accept ownership
Blockchain
Token address
No pending owner functionality found in this token.
Related Posts
Continue your journey with these related blog posts.
Discover how Avalanche crypto tokens provide a fast, secure and scalable environment using the underlying blockchain technology.
July 21, 2024
7 min read
Learn how to create Arbitrum tokens to leverage faster, more scalable transactions on layer 2 blockchain.
July 20, 2024
7 min read
Learn how to add liquidity to QuickSwap and launch your ERC-20 token. Step-by-step instructions for creating a trading pair and providing initial liquidity on Polygon.
January 31, 2025
8 min read
Learn what ERC-20 is and how it is standardizing tokens for cross-platform and cross-blockchain compatibility.
November 11, 2024
5 min read
The Core accept ownership tool is used in combination with the transfer ownership tool to complete secure Core token ownership transitions. This tool is only necessary for tokens that implement the two-step ownership transfer process and allows the pending owner to accept ownership and finish the transition process.
This tool is essential for completing two-step ownership transfer processes, ensuring intended recipients actually control the destination address, preventing accidental ownership transfers to wrong addresses, and maintaining security in ownership transition workflows.
The two-step ownership transfer process provides enhanced security through a confirm-and-accept mechanism:
- Step 1: Ownership Transfer Initiation - Current owner uses Core transfer ownership tool to propose a new owner address
- Pending State - Ownership transfer remains pending until accepted
- Step 2: Acceptance - Proposed owner uses Core accept ownership tool to actively accept ownership
- Completion - Ownership transfer is finalized only after acceptance
This process prevents accidental transfers to wrong addresses and ensures the new owner can actually access and control the designated address before ownership is transferred.
Only the specifically designated recipient address can accept a pending ownership transfer. This must be the exact address specified in the transfer proposal. It cannot be accepted by any other address, even the current owner, though multi-signature wallets can accept if they were the designated recipient.
This strict address matching ensures that ownership can only be claimed by the intended recipient, preventing unauthorized ownership claims or hijacking attempts.
When a proposed ownership transfer is not accepted, several scenarios may occur:
- Pending State Continues - The transfer remains pending indefinitely until accepted
- Current Owner Retains Control - All administrative functions remain with the original owner
The original owner maintains full control until the transfer is completed, ensuring continuity of operations during the transition period.
Yes, you can verify pending ownership transfers through multiple methods. The 20lab Core accept ownership tool interface shows pending transfer status for connected wallets. Core block explorers display contract state including pending owners. You can also use direct contract interaction to read the 'pendingOwner' function, and transaction history will show the initial transfer proposal.
If you're the designated recipient, the tool will clearly indicate that you have a pending ownership transfer waiting for acceptance.
Time limits for accepting ownership depend on the specific token implementation:
- Standard Implementations - Most have no time limit, pending transfers last indefinitely
- Custom Timeouts - Some contracts implement expiration mechanisms
- Manual Cancellation - Current owners may be able to cancel pending transfers
- Best Practices - Accept promptly to avoid operational delays
While many implementations allow indefinite pending periods, it's recommended to use Core accept ownership tool to accept ownership transfers promptly to complete the transition and avoid any potential complications.
After successfully accepting ownership, you gain main contract ownership and inherit whatever administrative capabilities are tied to the ownership role in your Core token's smart contract. The specific controls depend entirely on how the token contract was configured during creation:
- Owner-based Controls - Functions that require owner permissions (minting, pausing, blacklisting, etc.)
- Role-based Controls - May or may not transfer depending on implementation
- Custom Administrative Functions - Any owner-only features built into your specific contract
- Parameter Management - Ability to modify fees, limits, or other configurable settings
Not all Core tokens have the same ownership features - some may only have basic ownership with no special functions, while others may have extensive administrative controls. You also gain the ability to transfer ownership to another address or renounce ownership entirely.
Most standard implementations don't provide an explicit "reject" function, but you have several options:
- Simply Don't Accept - Leaving the transfer pending is effectively a rejection
- Wait for Timeout - If the contract has expiration mechanisms
- Custom Implementations - Some contracts may include explicit rejection functions
If you don't want to accept ownership, the best approach is to not accept it or initiate a transfer to a different address.
The Core accept ownership tool works only with Core tokens that successfully implement two-step ownership transfers, including tokens using OpenZeppelin's Ownable2Step contract, custom implementations with pending ownership functionality, all tokens created through 20lab, and advanced governance tokens with secure transfer mechanisms.
Standard Ownable contracts (single-step transfers) don't require acceptance and for their ownership transfer 20lab's Core transfer ownership tool can be used. The interface automatically detects whether your token supports the two-step process.
Want to access this tool for different blockchain?
Choose one of the supported blockchains from table below: