mirror of
https://github.com/bigchaindb/js-bigchaindb-driver.git
synced 2024-11-22 01:36:56 +01:00
include BigchainDB2.0 in README
This commit is contained in:
parent
7699e14705
commit
9023d061dd
@ -18,6 +18,7 @@
|
||||
| `0.10` | `0.1.x` |
|
||||
| `1.0.0` | `0.3.x` |
|
||||
| `>= 1.3.0` | `3.x.x` |
|
||||
| `>= 2.0.0` | `4.x.x` |
|
||||
|
||||
## Breaking changes
|
||||
Version 3.2 of BigchainDB JavaScript Driver introduces a new way of creating transfer transactions. Check [older versions](https://docs.bigchaindb.com/projects/js-driver/en/latest/readme.html#features)
|
||||
|
@ -44,9 +44,7 @@ Compatibility Matrix
|
||||
Older versions
|
||||
--------------------
|
||||
|
||||
#### Versions 4.x.x
|
||||
|
||||
|
||||
**Version 4.x.x**
|
||||
|
||||
As part of the changes in the BigchainDB 2.0 server, some endpoint were
|
||||
modified. In order to be consistent with them, the JS driver does not have
|
||||
@ -61,7 +59,7 @@ being sure that the transaction is validated and commited to a block, so
|
||||
there will not be any issue if you try to transfer the asset immediately.
|
||||
|
||||
|
||||
#### Versions 3.2.x
|
||||
**Version 3.2.x**
|
||||
|
||||
For versions below 3.2, a transfer transaction looked like:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user