-
Notifications
You must be signed in to change notification settings - Fork 46
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
Future of walletkit #413
Comments
Hi @cryptodev100! Thanks for your message. As we have been acqui-hired by Coinbase, we are no longer going to main walletkit actively. We will leave it as an open source project. You are welcome to fork the project and make whatever changes you like. @voisine has reviewed your code, so I hope that gives you the answers you need to proceed. Thanks! |
@shivangigandhi walletKit depends a lot on BlockSet API. How are we going to maintained without the server support? |
@fkirc has the right idea (use p2p mode or sub in your choice of replacement API). Thanks! |
If you guys agree to discuss what we can do on a telegram channel, I've created it: https://t.me/+hgpqH9F2DNVkYjBk maybe we can discuss further and split tasks. |
I just joined! |
A WalletKit |
Dear Blockset-team,
I submitted a PR with #410, but I have not yet received an answer, therefore I try to reach out to you via this issue.
I read that both Blockset and Breadwallet have been acquired by Coinbase and the Blockset-API might be terminally shutdown on March 1, 2022.
This makes me wonder what the future of walletkit will be.
Do you know whether there will be any continued maintenance of wallekit, or will walletkit be discontinued as well?
The text was updated successfully, but these errors were encountered: