Is there any free and unlimited wallet API service?

[Crowdsnatch]

So we really did our research and we can't seem to find any clear statement on limits and pricing at all! We've developed a platform using the Python programming language and are currently using a Bitcoin Client library which doesn't seem to be very scalable.

What we're searching

- A Bitcoin wallet service (has the benefit of visual representation and easy withdrawals)
- Most preferably we want to own the private keys!
- That service should be quite popular (-> reliable)
- There should be no (or almost no) fees involved - the service should be free and involve no monthly costs
- We want to receive Bitcoins (which should trigger notifications) and send Bitcoins
- All this should happen "behind the scenes" on the backend - we don't want to include any checkout page provided by the service provider
- We might need to generate 1 million addresses for a single wallet and hold up to worth $1M USD in BTC (but we could regularly withdraw)
- We need to get notified about each change in the number of confirmations

So basically we need a functional wallet API (for use together with the Python language). Does any such service exist? What for example about Coinbase? They do offer something... but no one attempts to clarify what's possible and what isn't!

Thank you in advance.

[DaveF]

Instead of a hosted service, did you look at btcpay?

https://btcpayserver.org/

It's all local to you, so you can setup your own API to deal with it.
You have all your own keys, no hosted no trust needed. etc.

As far as I know there is no unlimited service out there that is larger. If you get big enough and are good enough there is no reason to be free.

Stay safe.

-Dave

 

[Olmaca]

Instead of a hosted service, did you look at btcpay?

https://btcpayserver.org/

It's all local to you, so you can setup your own API to deal with it.
You have all your own keys, no hosted no trust needed. etc.

As far as I know there is no unlimited service out there that is larger. If you get big enough and are good enough there is no reason to be free.

Stay safe.

-Dave

 

Also came across this. Does this solution require to download the entire blockchain?

[OmegaStarScream]

Instead of a hosted service, did you look at btcpay?

https://btcpayserver.org/

It's all local to you, so you can setup your own API to deal with it.
You have all your own keys, no hosted no trust needed. etc.

As far as I know there is no unlimited service out there that is larger. If you get big enough and are good enough there is no reason to be free.

Stay safe.

-Dave

 

Also came across this. Does this solution require to download the entire blockchain?

Yes, it does. If you want to avoid that, you can use third party hosting but you'll have to deal with some restrictions.

As for the Python API, you can read more about it here: https://docs.btcpayserver.org/integrations/customintegration

[DaveF]

Also came across this. Does this solution require to download the entire blockchain?

As OmegaStarScream said above yes, you do. Or you wind up trusting a 3rd party.
If you really are going to do the numbers you stated in the 1st post it's worth the $250 of hardware and an hour or 2 of setup time to do it locally.
Yes, the initial download can take a bit of time but it's not worth compromising security to save a few dollars and some bandwidth.

Personal note, that probably does not belong in this thread but is worth mentioning.
For a VERY short time I offered both paid and free btcpay hosting. If you do use someones free service don't expect support. It starts and ends at yes it's up or no it's not up and I'm working on it. I really didn't care if it was not working the way you wanted or you could not figure out how to do something. All I cared about is can you get to it.

-Dave

[Crowdsnatch]

Thank you for all your replies!

BTCPay does indeed look quite promising. Unfortunately though it's not designed for sending payments which is actually a crucial requirement for us. I've also looked into Electrum (maybe in combination with the CLI), but I'm not sure if this is scalable enough.

[mocacinno]

Thank you for all your replies!

BTCPay does indeed look quite promising. Unfortunately though it's not designed for sending payments which is actually a crucial requirement for us. I've also looked into Electrum (maybe in combination with the CLI), but I'm not sure if this is scalable enough.

Eventough btcpay is great, i'd probably recommand either electrum daemon or just plain bitcoind (bitcoin core daemon), and use json-rpc.

Your requirements talk about not having to include a checkout page, and working completely "behind the scenes", so i'm not sure if the overhead of btcpay would actually be worth it for you.
For core, you could take a look at -alertnotify=,  -blocknotify=, -txindex

[nc50lc]

BTCPay does indeed look quite promising. Unfortunately though it's not designed for sending payments which is actually a crucial requirement for us.
I've also looked into Electrum (maybe in combination with the CLI), but I'm not sure if this is scalable enough.

You can send payments from BTCPay Wallet (if you're using a Hardware Wallet) or the main wallet where the xpub was extracted from.
The hardest requirement to fulfill is the 1m+ address which is only possible with Bitcoin Core (req. the whole blockchain).
Electrum will struggle to sync the wallet's transactions, don't know if their own BTCPay Wallet and Wasabi can.

If BTCPay Wallet can handle all those addresses: Purchase a Hardware wallet instead.

For Bitcoin Core: There's no official documentation to connect Bitcoin Core to BTCPay: docs.btcpayserver.org/getting-started/connectwallet
But since it only requires the main wallet's master public key, it's possible to connect it to Core.

[DaveF]

Thank you for all your replies!

BTCPay does indeed look quite promising. Unfortunately though it's not designed for sending payments which is actually a crucial requirement for us. I've also looked into Electrum (maybe in combination with the CLI), but I'm not sure if this is scalable enough.

For receiving and sending payments for security purposes should be separate. Unless there is a compelling reason for it they should not even be on the same server.
BTC comes in -> moves to cold wallet with multisig -> as needed move some to a different hot wallet -> BTC out.

If you have if all in 1 a programming error on the side of receiving payments can get to your main wallet and wipe you out. I know you said you were going to move the BTC out of the incoming wallet but putting it back in there or leaving a large amount in it is just asking for trouble.

Just my view.

Stay safe.

-Dave