freenancial / bitcoin-dca Goto Github PK

This is an important infrastructure to enable auto withdrawing BTC to different addresses of a hardware wallet.

Once #1 is implemented, we want to auto withdraw Bitcoin to our hardware wallet.

Only use available balance that doesn't include balance that is still on the pending orders.

We're currently using API_KEY for Coinbase API invocation, it doesn't allow us to easily track its usage.
So for better security, we should use oAuth instead for Coinbase authentication:
https://developers.coinbase.com/docs/wallet/coinbase-connect/integrating

We want to keep USD as USDC on Coinbase to earn interest.

In addition, we can set "recurring purchase" of USDC on Coinbase.

Once we enabled auto selling of USDC on Coinbase in this DCA tool, combining that with "recurring purchase" of USDC, we would be able to completely automate the Bitcoin DCA process with minimum fee while earning maximum interest.

We should not make withdrawal if the Bitcoin available for withdrawal is too little.

For example, if we only have 50,000 sats in the account, it doesn't make sense to withdraw it because it could be too expensive to spend this UTXO in the future. At this moment, a medium priority on-chain transaction cost around 75 sats/vB. If a transaction takes 300vB, it'd cost 22,500 sats on chain transaction fee.

It seems that a minimum of 500k sat to 1 million sat per UTXO would be a reasonable target.

Right now, the withdrawal xpub and beginning address are saved as plain text in config.ini. If a hacker changed the address, Bitcoin will be auto withdrawn to the hacker's address.

We should encrypt the addresses and move them to bitcoin_dca.secrets instead.

Right now, we allow withdrawal of Bitcoin to a target address as long as it has an empty balance. However, we should not reuse a Bitcoin address even if it has zero balance if it had already been transacted before.

So instead, we should check the transaction history of the target address, and avoid using it if it has had any transactions.

https://pycryptodome.readthedocs.io/en/latest/src/cipher/aes.html

Right now we're using AES-128-CBC mode for local encryption, we should use AES-GCM-256 instead for better security.