Sponsorship Policy API functions and Integrate with paymaster data generation endpoint #111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ates for APIKey entity references in backend and frontend components
…es for sponsorship_policy tables and api_keys association
…the sequelizePlugin
… while saving apiKey
…r and index files only
…sion upgrade for all 3 projects in arka
…new route functions
Deploying arka with
|
| Latest commit: |
024696e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c06b10c6.arka-3qg.pages.dev |
| Branch Preview URL: | https://pro-2455-sponsorship-policy.arka-3qg.pages.dev |
…intVersion and apiKey
…tion via policyId or apiKey
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11777939 | Triggered | Generic High Entropy Secret | 6c8ad04 | docker-compose.yml | View secret |
| 11777939 | Triggered | Generic High Entropy Secret | 5072ea1 | docker-compose.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
kanthgithub
changed the base branch from
PRO-2395-Sponsorship-Policies
to
master
kanthgithub
changed the base branch from
master
to
PRO-2395-Sponsorship-Policies
ch4r10t33r
reviewed
Jun 24, 2024
kanthgithub
changed the base branch from
PRO-2395-Sponsorship-Policies
to
master
…tgres database docker file setup to project root directory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
sponsorthen validate the userOp data with constraints built from sponsorship policy detailsSponsorship Policy Management
Arka needs to have the ability to setup sponsorship policies, these will be offered as a backend API within Arka and this can be consumed by our developer dashboard.
Types of changes
Design Doc
implementation (feature)
[ X] New feature (non-breaking change which adds functionality)
Documentation Update