Bitcart is 7 years old and Bitcart 0.10.3.0 released! As well as frontend source repository and cloudflare/behind reverse proxy guides!
After so many years I am happy that Bitcart is the most feature-polished solution out there, with some solutions implemented that even big companies struggle/don't implement.
Thanks to our community members helping troubleshoot issues together, and to everyone spreading the word!
It's hard to imagine that it was created that long ago, but I think it proves that we're there for the long run
Let's have many more amazing years together, and let's together spread the word about Bitcart!
We will try to increase our visibility to outside users, as using Bitcart is getting easier and easier for new users
Thank you!
See details below:
Bitcart now supports lightning network with both CLN and LND/LNDHub via Lightning Network + plugin!
LNBits supported as well, with more to come upon user request
This is additional to built-in Electrum lightning node
Available from plugin marketplace now
docs.bitcart.ai/guides/light…
Docs: Bitcart deployment guides about cloudflare and behind reverse proxy deployment
We spend countless hours to figure out the best and most secure out there approach to running Bitcart directly, Bitcart behind cloudflare, Bitcart with your own reverse proxy in the easiest way possible (or even cloudflare+reverseproxy)
This is now all documented in our new guides:
docs.bitcart.ai/proxying-bit…docs.bitcart.ai/proxying-bit…
Rewind: 1 Year Of Plugins
Exactly 1 year ago was Bitcart version 0.9.0.0, which introduced plugins support
This was a big change which changed the project forever, allowing it to be infinitely extensive.
The release of ETH plugin has been an important milestone in making sure the project is sustainable and allows us to add more features quickly. Alone I would have been unable to complete all the required frontend work, but thanks to the funds from ETH plugin we are able to have an advanced UI kit and frontend which will soon power all Bitcart deployments. So if you're considering whether to buy ETH plugin, know that it is not just a "paywalled feature", it solves a real limitation of blockchain in an innovative way, and it directly speeds up addition of new features to Bitcart in the best way possible.
Release: Bitcart Frontend Monorepo Public Release
For the last few months, thanks to people who bought ETH plugin, we were working on creating a new design system, UI kit and foundations for the future new admin panel and store.
Right now we have ported our landing website and directory to it. It might not seem much, but most of the components required for building a functional admin panel are already there: only e.g. datatable is needed to be added
We are starting our work on the new Checkout page, then Admin panel, and then new Store POS interfaces
github.com/bitcart/bitcart-f…
Improvement: Optimize admin and store operations
Optimize container networking: now admin and store no longer talk to API via publicly-accessible API url but prefer to use container networking if possible. This means that Bitcart should work properly in more usecases, initial load times are faster (especially over onion domains), and for example, if you use cloudflare, you no longer need to whitelist your own server ip in the firewall.
Optimize initial admin and store loading: to protect from web scrapers taking down API, if initial request is a 404 request, admin and store no longer fetch details from API server-side. It is loaded up on client-side in browser in such cases. For end users it doesn't impact the experience at all, but those who call server non-interactively (automated bots) will no longer trigger any useless data loading. This greatly optimizes API stability.
Add validation for invalid payout amounts (< 0)
Improvement: Massively reworked docker deployments
Our nginx deployments configs were massively refactored and improved in security.
All our deployment guides will be updated with the new recommended, even easier instructions on how to run Bitcart directly, or behind cloudflare, or with your own reverse proxy. All combinations were tested for and we figured out the optimal settings for each. Client ip address is now correctly detected in nginx access logs and in Bitcart API running. This is essential for features like reset password protection against attackers.
Add support for ready deployment presets, for example:
./setup.sh --preset cloudflare
Properly configures your instance to work under cloudflare.
Currently 4 presets are supported:
cloudflare Bitcart runs behind cloudflare directly
cloudflare-proxied Your server runs another reverse proxy, and Bitcart is behind that reverse proxy
proxied Bitcart is behind a reverse proxy that is not cloudflare (requires PROXY protocol)
proxied-legacy Bitcart is behind a reverse proxy that is not cloudflare (requires X-Forwarded-For HTTP header)
Proxyprotocol support via REVERSEPROXY_PROXYPROTOCOL - this is the recommended approach if you are running another reverse proxy on your server, more information in deployment guides.
Fix issues where when switching from BITCART_REVERSEPROXY nginx-https to nginx bitcart still tried to use ssl certificates.
SSL policy updates: drop TLS1 and TLS 1.1 and refresh SSL ciphers. This prevented connecting to cloudflare directly before. Now our SSL setup is modern and secure.
Enable gzip compression of API responses (this works seamlessly with any client). It should reduce the amount of data sent over the network.
Nginx configs are now nicely formatted.
Add generator.bitcart.ai - experimental demo site where you can choose your settings and generate a ready docker-compose.yml file.
Note that this is more for preview of what is generated or usage on specialized services where you need to upload docker-compose.yml file.
It is still recommended to use our docker deployment scripts for ease of use (and plugins support).
Trusted IP presets (with cloudflare support) for proper display of client ip address.
Nginx docker image in use is now bitcart/nginx with additional modules installed to allow our advanced secure config to work.
Proper support for cases when containers are running in multiple networks (e.g. if you run opentelemetry monitoring).
Enable keepalive for connections to bitcart API and frontend components: this should allow for faster and more efficient requests to APIs.
Improve security of reverse proxy: only if ip address is trusted, and if a header is known to be properly validated by the trusted ip address (e.g. cloudflare), it is passed to client unmodified. Otherwise it is replaced with a safe value.
Add support for JSON logs in nginx.
Fixes for default server when there are multiple servers hosted.
Improve handling of the case when ssl certificate is not yet ready, it now rejects ssl handshake.
Update acme.sh letsencrypt certificate manager to latest version
Improvement: Proper contract transfers detection of any complexity
As smart contract events are unreliable for tracking smart contract transfers, a few releases ago we switched to a more reliable parsing approach. This ensures that no transaction is ever missed because we parse blockchain directly and not events. But it made us not being able to parse complex transfers, for example Binance or Coinbase batching transactions in one. Now we found a reliable way to parse those, with no action required from your end. It means that we now parse any complexity transfers automatically.
Hi everyone! If you have a minute of free time, could you please leave a review of Bitcart? That would help a lot!
forms.gle/sMQwMV6Loou7wcsKA
We are collecting details on new features you would like, bugs to be fixed, and suggestions for the upcoming admin panel!
Next bitcart-cli release provides amazing tools for plugin authors to start their journey!
The hardest thing was to perform initial setup. Now, via interactive guide you can easily create plugin scaffolding and even link it to your development environment!
youtu.be/-hFjY5_v_nA
Getting started guide (4 pages) was replaced with a single, more concise page which displays up-to-date information on how to go from the process of deployment to creation of your first invoice:
docs.bitcartcc.com/your-firs…
BitcartCC deployment guides have been fully updated (and most of them re-written) as part of our efforts to give our docs an refreshed look
Check out the updated experience!
docs.bitcartcc.com/deploymen…
Your kind words of support, your attempts to try it out and your success stories - that's what makes me happy every day
Thank you everyone!
The project will continue to improve, and in 2022 there will be way more amazing features to add!
Maybe there were not that much updates, but this year we had our biggest release ever (0.6.0.0)!
Looking at BitcartCC now, I am happy to see that it is convenient to use and that more and more people start to provide their feedback and try it out