Feat/cosmwasm@v3 #11
Feat/cosmwasm@v3 #11
Conversation
|
We could not run your PR Review. We noticed that you are part of an Org. We require everyone who is part of an Org to SignUp via GitHub so we can track your individual usage and maximize on your usage capacity. Enroll into CodeSherlock system by signing up via GitHub using the SignUp link. Also, please note — every user pays for their own usage. |
Codoki - Action neededAlmost there! 🚀 We’ll run this review once you’re connected to Codoki. Quick setup (≈2 minutes):
What you’ll get:
Need help? info@codoki.ai |
Reviewer's GuideThis PR migrates the entire workspace to CosmWasm v3 by bumping crate versions to 0.28.0 and updating dependencies to 3.0.2, enhances documentation through structured markdown tables and layout improvements, and refines the procedural macro implementation by removing an unnecessary derive. Class diagram for updated procedural macro derive in saa-proto-coreclassDiagram
class SAAError {
<<derive(Debug, Error)>>
}
%% Note: PartialEq derive removed in v0.28.0
%% SAAError previously had PartialEq, now only Debug and Error
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Bito Automatic Review Skipped - Draft PR |
|
Bito Automatic Review Skipped - Draft PR |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
Credential specifc features allow you to include / exclude specific credential types for better control and optimisizing the binary size:
The following features give you access to additional logic related to better control or additional security
The following features enable or disable inner primitives to ether help you out or to reduce the binary size as much as possible
The following credentials are not meant to be specified directly and used only internal purposes 🚫
VerificationSingle Credential |
PR Code Suggestions ✨Explore these optional code suggestions:
|
||||||||||||
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey there - I've reviewed your changes - here's some feedback:
- Fix the missing
traitsfeature in the root crate’s Cargo.toml to resolve thecargo packageerror by declaring it under the[features]section. - Clean up duplicated bullet items and stray dash prefixes in the README before the tables to improve list consistency and formatting.
- Double-check the removal of
PartialEqfrom the derive macro inmacros-proto/coreto ensure it was intentional and update any affected tests or code.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Fix the missing `traits` feature in the root crate’s Cargo.toml to resolve the `cargo package` error by declaring it under the `[features]` section.
- Clean up duplicated bullet items and stray dash prefixes in the README before the tables to improve list consistency and formatting.
- Double-check the removal of `PartialEq` from the derive macro in `macros-proto/core` to ensure it was intentional and update any affected tests or code.
## Individual Comments
### Comment 1
<location> `README.md:6` </location>
<code_context>
# Smart Account Authentication
Authentication Library / SDK for working with various crypthograpghic credentials / authenticators
-- Client-side tools for requesting credentials abd their serilizations
-- Verification (+ storage) logic for Rust environments.
</code_context>
<issue_to_address>
**issue (typo):** Typo: 'crypthograpghic' should be 'cryptographic'.
```suggestion
Authentication Library / SDK for working with various cryptographic credentials / authenticators
```
</issue_to_address>
### Comment 2
<location> `README.md:8` </location>
<code_context>
# Smart Account Authentication
Authentication Library / SDK for working with various crypthograpghic credentials / authenticators
-- Client-side tools for requesting credentials abd their serilizations
-- Verification (+ storage) logic for Rust environments.
-- Ideal for smart accounts, wallets and apps with build-in authentication
</code_context>
<issue_to_address>
**issue (typo):** Typos: 'abd' should be 'and', 'serilizations' should be 'serializations'.
```suggestion
- Client-side tools for requesting credentials and their serializations
```
</issue_to_address>
### Comment 3
<location> `README.md:18` </location>
<code_context>
- Formatting data according to specs. Primarily with use of envelopes
- Serialisation and deserialisation of the date depending on context
- Passing data to underlying cryptographic APIs and libraries
-- Dealing with batches / multuple credentials at the same time
-- [FEAT] Protection against replay attacks
-- [FEAT] Encapsulated storage of the credentials
</code_context>
<issue_to_address>
**issue (typo):** Typo: 'multuple' should be 'multiple'.
```suggestion
- Dealing with batches / multiple credentials at the same time
```
</issue_to_address>
### Comment 4
<location> `README.md:25` </location>
<code_context>
- [FEAT] Encapsulated reconstruction & verification of credentials from payload
### Cryptography
-- ⚡ Delegations verifcation to available APIs for efficency
+
+- ⚡ Delegations verifcation to available APIs for efficency
</code_context>
<issue_to_address>
**issue (typo):** Typos: 'verifcation' should be 'verification', 'efficency' should be 'efficiency'.
```suggestion
- ⚡ Delegations verification to available APIs for efficiency
```
</issue_to_address>
### Comment 5
<location> `README.md:30` </location>
<code_context>
### Other Info
-- **Encoding:** By default using `base64` everywhere. The exceptions are primarily when it makes sence according to the specs of a credential such as Eth addresses using `hex` or webauthn challenge using `base64url`
-
-
</code_context>
<issue_to_address>
**issue (typo):** Typo: 'sence' should be 'sense'.
```suggestion
-- **Encoding:** By default using `base64` everywhere. The exceptions are primarily when it makes sense according to the specs of a credential such as Eth addresses using `hex` or webauthn challenge using `base64url`
```
</issue_to_address>
### Comment 6
<location> `README.md:83` </location>
<code_context>
+| ``solana`` | Solana programs (BPF) | In Development |
-Credential specifc features allow you to include / exclude specific credential types for better control and optimisizing the binary size
+Credential specifc features allow you to include / exclude specific credential types for better control and optimisizing the binary size:
-- `ethereum` - for Ethereum personal sign message specification ( [EIP-191](https://eips.ethereum.org/EIPS/eip-191) )
</code_context>
<issue_to_address>
**issue (typo):** Typos: 'specifc' should be 'specific', 'optimisizing' should be 'optimizing'.
```suggestion
Credential specific features allow you to include / exclude specific credential types for better control and optimizing the binary size:
```
</issue_to_address>
### Comment 7
<location> `README.md:185` </location>
<code_context>
### Basics
Requsting a credemtial is as simple as calling a function with a message to be signed and passing the neccecary signer information
+
```typescript
</code_context>
<issue_to_address>
**issue (typo):** Typos: 'Requsting' should be 'Requesting', 'credemtial' should be 'credential', 'neccecary' should be 'necessary'.
```suggestion
Requesting a credential is as simple as calling a function with a message to be signed and passing the necessary signer information
```
</issue_to_address>
### Comment 8
<location> `README.md:257` </location>
<code_context>
### Meta / Usage
-- OpenSource -> Low Funding / Resources -> Contributions are especially needed and welcomed
-- Authors of the library are also its main users. The expirience is iteratively used to improve the SDK by understaning the needs and shifting more and more logic from apps to the lib.
-- `CosmWasm` retains the status of the primary target and used the most often during feature design stage and for tests. The main reason is being funded through quadrating funding on [DoraHacks](https://dorahacks.io/aez).
-
</code_context>
<issue_to_address>
**issue (typo):** Typos: 'expirience' should be 'experience', 'understaning' should be 'understanding'.
```suggestion
-- Authors of the library are also its main users. The experience is iteratively used to improve the SDK by understanding the needs and shifting more and more logic from apps to the lib.
```
</issue_to_address>
### Comment 9
<location> `README.md:56` </location>
<code_context>
# Smart Contracts / Programs
-
## Instalation
```bash
</code_context>
<issue_to_address>
**issue (typo):** Typo: 'Instalation' should be 'Installation'.
```suggestion
## Installation
```
</issue_to_address>
### Comment 10
<location> `README.md:66` </location>
<code_context>
You can also give the library an alias to simplify typing
+
```toml
# tp import for CosmWasm(v1) contracts with all default features
saa = { package = "smart-account-auth", version = "0.24.5", features = ["cosmwasm"] }
</code_context>
<issue_to_address>
**issue (typo):** Typo: 'tp import' should be 'to import'.
```suggestion
# to import for CosmWasm(v1) contracts with all default features
```
</issue_to_address>
### Comment 11
<location> `README.md:224` </location>
<code_context>
### Replay Attack Protection
If replay attack protection is enabled on the contract side, the message to be signed must be a json strong of the following format
+
```typescript
</code_context>
<issue_to_address>
**issue (typo):** Typo: 'strong' should be 'string'.
```suggestion
If replay attack protection is enabled on the contract side, the message to be signed must be a json string of the following format
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Changes requested ❌
Reviewed everything up to 109c429 in 2 minutes and 5 seconds. Click for details.
- Reviewed
1458lines of code in14files - Skipped
0files when reviewing. - Skipped posting
23draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. README.md:6
- Draft comment:
Multiple typos found in the README – for example, 'crypthograpghic' (line 6), 'serilizations' (line 8), and 'Instalation' (line 56) should be corrected for clarity. Please proofread the document. - Reason this comment was not posted:
Comment was on unchanged code.
2. packages/auth/Cargo.toml:20
- Draft comment:
The 'ethabi' dependency is commented out. Confirm if that is intentional or if it should be enabled (perhaps with version 0.28.0) for Ethereum signature support. - Reason this comment was not posted:
Confidence changes required:50%<= threshold50%None
3. packages/bundle/Cargo.toml:31
- Draft comment:
Ensure consistency of feature flags (e.g. 'eth_personal', 'eth_typed_data', 'cosmos_arb', etc.) across packages. The use of optional dependency syntax (like 'saa-auth?') should be reviewed for clarity. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
4. packages/common/Cargo.toml:87
- Draft comment:
Review the 'eth_typed_data' feature dependency list; it depends on 'dep:serde_json', 'dep:schemars', and 'std'. Verify that these are the intended prerequisites for that feature. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
5. packages/macros-proto/core/src/lib.rs:101
- Draft comment:
Consider adding inline documentation for the procedural macros (such as 'saa_error' and 'saa_derivable'). The implementation in 'saa_error_impl' could benefit from comments explaining the derive behavior and error wrapping. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
6. packages/tests/Cargo.toml:21
- Draft comment:
Verify that the versions for dependencies like 'cosmwasm-std' (3.0.2), 'base64-url' (3.0.0) and 'hex' (0.4.3) in the tests are correct and consistent with the rest of the workspace. - Reason this comment was not posted:
Confidence changes required:50%<= threshold50%None
7. CHANGELOG.md:12
- Draft comment:
Typographical error detected: The date '2025-07-97' appears invalid (day '97' is not a valid day). Consider correcting to a valid date format. - Reason this comment was not posted:
Comment was on unchanged code.
8. README.md:6
- Draft comment:
Typo found: Instead of "crypthograpghic", consider using "cryptographic". - Reason this comment was not posted:
Comment was on unchanged code.
9. README.md:8
- Draft comment:
Typo found: "abd" should be "and" and "serilizations" should be "serializations". - Reason this comment was not posted:
Comment was on unchanged code.
10. README.md:10
- Draft comment:
Typo found: "build-in" should be "built-in". - Reason this comment was not posted:
Comment was on unchanged code.
11. README.md:14
- Draft comment:
Typo found: "trais" should be "traits" and "utlity" should be "utility". - Reason this comment was not posted:
Comment was on unchanged code.
12. README.md:16
- Draft comment:
Typo found: "date" should likely be "data". - Reason this comment was not posted:
Comment was on unchanged code.
13. README.md:18
- Draft comment:
Typo found: "multuple" should be "multiple". - Reason this comment was not posted:
Comment was on unchanged code.
14. README.md:25
- Draft comment:
Typo found: "verifcation" should be "verification" and "efficieny" should be "efficiency". - Reason this comment was not posted:
Comment was on unchanged code.
15. README.md:30
- Draft comment:
Typo found: "sence" should be "sense". - Reason this comment was not posted:
Comment was on unchanged code.
16. README.md:56
- Draft comment:
Typo found: "Instalation" should be "Installation". - Reason this comment was not posted:
Comment was on unchanged code.
17. README.md:66
- Draft comment:
Typographical error: In the comment, "# tp import for CosmWasm(v1) contracts with all default features" should likely read "# to import for CosmWasm(v1) contracts with all default features". - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While the comment is technically correct about the typo, it's an extremely minor documentation issue. The meaning is still clear even with the typo. According to the rules, we should not make purely informative comments or comments about obvious/unimportant issues. This falls into that category. The typo could potentially confuse new users who are copy-pasting the example. Documentation accuracy is important for user experience. While documentation accuracy matters, this typo is in a comment (not code) and the meaning is still obvious. The cost of the noise from the PR comment outweighs the minor benefit of fixing this typo. Delete this comment as it violates the rule about not making comments that are obvious or unimportant. The typo is too minor to warrant a PR comment.
18. README.md:101
- Draft comment:
Typo found: "ether" should be "either". - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% While this is a valid typo correction, the review rules emphasize focusing on code changes and logic issues. Documentation typos, while good to fix, are not critical issues that require comments. The typo doesn't impact code functionality or understanding of the feature's purpose. The typo does make the documentation slightly less professional. Some could argue that maintaining high quality documentation is important for the project. However, this is a minor cosmetic issue in documentation. The review rules specifically say to focus on code changes and logic, not purely informative or obvious comments. This comment should be deleted as it addresses a minor documentation issue rather than a substantive code or logic problem.
19. README.md:171
- Draft comment:
Minor typographical note: The heading reads "Typescript". It is typically styled as "TypeScript". Consider updating the capitalization for consistency. - Reason this comment was not posted:
Comment was on unchanged code.
20. README.md:185
- Draft comment:
There are a few typographical errors on this line: - "Requsting" should be "Requesting". - "credemtial" should be "credential". - "neccecary" should be "necessary". - Reason this comment was not posted:
Comment was on unchanged code.
21. README.md:224
- Draft comment:
Typo: "json strong" should be corrected to "JSON string". - Reason this comment was not posted:
Comment was on unchanged code.
22. README.md:257
- Draft comment:
Typographical issues found: - "expirience" should be "experience". - "understaning" should be "understanding". - Reason this comment was not posted:
Comment was on unchanged code.
23. README.md:258
- Draft comment:
Consider reviewing the phrase "quadrating funding". If the intended term is the commonly used "quadratic funding", please update it accordingly. - Reason this comment was not posted:
Comment was on unchanged code.
Workflow ID: wflow_JsKXMQVU6ly3lgvn
You can customize 
README.md
Outdated
| | ``solana`` | Solana programs (BPF) | In Development | | ||
|
|
||
| Credential specifc features allow you to include / exclude specific credential types for better control and optimisizing the binary size | ||
| Credential specifc features allow you to include / exclude specific credential types for better control and optimisizing the binary size: |
There was a problem hiding this comment.
Typo found: "specifc" should be "specific" and "optimisizing" should be "optimizing".
| Credential specifc features allow you to include / exclude specific credential types for better control and optimisizing the binary size: | |
| Credential specific features allow you to include / exclude specific credential types for better control and optimizing the binary size: |
Changelist by BitoThis pull request implements the following key changes.
|
![bito-code-review[bot]](https://avatars.githubusercontent.com/in/1061978?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review Agent Run #678501
Actionable Suggestions - 6
-
packages/tests/Cargo.toml - 1
- Missing feature flags · Line 21-21
-
packages/common/Cargo.toml - 1
- Version mismatch breaks compatibility · Line 16-17
-
Cargo.lock - 3
- ark-* version upgrade risk · Line 99-99
- Version conflict strsim · Line 713-713
- Dependency duplication · Line 1503-1514
-
packages/macros-proto/core/src/lib.rs - 1
- Missing PartialEq trait · Line 104-106
Review Details
-
Files reviewed - 12 · Commit Range:
b53abbf..109c429- Cargo.lock
- Cargo.toml
- packages/auth/Cargo.toml
- packages/bundle/Cargo.toml
- packages/common/Cargo.toml
- packages/macros-proto/core/Cargo.toml
- packages/macros-proto/core/src/lib.rs
- packages/macros-proto/solana/Cargo.toml
- packages/macros-proto/substrate/Cargo.toml
- packages/macros-proto/wasm/Cargo.toml
- packages/schema/Cargo.toml
- packages/tests/Cargo.toml
-
Files skipped - 2
- CHANGELOG.md - Reason: Filter setting
- README.md - Reason: Filter setting
-
Tools
- Whispers (Secret Scanner) - ✔︎ Successful
- Detect-secrets (Secret Scanner) - ✔︎ Successful
Bito Usage Guide
Commands
Type the following command in the pull request comment and save the comment.
-
/review- Manually triggers a full AI review. -
/pause- Pauses automatic reviews on this pull request. -
/resume- Resumes automatic reviews. -
/resolve- Marks all Bito-posted review comments as resolved. -
/abort- Cancels all in-progress reviews.
Refer to the documentation for additional commands.
Configuration
This repository uses Default Agent You can customize the agent settings here or contact your Bito workspace admin at kromsten@pm.me.
Documentation & Help
AI Code Review powered by
|
|
||
| serde_json = { version = "1.0.140" } | ||
| cosmwasm-std = { version = "2.2.2", default-features = false } | ||
| cosmwasm-std = { version = "3.0.2", default-features = false } |
There was a problem hiding this comment.
The cosmwasm-std upgrade from 2.2.2 to 3.0.2 is consistent with the broader codebase (common package also uses 3.0.2), but testing utilities may need feature flag adjustments. The current usage in src/utils.rs imports cosmwasm_std::testing::{message_info, mock_dependencies, MockApi, MockQuerier, MockStorage} which requires the 'staking' feature for full compatibility with v3.0.2. Add the 'staking' feature to ensure all testing utilities compile correctly.
Code suggestion
Check the AI-generated fix before applying
| cosmwasm-std = { version = "3.0.2", default-features = false } | |
| cosmwasm-std = { version = "3.0.2", default-features = false, features = ["staking"] } |
Code Review Run #678501
Should Bito avoid suggestions like this for future reviews? (Manage Rules)
- Yes, avoid them
| cosmwasm-std = { version = "3.0.2", optional = true } | ||
| cosmwasm-std-v1 = { version = "3.0.2", optional = true, package = "cosmwasm-std" } |
There was a problem hiding this comment.
The cosmwasm-std-v1 dependency is being incorrectly updated to version 3.0.2, which breaks the intended version differentiation pattern. This creates semantic duplication where both cosmwasm-std and cosmwasm-std-v1 would point to the same 3.x API, eliminating the backward compatibility provided by the 1.x API. The cosmwasm_v1 feature specifically uses cosmwasm_std_v1 as cosmwasm_std in src/env.rs to provide compatibility with contracts written for the 1.x API. Reverting to 1.5.11 maintains this compatibility layer while allowing the main cosmwasm-std to use the latest 3.0.2 version.
Code suggestion
Check the AI-generated fix before applying
| cosmwasm-std = { version = "3.0.2", optional = true } | |
| cosmwasm-std-v1 = { version = "3.0.2", optional = true, package = "cosmwasm-std" } | |
| cosmwasm-std = { version = "3.0.2", optional = true } | |
| cosmwasm-std-v1 = { version = "1.5.11", optional = true, package = "cosmwasm-std" } |
Code Review Run #678501
Should Bito avoid suggestions like this for future reviews? (Manage Rules)
- Yes, avoid them
| [[package]] | ||
| name = "ark-ff" | ||
| version = "0.4.2" | ||
| version = "0.5.0" |
There was a problem hiding this comment.
Major version upgrade of ark-* libraries from 0.4.2 to 0.5.0 introduces potential breaking changes. The cosmwasm-crypto package (v3.0.2) depends on these ark-* libraries, and upgrading them without compatibility verification could break cryptographic functionality. The changes include removal of derivative and rustc_version dependencies, addition of educe, arrayvec, and upgrade of itertools from 0.10.5 to 0.13.0. These changes may affect ark-ff trait implementations used by cosmwasm-crypto for BLS12-381 curve operations. Consider testing cryptographic operations thoroughly or pinning to compatible versions.
Code suggestion
Check the AI-generated fix before applying
-version = "0.5.0"
-checksum = "a177aba0ed1e0fbb62aa9f6d0502e9b46dad8c2eab04c14258a1212d2557ea70"
+version = "0.4.2"
+checksum = "ec847af850f44ad29048935519032c33da8aa03340876d351dfab5660d2966ba"
Code Review Run #678501
Should Bito avoid suggestions like this for future reviews? (Manage Rules)
- Yes, avoid them
| [[package]] | ||
| name = "itertools" | ||
| version = "0.13.0" | ||
| source = "registry+https://github.com/rust-lang/crates.io-index" | ||
| checksum = "413ee7dfc52ee1a4949ceeb7dbc8a33f2d6c088194d9f922fb8318faf1f01186" | ||
| dependencies = [ | ||
| "either", | ||
| ] | ||
|
|
||
| [[package]] | ||
| name = "itoa" | ||
| version = "1.0.15" |
There was a problem hiding this comment.
A new version of itertools (0.13.0) has been added alongside the existing 0.12.1 version. This creates a potential dependency duplication issue where both versions may coexist, increasing binary size and potentially causing type compatibility issues if types from different versions need to interact. The project should consolidate on a single itertools version.
Code suggestion
Check the AI-generated fix before applying
| [[package]] | |
| name = "itertools" | |
| version = "0.13.0" | |
| source = "registry+https://github.com/rust-lang/crates.io-index" | |
| checksum = "413ee7dfc52ee1a4949ceeb7dbc8a33f2d6c088194d9f922fb8318faf1f01186" | |
| dependencies = [ | |
| "either", | |
| ] | |
| [[package]] | |
| name = "itoa" | |
| version = "1.0.15" | |
| [[package]] | |
| name = "itoa" | |
| version = "1.0.15" |
Code Review Run #678501
Should Bito avoid suggestions like this for future reviews? (Manage Rules)
- Yes, avoid them
Code Review Agent Run #5e6067Actionable Suggestions - 0Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help AI Code Review powered by |
1 participant
User description
Testing Notes
cargo testworkscargo packageerrors:error: the package 'smart-account-auth' does not contain this feature: traitsOpening as draft as have not dove deep into resolving, needed a version compatible with v3 for improting as dep in bs-accounts
Summary by Sourcery
Upgrade to CosmWasm v3 and release v0.28.0 with dependency version bumps, macro cleanup, and README enhancements
Enhancements:
PR Type
Enhancement
Description
Upgrade CosmWasm dependencies to v3.0.2
Bump all workspace packages to v0.28.0
Remove PartialEq derive from error macro
Improve README with formatted tables and documentation
Diagram Walkthrough
File Walkthrough
3 files
Update workspace dependencies to CosmWasm v3.0.2Update CosmWasm std dependencies to v3.0.2Update test dependencies to CosmWasm v3.0.27 files
Bump version to 0.28.0Bump bundle package version to 0.28.0Bump macro core version to 0.28.0Bump macro solana version to 0.28.0Bump macro substrate version to 0.28.0Bump macro wasm version to 0.28.0Bump schema package version to 0.28.01 files
Improve documentation with formatted tables1 files
Remove PartialEq from error macro derive1 files
Update commented ethabi version referenceImportant
Upgrade dependencies to support CosmWasm v3 and enhance documentation for clarity and completeness.
cosmwasm-core,cosmwasm-crypto,cosmwasm-derive,cosmwasm-schema, andcosmwasm-stdto v3.0.2 inCargo.lockandCargo.toml.ark-*dependencies to v0.5.0 inCargo.lock.saa-*package versions to 0.28.0 inCargo.tomlandCargo.lock.README.mdwith improved formatting and added tables for supported credentials, VM support, and feature flags.CHANGELOG.mdto reflect version 0.28.0 changes.saa_error_implinlib.rsto removePartialEqderive for enums.This description was created by
for 109c429. You can customize this summary. It will automatically update as commits are pushed.
✨
Description by Callstackai
This PR upgrades CosmWasm dependencies to v3.0.2, bumps all workspace packages to version 0.28.0, removes PartialEq derive from error macro, and improves the README with formatted tables and documentation.
Diagrams of code changes
sequenceDiagram participant Client participant Auth participant Credential participant ReplayProtection Client->>Auth: Request Credential Verification Auth->>Credential: verify() Note over Credential: New unified verify method<br/>Returns CredentialInfo object alt Replay Protection Enabled Credential->>ReplayProtection: Check Nonce ReplayProtection-->>Credential: Validate No Replay end alt Multiple Credentials Auth->>Credential: with_native() Note over Credential: Returns copy instead<br/>of modifying in place end Credential-->>Auth: Return CredentialInfo Note over Auth: Optional address field<br/>for specific credentials Auth-->>Client: Verification ResultFiles Changed
This PR includes files in programming languages that we currently do not support. We have not reviewed files with the extensions
.md,.toml,.ts,.rs. See list of supported languages.Summary by Bito
This pull request upgrades CosmWasm dependencies to v3.0.2 and bumps workspace packages to version 0.28.0, ensuring consistency across modules. The changes include extensive library version updates in Cargo.lock, refinements to error macro implementation, and enhanced documentation in README and CHANGELOG files. These updates aim to improve compatibility, stability, and code clarity while paving the way for better performance.