* SDK - GetTransactionsStream add to rest/grpc
no session, pattern or user messages provided
* SDK - AppDataRepository added, store refactor
This patch introduces a significant refactor of the Ark SDK codebase. The primary changes involve:
1. **Domain Package Introduction**: A new `domain` package has been created under `store`, encapsulating core data structures and interfaces such as `ConfigData`, `Transaction`, `SdkRepository`, and various repository interfaces. This enhances modularity and separation of concerns.
2. **Replacement of Store with Domain Objects**: All references to the `store` package's `StoreData` have been replaced with `domain.ConfigData`. This change reflects a shift towards using domain-driven design, where the core business logic is represented by domain objects.
3. **Repository Pattern Implementation**: The code has been refactored to use repositories for accessing and managing data. `ConfigRepository` and `TransactionRepository` interfaces are introduced, providing methods for managing configuration data and transactions, respectively.
4. **New Storage Implementations**: New storage implementations using BadgerDB are introduced for persisting transactions (`transaction_repository.go`). This change indicates a move towards more robust and scalable data storage solutions.
5. **Service Layer Introduction**: A service layer (`service.go`) is introduced, which acts as a facade for the underlying data repositories. This layer abstracts the data access logic and provides a unified interface for interacting with configuration and transaction data.
6. **Code Simplification and Cleanup**: The patch removes redundant code and simplifies the existing codebase by consolidating store-related logic and enhancing the overall structure of the code.
7. **Testing Enhancements**: Test cases are updated to reflect the changes in the data access layer, ensuring that the new repository pattern and domain objects are properly tested.
Overall, this refactor aims to improve the maintainability, scalability, and testability of the codebase by adopting best practices such as domain-driven design, repository pattern, and separation of concerns.
* 'SDK listen for tx stream
This diff represents a substantial refactor and enhancement of the `ark-sdk` client, which involves modifications to multiple files, primarily in the `pkg/client-sdk` and `server/internal/core/application` directories. Here's a summary of the key changes:
1. **Configuration and Initialization**:
- Refactor to replace file-based configuration store with a domain-based approach.
- Introduced `ListenTransactionStream` configuration to allow real-time transaction event listening.
2. **Client SDK Enhancements**:
- The client SDK now supports asynchronous transaction streaming and handling.
- Introduced methods to get transaction event channels and stop the client gracefully.
- Expanded the `ArkClient` interface to include these new functionalities.
3. **Transaction Handling**:
- Added support for listening to and processing transaction events in real-time.
- Implemented methods to handle different types of transactions, including boarding, redeem, and round transactions.
- Expanded the `Transaction` struct to include more metadata, such as `BoardingVOut`.
4. **Repository Changes**:
- Introduced `VtxoRepository` for managing VTXO-related operations.
- Modified `AppDataRepository` to include `VtxoRepository`.
5. **Example and Test Adjustments**:
- Updated example code to utilize the new transaction streaming capabilities.
- Adjusted tests to reflect changes in client initialization and configuration handling.
6. **Dependency Updates**:
- Updated `go.mod` and `go.sum` to include new dependencies such as `badger` for data storage and potentially updated versions of existing packages.
These changes collectively enhance the functionality of the `ark-sdk` client by enabling real-time transaction handling, improving configuration management, and providing a more robust and scalable client architecture. This update seems to be aimed at improving the efficiency and responsiveness of the client application, likely in response to increased demands for real-time data processing and analysis.'
* merge
* go work sync
* test fix
* Tiny refactor (#2)
* tiny refactor
* renaming
* Renamings
* Fixes (#3)
---------
Co-authored-by: Pietralberto Mazza <18440657+altafan@users.noreply.github.com>
* empty config check & version flag support
* fix: empty config check & version flag support (#309)
* fix
* cli init check
Prevent execution without initialization by checking cfgData and returning error if not initialized
* merge with master
* Replace errors.New with fmt.Errorf
Signed-off-by: Pietralberto Mazza <18440657+altafan@users.noreply.github.com>
---------
Signed-off-by: Pietralberto Mazza <18440657+altafan@users.noreply.github.com>
Co-authored-by: Pietralberto Mazza <18440657+altafan@users.noreply.github.com>
* Export new methods
* Use sdk in CLI
* pr review refactor
* go sync
* Fixes
* run integration test on every change
* fixes
* go sync
* fix
* Persist explorer url
* Fix decoding bitcoin address
* Add missing timeout to e2e test
* Fix
* Fixes
---------
Co-authored-by: altafan <18440657+altafan@users.noreply.github.com>
* [proto] add APIs to send and receive musig2 signing data
* [common] add serialization functions for nonces and signatures
* [application] implements tree signing
* fix: remove old debug logs
* [proto] cleaning
* [common] fix musig2.go
* [application] fixes and logs
* [interface] fix: stop forwarding 2 times the events
* [client] add musig2 support + sign the tree when joining a round
* [interface] add new APIs into permissions.go
* [application][proto] rework PingResponse (return all events type)
* [common] split SetKeys into 2 distinct methods
* [client] fixes according to musig2.go changes
* [sdk] support tree signing + new PingResponse
* [sdk] fixes
* [application] revert event channel type
* [application] use domain.RoundEvent as lastEvent type
* [application] remove IsCovenantLess
* comments
* [application] revert roundAborted changes
* [interface] remove bitcointree dependencie
* pass MutinyNet parameters
* set signetblocktime=30
* supports signet in client and sdk
* ark: --network help message to support signet
* revert intialPeers set
* api-spec: move the api-spec to root and init go.mod
* go mod tidy
* move buf files in the root as well
* gh action for api-spec changes only
* gh action for api-spec on push and pr
* introduce go.work and remove all replaces
* solve dependencies and force btcd/btcec@v2.3.3
* go work sync
* force btcd/btcec@v2.3.3
* go mod tidy
* api-spec: move the api-spec to root and init go.mod
* go mod tidy
* move buf files in the root as well
* gh action for api-spec changes only
* gh action for api-spec on push and pr
* Add bitcoin networks
* Refactor client
* Refactor explorer
* Refactor store
* Refactor wallet
* Refactor sdk client
* Refactor wasm & Update examples
* Move common util funcs to internal/utils
* Move to constants for service types
* Add unit tests
* Parallelize tests
* Lint
* Add job to gh action
* go mod tidy
* Fixes
* Fixes
* Fix compose file
* Fixes
* Fixes after review:
* Drop factory pattern
* Drop password from ark client methods
* Make singlekey wallet manage store and wallet store instead of defining WalletStore as extension of Store
* Move constants to arksdk module
* Drop config and expect directory store and wallet as ark client factory args
* Fix
* Add constants for bitcoin/liquid explorer
* Fix test
* Fix wasm
* Rename client.Client to client.ASPClient
* Rename store.Store to store.ConfigStore
* Rename wallet.Wallet to wallet.WalletService
* Renamings
* Lint
* Fixes
* Move everything to internal/utils & move ComputeVtxoTaprootScript to common
* Go mod tidy
* Add gRPC, REST, and gRPC-Web clients for server access
This commit introduces clients for gRPC, REST, and gRPC-Web to access the server.
- gRPC client: Includes additional argument opts ...grpc.CallOption in the interface for future extensibility.
- REST client: Factory function accepts http.Client as an argument to allow user customization.
- gRPC-Web client: Added a Log method for fast debugging in JavaScript.
The decision to use different interfaces for each client type is to accommodate specific features and extensibility requirements for each protocol.
* remove grpc web
* generate rest
* use grpc sdk in CLI
* temp wasm
* ark sdk
* renaming
* pr review refactor
* pr review refactor
* walletStore & configStore
* ark sdk wasm wrapper
* handle event stream with rest
* wip on supporting rest
* store init
* simulate event stream with rest
* fix rest sdk wip
* Fix returning forfeit txs in round event
* wasm first working e2e example
* pr review refactor
* pr review refactor
* pr review refactor
* Fixes
---------
Co-authored-by: altafan <18440657+altafan@users.noreply.github.com>
* Renaming
* Add server-side support for onboarding
* add onboard --amount command
* support client side onboarding
* Drop dummy tx builder
* Drop faucet
* Fixes
* fix public key encoding
* fix schnorr pub key check in validation
* fix server/README to accomodate onboarding
---------
Co-authored-by: Louis <louis@vulpem.com>
Co-authored-by: João Bordalo <bordalix@users.noreply.github.com>
