Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to accept Bitcoin payments without running a full node

incoherency.co.uk

Post reply on HN
Print view View original

11–20 of 28 posts

Re: How to accept Bitcoin payments without running a full node

#11

Post by jstanley »

therealidiot wrote: post #2

The author mentions being plagued by crashes/corruption, but I've never experienced this and I've been running a full node for a few years. Other than the large (well, not _that_ large) storage requirements (.bitcoin is currently 101G) I've not got any complaints... Unless there's a bug in a recent version of bitcoind which causes it to crap out when initially catching up with the network?

I've been informed that crashes+corruption indicate either lack of memory or hardware faults. Bitcoin needs to do an awful lot of cryptography, and it all needs to come out perfectly for it to work, so it tends to be sensitive to hardware faults.

Re: How to accept Bitcoin payments without running a full node

#12

Post by ChemicalWarfare »

csomar wrote: post #3

> Third-party Bitcoin payments services typically take a 1% fee. This is not accurate. Bitpay (most popular payment provider) charges you only if you settle (convert your BTC to USD). If you are going through an exchange (bitfinex for example), you'll pay 0.2% for taker rates. 0.8% seems reasonable enough for me considering that Bitpay provides a decent interface and decent tools.

+1. That ~1% fee is for merchants who want to accept btc but don't want to deal with the ecosystem. They just provide their bank info to the processor and get fiat deposited there.

Re: How to accept Bitcoin payments without running a full node

#13

Post by Bombthecat »

jstanley wrote: post #9

Author here, surprised to see this on HN! I considered submitting it myself but didn't think this crowd was that into Bitcoin. Nice to be proven wrong :) A couple of people mentioned HD wallets: I initially tried using an HD wallet, but the mechanism for interacting with it was more inconvenient than generating keys manually - especially considering that you might have to generate hundreds of addresses in a row that…

The sentiment is really changing. Two ago bitcoin was scam and idiotic.

But as usual. People not to a) priven wrong and they need to get with it in touch with it every few weeks/ days to accept a new concept.

And i think for that. We as bitcoin fans and user should and now can get more cocky :)

Re: How to accept Bitcoin payments without running a full node

#14

Post by snitko »

I'm the original author of "Straight", a stand-alone opensource Bitcoin payment gateway - a software that allows you to accept Bitcoin payments: https://github.com/MyceliumGear/straight-server

It is now part of the Mycelium Gear project, which is a hosted commercial version of it, and I don't work for the company anymore, but the team behind it that I hired and worked with is really great and they keep working on the product.

Re: How to accept Bitcoin payments without running a full node

#16

Post by john111 »

jstanley wrote: post #9

Author here, surprised to see this on HN! I considered submitting it myself but didn't think this crowd was that into Bitcoin. Nice to be proven wrong :) A couple of people mentioned HD wallets: I initially tried using an HD wallet, but the mechanism for interacting with it was more inconvenient than generating keys manually - especially considering that you might have to generate hundreds of addresses in a row that…

Glad to see the author here! Just curious, how did you know this was submitted?

Re: How to accept Bitcoin payments without running a full node

#17

Post by j2kun »

21 Inc. (where I work) has a very easy to use python library [1] allowing you to accept bitcoin payments via HTTP 402. But you can also just use the library to serve up a fresh payout address in plaintext on a website.

If you like the CLI, it has that too; it's a fully-compliant HD wallet. Getting set up is as simple as it can be

    $ curl https://21.co > setup.sh
    $ sh setup.sh
    $ wallet create
    [write down mnemonic]
    $ wallet payoutaddress
    [printed payout address]
Then you can use `wallet history` or `wallet balance` to see incoming payments, and `wallet send` to send money to a recipient.

If you like the advanced stuff, it has support for micropayment channels, too.

[1] https://github.com/21dotco/two1-python/

Re: How to accept Bitcoin payments without running a full node

#18

Post by jstanley »

john111 wrote: post #16
jstanley wrote: post #9

Author here, surprised to see this on HN! I considered submitting it myself but didn't think this crowd was that into Bitcoin. Nice to be proven wrong :) A couple of people mentioned HD wallets: I initially tried using an HD wallet, but the mechanism for interacting with it was more inconvenient than generating keys manually - especially considering that you might have to generate hundreds of addresses in a row that…

Glad to see the author here! Just curious, how did you know this was submitted?

I got an email about the post, and asked the person where they found it.

I also browse HN quite frequently so would have been likely to see it anyway :)

Re: How to accept Bitcoin payments without running a full node

#20

Post by Senji »

jstanley wrote: post #11
therealidiot wrote: post #2

The author mentions being plagued by crashes/corruption, but I've never experienced this and I've been running a full node for a few years. Other than the large (well, not _that_ large) storage requirements (.bitcoin is currently 101G) I've not got any complaints... Unless there's a bug in a recent version of bitcoind which causes it to crap out when initially catching up with the network?

I've been informed that crashes+corruption indicate either lack of memory or hardware faults. Bitcoin needs to do an awful lot of cryptography, and it all needs to come out perfectly for it to work, so it tends to be sensitive to hardware faults.

If you're doing bitcoin crypto on a machine without ECC RAM, you're a madman.
Post reply on HN