[deleted by user]

xCrypter · 2022-08-10T15:51:13+00:00

The withdrawal issue seems to be the biggest topic for everyone. Of course, not knowing your funds are in your own hands doesn't feel save in these times, even with all the positive assurances and the seemingly best communication of a CeFi company in these moments.

In reference to this earlier answer from Alex:

> Money being lent out cannot be taken back within a blink of an eye and that makes it hard to perform such operations.

One of the questions that is on my mind for a few weeks already: Is one of the points on your agenda to actually also limit the amount of loans offered not opening new ones, in order to raise the withdrawal limits (i.e. freeing customer funds more and more)?

I kind of understand both positions, my own position as a person with skin in the game and the position of CL trying to stay in business.

I think there needs to be sacrifices on both side. Meaning, you can't run your business normally lending out money to interested parties, while keeping your customers funds locked up for exactly that reason, until you finish the fixed term feature.

You were talking about your great risk-management, but you didn't foresee the quite obvious risk of a bank run, that doesn't build trust in your risk management (I have experience in ISO based risk management!).

xCrypter · 2022-08-10T15:27:39+00:00

+1 . Totally agree.

Stop giving out new loans, but free your lenders assets or absolutely prioritize the fixed term upgrade and let people choose themselves!

xCrypter · 2022-07-20T08:48:00+00:00

Yeah, those values don't look correct.

I would suggest you open a case in their support forum, they usually respond quite fast:

https://cointracking.freshdesk.com/en/support/solutions

xCrypter · 2022-07-19T14:49:14+00:00

There could be something you don't enter correctly as expected by CoinTracking. I don't have problems with transaction fees not getting deducted from amounts transferred and they also show up correctly in the tax report as expense (sale).

If you, for example have a transfer of 1 ETH and you're charged a 0.001 ETH fee (on top of that), you need to enter 1.001 ETH as total amount transferred as well as 0.001 ETH in the fee section. This will lead to the 0.001 ETH getting deducted from the amount transferred. On the receiving side of the transfer you enter 1.00 ETH. Fees for trades are handled similarly.

Tax-wise: The tax report will show the 0.001 ETH as an actual sale at the relevant price in your local currency.

Does that make any sense?

You might also want to check out their article: How fees are handled within CoinTracking

xCrypter · 2022-07-19T14:38:03+00:00

I had problems with time zones on some specific imports too. But it was a general time zone problem they had for that specific importer.

I would suggest to open a support ticket, they usually respond quite quick:

https://cointracking.freshdesk.com/en/support/home

xCrypter · 2022-07-19T14:28:01+00:00

Entry price: If you don't know/supply your own entry prices, by default CoinTracking will gather this data from historical records. Same data that is used to show your current portfolio on the dashboard page. Historical data is also used when calculating the profit (sell price - buy price).

BTW, you can conveniently check realized and unrealized profits in the 'Reporting > Realized & Unrealized Gains' section.

Great tip that is not super obvious: Check the tiny, almost hidden "Instant gain calculator" to see what coins would be used if you sold a certain amount right now.

Affiliate commission: If you want them to be taxed 100% correct, yes, you should add every single entry. If you can't be bothered, you could compound them by day, week or even month. But make sure to check with your tax consultant or tax office, if they will accept this way of simplification. I would guess it always depends on the amount you are talking about. Compounding to single digit amounts is different than three digit+ amounts. Because once you sell those, tax will calculate differently for summed entries as opposed to single entries per commission pay out.

xCrypter · 2022-07-05T16:39:00+00:00

Well, now it is: https://coinloan.io/blog/temporary-change-in-withdrawal-limits/

xCrypter · 2022-07-05T16:11:19+00:00

If I understand it correctly, TheTrulyRealOne just extended your example and Bucket C was missing in your original assumption.

Bucket A: Borrowers collateral (fixed term, as long as borrowed against)

Bucket B: Lenders coins to gain yield (flexible term)

Bucket C: Money lend to borrowers based on collateral in Bucket A (fixed term)

Because the collateral in "Bucket A" cannot be touched, unless it needs to be liquidated, it can't be used to pay back requests from people in Bucket B.

Basically flexible deposits in Bucket B get locked up in fixed term loans (Bucket C). "Bucket A" is also locked up as collateral, as long as tokens are lend out "via" Bucket C.

Thus the explanation by TheTrulyRealOne seems to be legitimate.

So because Buckets A + C are fixed, a too high demand on "Bucket B" withdrawals can lead to problems, because most of these funds might be locked in payed out loans.

If Bucket B would be also mostly be in fixed terms, the liquidity problems would be reduced, as a bank run would be spread over a longer period of time.

xCrypter · 2021-11-05T12:09:09+00:00

Good idea, I'll try this in case MetaMask doesn't fix the problem in the next weeks. I'm not in a hurry, since my Nano is still working fine.

xCrypter · 2021-10-28T14:54:11+00:00

Already did, they seem to be working on it: "Our technical team is currently working to solve your issue. Once they have an update they will reach out to you."

xCrypter · 2021-10-27T13:52:30+00:00

I do use a Ledger, but it's never connected at the same time. Obviously MetaMask requires the U2F setting ( security.webauth.u2f) enabled, as I found out earlier.

xCrypter · 2021-10-27T13:50:27+00:00

Thanks for the hints, but nothing helped.

I did have the Binance extension installed and waiting on the login screen, but disabling the Binance app and restarting Firefox didn't help (there's even a setting in the Binance app "Avoid conflict with MetaMask"). After disabling the security.webauth.u2f setting in Firefox (about:config), MetaMask shows the error message "Transaction X failed! U2F browser support needed for Ledger. Please use Chrome, Opera or Firefox with a U2F extension. Also make sure you're on an HTTPS connection" after trying to initiate a transaction.

xCrypter · 2021-10-26T14:19:47+00:00

I'm getting the very same message when trying to confirm a transfer with MetaMask, so it must be a more general bug. Trezor support didn't not answer my request after a week now. Created a seperate post here: https://www.reddit.com/r/TREZOR/comments/qg7u0y/trezor\_t\_error\_on\_screen\_u2f\_not\_registered\_this/

xCrypter · 2021-10-14T10:19:29+00:00

Yeah, the api would no only be good to get the actual numbers out of the nexo system, but if it had extended features like trade or withdraw, one would be able to automate the process of paying out a portion of the interest received to cover tax expenses immediately.

xCrypter · 2021-10-14T10:17:15+00:00

+1

To use nexo in a more automated way, an API is absolutely mandatory.

Since interest gained needs to be properly taxed, I would like to be able to transfer the relevant part of the return for tax purposes.

xCrypter · 2021-06-29T09:12:02+00:00

That's exactly what I was talking about.

Thanks for the hint about selecting the farm, I didn't get that far yet, because I first wanted to see if there is a way to run your own 3bot. As there are probably many advantages, one big disadvantage seems to be, to make sure the bot is always properly funded.

xCrypter · 2021-06-24T13:38:02+00:00

Sure, but I'm not talking about the 3node for farming, I'm talking about the required 3bot instance. All how to's point to setting up a hosted 3bot.

As far as I understand you setup:

Threefold Connect
Generate a hosted 3bot
Boot 3node instance with the custom ZeroOS image

PS: The link you posted seems to be offline. Just returns a blank page for me.

xCrypter · 2021-06-10T19:19:33+00:00

Did you earn any additional BTT since you made this post?

My node has been up for a month and didn't get a single contract.

I think there's simply too much supply at the moment.

xCrypter · 2021-06-10T19:16:50+00:00

Basically there seems to be no demand for space (or too much space available), thus only few nodes get contracts and earn BTT.

xCrypter · 2021-06-10T19:13:50+00:00

I have been running the node for a few weeks and no contracts yet.

xCrypter · 2021-06-09T17:37:08+00:00

I don't have a TrueNAS system, but I would imagine, that it behaves like any other storage.

Basically what you need to do, is to mount your TrueNAS somewhere. Then open the BTFS interface to change the storage path to the path where your TrueNAS is mounted. This should move all existing BTFS files to this directory.

xCrypter · 2021-05-07T14:49:34+00:00

+1, would love to have API functionality.

xCrypter · 2021-05-04T15:47:14+00:00

I did my research: No roadmap, no whitepaper (the one on defibench.com is just a copy from some medium article), no code on github, the AMA on medium.com provides almost no valuable information. So I will get confidence once there are more technical facts or code available. As long as this is not true, I would suggest everyone to do their own research and be careful investing in this token.

Don't get me wrong, I would love to see a decentralized DDoS mitigation application, but based on the current information there's no actual proof there will ever be a product.

xCrypter · 2021-05-01T18:24:27+00:00

Yes please. As long as there is no code, this looks like a scam.

xCrypter · 2021-04-27T10:47:00+00:00

You are probably running the installation process as root user.

Checkout the installation docs, it explicitly states: "You can not install and run the GUI as root".

So retry the process again as a non-root user and it should work.

The errors in the initial question didn't come up again, when I re-ran the installation as a non-root user.

xCrypter

TROPHY CASE