Proposal: Canton DeFi SafeVault Framework#266
Open
reborntaichi wants to merge 1 commit into
Open
Conversation
Signed-off-by: reborntaichi <reborntaichi@gmail.com>
This file contains hidden or 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
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.
Development Fund Proposal Submission
Proposal file:
proposals/Canton-DeFi-SafeVault-framework.mdSummary
This PR submits the Canton DeFi SafeVault Framework proposal for Development Fund review.
Canton SafeVault is a reusable capital control and risk management framework for Canton DeFi protocols. It provides standardized workflows for capital entry, ownership recording, allocation approval, risk restriction, redemption, recovery, and responsibility alignment.
The framework is designed as critical ecosystem infrastructure for Canton DeFi. It uses Canton-native mechanisms including Daml contract state, Party-based permissions, signatories, controllers, observers, multi-party workflows, and selective visibility.
Checklist
/proposals/Related Issue
Closes #265