-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Cryptocurrencies #156
Comments
@deltagolf Hi Diego! Thanks for reaching out! We have considered adding cryptocurrencies but quickly ran into some trouble- the current way Cobudget stores and calculate numbers is with only 2 decimal points. Because different cryptocurrencies need differing amounts of decimals (and typically more than 2) adding them would mean doing a systemic change to the way we store and calculate numbers. That being said, it's still on our minds and we would hope to add it in the future. P.S. We <3 PRs if you're interested in contributing! |
@nicosmaris Both. As @jlopker write above the DB setup etc. is based on currencies with 2 decimal places. |
Any updates about this issue? Discovering idea about making App-Connector of Co-Budget with Cryptocurrencies and Tokens. |
At the moment this is feature not being actively pursued by the core Cobudget team to be built into Cobudget, because other platforms that are more focused on Cryptocurrency only are building similar functionalities (check out http://alchemy.daostack.io for more information about a cryptocurrency-cobudget like platform) There was a conversation last year among various open source developers about integrating cryptowallets with Cobudget, which can also be followed up here: https://www.loomio.org/d/wu6ryS2d/cobudget-crypto-continuing-the-thread-from-the-network-convergence-. |
Hi team, lovely project! I wonder if you've considered adding support for cryptocurrencies on your roadmap for cobudget, but as technology evolves, I think that should be a must. Thanks for all your work!
The text was updated successfully, but these errors were encountered: