Meet BigchainDB. The blockchain database.
Several dependencies updated including Flask that had vulnerability.
Removed support for TLSv1 and TLSv1.1 in all NGINX config files. Kept support for TLSv1.2 and added support for TLSv1.3. Pull Request #2601
Fixed two issues with schema validation. Pull requests #2606 & #2607
@gamjapark and team translated all the BigchainDB root docs into Korean. Pull Request #2603
nginx/nginx.conf
to enable CORS. Pull Request #2580
Fixed a typo in the Kubernetes ConfigMap template. Pull Request #2583
@gamjapark translated the main README.md
file into Korean. Pull Request #2592
Completed the implementation of chain-migration elections (BEP-42). Pull requests #2553, #2556, #2558, #2563 and #2566
Benchmark logs. Pull request #2565
A bug caused by an incorrect MongoDB query. Pull request #2567
There's now better documentation about logs, log rotation, and the server.bind
config setting. Pull requests #2546 and #2575
config.toml
. Pull request #2516
bigchaindb upsert-validator
subcommands) was completely changed and is now fully working. See issue #2372 and all the pull requests it references. Pull requests #2439 and #2440
cryptoconditions
package to a newer one. Pull request #2494
@danacr - Pull request #2447
The docs section titled "Production Deployment Template" was renamed to "Kubernetes Deployment Template" and we no longer consider it the go-to deployment template. The "Simple Deployment Template" is simpler, easier to understand, and less expensive (unless you are with an organization that already has a big Kubernetes cluster).
0.22.3
-> 0.22.8
. Pull request #2429.Fixed a bug in transaction validation. For some more-complex situations, it would say that a valid transaction was invalid. This bug was actually fixed before; it was issue #1271. The unit test for it was turned off while we integrated Tendermint. Then the query implementation code got changed, reintroducing the bug, but the unit test was off so the bug wasn't caught. When we turned the test back on, shortly after releasing Beta 2, it failed, unveiling the bug. Pull request #2389