Search content
Sort by
Showing 20 of 30 results by overtorment2
Re: Cashier-BTC: Process Bitcoin payments on your end, paying zero commissions
OK another stupid question, because I'm not sure I totally get what's in the README...
After creating a seller, if I remove his WIF and replace the pubkey with a cold storage address, it will never be overwritten?
After creating a seller, if I remove his WIF and replace the pubkey with a cold storage address, it will never be overwritten?
Happy to help!
Absolutely, once the database record for seller exists - it is never overwritten.
Re: Cashier-BTC: Process Bitcoin payments on your end, paying zero commissions
Hi,
First of all, thank you for your excellent work. I was looking for a full-node based self-hosted payment solution for several of my companies and it fits perfectly.
I'm testing it since yesterday but I'm running into a few minor issues :
Don't hesitate to ask me for more info
First of all, thank you for your excellent work. I was looking for a full-node based self-hosted payment solution for several of my companies and it fits perfectly.
I'm testing it since yesterday but I'm running into a few minor issues :
- I made small payments to test (0.0001 BTC) which seem to be equal to the fee to transfer to the merchant account, so I'm getting stuck in a loop of
Code:
worker2.js address: XXX expect: 0.0001 confirmed: 0.0001 unconfirmed: 0.0001
worker2.js transferring 0.0001 BTC (minus fee) from XXX to seller XXX ( XXX )
worker2.js broadcasting XXX
worker2.js transferring 0.0001 BTC (minus fee) from XXX to seller XXX ( XXX )
worker2.js broadcasting XXX
- Is there a way to cleanup old payment requests ? I have a few of those looping in the logs of worker.js
Code:
worker.js address: XXX expect: 0.001 confirmed: 0 unconfirmed: 0
worker.js address: XXY expect: 0.001 confirmed: 0 unconfirmed: 0
worker.js address: XXZ expect: 0.001 confirmed: 0 unconfirmed: 0
worker.js address: XXW expect: 0.001 confirmed: 0 unconfirmed: 0
worker.js address: XXY expect: 0.001 confirmed: 0 unconfirmed: 0
worker.js address: XXZ expect: 0.001 confirmed: 0 unconfirmed: 0
worker.js address: XXW expect: 0.001 confirmed: 0 unconfirmed: 0
- I don't know if it's a consequence of the items above, but I created new payment requests which were paid and arrived in the sub-addresses (I can see them in bitcoin-cli listaddressgroupings) but they are not transferred to the seller account, no trace of them in cashier-btc-out.log
Don't hesitate to ask me for more info
Hey!
Super small payments are kind of an issue. The fee to aggregate payments is hardcoded here
https://github.com/Overtorment/Cashier-BTC/blob/f0fb18c8186f87373c267b1a7e7b42daedb6449d/worker2.js#L54
I suggest you change it to a smaller amount (it's currently 0.0001) or deal with such payments manually (the WIF for the hot address is in the database).
Old requests are being re-checked for 24 hours. That's configurable in config https://github.com/Overtorment/Cashier-BTC/blob/master/config.js.dev
You can lower that to your taste, but everything works okay with the way it is.
If you really want to cleanup old requests, you need to write a small script for that, but that's not a very good idea. Occasionally clients
might be paying to some old addresses.
The third question I didn't quite understand.
Probably the payment requests are old enough (>24h) to be ignored by worker.
You can always check out whats wrong with the payment request right in the database.
Released to Appstore. Apple gives hard times...
APPLE APPSTORE LINK: https://itunes.apple.com/us/app/bluewallet-bitcoin-wallet/id1376878040?l=ru&ls=1&mt=8
Official website: http://bluewallet.io/
APPLE APPSTORE LINK: https://itunes.apple.com/us/app/bluewallet-bitcoin-wallet/id1376878040?l=ru&ls=1&mt=8
Official website: http://bluewallet.io/
BIP21 support added. Wallet available on https://expo.io/@overtorment/bluewallet
Native iOS Appstore build is on the way
Native iOS Appstore build is on the way
Also,
https://github.com/Overtorment/BlueWallet (ios wallet)
https://github.com/Overtorment/cli-cold-wallet (paper wallet)
disclaimer: all made by me
https://github.com/Overtorment/BlueWallet (ios wallet)
https://github.com/Overtorment/cli-cold-wallet (paper wallet)
disclaimer: all made by me
Re: Lost the last word of my Metamask seed (please help)
Well, making a bruteforcer is rather easy. Brutforcer should not only check the validity of the seed, but also the fact that there are any transactions on derived addresses.
This is pretty trivial, and might be outsourced to a freelancer.
This is pretty trivial, and might be outsourced to a freelancer.
Re: iOS BlueWallet (possibly Android in future). Opensource.
Are you planning on implementing Hardware Wallet support for Ledger and/or Trezor wallets in the future?
Probably, but I haven't implemented 12/24 seed recovery yet. only private keys for now.
Looks nice!
Opensource is a right way to go, I hope you'll create some dev community with this project.
How could I backup my wallet or restore it? What if I lost or broke my phone?
Opensource is a right way to go, I hope you'll create some dev community with this project.
Quote
Private keys never leave your device
How could I backup my wallet or restore it? What if I lost or broke my phone?
There's an export feature, so you can backup your private keys in WIF format
I'm working on opensource iOS Bitcoin wallet. Anyone can build it and run it (if you care typing a couple of commands on terminal). SegWit-ready; Replace-By-Fee implemented; arbitrary fees. Built with ReactNative & Expo.
APPLE APPSTORE LINK: https://itunes.apple.com/us/app/bluewallet-bitcoin-wallet/id1376878040?l=ru&ls=1&mt=8
Official website: http://bluewallet.io/
And the reason I started working on it is because I was unhappy with BreadWallet.
---> Heres the link: https://github.com/Overtorment/BlueWallet <---
I'm working on getting it to the Appstore (got issues with Apple moderators), but meanwhile it's trivial to run it with Explo Launcher.
Just install Expo from Appstore, and launch BlueWallet either from dedicated hosted page here https://expo.io/@overtorment/bluewallet
or from your localhost (build from sources).
Beta, but pretty usable (use it myself in the first place). Still, don't store large amounts. Would really love some contributions on the project. It's ReactNative which means Javascript is used a lot, so if you wanted to jump in Bitcoin development - nows the chance.
PS. I'm thinking about making it an official thread where I'll post news and updates.
APPLE APPSTORE LINK: https://itunes.apple.com/us/app/bluewallet-bitcoin-wallet/id1376878040?l=ru&ls=1&mt=8
Official website: http://bluewallet.io/
And the reason I started working on it is because I was unhappy with BreadWallet.
---> Heres the link: https://github.com/Overtorment/BlueWallet <---
I'm working on getting it to the Appstore (got issues with Apple moderators), but meanwhile it's trivial to run it with Explo Launcher.
Just install Expo from Appstore, and launch BlueWallet either from dedicated hosted page here https://expo.io/@overtorment/bluewallet
or from your localhost (build from sources).
Beta, but pretty usable (use it myself in the first place). Still, don't store large amounts. Would really love some contributions on the project. It's ReactNative which means Javascript is used a lot, so if you wanted to jump in Bitcoin development - nows the chance.
PS. I'm thinking about making it an official thread where I'll post news and updates.
MetaMetaMeta! Token
Meta-mining on ethereum network concept
DAPP hosted here : https://overtorment.github.io/MetaMining/
Yo dawg. I heard you like mining... So I put a PoW mining inside Ethereum ERC20 token so you can mine tokens while you mine Ether!
Imagine standard ERC20-compliant token on Ethereum platform. Now, lets add simple proof-of-work check inside token contract, and reward whoever solves the PoW task with tokens. Bam! You've got lightweight implementation of Bitcoin on top of Ethereum. Isn't it meta?
Ofcourse its just for fun only. Mining (spending computational resources) doesn't protect the network from attacks (Ethereum network is already protected with its own mining), so it's only a tokens distribution to miner (and those tokens are useless and worth nothing).
Bonus! You can mine in your browser. I made a tiny Dapp for that. Requires Metamask plugin.
M4K3 M1N1ИG GЯE4T 4G41И!
Current specs
I need your oppinion and feedback on this.
PS. Opensourced here https://github.com/Overtorment/MetaMining License:WTFPL.
Meta-mining on ethereum network concept
DAPP hosted here : https://overtorment.github.io/MetaMining/
Yo dawg. I heard you like mining... So I put a PoW mining inside Ethereum ERC20 token so you can mine tokens while you mine Ether!
Imagine standard ERC20-compliant token on Ethereum platform. Now, lets add simple proof-of-work check inside token contract, and reward whoever solves the PoW task with tokens. Bam! You've got lightweight implementation of Bitcoin on top of Ethereum. Isn't it meta?
Ofcourse its just for fun only. Mining (spending computational resources) doesn't protect the network from attacks (Ethereum network is already protected with its own mining), so it's only a tokens distribution to miner (and those tokens are useless and worth nothing).
Bonus! You can mine in your browser. I made a tiny Dapp for that. Requires Metamask plugin.
M4K3 M1N1ИG GЯE4T 4G41И!
Current specs
- 2.5 min block time (I know, there's no blocks here, its just a figure of speech)
- Block reward: 5 tokens
- Decimals: 8 (digits after dot)
- Halving each: 210,000 blocks (1 year?)
- Difficulty retarget: each block; simple (exactly as in bitcoin-core)
- Algo: sha3 (aka keccak256)
- Max cap: count yourself (mining wont stop after 64 halvings as in bitcoin-core)
I need your oppinion and feedback on this.
PS. Opensourced here https://github.com/Overtorment/MetaMining License:WTFPL.
It is a good idea and i too had a similar idea. But the gas that has to be paid as the transaction fee is the problem here. How much gas is required for mining each coin?
Haven't checked it. Why don't you mine one coin and see for yourself?
Question about addresses - different addresses controlled by single private key
⭐ Merited by ETFbitcoin (2)
To my understanding, I can generate 3 (4??) different addresses from my private key:
* Legacy address 1ABCDE..... (plus one in uncompressed format)
* Segwit P2SH address 3ABCDE....
* Segwit Bech32 address bc1ABCDE....
*
P2SH multisig address (1-out-of-1) 3ABCDE.... - unsure
I can send coins to all of those addresses, and to 3rd party observer that will look like balances on different unrelated addresses.
If I'm correct, are there any flaws or security risks in this?
And if I'm importing private key to some kind of wallet software, how wallet determines which address to scan on blockchain and which balance to consider as wallet's balance?
Thank you for your answers, I realize there are chances this is a pretty dumb question :-)
* Legacy address 1ABCDE..... (plus one in uncompressed format)
* Segwit P2SH address 3ABCDE....
* Segwit Bech32 address bc1ABCDE....
*
P2SH multisig address (1-out-of-1) 3ABCDE.... - unsureI can send coins to all of those addresses, and to 3rd party observer that will look like balances on different unrelated addresses.
If I'm correct, are there any flaws or security risks in this?
And if I'm importing private key to some kind of wallet software, how wallet determines which address to scan on blockchain and which balance to consider as wallet's balance?
Thank you for your answers, I realize there are chances this is a pretty dumb question :-)
I made a cli cold walled generator for console nerds like you and me!
Long story short: https://github.com/Overtorment/cli-cold-wallet
Screenshot:
Example output:
Thinking whether to add segwit...
Screenshot:
Example output:
Code:
burn@laptop2:~/Documents/cli-cold-wallet$ nodejs cli-cold-wallet.js
┌────────────────────────────────────┬──────────────────────────────────────────────────────┬──────────────────────────────────────────────────────┐
│ BITCOIN PUBLIC ADDRESS │ │ BITCOIN PRIVATE KEY (WIF) │
├────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┤
│ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ │ ▄▄▄▄█████▄▄▄ │ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ │
│ █ ▄▄▄▄▄ █▄▀▀▄▄██▄ ▄▀▀▄█ ▄▄▄▄▄ █ │ ▄███████████████████▄ │ █ ▄▄▄▄▄ █▀ ▄▀▀▀▀ ███▄█ ▄▄▄▄▄ █ │
│ █ █ █ ███▄█ ██▄ ▀█▄ █ █ █ █ │ ▄█████▀▀ ▀██████▄ │ █ █ █ █▀▄▀ ▀█ ▀▄▀▄ ▀█ █ █ █ │
│ █ █▄▄▄█ ██▄▀▄▀█▄ ▀▄▀█ █▄▄▄█ █ │ ▄████▀ ▄ ▄▄ ▀████▄ │ █ █▄▄▄█ █▀ ▄▀▀█▀▄▄▀▄▄█ █▄▄▄█ █ │
│ █▄▄▄▄▄▄▄█ █ ▀▄▀▄▀ █▄█ █▄▄▄▄▄▄▄█ │ ▄████ ▐██ ▐██ ▀████ │ █▄▄▄▄▄▄▄█▄▀▄█ █▄▀ █▄▀▄█▄▄▄▄▄▄▄█ │
│ █ ▄▀ ▄█▄██ ▄▄▀ ██ ▀█▄▄█▄▀▀▀▀▀ █ │ ▄███▀ ▐████████████▄▄▄ ████ │ █▄▄ ▄█▄▄▄▄█ ▄█ ▀▀▄▄█▀▄▀ ▀ █ ▀█ │
│ █ ▄█ ▀▀▄▄▀▀ ▀ █▄▀ ▀▄ ▄ ▄▀█▀██ │ ▐███▀ ▐████ ▀████▄ ████ │ █ ▀██ ▄▀▀█▄▀█▄▄ ▀▄ ▀▄█▀▄▄▀▄▀▀█ │
│ █▀███ ▄▄▀▄█▄▄ ▀ ▀▄▀▀▄█ █▀▀ ▄▄█ │ ████ ▐████ ▐████ ████ │ ███ █▀█▄▀▄▄▄▀▀█▄ ▀▀▀▄▀▀▀ ▀███▀█ │
│ █ ▄▀█▀▄▀█▄▀ ▄▄█▄███▄▀▀ ▄▀▀ █▄█ │ ▐███▌ ▐████▄▄▄▄▄███▀ ████ │ ██ █▄▀█▄▀▀ ▀█ █▀ ▄██▀▀█ █▄ █▀▀█ │
│ █ ▄▀▄▄ ▀▀▀▀▀▀ █████▀███ ▄ ██ │ ▐███ ▐████▀▀▀▀▀█████ ████ │ █ ▀ ▄▀▀▄▄▀█████▄█▀▄▀▄▀▀█ ▀ ▄▄▀█ │
│ █ █ █▄██ ▄▀█▀ ▄█ ▄█ █ ▀█ ▄█ │ ▐███▌ ▐████ ▐████ ████ │ █ █▀███▄▀▀▄ ██▄ ▄█▄▄█▀▄█▄ ▀█ ██ │
│ █▄▄██▄▄▄▄▀ ██▄▄ ▄█▄▀█ ▄▄▄ ▄ ▄█ │ ████ ▐████ ▄████ ▐███▌ │ █▄█▄▄██▄█▀█ ███▄█▀▄▄█ ▄▄▄ █ ▀▄█ │
│ █ ▄▄▄▄▄ ██▄▀█▄█ █ ▄ █▄█ ▄▄██ │ ████ ▄▄██████████████▀ ▐████ │ █ ▄▄▄▄▄ █▄▀████ ▄▄▄█▀ █▄█ ▀▄▀██ │
│ █ █ █ █ ▄█▀▄▄ ██▄▄▄ ▄▄▄ ▄ █ │ ████▄ ▐██ ▐██ ▄████ │ █ █ █ █ ▀▀▄▄▀▀███▄▄▄▄▄▀▄█▀█ │
│ █ █▄▄▄█ █▀▀ █▀▀ ▄█▄▀ █▄▀ █ ▄ █ │ ▀████▄ ▐██ ▐██ ▄████ │ █ █▄▄▄█ █ ▀ █▀█ ▄▀██▀▄█▄▄ ▀▄ ██ │
│ █▄▄▄▄▄▄▄█▄▄▄▄▄██▄▄███▄▄▄█▄▄████ │ ▀█████▄ ▄█████▀ │ █▄▄▄▄▄▄▄█▄▄▄███▄████▄█▄▄▄▄▄████ │
│ │ ▀████████▄▄▄▄▄▄▄███████▀ │ │
│ │ ▀▀█████████████▀▀ │ │
├────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┤
│ DEPOSIT / VERIFY │ │ WITHDRAW │
├────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┤
│ 12CVSYaC5fS8keib3oPJSe1qXEza6u6RMp │ │ L2vfAtjfTaxywoAvXDNKBzTy2Mc7UNKjiDLggBVAGEeQ5UP7hntt │
└────────────────────────────────────┴──────────────────────────────────────────────────────┴──────────────────────────────────────────────────────┘
burn@laptop2:~/Documents/cli-cold-wallet$
┌────────────────────────────────────┬──────────────────────────────────────────────────────┬──────────────────────────────────────────────────────┐
│ BITCOIN PUBLIC ADDRESS │ │ BITCOIN PRIVATE KEY (WIF) │
├────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┤
│ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ │ ▄▄▄▄█████▄▄▄ │ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ │
│ █ ▄▄▄▄▄ █▄▀▀▄▄██▄ ▄▀▀▄█ ▄▄▄▄▄ █ │ ▄███████████████████▄ │ █ ▄▄▄▄▄ █▀ ▄▀▀▀▀ ███▄█ ▄▄▄▄▄ █ │
│ █ █ █ ███▄█ ██▄ ▀█▄ █ █ █ █ │ ▄█████▀▀ ▀██████▄ │ █ █ █ █▀▄▀ ▀█ ▀▄▀▄ ▀█ █ █ █ │
│ █ █▄▄▄█ ██▄▀▄▀█▄ ▀▄▀█ █▄▄▄█ █ │ ▄████▀ ▄ ▄▄ ▀████▄ │ █ █▄▄▄█ █▀ ▄▀▀█▀▄▄▀▄▄█ █▄▄▄█ █ │
│ █▄▄▄▄▄▄▄█ █ ▀▄▀▄▀ █▄█ █▄▄▄▄▄▄▄█ │ ▄████ ▐██ ▐██ ▀████ │ █▄▄▄▄▄▄▄█▄▀▄█ █▄▀ █▄▀▄█▄▄▄▄▄▄▄█ │
│ █ ▄▀ ▄█▄██ ▄▄▀ ██ ▀█▄▄█▄▀▀▀▀▀ █ │ ▄███▀ ▐████████████▄▄▄ ████ │ █▄▄ ▄█▄▄▄▄█ ▄█ ▀▀▄▄█▀▄▀ ▀ █ ▀█ │
│ █ ▄█ ▀▀▄▄▀▀ ▀ █▄▀ ▀▄ ▄ ▄▀█▀██ │ ▐███▀ ▐████ ▀████▄ ████ │ █ ▀██ ▄▀▀█▄▀█▄▄ ▀▄ ▀▄█▀▄▄▀▄▀▀█ │
│ █▀███ ▄▄▀▄█▄▄ ▀ ▀▄▀▀▄█ █▀▀ ▄▄█ │ ████ ▐████ ▐████ ████ │ ███ █▀█▄▀▄▄▄▀▀█▄ ▀▀▀▄▀▀▀ ▀███▀█ │
│ █ ▄▀█▀▄▀█▄▀ ▄▄█▄███▄▀▀ ▄▀▀ █▄█ │ ▐███▌ ▐████▄▄▄▄▄███▀ ████ │ ██ █▄▀█▄▀▀ ▀█ █▀ ▄██▀▀█ █▄ █▀▀█ │
│ █ ▄▀▄▄ ▀▀▀▀▀▀ █████▀███ ▄ ██ │ ▐███ ▐████▀▀▀▀▀█████ ████ │ █ ▀ ▄▀▀▄▄▀█████▄█▀▄▀▄▀▀█ ▀ ▄▄▀█ │
│ █ █ █▄██ ▄▀█▀ ▄█ ▄█ █ ▀█ ▄█ │ ▐███▌ ▐████ ▐████ ████ │ █ █▀███▄▀▀▄ ██▄ ▄█▄▄█▀▄█▄ ▀█ ██ │
│ █▄▄██▄▄▄▄▀ ██▄▄ ▄█▄▀█ ▄▄▄ ▄ ▄█ │ ████ ▐████ ▄████ ▐███▌ │ █▄█▄▄██▄█▀█ ███▄█▀▄▄█ ▄▄▄ █ ▀▄█ │
│ █ ▄▄▄▄▄ ██▄▀█▄█ █ ▄ █▄█ ▄▄██ │ ████ ▄▄██████████████▀ ▐████ │ █ ▄▄▄▄▄ █▄▀████ ▄▄▄█▀ █▄█ ▀▄▀██ │
│ █ █ █ █ ▄█▀▄▄ ██▄▄▄ ▄▄▄ ▄ █ │ ████▄ ▐██ ▐██ ▄████ │ █ █ █ █ ▀▀▄▄▀▀███▄▄▄▄▄▀▄█▀█ │
│ █ █▄▄▄█ █▀▀ █▀▀ ▄█▄▀ █▄▀ █ ▄ █ │ ▀████▄ ▐██ ▐██ ▄████ │ █ █▄▄▄█ █ ▀ █▀█ ▄▀██▀▄█▄▄ ▀▄ ██ │
│ █▄▄▄▄▄▄▄█▄▄▄▄▄██▄▄███▄▄▄█▄▄████ │ ▀█████▄ ▄█████▀ │ █▄▄▄▄▄▄▄█▄▄▄███▄████▄█▄▄▄▄▄████ │
│ │ ▀████████▄▄▄▄▄▄▄███████▀ │ │
│ │ ▀▀█████████████▀▀ │ │
├────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┤
│ DEPOSIT / VERIFY │ │ WITHDRAW │
├────────────────────────────────────┼──────────────────────────────────────────────────────┼──────────────────────────────────────────────────────┤
│ 12CVSYaC5fS8keib3oPJSe1qXEza6u6RMp │ │ L2vfAtjfTaxywoAvXDNKBzTy2Mc7UNKjiDLggBVAGEeQ5UP7hntt │
└────────────────────────────────────┴──────────────────────────────────────────────────────┴──────────────────────────────────────────────────────┘
burn@laptop2:~/Documents/cli-cold-wallet$
Thinking whether to add segwit...
Cashier-BTC: Process Bitcoin payments on your end, paying zero commissions
⭐ Merited by ETFbitcoin (11)
Hi all!
A couple of years ago I was really unhappy with Bitpay, so I coded a universal solution to accept Bitcoin on any website: https://github.com/Overtorment/Cashier-BTC
It is opensource and being used in several companies around the world now (no big names here, afaik). Recently I got tired of high fees and low Segwit adoption and rewrote it completely to support Segwit (P2SH addresses for now, bech32-ready; will be pushed to production, Im waiting for the spec to be formally approved and stripped of 'draft' status). Also, it relies on the one and only Bitcoin Core, so it is completely independent from 3rd parties (and using it helps strengthen the network!)
It does require basic web-development and linux skills to install and use this, but overall it is simple.
If you're unhappy with Bitpay (or any other bitcoin processor), want to enjoy Segwit and low fees, don't want to pay any cut to middlemen - I encourage you to try Cashier-BTC. It's opensource and free.
I also provide free support if you are having any issues, just let me know, would be happy to help. Spreading the word would also help increase merchant adoption!
https://github.com/Overtorment/Cashier-BTC
A couple of years ago I was really unhappy with Bitpay, so I coded a universal solution to accept Bitcoin on any website: https://github.com/Overtorment/Cashier-BTC
It is opensource and being used in several companies around the world now (no big names here, afaik). Recently I got tired of high fees and low Segwit adoption and rewrote it completely to support Segwit (P2SH addresses for now, bech32-ready; will be pushed to production, Im waiting for the spec to be formally approved and stripped of 'draft' status). Also, it relies on the one and only Bitcoin Core, so it is completely independent from 3rd parties (and using it helps strengthen the network!)
It does require basic web-development and linux skills to install and use this, but overall it is simple.
If you're unhappy with Bitpay (or any other bitcoin processor), want to enjoy Segwit and low fees, don't want to pay any cut to middlemen - I encourage you to try Cashier-BTC. It's opensource and free.
I also provide free support if you are having any issues, just let me know, would be happy to help. Spreading the word would also help increase merchant adoption!
https://github.com/Overtorment/Cashier-BTC