* feat(did): remove account types
* feat: Refactor Property to Proof in zkprop.go
* feat: add ZKP proof mechanism for verifications
* fix: return bool and error from pinInitialVault
* feat: implement KeyshareSet for managing user and validator keyshares
* feat: Update Credential type in protobuf
* feat: update credential schema with sign count
* feat: migrate and modules to middleware
* refactor: rename vault module to ORM
* chore(dwn): add service worker registration to index template
* feat: integrate service worker for offline functionality
* refactor(did): use DIDNamespace enum for verification method in proto reflection
* refactor: update protobuf definitions to support Keyshare
* feat: expose did keeper in app keepers
* Add Motr Web App
* refactor: rename motr/handlers/discovery.go to motr/handlers/openid.go
* refactor: move session related code to middleware
* feat: add database operations for managing assets, chains, and credentials
* feat: add htmx support for UI updates
* refactor: extract common helper scripts
* chore: remove unused storage GUI components
* refactor: Move frontend rendering to dedicated handlers
* refactor: rename to
* refactor: move alert implementation to templ
* feat: add alert component with icon, title, and message
* feat: add new RequestHeaders struct to store request headers
* Feature/create home view (#9)
* refactor: move view logic to new htmx handler
* refactor: remove unnecessary dependencies
* refactor: remove unused dependencies
* feat(devbox): integrate air for local development
* feat: implement openid connect discovery document
* refactor: rename to
* refactor(did): update service handling to support DNS discovery
* feat: add support for user and validator keyshares
* refactor: move keyshare signing logic to signer
* 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
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.
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.