You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Compatibility**: Last merge from `cosmos/gaia` was `090c545347b03e59415a18107a0a279c703c8f40` (Jan 23, 2020)
17
-
18
18
## Supported Systems
19
19
20
20
The supported systems are limited by the dlls created in [`go-cosmwasm`](https://github.com/CosmWasm/go-cosmwasm). In particular, **we only support MacOS and Linux**.
@@ -38,16 +38,21 @@ and everything with `v0.7.x` tags is compatible with each other.
38
38
We will have a series of minor version updates prior to `v1.0.0`,
39
39
where we offer strong backwards compatibility guarantees.
40
40
41
-
We are currently on `v0.9`and targeting `v0.10` for late July, at which point
42
-
we will have feature freeze for the `v1` tag and only perform needed bugfixes
43
-
(which may be API breaking).
41
+
We released `v0.10` on July 31, 2020, and have a `v1.0` feature freeze now.
42
+
We will be performing bug fixes, security patches, and performance improvements,
43
+
but the API should be stable and compatible with `v1.0`.
44
44
45
45
Thank you to all projects who have run this code in your testnets and
46
46
given feedback to improve stability.
47
47
48
48
## Encoding
49
49
50
-
We use standard cosmos-sdk encoding (amino) for all sdk Messages. However, the message body sent to all contracts, as well as the internal state is encoded using JSON. Cosmwasm allows arbitrary bytes with the contract itself responsible for decodng. For better UX, we often use `json.RawMessage` to contain these bytes, which enforces that it is valid json, but also give a much more readable interface. If you want to use another encoding in the contracts, that is a relatively minor change to wasmd but would currently require a fork. Please open in issue if this is important for your use case.
50
+
We use standard cosmos-sdk encoding (amino) for all sdk Messages. However, the message body sent to all contracts,
51
+
as well as the internal state is encoded using JSON. Cosmwasm allows arbitrary bytes with the contract itself
52
+
responsible for decodng. For better UX, we often use `json.RawMessage` to contain these bytes, which enforces that it is
53
+
valid json, but also give a much more readable interface. If you want to use another encoding in the contracts, that is
54
+
a relatively minor change to wasmd but would currently require a fork. Please open in issue if this is important for
0 commit comments