bug

Cryptocurrency is software handled with other software (wallets, exchanges, etc.), therefore, some technical issues are bound to happen here and there for its users. As with any other software, these problems are occasional and not everyone experiences them. Also, they’re often related to something the user did or didn’t do, and are easily fixable. Crypto troubleshooting may vary widely among different platforms and networks, but some common issues have easy solutions, without waiting for support.
Whether transferring funds, managing private keys, or dealing with network settings, crypto users may face some technical hiccups. Understanding how deposits, withdrawals, and fees work can prevent common mistakes while knowing what to do in case of lost access or incorrect transactions can save time and stress. Let’s explore some cases.
Loss of Devices or Private Keys
You’ll need to remember this, always: cryptocurrencies aren’t banks or companies. There’s no “I forgot my password” button to recover your funds. The greatest strength of decentralized cryptocurrencies can also be their biggest drawback — it all depends on personal responsibility. Private keys are the sole means of accessing funds, giving owners complete control. However, because only they have access to these keys, losing them means losing their funds permanently, with no way to recover them or seek assistance.
Private keys are usually made up of twelve or more random words, much easier to memorize than any crypto address. You can do that, but, of course, it’s heavily advised to write them down offline and keep them in a safe place, far from curious eyes. The “offline” bit is important: leave them in your digital spaces as a screenshot or text, and you’re risking that a hacker (or even a family member or coworker?) can gain access to them. Anyone who has these words (keys) can trade with those funds. Don’t forget it.
Now, if you lost the device (mobile, desktop, or another) where you had your crypto wallet, that does have a very easy solution, at least for funds. The coins were never there, in the first place. Just go to another (personal) device, download the wallet app of your preference, and, instead of creating a new wallet, select the option to recover a wallet. Type your private keys there, and voilá.
It’s important to notice that this works only for public-token funds in Obyte. The private assets, like Blackbytes, and other data stored in the wallet (private profiles, smart contracts, prosaic contracts, contracts with arbitration, chats, contacts, etc.) are actually stored in the user’s device. Therefore, it’s critical that you make separate backups for this data.
On the other hand, if you don’t remember your private keys or lost the paper/metal tag on which you have written them, but still have access to the digital app, you can recover your seed from there again if the function is still available. If it’s not, run and transfer all the funds to another wallet of your own (with private keys) before it’s too late.
Deposits & Withdrawals
Depositing and withdrawing cryptocurrency can sometimes be tricky, especially for beginners. The process varies depending on whether you’re using a centralized exchange (CEX) or a non-custodial wallet or a decentralized exchange (DEX). In centralized exchanges (companies that offer this service, like Binance or Biconomy), deposits and withdrawals may be delayed or made impossible if your account isn’t fully verified, or if the exchange is undergoing maintenance, or if it went bankrupt, or it was hacked.
Additionally, most centralized exchanges have deposit and withdrawal limits, which may require identity verification (KYC) to increase. It’s also important to double-check the selected crypto network when withdrawing, as sending funds to the wrong network could result in permanent loss or, at best, a complicated recovery process if the exchange allows it. We’ve written a guide to identify crypto networks.
Decentralized Trading
On decentralized exchanges and wallets, the process is more self-managed, meaning there’s often no customer support to assist with failed transactions. These aren’t that common, though. One key issue can be liquidity — certain tokens may not have enough buy/sell activity, causing delays or price slippage.
That’s the difference between the expected price of a trade and the actual price at which it is executed, usually due to low liquidity or high market volatility. You could lose important percentages this way, but the DEX will always warn you beforehand.
Warning of Price Slippage on Uniswap. Image by CryptoNews
Network congestion can also lead to longer confirmation times and higher fees. Constantly ensure you have enough balance to cover gas fees, as all non-native tokens (including stablecoins) require the native coin of the network (such as ETH or GBYTE) to process transactions. If a transaction is stuck due to low fees, you may be able to speed it up by replacing it with a higher-fee version, depending on the network’s features. Also, depending on your wallet provider, you may be able to change transaction fee percentages in the settings.
Regardless of the platform, always confirm the wallet address before sending funds, as crypto transactions cannot be reversed. If you experience issues, checking transaction explorers can provide insight into what went wrong. Most wallets offer links to chain explorers in every transaction.
Incorrect Address or Network
Sending cryptocurrency to the wrong address or network is a common mistake, often caused by human error, scams, or malware. Scammers use tactics like address poisoning, where they send small amounts to a user’s wallet to create a malicious but similar address in their transaction history, hoping the user copies it by mistake. Another risk comes from clipper malware, which modifies copied wallet addresses to replace them with an attacker’s address.
To avoid these threats, always double-check the address character by character before confirming a transaction, and consider using a hardware wallet with a secure display for address verification. Some digital wallets, like MetaMask and Obyte, also allow the addition of addresses as contacts, making the process easier and more secure. In Obyte, you can also avoid addresses completely and use textcoins and attestations instead.
If coins are mistakenly sent to an unknown address, recovery is nearly impossible unless the recipient willingly returns them. You could send them a message (data) through another transaction if the network allows this function. For instance, this is possible through memos or tags in Ripple and Stellar, through OP_Return in Bitcoin, and just by sending data instead of funds in Obyte.
Wrong Networks
If funds are sent to the wrong network or chain, recovery may be possible depending on compatibility. Some chains, like Ethereum and Binance Smart Chain (BSC), share the same address system, meaning assets may still be accessible through the same wallet on the correct network. In this case, adding the missing network to your multicurrency wallet (like MetaMask) and switching networks might reveal the funds.
However, non-compatible networks, such as Ethereum and Algorand, use different address structures, meaning tokens sent across them (if the transaction doesn’t fail before being sent) are often lost permanently. Before transferring funds, always confirm the correct network and use a reputable cross-chain bridge if you need the funds in a different chain.
In cases where funds are sent to an exchange by mistake, contacting their support team may help, though success depends on their policies. As a preventive measure, always test with a small amount first, ensure you are using the correct address, and verify network compatibility before making significant transactions.
As a last resource, you could hire a company that specializes in funds recovery, like CNC Intelligence or CipherBlade. They may not succeed, though, and note that there are a lot of scammers claiming to be able to help with funds recovery. Always do your own research.
Troubleshooting in Obyte
We follow general crypto best practices here: always backup your private keys, double-check addresses before sending (or better yet, use textcoins or attestations), and ensure you have enough GBYTE to cover transaction fees.
If you’re using our decentralized exchanges (Oswap.io and ODEX) or our cross-chain bridge (Counterstake), check liquidity first to avoid failed swaps or delays. Additionally, since the major Obyte network upgrade in November 2024, older wallet versions are no longer compatible. If you’re experiencing issues, updating to the latest version is the first step to resolving many problems.
Some common transaction errors can be fixed easily. If you encounter “could not send payment: authentifier verification failed,” it likely means smart contract conditions haven’t been met. Contact your counterparty and, if applicable, your arbiter. “No bytes to pay fees” simply means you need to add GBYTE to your wallet before making a transaction that uses another token. Connection-related issues, such as “connect to light vendor failed,” or “internal connection closed” might require checking your connection, your firewall settings, disabling Tor, or switching to a different hub. The last two options are available in the Settings (Global Preferences) of the wallet.
For private transactions, a “too many messages” error when sending Blackbytes can often be fixed by splitting the transfer into smaller amounts. If none of these solutions work, the #helpdesk channel in the Obyte Discord server is the best place to seek further assistance.
Featured Vector Image by vectorjuice / Freepik
Originally Published on Hackernoon
#Troubleshooting #BUG #bitcoin #support #Obyte

There are numerous ways to earn in the Obyte ecosystem, and one of those ways could give a massive reward to skilled developers. We take our security very seriously, so we have a bug bounty program for enthusiasts worldwide to check if our code and features could be vulnerable to threats. This program, hosted by the platform Immunefi, is offering up to $50,000 per critical bug.
Immunefi serves as a leading bug bounty and security services hub for crypto projects, ensuring the protection of over $60 billion in user funds across numerous projects. With an inclusive approach, they cover a wide range of chains and networks, including Obyte. They classify the bugs on a 5-level scale: none, low, medium, high, and critical for the ledger itself (DLT), their smart contracts, or their websites and apps.
In the case of Obyte potential bugs, the payouts start at a medium level with 1,000 USD per reported threat on websites, applications, and smart contracts. High severity threats receive 2,500 USD, and critical bugs in the ledger or its smart contracts have the maximum allocation (50,000 USD). All of this could be paid in GBYTE, BTC, or OUSD (a stablecoin on Obyte).
What kind of bugs count for rewards?
The Obyte bug bounty rewards program encompasses specific impacts in different domains. For the DLT category, critical impacts like network shutdown, unintended chain splits requiring hard forks, and direct loss or freezing of funds of the users are eligible. Critical and high impacts also involve network stability concerns, including RPC API crashes and consensus failures. Medium and low impacts cover scenarios such as excessive node compute consumption and transaction fee underpricing.
Within the Smart Contract domain, critical impacts extend to direct theft or freezing of user funds, as well as manipulation of governance voting results. High impact includes theft or freezing of unclaimed yield, while medium impact involves cases like smart contract operation hindrance and griefing attacks. Low-impact instances involve contract failures to meet return commitments without losing value.
In the Websites and Applications sector, critical impacts encompass severe actions like executing system commands, stealing sensitive data, and disrupting applications. High impacts involve actions such as spoofing content or disclosing confidential information, while medium impacts pertain to privilege escalation and API key leakage.
Certain vulnerabilities and activities are excluded, like attacks where an individual exploits themselves, and theoretical vulnerabilities without proof. Testing on mainnet or public testnet contracts, phishing attempts, and DDoS attacks are prohibited. Automated testing generating significant traffic is also disallowed, and public disclosure of unpatched vulnerabilities under embargo isn’t allowed.
How to report bugs?
The first step is to sign up on Immunefi and press “Submit a report” in the personal dashboard. Then, you select the asset involved (Obyte, in this case), the GitHub repository in which you found the bug, and the impact that bug may cause —direct theft of user funds, for example. The next stage is selecting the severity level, according to the Immunefi scale.
The report itself comes afterward and must include details like description, impact, risk breakdown, recommendations, and references. In the case of Obyte, all web and app bug reports must come with a Proof-of-Concept (PoC) or detailed steps to reproduce the issue. Bug reports submitted without a PoC will be rejected with instructions to provide one. You can add a secret Gist environment to support your PoC.
Finally, if you’re eligible for a reward, you need to share your wallet address to receive it. A review process will start from there by the Obyte development team, and you can check the status of your submission in your Immunefi dashboard. It could have nine conditions: Reported, In Review, Needs More Information, Triaged, Escalated, Confirmed, Mitigated, Paid, and Closed. And that’s it!
Obyte has already paid around 47.800 USD to white hats through Immunefi –and around 10,000 USD for bug reports before this program as well. If you’re ready to help us improve the Obyte ecosystem, you can also check our resources for developers and our GitHub repositories. Happy coding!
*
Featured Vector Image by storyset / Freepik
Originally Published on Hackernoon
#BUG #BugBountyProgram #Immunefi #CryptoDevelopment #Obyte