eprbell
eprbell
I am no futures expert, so I'm just spitballing here. I read a bit about futures, including your link and initially I thought we had a couple of options: Option...
This already came up when designing the unique id logic. There are 2 problems with this proposal: * I'm not aware of any programmatic way to distinguish transaction hashes of...
> The vast majority will be on-chain transfers and for those we don't add ``. This means you need a way to distinguish on-chain transfers from other kinds of transfers...
Sounds like a good idea to me. Is this the library you're referring to: https://pypi.org/project/web3/ ?
I second what @macanudo527 said. We are experimenting with CCXT, which hopefully has all the functionality we need both in the abstract class and in subclasses like Kraken and Binance....
BTW, @nitrocode a Kraken plugin would be very impactful: let me know if you would like to take on this issue.
You'll need to create a PR. You can fork dali-rp2 and then follow these instructions: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
It's all good, no worries.
Interesting case. Probably you can use 0 as the sale price if the coin is dead, but you still need to know historical prices so that RP2 can compute the...
The Cointracker article is helpful. Yes, probably adding a new BURN transaction type (and a FAQ) is the best way to capture this case properly.