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
| cw1 |[](https://crates.io/crates/cw1)|[](https://docs.rs/cw1)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
8
-
| cw2 |[](https://crates.io/crates/cw2)|[](https://docs.rs/cw2)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
9
-
| cw3 |[](https://crates.io/crates/cw3)|[](https://docs.rs/cw3)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
10
-
| cw4 |[](https://crates.io/crates/cw4)|[](https://docs.rs/cw4)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
11
-
| cw20 |[](https://crates.io/crates/cw20)|[](https://docs.rs/cw20)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
| cw-controllers |[](https://crates.io/crates/cw-controllers)|[](https://docs.rs/cw-controllers)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
| cw1 |[](https://crates.io/crates/cw1)|[](https://docs.rs/cw1)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
8
+
| cw2 |[](https://crates.io/crates/cw2)|[](https://docs.rs/cw2)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
9
+
| cw3 |[](https://crates.io/crates/cw3)|[](https://docs.rs/cw3)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
10
+
| cw4 |[](https://crates.io/crates/cw4)|[](https://docs.rs/cw4)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
11
+
| cw20 |[](https://crates.io/crates/cw20)|[](https://docs.rs/cw20)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
| cw-controllers |[](https://crates.io/crates/cw-controllers)|[](https://docs.rs/cw-controllers)|[](https://codecov.io/gh/CosmWasm/cw-plus)|
@@ -57,7 +58,7 @@ The most reusable components are the various cwXYZ specifications under
57
58
`packages`. Each one defines a standard interface for different domains,
58
59
e.g. [cw20](./packages/cw20/README.md) for fungible tokens,
59
60
[cw721](https://github.com/CosmWasm/cw-nfts/blob/main/packages/cw721/README.md) for non-fungible tokens,
60
-
[cw1](./packages/cw1/README.md) for "proxy contracts", etc.
61
+
[cw1](./packages/cw1/README.md) for "proxy contracts", etc.
61
62
The interface comes with a human description in the READMEs, as well
62
63
as Rust types that can be imported.
63
64
@@ -68,8 +69,7 @@ the real bonus of specifications, we can create an escrow contract that
68
69
can handle many different fungible tokens, as long as they all adhere to
69
70
the cw20 specification.
70
71
71
-
If you have ideas for new specifications or want to make enhancements to
72
-
existing spec, please [raise an issue](https://github.com/CosmWasm/cw-plus/issues)
72
+
If you have ideas for new specifications , please [raise an issue](https://github.com/CosmWasm/cw-plus/issues)
73
73
or [create a pull request](https://github.com/CosmWasm/cw-plus/pulls) on this repo.
74
74
75
75
## Contracts
@@ -84,42 +84,42 @@ contract you want to build on it.
84
84
85
85
CW1 Proxy Contracts:
86
86
87
-
*[`cw1-whitelist`](./contracts/cw1-whitelist) a minimal implementation of `cw1`
88
-
mainly designed for reference.
89
-
*[`cw1-subkeys`](./contracts/cw1-subkeys) a simple, but useful implementation,
90
-
which lets us use a proxy contract to provide "allowances" for native tokens
91
-
without modifying the `bank` module.
87
+
-[`cw1-whitelist`](./contracts/cw1-whitelist) a minimal implementation of `cw1`
88
+
mainly designed for reference.
89
+
-[`cw1-subkeys`](./contracts/cw1-subkeys) a simple, but useful implementation,
90
+
which lets us use a proxy contract to provide "allowances" for native tokens
91
+
without modifying the `bank` module.
92
92
93
93
CW3 Multisig:
94
94
95
-
*[`cw3-fixed-multisig`](./contracts/cw3-fixed-multisig) a simple implementation of the
96
-
[cw3 spec](./packages/cw3/README.md). It is a multisig with a fixed set of addresses,
97
-
created upon initialization.
98
-
Each address may have the same weight (K of N), or some may have extra voting
99
-
power. This works much like the native Cosmos SDK multisig, except that rather
100
-
than aggregating the signatures off chain and submitting the final result,
101
-
we aggregate the approvals on-chain.
102
-
*[`cw3-flex-multisig`](./contracts/cw3-flex-multisig) builds on cw3-fixed-multisig,
103
-
with a more powerful implementation of the cw3 spec. It's a multisig contract
104
-
backed by a cw4 (group) contract, which independently maintains the voter set.
95
+
-[`cw3-fixed-multisig`](./contracts/cw3-fixed-multisig) a simple implementation of the
96
+
[cw3 spec](./packages/cw3/README.md). It is a multisig with a fixed set of addresses,
97
+
created upon initialization.
98
+
Each address may have the same weight (K of N), or some may have extra voting
99
+
power. This works much like the native Cosmos SDK multisig, except that rather
100
+
than aggregating the signatures off chain and submitting the final result,
101
+
we aggregate the approvals on-chain.
102
+
-[`cw3-flex-multisig`](./contracts/cw3-flex-multisig) builds on cw3-fixed-multisig,
103
+
with a more powerful implementation of the cw3 spec. It's a multisig contract
104
+
backed by a cw4 (group) contract, which independently maintains the voter set.
105
105
106
106
CW4 Group:
107
107
108
-
*[`cw4-group`](./contracts/cw4-group) a basic implementation of the
109
-
[cw4 spec](./packages/cw4/README.md). It handles elected membership, by admin or multisig.
110
-
It fulfills all elements of the spec, including raw query lookups,
111
-
and is designed to be used as a backing storage for [cw3 compliant contracts](./packages/cw3/README.md).
112
-
*[`cw4-stake`](./contracts/cw4-stake) a second implementation of the
113
-
[cw4 spec](./packages/cw4/README.md). It fulfills all elements of the spec, including raw query lookups,
114
-
and is designed to be used as a backing storage for [cw3 compliant contracts](./packages/cw3/README.md).
115
-
It provides a similar API to [`cw4-group`], but rather than appointing members,
116
-
their membership and weight are based on the number of staked tokens they have.
108
+
-[`cw4-group`](./contracts/cw4-group) a basic implementation of the
109
+
[cw4 spec](./packages/cw4/README.md). It handles elected membership, by admin or multisig.
110
+
It fulfills all elements of the spec, including raw query lookups,
111
+
and is designed to be used as a backing storage for [cw3 compliant contracts](./packages/cw3/README.md).
112
+
-[`cw4-stake`](./contracts/cw4-stake) a second implementation of the
113
+
[cw4 spec](./packages/cw4/README.md). It fulfills all elements of the spec, including raw query lookups,
114
+
and is designed to be used as a backing storage for [cw3 compliant contracts](./packages/cw3/README.md).
115
+
It provides a similar API to [`cw4-group`], but rather than appointing members,
116
+
their membership and weight are based on the number of staked tokens they have.
117
117
118
118
CW20 Fungible Tokens:
119
119
120
-
*[`cw20-base`](./contracts/cw20-base) a straightforward, but complete
121
-
implementation of the cw20 spec along with all extensions. Can be deployed
122
-
as-is, or imported by other contracts.
120
+
-[`cw20-base`](./contracts/cw20-base) a straightforward, but complete
121
+
implementation of the cw20 spec along with all extensions. Can be deployed
122
+
as-is, or imported by other contracts.
123
123
124
124
## Compiling
125
125
@@ -173,6 +173,10 @@ analyze this package, which gives much faster turn-around:
173
173
Note that it will produce a code coverage report for the entire project, but only the coverage in that
174
174
package is the real value. If does give quick feedback for you if you unit test writing was successful.
175
175
176
+
## Contributing
177
+
178
+
See our [Contributing Guidelines](CONTRIBUTING.md).
179
+
176
180
## Generating changelog
177
181
178
182
To generate a changelog we decided to use [github-changelog-generator](https://github.com/github-changelog-generator/github-changelog-generator).
@@ -202,7 +206,6 @@ auto-detect the latest version tag for you, with --latest-tag.
202
206
203
207
This repo is licensed under [Apache 2.0](./LICENSE).
204
208
205
-
All *specifications* will always be Apache-2.0. All contracts that are
206
-
meant to be *building blocks* will also be Apache-2.0. This is along
209
+
All _specifications_ will always be Apache-2.0. All contracts that are
210
+
meant to be _building blocks_ will also be Apache-2.0. This is along
207
211
the lines of Open Zeppelin or other public references.
0 commit comments