1. Vault Interest
Unfortunately, the DeFiChain Core does not currently provide this information via the blockchain. We have submitted a request and must wait for an update from the DeFiChain Core developers.
For unrecorded vault interest, we recommend the following workaround:
Record all interest receipts with a transaction type of other income. Due to the lack of information, you cannot see when vault interest was distributed. However, if you have closed the vault, you will see the exact amount of the received vault interest in the mistakenly remaining amount in the vault. You could now record this exact amount as other income at the time of the vault closure by manually creating a transaction for it.
The workaround is explained in more detail here
Here you can find the tax assessment of "negative interest" that we follow
2. Account-to-Account Transactions
Unfortunately, DeFiChain account-to-account transactions are not currently supported. These transactions are read as a multi-coin withdrawal in one transaction, resulting in a defective transaction in chain.report.
Recommended action:
1) In the case of a multi-withdrawal, e.g.:
You would need to edit this defective transaction (deposit or withdrawal of 2 tokens simultaneously) so that the withdrawal is split into 2 transactions. Also, consider that, for example, when splitting into 2 transactions during a withdrawal, the deposit at the target address may need to be adjusted.
2) You could enter one token as a fee - provided it is indeed a fee.
3. Vault Transfers
Vault transfers are also not supported.
This particularly affects multi-layered vault withdrawals consisting of multiple tokens. Due to ambiguous information, it cannot be determined which tokens are associated with the withdrawal. However, a simple withdrawal of a token from the vault can be tracked.
4. Missing Transactions Due to Node Disconnects
Unfortunately, the DeFiChain node software remains unstable up to the current version. As a result, our nodes occasionally lose connection. This means transactions may be missing and cannot be reloaded. Consequently, balances may also differ.
We hope for a stability update of the DeFiChain node software soon. For now, the only solution is to create a new setup, e.g., with the X button. Therefore, you should also plan for new setups in the future.
5. Newly Generated Addresses in Masternodes
If a new change address is created in a masternode/desktop wallet as part of a UTXO transaction, it is not automatically added to chain.report. You should create a new masternode/desktop wallet to include all subaddresses.
This can result in, for example, your DFX or DeFiChain wallet balance being too low or even negative.
6. Are Transfer-Domain Transactions missing in your MetaChain Wallet?
These are not really missing here, because for every TransferDomain deposit, there is also, for example, a native deposit. If the TransferDomain deposit were recorded, the deposit would end up being recorded twice.
Edit: before 31.03.2024, this native accompanying deposit is unfortunately not always present, so a TransferDomain deposit before this date
IMPORTANT:
DeFiChain is a highly dynamic environment. There have been and continue to be ongoing updates to the node software, as well as, for example, hard forks, which will most likely require a new setup after several months at the latest.
Example:
After the dToken hard fork, all old dTokens are technically replaced by new ones. We have merged these in the database with the new token and also provided them with the old price information. This hard fork is an example of why a new wallet setup is necessary.
We will keep you updated in our Telegram channel as soon as there are any news on this.