Ask SN: accepting vanilla BTC programmatically \ stacker news ~bitdevs

Ask SN: accepting vanilla BTC programmatically

675 sats \ 50k boost \ 20 comments \ @mikhael28 17 Aug bitdevs

I wanted to quickly ask, concurrently while I’m doing my own research, the best way to accept BTC in Q3 2024.

I could essentially have a recurring API request to check if an ‘active transaction’ has been recorded to the blockchain through some API request, but I’m wondering if there are any best practices/libraries and tools I should use? Just vanilla BTC, no lightning.

Additionally, what are the risk factors for accepting BTC from anyone? Are ‘blacklisted’ wallets a thing, where if some North Korean hacker sends me something, is my whole wallet going to be blacklisted? How would I prevent that?

Any other suggestions or advice would be much appreciated - thank you!

view all related items

10 sats \ 1 reply \ @Satosora 17 Aug

I dont think wallets get blacklisted unless there is a lot of suspicious activity.

0 sats \ 0 replies \ @sangekrypto 17 Aug

As far as I know, usually if there is suspicious activity, for example a user breaking the rules, they will be blacklisted, but if there is no abuse, of course there is no problem, agree with your opinion.

918 sats \ 2 replies \ @k00b 17 Aug

Govs publish the blacklist, but you can’t prevent them sending you money. Idk but I’d guess you’d be expected to report it and not provide services.

0 sats \ 1 reply \ @mikhael28 OP 18 Aug

Where is it published? Do they have an API to access up to date wallet ID’s?

908 sats \ 0 replies \ @k00b 18 Aug

I think they publish it in a machine readable format.

https://ofac.treasury.gov/sanctions-programs-and-country-information

1028 sats \ 0 replies \ @ChrisS 17 Aug

Use your own node. Don’t reuse addresses. And don’t combine utxos you don’t want connected when you spend them. If you do these things it will be very difficult for an attacker to know two addresses are connected. Also bitcoin has no concept of blacklists.

897 sats \ 0 replies \ @025738dda8 17 Aug

Accepting bitcoin means "you give a BTC address to somebody while owning the appropriate private key". Every single wallet solves this issue. Maybe, you search for more privacy? Maybe you search for simple UX? What do you mean by "best"?

Being notified about received money means "I know my addresses and search for them in the blockchain". To stay private, I need my copy of blockchain on my own node. The node has documented RPC API.

The question about blacklisting sounds strange. This is a fundamental bitcoin property that transactions/addresses are very difficult to be efficiently blacklisted. Even if mining becomes more centralized, there is still high possibility for you to transact. It just might become more expensive. Moreover, there is the concept of stealth addresses.

And finally, lightning IS vanilla bitcoin as well. Maybe you wanted to say "on-chain" only bitcoin. With Bolt12, you can receive lightning bitcoin by having similar user experience as with on-chain. Anyway, it is still vanilla bitcoin.

920 sats \ 1 reply \ @alexbit 17 Aug

Self hosted BTC Pay server.

If you also run a Lightning node, it can accept both onchain and lightning.

That's what I am using at https://bitcoinisdata.com/

21 sats \ 0 replies \ @patrick1 26 Aug

This is the real answer.

899 sats \ 2 replies \ @teremok 17 Aug

I recommend you use BTCPayServer

Don't reuse addresses, it's bad practice. If you never reuse or consolidate, your chances of being blacklisted are very low

30 sats \ 1 reply \ @nkmg1c_ventures 17 Aug

This is going to sound dumb probably, but when when people say "don't re-use addresses", they mean generate / provide a different public address for each payment / invoice you wish to accept BTC?

Is it necessary to use a different mnemonic / private key or is it sufficient to use different public addresses from the same private key by increasing the index?

888 sats \ 0 replies \ @teremok 18 Aug

Yes, all addresses are derived from one extended private key.

You can play around this tool to give you an idea:

https://iancoleman.io/bip39/

888 sats \ 0 replies \ @adamsoltys 18 Aug

Install bitcoin core from https://bitcoin.org/en/bitcoin-core/ and then use the walletnotify setting to have it call a custom script any time you receive a transaction. Your script can call other API's or programs that notify you or take some automated action.

Here's some info on using walletnotify: https://bitcoin.stackexchange.com/a/24483/31974

888 sats \ 1 reply \ @160ed04091 17 Aug

To accept Bitcoin (BTC) programmatically in a vanilla way, you'll need to interact with the Bitcoin network, usually through an API or a library that lets you handle transactions and addresses. Here’s a high-level guide to get you started

0 sats \ 0 replies \ @mikhael28 OP 18 Aug

Can I get the guide? ☠️

Tipping you in advance.

888 sats \ 0 replies \ @kruw 17 Aug

the best way to accept BTC in Q3 2024.

BTCPay Server!

Additionally, what are the risk factors for accepting BTC from anyone? Are ‘blacklisted’ wallets a thing, where if some North Korean hacker sends me something, is my whole wallet going to be blacklisted? How would I prevent that?

Use BTCPay Server's coinjoin plugin to make the source and destination of your funds untraceable on chain: https://docs.btcpayserver.org/Wabisabi/

888 sats \ 0 replies \ @profullstack 17 Aug

https://cryptapi.io/resources/nodejs-library

0 sats \ 0 replies \ @mikhael28 OP 18 Aug

Just got around to replying everyone, cheers!

0 sats \ 0 replies \ @Akg10s33 17 Aug

No, there really isn't that blacklist concept in bitcoin." You just have to be attentive to the safest way to have or manage your wallets... and don't go to addresses that are not safe... this is one of the best things What does Bitcoin have that if one follows the security steps that are established... one can be happy💪

0 sats \ 0 replies \ @Octopus 17 Aug outlawed

stackers have outlawed this. turn on wild west mode in your /settings to see outlawed content.