-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Xcavate Blockchain & realXchange dApp #2109
Conversation
hosted images on our server
correction to image URLs
hosted elsewhere
hosted elsewhere
hosted elsewhere
hosted elsewhere
Reduced scope of work to focus on onboarding the project in to the Polkadot eco system
Hopefully addressing the questions / issues raised
requested to move file to applications folder
old project submission
Revised W3F grant to only focus on building a PoC of the lending protocol dApp
Revised application... more details and new dev team added
Added new member of the team
added another team member
added current symbol to milestone fund request + moved the milestone deliverables inline with template. updated one team members linkedin and full name.
Adapt grant application to focus on ink! contract use case
Removed one member and added a new member
Amended grant application - remove two deliverables
Removed the following deliverables: | 5. | Verification pallet | * We need to remove this deliverable because it is reliant on the Acurast Oracle Pallet which is struggling due to Substrate dependency issues | | 7. | Decentralized Developer Loan dApp / Front End Repo | We are struggling to interact through the frontend dApp so wish to remove this as a deliverable, however interacting through polkadot.js is fine. |
Submission of Milestone 2 grant application
Milestone 2 = Building out the full functionality of the Xcavate protocol to be able to interact with a number of existing Parachains in the Dotsama ecosystem through XCM.
Correct info update error
Amended deliverables & FTE
changes to FTE, adding supported wallets to deliverable & formatting
amalgamate deliverable 5 (loan governance) in to community loan pallet.
Updated suggestion Co-authored-by: S E R A Y A <[email protected]>
Update suggestion Co-authored-by: S E R A Y A <[email protected]>
FTE update
Update title and milestone number
New phase of Xcavate project
add flow chart
add mark down extension
text changes & added jpg link
update image link URL
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | View secret |
- | Google Bard API Key | b4f774f | applications/Doter.md | 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.
Our GitHub checks need improvements? Share your feedbacks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed fully before creating a PR
getting file name error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your interest in our grants program. Is there a reason why you opened the same application twice, see #2110?
Project Abstract
Grant level
Application Checklist
project_name.md
).@_______:matrix.org
(change the homeserver if you use a different one)