HostDudes Join Our Discord
← Forked node tutorials
Forked Nodes Tutorial

Lock In Your Forked Node Claim

Learn how to lock in your Forked node claim by submitting your eligible Datagram address, setting a receiving address, completing the verification transfer, and checking your claim status.

Before you start

This guide is only for people whose Datagram address held an eligible Full Core Node License when Forked took its snapshot. If you did not have a qualifying Datagram node license at that time, this claim process does not apply to you.

Forked controls the claim process, the snapshot, eligibility decisions, and delivery of Forked node licenses. This guide is only meant to help users follow the process. HostDudes has no control over it and cannot change snapshot results, approve claims, or deliver licenses.

This is a Forked-specific claim process. You will need access to Forked's official Discord, your Datagram Dashboard, the Datagram address that held your eligible Full Core Licenses at the snapshot, and the address where you want to receive your Forked nodes.

The claim bot asks you to send a small, unique amount of DGRAM to a specific destination address to prove that you control the Datagram address. Use only the amount and destination address shown in your own current bot message. Never copy either value from this guide or another member.

HostDudes will never ask for your seed phrase, private key, or wallet connection access. HostDudes also does not receive this verification transfer. See what access HostDudes needs for more details.

  1. Open Forked's official Discord and select the claim command

    Join the Forked.gg Discord. In any channel where bot commands are enabled, type /claim. When Discord's command menu appears, click the /claim option from the Node Claim Bot, labeled Claim your Forked nodes and grow the network, as shown below.

    Discord command picker showing the Forked Node Claim Bot claim command

  2. Enter both addresses

    • datagram_address: the Datagram address that held your Full Core Licenses at the snapshot.
    • receiving_address: the address where you want the Forked nodes delivered.

    These addresses serve different purposes, so check every character before continuing.

    Forked claim command with fields for the Datagram address and receiving address

  3. Submit both addresses

    To find your Datagram address, sign in to the official Datagram Dashboard, open Wallet, and copy the full address shown next to Your wallet address. Use this as the datagram_address in the Forked claim command.

    Datagram Dashboard wallet page showing where to copy the user's wallet address, with the example address altered
    Copy the address from your own Datagram wallet. The address shown here is an altered example.

    For the receiving_address, use a BNB Smart Chain (BSC) wallet address that you control.

    Return to Forked's Discord. After both fields are complete, check the values once more and press Enter. The addresses in the next screenshot are altered examples and should not be copied.

    Completed Forked claim command with example Datagram and receiving addresses
    The addresses shown are examples. Enter your own addresses.

  4. Check for address errors

    If the bot says the address held no Full Core Licenses in the snapshot, confirm that you entered the exact Datagram address with no extra spaces or missing characters. If it says the address was already claimed by another Discord account, that Datagram address already has an active claim.

    Forked Node Claim Bot messages for an address with no Full Core Licenses in the snapshot and an address already claimed by another Discord account
    Examples of the two address errors you may see.

  5. Read your verification instructions

    If the address is eligible, the bot returns a private verification response. It identifies the Datagram address being verified, the exact amount of DGRAM to send, the destination address, and an expiration time. Confirm that the response came from the Node Claim Bot in Forked's official Discord.

    Example private Node Claim Bot message with the Datagram address, node count, verification amount, destination address, and snapshot date blurred
    Example only. Use the values and deadline in your own current bot message.

  6. Open the Datagram withdrawal screen

    Sign in to the official Datagram Dashboard, open the wallet area, and select Withdraw. Make sure you have enough DGRAM for the exact verification amount and any network fee shown during confirmation.

    Datagram wallet screen with the Withdraw button highlighted
    The balance shown is an example. Your balance will be different.

  7. Enter the amount and destination from the bot

    In Amount, enter the exact DGRAM amount from your bot response. In Send To, paste the destination address from that same response. Check both values again, then click Next.

    Datagram withdrawal form with Amount and Send To fields and the account balance blurred

  8. Review and submit the withdrawal

    Compare the destination and verification amount with your current bot response one final time. The network fee is separate and can vary. If anything does not match, go back and correct it before selecting Withdraw.

    Example Datagram withdrawal confirmation showing shortened From and To addresses, an amount, an estimated gas fee, and a Withdraw button
    The addresses, amount, and fee shown here are examples. Do not reuse them.

  9. Run the claim status command

    After submitting the withdrawal, return to Forked's Discord, type /claim, and select /claim-status from the Node Claim Bot.

    Discord command picker with the Node Claim Bot claim-status command highlighted

  10. Confirm that your claim is locked in

    A successful response confirms that the Datagram address was verified and the Forked nodes were reserved for your receiving address. The exact wording, node count, and any additional eligibility message can differ from the example below.

    If the transfer is still processing, wait and check again. Do not send a second verification transfer unless a new bot prompt explicitly tells you to do so.

    Example Node Claim Bot success response confirming a locked Forked node claim, with wallet addresses and node count blurred
    Example success response. Your addresses, node count, and eligibility details will differ.

Common issues

No Full Core Licenses in the snapshot: Check that you entered the exact Datagram address that held the licenses at the snapshot, with no extra spaces or missing characters. Moving licenses after the snapshot does not change the claim tied to that snapshot.

Address already claimed: The address has already been linked to another Discord account. Use /claim-status from that account if possible, or ask Forked's official support team to review it.

No confirmation yet: Check the withdrawal status and then run /claim-status. Verification prompts expire, so rely on the deadline in your current bot message.

The bot wording looks different: The wording may be slightly different from what is shown in this guide. If the steps are significantly different, pause before transferring anything and let us know in the HostDudes Discord so we can review the change and update the guide.

Need a second set of eyes?

HostDudes can help you work through the steps and spot mismatched fields. Forked controls snapshot eligibility, address locks, and final claim decisions.

Ask in Discord
← Forked node tutorials