Transaction fees with Dogecoin or Ripple for small amounts

Transaction fees with Dogecoin or Ripple for small amounts

We are a company which sells low priced items online ($0.05 - $0.50). Due to the crypto currency hype, we also would like to accept payments through at least one crypto currency.

I have analyzed a couple of crypto currencies by their average transaction fees, market cap, avg. transaction confirmation, etc.

I found out that Dogecoin and Ripple have currently cheap fees, less than $0.01 cents average.

Question: Can we hire the company that integrates this in our E-Commerce backend or is there anything else important to know beside the exchange fees? Are our transactions too small?

So far I have taken following into account

  • Transaction fees are not fixed, but as of writing this question the fees are acceptable for my case
  • Exchange fees (mostly a bit higher since traded through BTC from USD/EUR)
  • Average fees are less than $0.01, but theoretically they can be higher (if not average)

For most transactions I would assume the fees are <= $0.02. This would be okay for us, but which crypto currency should we choose?

https://ift.tt/2sg06bE

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more