defich / ain Goto Github PK

I want to change the token property "Minting Support" of an existing Token via CLI.
My command syntax failed (it seems to be not correct and I already had a look on the API-documentation)

Minting-Support of Token should be "no"/false

I used the following command
defi-cli updatetoken "DGT" ( {"symbol":"DGT", "name":"DeFi Genesis Token", "isDAT":false, "mintable":false, "tradeable":bool, "finalize":bool})
and got the error shown on the screenshot

The error is reproduceable with the used syntax => seems to be wrong

Used Version: defichain-1.3.3-x86_64-w64-mingw32

Hi all,

I tried to swap DFI to BTC/ETH/USDT in DEX and get the error "recipient () does not refer to any valid address"

Wallet: 2.1.13
Type: Windows 10 - 10.0.19042

App Log: recipient_error.log

[2021-01-28 00:36:38.039] [IPC-RENDERER-error] [isBlockchainStarted] {"message":"Request failed with status code 500","name":"Error","stack":"Error: Request failed with status code 500\n    at e.exports (file:///vendor.d5241135cfdddf9a65b1.js:8:101767)\n    at e.exports (file:///vendor.d5241135cfdddf9a65b1.js:8:104168)\n    at XMLHttpRequest.f.onreadystatechange (file:///vendor.d5241135cfdddf9a65b1.js:8:97988)","config":{"url":"/","method":"post","data":"{\"jsonrpc\":\"1.0\",\"id\":\"7307471533660646\",\"method\":\"getblockchaininfo\",\"params\":[]}","headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json;charset=utf-8","cache-control":"no-cache"},"baseURL":"http://VbdLrwkL:a190c202d4321c8ef4f108c5db0cb9f715556e7bf254c55483118644611275e3@127.0.0.1:8555","transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1}}
[2021-01-28 00:36:40.036] [IPC-RENDERER-error] [isBlockchainStarted] {"message":"Request failed with status code 500","name":"Error","stack":"Error: Request failed with status code 500\n    at e.exports (file:///vendor.d5241135cfdddf9a65b1.js:8:101767)\n    at e.exports (file:///vendor.d5241135cfdddf9a65b1.js:8:104168)\n    at XMLHttpRequest.f.onreadystatechange (file:///vendor.d5241135cfdddf9a65b1.js:8:97988)","config":{"url":"/","method":"post","data":"{\"jsonrpc\":\"1.0\",\"id\":\"19090923680263283\",\"method\":\"getblockchaininfo\",\"params\":[]}","headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json;charset=utf-8","cache-control":"no-cache"},"baseURL":"http://VbdLrwkL:a190c202d4321c8ef4f108c5db0cb9f715556e7bf254c55483118644611275e3@127.0.0.1:8555","transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1}}
[2021-01-28 00:36:42.036] [IPC-RENDERER-error] [isBlockchainStarted] {"message":"Request failed with status code 500","name":"Error","stack":"Error: Request failed with status code 500\n    at e.exports (file:///vendor.d5241135cfdddf9a65b1.js:8:101767)\n    at e.exports (file:///vendor.d5241135cfdddf9a65b1.js:8:104168)\n    at XMLHttpRequest.f.onreadystatechange (file:///vendor.d5241135cfdddf9a65b1.js:8:97988)","config":{"url":"/","method":"post","data":"{\"jsonrpc\":\"1.0\",\"id\":\"6279281580117477\",\"method\":\"getblockchaininfo\",\"params\":[]}","headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json;charset=utf-8","cache-control":"no-cache"},"baseURL":"http://VbdLrwkL:a190c202d4321c8ef4f108c5db0cb9f715556e7bf254c55483118644611275e3@127.0.0.1:8555","transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1}}
[2021-01-28 00:37:04.887] [IPC-RENDERER-info] [handleTestPoolSwapTo] "Starting"
[2021-01-28 00:37:11.277] [IPC-RENDERER-info] [handlePoolSwap] "Starting"
[2021-01-28 00:37:11.314] [IPC-RENDERER-info] [handlePoolSwap] "1. Address  Amount 0"
[2021-01-28 00:37:11.317] [IPC-RENDERER-info] [handlePoolSwap] "Account to Account"
[2021-01-28 00:37:11.319] [IPC-RENDERER-info] [handlePoolSwap] "UTXOs to Account"
[2021-01-28 00:37:11.337] [IPC-RENDERER-error]  "Request failed with status code 500"
[2021-01-28 00:37:44.411] [IPC-RENDERER-info] [handleTestPoolSwapTo] "Starting"
[2021-01-28 00:37:55.788] [IPC-RENDERER-info] [handlePoolSwap] "Starting"
[2021-01-28 00:37:55.818] [IPC-RENDERER-info] [handlePoolSwap] "1. Address  Amount 0"
[2021-01-28 00:37:55.819] [IPC-RENDERER-info] [handlePoolSwap] "Account to Account"
[2021-01-28 00:37:55.820] [IPC-RENDERER-info] [handlePoolSwap] "UTXOs to Account"
[2021-01-28 00:37:55.844] [IPC-RENDERER-error]  "Request failed with status code 500"

I'm using Windows GUI 2.3.1. I'm failing to send DFI tokens to Cake DeFI wallet. What I see is the following error screen. My wallet is fully synchronized so I can't find the cause.

Below API call already report parameter is not a valid json value.

./src/defi-cli -testnet getaccount 76a91417c6c6844421f0bd738cd2971305852fc82b03c988ac "{}" true

As preperation for further wallets which will be built with the definition of BIP44, I would like to ask for registering an index for DFI at SLIP-0044:
https://github.com/satoshilabs/slips/blob/master/slip-0044.md

My ideas would be:

• index 1129, hexa 0x80000469 (D=4,F=6,I=9)
• index 4474441, hexa 0x80444649 (DFI in ASCII)

defi-cli gettransaction returns

error code: -32601
error message:
Method not found

What behavior did you expect?

https://developer.bitcoin.org/reference/rpc/gettransaction.html

How reliably can you reproduce the issue, what are the steps to do so?

./defi-cli gettransaction "daaabd7f2f28d8c48f5a121bebab32f23cbee19b4a3f3d6cedbbc09146048aed"
block 11111 with single tx

getrawtransaction kind of works; for ex (same tx):

./defi-cli "daaabd7f2f28d8c48f5a121bebab32f23cbee19b4a3f3d6cedbbc09146048aed" false "da32b4dbda3b16766cf4fbce51ac29be15ecb5514809384a84e4780f22591108"  

returns

020000000001010000000000000000000000000000000000000000000000000000000000000000f
fffffff0402672b00ffffffff030034e230040000001976a914a242da9ba2e9a2a554051a559411
040881951b1c88ac009435770000000017a914dd7730517e0e4969b4e43677ff5bee682e53420a8
70000000000000000266a24aa21a9ede2f61c3f71d1defd3fa999dfa36953755c690689799962b4
8bebd836974e8cf9012000000000000000000000000000000000000000000000000000000000000
0000000000000

What version of DeFi Blockchain are you using, where did you get it (website, self-compiled, etc)?

tried with https://github.com/DeFiCh/ain/releases/tag/v1.4.5 (and v1.4.4)
defichain-1.4.5-x86_64-pc-linux-gnu.tar.gz

For the GUI-related issue on Linux provide names and versions of a distro, a desktop environment and a graphical shell (if relevant).

OS: Arch Linux x86_64
Host: A320M-S2H V2
Kernel: 5.10.16-arch1-1

Hello everybody,

it's about this topic:
https://www.reddit.com/r/defiblockchain/comments/ky4qz2/bug_coins_are_stuck_on_the_blockchain/

I've tried the reindex option before. Additionally on another PC. The 64 DFI are no longer displayed.
Can someone help me there? If log files are required, I will be happy to provide them.

Version 2.1.10 (But I also tried older versions.)

Thank you!

At DeFiChain security is our top priority. As one of our initiatives to both encourage community involvement and ensure the security of our blockchain, we are launching the DeFiChain Testnet Bounty Program.

How to participate

There are many ways to get started finding a bug bounty. You can start by connecting to the DeFiChain testnet by running defid -testnet. Alternatively, you could study our source code at https://github.com/defich/ain.

If you find a bug through interacting with our program and/or studying our source code, we can offer a bug bounty of up to USD 50,000 worth of DFI provided that we find the bug significant, and you are able to provide useful info in regards to fixing or reproducing the issue.

Be sure to study the code that is tagged for official releases, not the master branch or other code that is still currently under development

Submission process

As security is a sensitive issue, we encourage users not to submit public issues regarding the security of the blockchain. We encourage using your own descretion, if you feel the issue is not something the public can easily exploit, then feel free to create an issue at the repo over at https://github.com/defich/ain. If the issue presents some critical exploit, then please email us instead at [email protected].

In your submission please include:

• A clear description of the issue
• A fix for the issue, preferably in PR form
• If unable to provide a fix, then please provide clear directions on how to reproduce the issue
• Your email address or other relevant contact details (e.g. Telegram ID)
• Your DFI address for receiving the bounty if your submission is approved

using listpoolpairs get below result:

{
  "1": {
    "symbol": "LP128129",
    "name": "-",
    "status": true,
    "idTokenA": "129",
    "idTokenB": "128",
    "reserveA": 0.00000000,
    "reserveB": 0.00000000,
    "commission": 0.01000000,
    "totalLiquidity": 0.00000000,
    "reserveA/reserveB": "0",
    "reserveB/reserveA": "0",
    "tradeEnabled": false,
    "ownerAddress": "76a9148857c8c3ce618fe7ae5f8ee11ecc8ea421a1d82988ac",
    "blockCommissionA": 0.00000000,
    "blockCommissionB": 0.00000000,
    "rewardPct": 0.00000000,
    "creationTx": "77d87bab82b29ef83e89cda510fbe1e0c2060e712d02fe0afbd06e41e37518ea",
    "creationHeight": 556
  },
  "2": {
    "symbol": "LP129130",
    "name": "-",
    "status": true,
    "idTokenA": "129",
    "idTokenB": "130",
    "reserveA": 0.00000000,
    "reserveB": 0.00000000,
    "commission": 0.01000000,
    "totalLiquidity": 0.00000000,
    "reserveA/reserveB": "0",
    "reserveB/reserveA": "0",
    "tradeEnabled": false,
    "ownerAddress": "76a9148857c8c3ce618fe7ae5f8ee11ecc8ea421a1d82988ac",
    "blockCommissionA": 0.00000000,
    "blockCommissionB": 0.00000000,
    "rewardPct": 0.00000000,
    "creationTx": "a10b0bead42ede793452b55b4c64139d078d9c975b4f88a760bfde3d412a8b5e",
    "creationHeight": 571
  },
  "3": {
    "symbol": "LP130131",
    "name": "-",
    "status": true,
    "idTokenA": "131",
    "idTokenB": "130",
    "reserveA": 20.90000000,
    "reserveB": 10.90000000,
    "commission": 0.01000000,
    "totalLiquidity": 10.90000000,
    "reserveA/reserveB": 1.91743119,
    "reserveB/reserveA": 0.52153110,
    "tradeEnabled": true,
    "ownerAddress": "76a9148857c8c3ce618fe7ae5f8ee11ecc8ea421a1d82988ac",
    "blockCommissionA": 0.00000000,
    "blockCommissionB": 0.00000000,
    "rewardPct": 0.00000000,
    "creationTx": "25216977417c543a43c96a48a324952b4745a7b5f94c7a8e4ee9e711f3d40641",
    "creationHeight": 586
  }
}

Using getpoolpair with id can work correctly.

defi-cli getpoolpair 3

This is the result get by id 3.

{
  "3": {
    "symbol": "LP130131",
    "name": "-",
    "status": true,
    "idTokenA": "131",
    "idTokenB": "130",
    "reserveA": 20.90000000,
    "reserveB": 10.90000000,
    "commission": 0.01000000,
    "totalLiquidity": 10.90000000,
    "reserveA/reserveB": 1.91743119,
    "reserveB/reserveA": 0.52153110,
    "tradeEnabled": true,
    "ownerAddress": "76a9148857c8c3ce618fe7ae5f8ee11ecc8ea421a1d82988ac",
    "blockCommissionA": 0.00000000,
    "blockCommissionB": 0.00000000,
    "rewardPct": 0.00000000,
    "creationTx": "25216977417c543a43c96a48a324952b4745a7b5f94c7a8e4ee9e711f3d40641",
    "creationHeight": 586
  }
}

But if try to get by symbol, it always report error

defi-cli getpoolpair LP130131

error: Error parsing JSON:LP130131

Describe the issue
When I call .\defi-cli.exe listaccounthistory "valid address" I get back the same data, doesn't matter which address I'm typing in. It looks like I get back the data as I would type .\defi-cli.exe listaccounthistory "mine"

What behavior did you expect?
I would expect the history for the specified address.

What version of DeFi Blockchain are you using, where did you get it (website, self-compiled, etc)?
DeFi Blockchain version 1.3.15 (release build)

What type of machine are you observing the error on (OS/CPU and disk type)?
Microsoft Windows [Version 10.0.18363.1256]
I9-9900
32 GB RAM

What would you like to be added:

I am proposing a new re-design of the DFI anchor system to make it fair and transparent as it should be.
At the moment a lot of users a not anchoring anymore due to some technical disadvantages on the user side.

DFI anchoring was designed to set anchor on the Bitcoin chain in a regular time intervals and at the convenient of an anchor-user.
At the moment a lot of technical requirement is needed to protect your anchor against stealing anchor attempt. Stealing anchors is successfully performed at the moment on DFI chain.

Anchoring was described in the Whitepaper https://defichain.com/white-paper/ and it got funded/activated at DFIP#1 & DFIP#2 and also documented here https://github.com/DeFiCh/ain/wiki/What-is-an-anchor%3F

Latest changed to the anchoring where done in #277.

Currently we see the following anchoring happening on DFI & BTC blockchain:

1. User#1 sends an valid anchor
2. Another User#2 sends a bit later (between 2-10min) also an anchor which has a lower transaction hash value
3. User#2 gets the anchor although he did send the anchor later then User#1.

Based on public documentation about DFI anchoring, the first user should get the anchor independently of anyone sending another anchor later if User#1 gets confirmed first or at the same time as User#2.

But., as we can see here

Why is this needed:

To restore the balance in anchoring and have some more competing users and let them anchor whenever they think its appropriate.

#36 updates the header numbers for a security audit that is conducted and it would break the compatibility of the node with the current state of DeFiChain mainnet.

Hardfork mechanism needs to be implemented to properly transition to the new header numbers.

at the moment the calculation of the exchange-process is wrong, because the amount of the change depends on the amount of the coins in the pool - in my example (simulated with testpoolswap-command) you get - depending on the size of your transaction - less LTC out of pool than you gave in DFI - and after a great swap (or many less swaps in the same direction) the pool is totally unbalanced - and the next step is, that you can get out more money then you gave in

my example is done today (the address in the command is not mine... it was the last address in the DFI-Richlist; the Result of the call is marked as bold - and size is 10, 100, 1000, 10k, 100k, 1m and 10m DFI as input, the output is not in the same proportion - DFI was about 3,02 USD, LTC about 155 USD):
defi-app_v2.1.15
getpoolpair "LTC-DFI"
{
"10": {
"symbol": "LTC-DFI",
"name": "Litecoin-Default Defi token",
"status": true,
"idTokenA": "9",
"idTokenB": "0",
"reserveA": 5869.64442322,
"reserveB": 297019.60779815,
"commission": 0.002,
"totalLiquidity": 40931.15562124,
"reserveA/reserveB": 0.0197618,
"reserveB/reserveA": 50.60265773,
"tradeEnabled": true,
"ownerAddress": "8UAhRuUFCyFUHEPD7qvtj8Zy2HxF5HH5nb",
"blockCommissionA": 2e-7,
"blockCommissionB": 0.00000102,
"rewardPct": 0,
"customRewards": [
"0.02000000@0"
],
"creationTx": "75a25a52c54d12f84d4a553be354fa2c5651689d8f9f4860aad8b68c804af3f1",
"creationHeight": 614026
}
}
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"10.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
0.19721622@9
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"100.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
1.97156597@9
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"1000.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
19.65623837@9
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"10000.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
190.81148593@9
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"100000.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
1476.21362939@9
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"1000000.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
4523.41037858@9
testpoolswap {"from":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenFrom":"DFI","amountFrom":"10000000.00000000","to":"dR7Huoh5HFkdSjW1gHUYkqvYbyzFApG5KU","tokenTo":"LTC","maxPrice":"0.0197618"}
5700.00385125@9

Enhanced chainstate, stored at enhacnedcs currently holds generic account (tokens) chainstate and wallet-specific chainstate, esp. tokens and rewards history.

With a community-hosted bootstrap like BirthdayResearch/defichain-app#434 this brings about the following issues:

• Including enhancedcs serves no real purpose and may even create a confusing scenario with mismatched wallet transactions.
• Excluding enhancedcs from the bootstrap as it is wallet-specific and not universal would affect the effectiveness of such a bootstrap as enhancedcs is the largest one of all the files.

I would like to suggest the following:

1. Split the current enhancedcs into 2: generic universally identical enhancedcs and wallet-specific walletstate.
2. walletstate should have a HD seed check upon startup to ensure that the same walletstate is loaded for a wallet. Currently enhancedcs is missing that and may result in a confusing transactions history when loaded with mismatched wallets.

Hi, just found a small typo...

~/.defi# defi-cli getmininginfo
error code: -32601
error message:
Method not found

but:

~/.defi# defi-cli getmintinginfo
{
  "blocks": 81776,
  "difficulty": 436865480.6849026,
  "isoperator": false,
  "networkhashps": 6.198374690712178e+16,
  "pooledtx": 0,
  "chain": "main",
  "warnings": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
}

Unintended typo I guess, instead of "getmininginfo" it is "getmintinginfo" with an extra t.

I'm running a docker node with the following specs

~/.defi# defi-cli -getinfo
{
  "version": 1000000,
  "protocolversion": 70015,
  "blocks": 81786,
  "timeoffset": 25,
  "connections": 8,
  "proxy": "",
  "difficulty": 287411770.450339,
  "chain": "main",
  "walletversion": 169900,
[...]
}

The application is stuck in synchronizing status on 95.87% with the message
Verbindung mit der Node ist getrennt
Connection to the node is interrupted.

App being synchronized.

App being synchronized.

Start App -> Sync -> Block 577304/602166 stuck

DeFi App for Windows 10

Windows 10 H2 Build 19042.746 WinFeatures Experience Pack 120.2212.551.0 , Intel Core i7, 16 GB RAM

Issue is, that 'make' failed while running with rule faults. More faults with 'make -i' most of it related to './masternodes/masternodes.h'

I expected to compile defichain to get defi-qt

I can reproduce the issue on 2 Notebbok with same fault.
I tryed with 'make -i' -> several more rule faults occurred.

I'm using the source code version from Github: ain-1.0.0-beta2.tar.gz

Machine is on Linux MX-18.3_x64 Continuum (Debian 9) / HP Elitebook 8760w / SSD 1TB

Please find attached the log:
Make DeFi.txt

Hi,
i have an issue. Maybe you can help me out.
I want to put Liquidity in the Liquidity Mining. In
Both in BTC-DFI and ETH-DFI I get the same error.
It is showing up:

txn-mempool-conflict (code 18)

What can I do?

OS Version: Windows 10 (20H2, Build 19042.746)
Wallet App Version: 2.1.5

Issue:
Could not send DFI from DeFi App to other DeFi App DFI Address. Error is displyed "There was an error sending the amount". See attached screenshot.
What is the root cause of this issue?
What to do now?

Expected behavior :
It should be possible send DFI from DeFi App to other DeFi App/DFI address without error.

Proposal:

• In case of this error please display a readable message which makes it clear what the root cause of the error is. Use an unique error Code which is explained in detail in the Help Menu or in a FAQ section, add a link to it on this App page. Also explain what the user should do now.
• The DeFi App "Logs" menu should lead to specific Log files (or a function witch creates a DebugInfo.zip which can be uploaded here) to support the developer.

Steps to Reproduce:
Launch the wallet app
Select the DFI Wallet
Click on "Send"
Capture an amount that is 10% less than available amount of DFI.
Capture target DFI Address
Click "Next" --> Error will be displayed

Comment:
Looks like there is probably a mismatch between available coins and tokens. The point is the end user can not know what the issue is here and what to do next. The system should fix this in the background.

I have a fast internet line and high-end PC.

Please let me know if I can support you.

Attachment:

Version used: App 2.1.15
OS: Manjaro Linux

Update: The Problem was caused by a conflict with old transactions which never made it to the blockchain
Question: How can we delete old transactions which were not received by the blockchain?

The problem:
Today at 12:10 two pool swaps were executed without any action from my side!

What did I do:
I performed a poolswap today from DFI to DOGE.

What happened:
The swapped DOGE were automatically swapped back to DFI in the same Block without any action from my side!

The containing block of the 3 swaps:
deleted

Info from the block explorer: All 3 transactions were received in the same second: Feb 5, 2021, 12:10:59 PM

Here are the swaps:
deleted

Additional Infos:
I just noticed that the 2 automatically generated swaps contain walletconflicts when i view them with listtransactions. What does this mean?, Can this be the cause for the generation of the swaps?

What happened:

In chainparams.cpp is a URL seed.defichain.io with 2 IP-Adresses.
Name: seed.defichain.io
Addresses:
173.230.129.187
172.105.126.56

172.105.126.56 is reachable and runs a Node on it over Port 8555.

173.230.129.187 has no open port 8555, cant reach the Node.

What you expected to happen:

Masternode or Fullnode reachable on Port 8555 at this IPs.

How to reproduce it (as minimally and precisely as possible):

nslookup seed.defichain.io
Test Port 8555 or use bitnodes.io

I create a new DNS-Seed seed.mydeficha.in with multiple Community Fullnodes or Masternodes. Please let me know, if its possible to hardcode this DNS-Seed in the Code, too. Must i open a separate Feature Request?

What happened:

Try to get the mintinginfo of a operatornode which minting with more then 1 Collateral. Only infos from one Operatornode as result. In the Logfiles are several Thread Stakers, but with getminntinginfo i get only one operator, MN-ID and Operator-ID. There is no context between the Operator Legacy Address, Masternode-ID and Threadstaker-ID (masternodeoperator-value from getmintinginfo)

What you expected to happen:

Get Infos from all running Operatornodes an Thread Staker to monitor the Hashrate.

How to reproduce it (as minimally and precisely as possible):

Mor then one Staker per VPS and try to figure out Operator, MN-ID and Thread Staker-ID.

What are your environment parameters:

Debian 10 with Nodeversion 1.6.0

Anything else we need to know?:

System runs in Testnet.

What happened;

Update Node to version 1.6, Nodes with this version are marked as down on bitnodes.io. Port 8555 is open and reachable, getconnectioncount lists 48 connections on example-Node.

What you expected to happen:

For monitoring i expected that bitnodes.io can monitor the nodes.

How to reproduce it (as minimally and precisely as possible):

Check on bitnodes.io, Update Node to 1.6, check again.

What are your environment parameters:

Tested on Debian 10, Ubuntu 16.04 and Ubuntu 18.04

Anything else we need to know?:

https://defichain-wiki.com/wiki/Fullnode#List_of_Fullnodes
Some public Fullnodes

Is there currently some easy way to obtain coins on the testnet? If not, what is current recommended way or whom shall we contact to get some coins?

Is it planned to automate this process in the future?

OS Version: Windows 10 (20H2, Build 19042.746)
Wallet App Version: 2.1.9

Issue:
Blockchain synchronisation takes to long.
After a App Version update a complete synchronisation is startet even if one minute before the update the App was already in sync.
Sometimes it takes over 60 Minutes to sync.
The displayed amount is zero till synchronisation is finished.
Sometimes the synchronisation even failes and has to be restarted.

Expected behavior:
Synchronisation should be faster and should not block the display of last account balance.
What is the root cause if the synchronisation takes very long even with a fast internet connection and a fast High-End PC?

Proposal:
Would it be possible to do some kind of caching? Because the blockchain is anyway already stored local the last balance could also be stored and displayed while the synchronisation is still running in the background.
Some user could be confused about the zero amount balance.
Would it be possible to first compare and sync only the last/new blocks with the local copy then load the new blocks and then to check the whole blockchain after the current amount is already displayed.
If I compare with Ledger Live and Exodus it should be possible somehow.

Steps to Reproduce:
Launch the DeFi App
Do an update
Restart the DeFi App

Comment:
I have a fast internet connection and high-end PC.

Attachment:

The transaction history and BTC-DFI LP token missing from wallet. Only the second transaction amount is showing up in the wallet. Even DFI rewards are missing. I have been providing liquidity for more than a month.

Wallet address: dF6cA39pHXfQsjdgUt8YvRZe9B49CrL8QK
 
Tx ID(1st): cab84868b51b1c3e94d0dfef8cb38c466a58671a96fbc7d26f0ffa7902e130d0 (439.04 DFI which I swapped 50% for BTC and provided liquidity for a month+ which is missing)
Swap TX ID: 9baf3954c4c40ff4071e610027f7137f3daa660df9dceda5445a8413e869ff37

TX ID(2nd): e871b27681f9ce3982c9e512466962cba17673f612a80282dcc1aff3b2b66efa( 2508 DFI which currently is the balance displaying in the wallet)

To see all my tokens and Tx history+LP tokens in my wallet.

100% when i restore wallet.

Version: 2.1.11, Website

OS Version: Windows 10 (1909, Build 18363.1316)
Wallet App Version: 2.1.6

Issue:
Not possible to add BTC/DFI to Liquidity Mining.
Error message is displayed (Code 16). See attached picture.

Expected behavior :
It should be possible to add BTC/DFI to Liquidity Mining without error.

Proposal:

• In case of error please display a readable message which makes it clear what the root cause of the error is. Use an unique error Code which is explained in detail in the Help Menu or in a FAQ section, add a link to this in the error message. Also explain what the user should do now.
• The DeFi App "Logs" menu should lead to specific Log files (or a function witch creates a DebugInfo.zip which can be uploaded here) to support the developer.

Steps to Reproduce:
Go to Liquidity section.
Select BTC-DFI
Click on Add more
Click on "MAX" next to DFI
Click on Next
Click Supply
→ Error is displayed (code 16)

Comment:
Looks like there is probably a mismatch between available coins and tokens. The point is the end user can not know what the issue is here and what to to next. The system should fix this in the background.

Please let me know if I can support you.

Attachment:

I created a Token on DefiChain via App with specific settings. The result was not like the specification

The token should have the following setting:

• mintable support = No
• Limit = 1000
• Decimal = 0
  

After the creation I got the following result:

• mintable support = Yes
• Limit = 0
• Decimal = 8
  

Not tried to create another Token.
But Daniel Mustermann reported same behavior for the ArbitrageToken and the mintable-Feature

all from WebSite, Client-Version 2.0.0

After installation a fresh new installation of the DeFi app, I want to swap my DFI token with another Token ETH, BTC, USDT
I'm always getting that error "Etwas lief schief"

Version: 2.1.12
app.log

DEX DFI to BTC not working; see attachement

DEX DFI BTC error.pdf

OS Version: Windows 10 (20H2, Build 19042.746)
Wallet App Version: 2.1.10

Issue:
Not possible to exchange BTC to DFI with DEX.
Entered available amount of BTC but system shows error "Something went wrong", see attched picture.
Next button not available.
Unclear error message is displayed.
Funds are available and address is valid (same address was used to receive DFI and BTC from Cake).

Expected behavior :
It should be possible to swap BTC to DFI without error.

Proposal:

• In case of error please display a readable message which makes it clear what the root cause of the error is, a unique error Code which is explained in detail in the Help Menu or in a FAQ section. Also user should get to know what he needs to do now.
• Please check in the code for which root cause the error code "Something went wrong" is displayed and add a precise information what is wrong and what to do now.
• If possible display the amount of target coins the user will get as soon the first field is left.
• The DeFi App "Logs" menu should lead to specific Log files which are helpful for the developer to fix issues. I could not identify which file would be helpful in this case.

Steps to Reproduce:
After automatic update to 2.1.10 restart DeFi App.
Initial Version 2.1.9. was from Defichain webpage.
Go to DEX section.
Enter amount of BTC (in this case 50%) and select DFI as target coin.
→ Error is displayed
If I go back to Wallets and try again later the same use case I get the same result again.

Comment:
How to swap now?
Please let me know if I can support you.
I have very fast optical internet line and high end fast PC (32GB/Samsung Evo Pro M2).

The App cannot be opened on macOS Catalina 10.15.7

"Defi-app" cannot be opened because Apple cannot search for malware in it.

This software needs to be updated. Contact the developer for more information.

What happened:

I have added liquidity to the USDT-DFI pair, but the amount of rewards did not increase.
After investigating, I found out that the Defichain App had preselected by Masternode legacy address as the receipient for the LP token. And, for some reason, the LP token in the legacy address did not generate any rewards whatsoever (neither in token balances nor in the account history)

For your reference, please check the the screenshot (https://raw.githubusercontent.com/muirglacier/coinmate-vue/master/nosense.png). You see that the rewards before and after adding liquidity stayed the same. Its not a problem with the app, cli output shows the same weird behaviour.

The root of this issue is when I started running a masternode and, from that point on, the GUI app always pre-selected the legacy address when adding liquidiy because the address started with "8" and hence was at the top of the list.

What you expected to happen:

Rewards!

How to reproduce it (as minimally and precisely as possible):

Just put LP token into a legacy address

What are your environment parameters:

Linux, latest defid as of today

Anything else we need to know?:

Windows 10 / Wallet 2.1.13

Hi there.

with release 2.1.13, I encounter a new problem regarding the syncing process, that was not an issue before.
I have an unreliable and unstable WiFi connection, and Internet is spotty sometimes. So before when I lost the connection, syncing of the blockchain was just halted and continued automatically once I regained connection.

When I lose WiFi / Internet now, the wallet will constantly throw Windows Errors and will not continue loading after regaining connection.

I can't quit the app either. When I try to close the app, it will just show this image with the rotating loading circle. But nothing happens (I waited for 20 minutes).

Thanks

What happened: Tab Masternodes shows only 898 enabled Masternodes. Maybe the default value from listmasternodes of 1000 is used to display.

What you expected to happen: Show all enabled MN in the Network. Current Stats: http://mydeficha.in/masternodes.php

How to reproduce it (as minimally and precisely as possible):

Open Wallet, click Tab Masternodes

What are your environment parameters:

Windows, APP-Version 2.3.0

Anything else we need to know?:

It seems same behaviour in MAC APP, some Users reported in Telegram.

OS Version: Windows 10 (20H2, Build 19042.746)
Wallet App Version: 2.1.6

Issue:
After creating first DFI address a warning is displayed below the address.
(Warning: Not saved by seed phrase)
Same for created second address.
Blockchain is in sync.

Expected behavior :
It should be possible to create a valid address without warning message.

Proposal:

• In case of this error/warning please display a readable message which makes it clear what the root cause of the error is. Use an unique error Code which is explained in detail in the Help Menu or in a FAQ section, add a link to it on this page. Also explain what the user should do or should not do. Explain if the address anyway usable.
• The DeFi App "Logs" menu should lead to specific Log files (or a function witch creates a DebugInfo.zip which can be uploaded here) to support the developer.

Steps to Reproduce:

• After first installation of the DeFi App,
• Create new Wallet, save the seed,
• Create first DFI address
  → Address will be displayed with (Warning: Not saved by seed phrase)
  If warning is displayed try to create a second address

What to do now?
Can I still use this address to receive DFI/BTC/ETH from Cake?

Comment:
This issue was found on two Windows 10 machines with Version 2.1.6, 2.1.9 and with 2.1.10.

Please let me know if I can support you.

Attachment:

VM Mac, though to have some disfunction

To be abale to send, after DEX

Exchanged, not able to send

I am starring at the same wallet on two machines, and one is missing 2Eth:/

2.1.10

MAC VM

Test on testnet, create a a new token with command

./defi-cli -testnet createtoken "{\"symbol\":\"MyToken2\",\"collateralAddress\":\"75EmSChXBbfZ3zkPZ3YiarA8bRsUNs5qw9\"}"

Then call minttokens,

./defi-cli -testnet minttokens "1000@MyToken2#129"

The transaction hash is 8cfd0b08caa99d7b221ba8ac705ecd92c5503de1a9e418d51791abc5c6d41fd7,

And call accounttoaccount,

./defi-cli -testnet accounttoaccount 75EmSChXBbfZ3zkPZ3YiarA8bRsUNs5qw9 "{\"tYAg9dEAHcUo26W6YLLeX7Ph55QCpgjCvA\":\"1.0@129\"}"

the transaction hash is ee1cad7243fdac31d9361fb2c2f729c8cc01296b07c01699cc1d21c2f0ac4120,

from the transaction hash 8cfd0b08caa99d7b221ba8ac705ecd92c5503de1a9e418d51791abc5c6d41fd7 we can get block hash 6309b914bcd7dc0a2869c679451591b5875530aa9e077dfd23b5ef584763e085, and call below command to get the block details, found that the token id in the transaction is always 0.

./defi-cli -testnet getblock 6309b914bcd7dc0a2869c679451591b5875530aa9e077dfd23b5ef584763e085 2

Get block details, the nTokenId is 0

{
  "hash": "6309b914bcd7dc0a2869c679451591b5875530aa9e077dfd23b5ef584763e085",
  "confirmations": 4763,
  "strippedsize": 585,
  "size": 621,
  "weight": 2376,
  "height": 339598,
  "minter": "3b0c81003dc10d97d9024dc73a4932586f7cf539",
  "mintedBlocks": 83667,
  "stakeModifier": "246e09ced93c12cc1b880097862c82f4ac2e592a31a180aa4ecaf32e4edcfc94",
  "version": 536870912,
  "versionHex": "20000000",
  "merkleroot": "8824631f809711e78554b486fad689a7b10a692dcaaba97b17592cd93db2b8bc",
  "tx": [
    {
      "txid": "5a2fee42af2216cb6f322b4dff8bd15eae653ad996849dc291620aad982813a3",
      "hash": "51371e12fac0a3943912038e5e5af1f6f822617d58446ff02c1c04d1af714bac",
      "version": 4,
      "size": 210,
      "vsize": 183,
      "weight": 732,
      "locktime": 0,
      "vin": [
        {
          "coinbase": "038e2e0500",
          "sequence": 4294967295
        }
      ],
      "vout": [
        {
          "value": 135.00004400,
          "n": 0,
          "scriptPubKey": {
            "asm": "OP_DUP OP_HASH160 79421e2165abbfc24e1eeb0111bb132acba5dc04 OP_EQUALVERIFY OP_CHECKSIG",
            "hex": "76a91479421e2165abbfc24e1eeb0111bb132acba5dc0488ac",
            "reqSigs": 1,
            "type": "pubkeyhash",
            "addresses": [
              "7E8Cjn9cqEwnrc3E4zN6c5xKxDSGAyiVUM"
            ]
          },
          "tokenId": 0
        },
        {
          "value": 19.90000000,
          "n": 1,
          "scriptPubKey": {
            "asm": "OP_DUP OP_HASH160 e5ed1bfa532e2358e964381a70e0df6d4dd00419 OP_EQUALVERIFY OP_CHECKSIG",
            "hex": "76a914e5ed1bfa532e2358e964381a70e0df6d4dd0041988ac",
            "reqSigs": 1,
            "type": "pubkeyhash",
            "addresses": [
              "7Q2nZCcKnxiRiHSNQtLB27RA5efxm2cE7w"
            ]
          },
          "tokenId": 0
        },
        {
          "value": 0.00000000,
          "n": 2,
          "scriptPubKey": {
            "asm": "OP_RETURN aa21a9ed32666efebd95367181863ddb2d538162a1e8af40c1c884e64a8eaa1ee4142b51",
            "hex": "6a24aa21a9ed32666efebd95367181863ddb2d538162a1e8af40c1c884e64a8eaa1ee4142b51",
            "type": "nulldata"
          },
          "tokenId": 0
        }
      ],
      "hex": "040000000001010000000000000000000000000000000000000000000000000000000000000000ffffffff05038e2e0500ffffffff0330b8a924030000001976a91479421e2165abbfc24e1eeb0111bb132acba5dc0488ac0080fd9c76000000001976a914e5ed1bfa532e2358e964381a70e0df6d4dd0041988ac000000000000000000266a24aa21a9ed32666efebd95367181863ddb2d538162a1e8af40c1c884e64a8eaa1ee4142b51000120000000000000000000000000000000000000000000000000000000000000000000000000"
    },
    {
      "txid": "8cfd0b08caa99d7b221ba8ac705ecd92c5503de1a9e418d51791abc5c6d41fd7",
      "hash": "8cfd0b08caa99d7b221ba8ac705ecd92c5503de1a9e418d51791abc5c6d41fd7",
      "version": 4,
      "size": 220,
      "vsize": 220,
      "weight": 880,
      "locktime": 0,
      "vin": [
        {
          "txid": "6e3c5ca510a1daf5184fd8942f71741d4ac757d63bc9e8f7458024ed540d9204",
          "vout": 0,
          "scriptSig": {
            "asm": "304402205e4b64ded3669ac2a7a67f7a0d68557cd78ce431c442d35b102a0b98eb81173d022070269037a9863933455eb86b663a524f081a7abe5c8e4e6dee2265c0078d36cf[ALL] 029201addf2c84a298829da7dcdf3ba2441e5664af26551157bb5899ac86c7073d",
            "hex": "47304402205e4b64ded3669ac2a7a67f7a0d68557cd78ce431c442d35b102a0b98eb81173d022070269037a9863933455eb86b663a524f081a7abe5c8e4e6dee2265c0078d36cf0121029201addf2c84a298829da7dcdf3ba2441e5664af26551157bb5899ac86c7073d"
          },
          "sequence": 4294967295
        }
      ],
      "vout": [
        {
          "value": 0.00000000,
          "n": 0,
          "scriptPubKey": {
            "asm": "OP_RETURN 446654784d018100000000e8764817000000",
            "hex": "6a12446654784d018100000000e8764817000000",
            "type": "nulldata"
          },
          "tokenId": 0
        },
        {
          "value": 134.99995600,
          "n": 1,
          "scriptPubKey": {
            "asm": "OP_HASH160 f844dd543caaa49202219b42c45cbaefa3d8a33b OP_EQUAL",
            "hex": "a914f844dd543caaa49202219b42c45cbaefa3d8a33b87",
            "reqSigs": 1,
            "type": "scripthash",
            "addresses": [
              "tttw7GVYUZ9HbqXC29Hdmo65pseiuGY4qh"
            ]
          },
          "tokenId": 0
        }
      ],
      "hex": "040000000104920d54ed248045f7e8c93bd657c74a1d74712f94d84f18f5daa110a55c3c6e000000006a47304402205e4b64ded3669ac2a7a67f7a0d68557cd78ce431c442d35b102a0b98eb81173d022070269037a9863933455eb86b663a524f081a7abe5c8e4e6dee2265c0078d36cf0121029201addf2c84a298829da7dcdf3ba2441e5664af26551157bb5899ac86c7073dffffffff020000000000000000146a12446654784d018100000000e876481700000000d095a9240300000017a914f844dd543caaa49202219b42c45cbaefa3d8a33b870000000000"
    }
  ],
  "time": 1601445290,
  "mediantime": 1601444953,
  "bits": "1a057e15",
  "difficulty": 3054517.207777596,
  "chainwork": "000000000000000000000000000000000000000000000135a1dc94240027600e",
  "nTx": 2,
  "previousblockhash": "d5c16b77d8a3bc4bd096b911ab493e8828e2098fb185c74fab8c2da7171bd0c5",
  "nextblockhash": "f83a3d390e009115c194aef5ebbda1f7ec5f49d06a41e8d2890ce3f960a64503"
}

Based on: https://defichain.com/learn/run-a-masternode/
When delegate the masternode duties to another node

Can you please clarify where we have to use the createmasternode command ?

Do we need to run it on our dfi-wallet locally where we keep the collateral or do we need to run it on the remote dfi-node which will be the new masternode ?

This is key for us to prepare for the next week, as we need time to setup all nodes and fund them properly.
It would be fair to all of us users who want to make DFI more decentralized by helping setting up masternodes.

Some of the users already did try to help by describing their experiences:

• https://www.reddit.com/r/defiblockchain/comments/lq28mv/recommended_masternode_setup/
• https://www.reddit.com/r/defiblockchain/comments/ldigdw/from_a_dfinode_to_dfi_masternode_the_long_journey/

Sync Stops at block 469818

I did synced the blockchain on a Ubuntu Server (at Home) and a Ubuntu VPS with defid. Both can't sync further than block hight 469818. No Mem or CPU problem could be detected.

Version: Current Version

Ubuntu VPS:
CPU: 2 vCore
RAM: 2 GB
SSD: 80 GB
OS: Ubuntu 20.04

Ubuntu Server at Home: Unknown

This is the Output for root@localhost:~# ./.defi/defi-cli getchaintips :

[
  {
    "height": 565456,
    "hash": "f468efaa3c202e88822c904e81f26c0fe487d3db902bbcb51f2e1627313594a8",
    "branchlen": 95638,
    "status": "invalid"
  },
  {
    "height": 469818,
    "hash": "74defd2d641cc2111fa260fe22ef86b9ddeb08a075c48c96c9b3247a12623bc4",
    "branchlen": 0,
    "status": "active"
  }
]

I always get this error message when I am trying to transfer my DFI to another wallet.

OS Version: Windows 10 (20H2, Build 19042.746)
Wallet App Version: 2.1.10

Issue:
When launching the DeFi App and waiting for 5 minutes while spinner is turning
then error "Unable to start blockchain" is displayed.
This happens regularly, with all App versions.

What is the root cause of this issue?
I guess the blockchain can not be "down".
What should the user do now?

Expected behavior:
It should be possible to start the DeFi App without error.

Proposal:

• In case of error please display a readable message which makes it clear what the root cause of the error is. Use an unique error Code which is explained in detail in the Help Menu or in a FAQ section, add a link to it on this App page. Also explain what the user should do now.
• The DeFi App "Logs" menu should lead to specific Log files (or a function witch creates a DebugInfo.zip which can be uploaded here) to support the developer.

Steps to Reproduce:
Launch the wallet app

Comment:
I have a fast internet line and high-end PC.

Please let me know if I can support you.

Attachment:

OS Version: Windows 10 (20H2, Build 19042.746)
Wallet App Version: 2.1.10

Issue:
Not possible to add Liquidity for BTC-DFI even if some coins are available.
Error message displayed: "recipient () does not refer to any valid address"

I guess this is related to this bug: #172

Expected behavior :
It should be possible to add BTC-DFI to Liquidity Mining without error.
If address is somehow not valid even if receivement of coins was possible then the App should come with advice what to do.

Proposal:

• In case of this error please display a readable message which makes it clear what the root cause of the error is. Use an unique error Code which is explained in detail in the Help Menu or in a FAQ section, add a link to it on this page. Also explain what the user should do now.
• The DeFi App "Logs" menu should lead to specific Log files (or a function witch creates a DebugInfo.zip which can be uploaded here) to support the developer.

Steps to Reproduce:

• After first installation of the DeFi App,
• Create a address
• Receive some DFI and BTC from Cake
• Go to Liquidity Section
• Try to add Liquidity to BTC-DFI, Select BTC and DFI
• Select "MAX" next to DFI

What to do now?

Comment:
Error is displayed even after restart. This Wallet Address is not usable.

Please let me know if I can support you.

Attachment:

Address looks correct:

What happened:

There was/is some confusion in my mind in which version of ain is now the one we should all be using?
I in particular did receive a lot of release e-mails/github requests of changing ain version numbers.

At the moment my servers are running with:

# ./defid --version
DeFi Blockchain Daemon version 1.5.1
Copyright (C) 2009-2020 The DeFi Blockchain developers

but on Gihub https://github.com/DeFiCh/ain/releases/tag/v1.5.1 is marked as pre-release ? (while writing this issue)
Two days ago it was the latest version, which we are using currently.

Questions:

• (1) Can we safely use the v1.5.1 on our servers? or should we roll back to latest version which is currently v.1.5?
• (2) Ca a master-node operator safely use the v1.5.1

Can you also please explain the release cycle issues you having last 2 days?

Some background information:
We are checking the GitHub repository for new latest releases based on some GitHub commands and do compile the source for our servers at the moment. But with the software changes we run into some compiling problems and rolled back to the provided v.1.5.1 binaries aprox. 1-2 days ago.

At the moment createpoolpair does not allow token symbol name clash, this allows someone to hijack a token pair. Even if different tokens are used to create the pair, if the same ID is generated e.g. DFI-Test this will result in the following error message:

{
  code: -32600,
  message: "Execution test failed:\nPoolPair creation DFI-Test: token 'DFI-Test' already exists!"
}

createpoolpair should allow clash of pool pair id even if the pool contains the exact same tokens as another pool pair. Users should be able to create multiple pool pairs for the same token combinations as these pools may have different qualities such as different commision.

//\ To began with, I just deleted all DeFi app files and reinstalled DeFi app. Starting from fresh.

//\ Synchronizing begins to start at ~25%. As soon as the sync has been completed, blank white screen and nothing comes up.

//\ The only thing I noticed other than the past issues from other DFI members I would get "_Node Disconnecte_d" which rarely happens unless I shut off my computer. It would stay connect even during sleep mode and this was two updates ago.

//\ OK, Right now SYNC is at ### 86.12% and none of my assets are popping up. That usually would happen by now. I hoping at this point, restoring the wallet would do the trick.

//\ My assets popped up at ### ~90% block ~544101

//\ As soon as SYNC is completed, straight to a blank white screen. The upper left tabs work but nothing comes up.

//\ Not really understanding the question? I expected the issue to repeat after the 3_failed attempt. Then after the recent update, it didn't fix the problem and that brought it to 8_failed attempts,

//\

//\ At this point, I'm 10 for 10 , pretty much 100% success rate to bring up the problem every time. Its either a reboot of the computer or close the screen and reopen.

//\ *********** defi-app-Setup-2.1.12 *************

//\ I'm received app though this address>>>> ********** https://defichain.com/downloads/ **********

//\

Hello!
System is iMac os Big Sur Vers. 11.2, Defichain-App-Vers. 2.1.215 (download from the homepage)
after trying to send DFI from the app to cake and getting several days the error "insufficient funds" and also not being able anymore to convert DFI-Token to DFI-Coins on version 2.1.15 (did it twice before with the reddit instructions but in earlier versions, I think it was with 2.1.10 & 2.1.13) I first tried to reindex, no effect.
Then I tried to use the new "reload UTXOS" button, no effect.
Then i tried to restart the app and I waited till the app closed and started it again and since that I got the error "unable to start blockchain".
I hear about the beta release to the 2.1.16 and gave it a try (download from GitHub). installed the beta of 2.1.16 in hope it would fix it but no effect.
the next day official announcement of the 2.1.16 (download from homepage again) and thought maybe some updaten in the back and tried it again, no effect!
so last hope was to delete everything from my Mac and try to reinstall everything, I bet you can guess already, no effect. same issue.
so far every time I start the app the loading circle under the app version starts turning and after a while the error appears "unable to start Blockchain".

I hope all necessary data is provided!

Archiv.zip

So I wanted to send some DFI to cake and as like most of the time it tells me insufficient funds because of the "DFI token to DFI coin swap issue" and I wanted to swap them by following the reddit tutorial and by getting an error with one of my addresses showing me token and try to make the command to swap to coins it gave me an error "recipient (MY_ADRESS) does not refer to any valid address" then I tried the second dress and with this one it worked to swap because it showed me the tx. I checked the tx in the explorer as suggested in the reddit post and while doing that i thought why not check the address wich did not work before and suprisingly it showed me "0 Dfi" but in the console of the app it showed me an amount XX. so I don't know if this is an critical issue but I wanted to let you guys know...

DEFI_binary_error.log
DEFI_error.log

What happened:

I closed the DEFI APP normally and restarted my machine.
It seems the app was removed after the restart without any warnings
I downloaded and installed DEfi 2.30. After launching the app, i am getting "Corrupted block database detected. Please restart with -reindex or -reindex-chainstate to recover. Do you want to restart? "

There is no option to access the setting.

I restart but always getting the problem with the pop-up error message.
I re-install it but getting the problem with the pop-up error message.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

What are your environment parameters:

Windows 10 Pro
Thinkpad T14S Ryzen 5 Pro
SSD

Anything else we need to know?: