- **refactor: refactor DID module types and move to controller package**
- **refactor: move controller creation and resolution logic to keeper**
- **refactor: update imports to reflect controller package move**
- **refactor: update protobuf definitions for DID module**
- **docs: update proto README to reflect changes**
- **refactor: move hway to gateway, update node modules, and refactor
pkl generation**
- **build: update pkl-gen task to use new pkl file paths**
- **refactor: refactor DWN WASM build and deployment process**
- **refactor: refactor DID controller implementation to use
account-based storage**
- **refactor: move DID controller interface to base file and update
implementation**
- **chore: migrate to google protobuf**
- **feat: Add v0.52.0 Interfaces for Acc Abstraction**
- **refactor: replace public_key with public_key_hex in Assertion
message**
- **refactor: remove unused PubKey, JSONWebKey, and RawKey message types
and related code**
Bumps
[github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v8](https://github.com/cosmos/ibc-apps)
from 8.0.2-0.20240228211029-91e486ec4dbb to 8.0.2.
Release notes
*Sourced from*
[*github.com/cosmos/ibc-apps/middleware/packet-forward-middleware/v8's
releases*](https://github.com/cosmos/ibc-apps/releases)*.*
> ## packet-forward-middleware v8.0.2
>
> ## Note
>
> This release includes the patch for the [Mandrake
vulnerability](https://github.com/cosmos/ibc-apps/security/advisories/GHSA-v8p4-qhq4-f7h8)
>
> We recommend that you upgrade to the patched version, create a new
release for your chain binary, and coordinate an upgrade with validators
as soon as reasonable.
>
> In addition to patching packet-forward-middleware, it is imperative
that you check the balances of each escrow account against the total
supply of each asset on the associated counterparty chain. Failure to
verify parity between the escrow accounts and the counterparty total
supply can result in a type of Denial-of-Service where users may not be
able to unwind their assets through your chain. You can use our [escrow
checker tool](https://github.com/strangelove-ventures/escrow-checker) or
whatever means you deem fit to validate these balances against the
counterparty total supply. If a discrepancy is found, you will need to
build an upgrade handler that mints and transfers assets to the escrow
account(s) with the discrepancy. Strangelove has provided an [example
upgrade
handler](https://gist.github.com/jtieri/0b41fa96eac44ea1c0b5de63d23aa662)
or you can see the upgrade handler used by the [Cosmos
Hub](https://github.com/cosmos/gaia/blob/0b1f3d80359709de48116baecb810c521960a575/app/upgrades/v15/upgrades.go#L360-L458).
>
> ## What's Changed
>
> * Remove gogo/protobuf replace directive in async-icq/v8 by
`@Taztingo` in
[cosmos/ibc-apps#168](https://redirect.github.com/cosmos/ibc-apps/pull/168)
> * fix: mint and transfer funds back to escrow account on timeout or
ack error by `@jtieri` in
[cosmos/ibc-apps#170](https://redirect.github.com/cosmos/ibc-apps/pull/170)
>
> **Full Changelog**:
<https://github.com/cosmos/ibc-apps/compare/middleware/packet-forward-middleware/v8.0.1...middleware/packet-forward-middleware/v8.0.2>
Commits
* See full diff in [compare
view](https://github.com/cosmos/ibc-apps/commits/middleware/packet-forward-middleware/v8.0.2)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
* `@dependabot rebase` will rebase this PR
* `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
* `@dependabot merge` will merge this PR after your CI passes on it
* `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
* `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
* `@dependabot reopen` will reopen this PR if it is closed
* `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
* `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
* `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
* `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
* `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Prad Nukala <prad@sonr.io>
Bumps
[github.com/strangelove-ventures/globalfee](https://github.com/strangelove-ventures/globalfee)
from 0.50.0 to 0.50.1.
Release notes
*Sourced from* [*github.com/strangelove-ventures/globalfee's
releases*](https://github.com/strangelove-ventures/globalfee/releases)*.*
> ## v0.50.1
>
> **This is a consensus breaking release and requires a software upgrade
to implement.**
>
> This is just of a cleanup patch, no need to update if you do not want
too.
>
> ## What's Changed
>
> * refactor!: remove staking keeper usage in ante by `@Reecepbcups` in
[strangelove-ventures/globalfee#5](https://redirect.github.com/strangelove-ventures/globalfee/pull/5)
>
> **Full Changelog**:
<https://github.com/strangelove-ventures/globalfee/compare/v0.50.0...v0.50.1>
Commits
* `905a334` refactor!: remove staking keeper & use "stake" for default 0
fee
([#5](https://redirect.github.com/strangelove-ventures/globalfee/issues/5))
* See full diff in [compare
view](https://github.com/strangelove-ventures/globalfee/compare/v0.50.0...v0.50.1)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
* `@dependabot rebase` will rebase this PR
* `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
* `@dependabot merge` will merge this PR after your CI passes on it
* `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
* `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
* `@dependabot reopen` will reopen this PR if it is closed
* `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
* `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
* `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
* `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
* `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Prad Nukala <prad@sonr.io>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Prad Nukala <prad@sonr.io>
* feat: add enums.pulsar.go file for PermissionScope enum
* refactor: remove PERMISSION_SCOPE_IDENTIFIERS_ENS enum value
* feat: Add MsgRegisterService to handle service registration
The commit message for these changes would be:
feat: Add MsgRegisterService to handle service registration
This commit adds a new message type `MsgRegisterService` to the DID module's transaction proto file. This message allows users to register a new service with a given permission scope and origin URI. The domain must have a valid TXT record containing the public key.
The changes include:
- Adding the `MsgRegisterService` message type with fields for authority, origin URI, and scopes
- Adding the `MsgRegisterServiceResponse` message type to handle the response
- Updating the Msg service to include a new `RegisterService` RPC method
- Implementing the `RegisterService` method in the keeper
This feature allows users to register new services on the DID chain, which is an important part of the overall DID functionality.
* (no commit message provided)
* fix: Add ProveWitness and SyncVault RPCs
The commit message should be:
feat: Add ProveWitness and SyncVault RPCs
This change adds two new RPCs to the DID module:
1. ProveWitness: An operation to prove the controller has a valid property using ZK Accumulators.
2. SyncVault: Synchronizes the controller with the Vault Motr DWN WASM Wallet.
These new RPCs allow for more advanced DID management functionality.
* fix: Remove unused `Meta` message from `genesis.proto`
* refactor: Simplify the types and properties to keep a consistent structure for the blockchain
* (no commit message provided)
* {}
* feat: add Equal methods for AssetInfo and ChainInfo types
