-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add saya service #1495
feat: add saya service #1495
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1495 +/- ##
==========================================
- Coverage 70.06% 69.81% -0.25%
==========================================
Files 236 257 +21
Lines 22531 24453 +1922
==========================================
+ Hits 15786 17073 +1287
- Misses 6745 7380 +635 ☔ View full report in Codecov by Sentry. |
Awesome work @glihm! Looks good so far nothing out of the ordinary from what I've seen. I'm keen on merging this straight away as it's just meant to set the foundation of Saya. Do you mind listing out blockers/stuff from external dependencies that we may have to wait for in the Saya's README ? Would be helpful in understanding the high level overview of external dependencies that Saya's relies on. Also we may want to exclude building |
Co-authored-by: Ammar Arif <[email protected]>
As discussed, it is not included in the archive, but only in the |
This PR aims at adding the basis for Saya service.
Saya service is responsible of the settlement of a Katana instance.
Here's a recap for Saya's needs:
This PR adds the skeleton of Saya, where the DA part is first implemented.
Example of usage:
For the other steps, we still depend on external dependencies. Once they are all updated, we will be able to update Saya to support them.
I will open some issues to keep improving Saya's service, like: