credible.toml, then create a release with pcl apply.
Prerequisites:
- Approved policies and assigned reviewers
- pcl installed
- An assertion written and tested
- A project created in the platform
Step 1: Authenticate
Before deploying, authenticate with the Credible Layer:pcl displays a device code and verification URL. Press Enter to open the browser. Sign in and approve the request.
Confirm that the intended Protocol Manager is authorized for the contracts in
credible.toml. Platform login and on-chain management authority are separate. See Managing Policy Deployments for the supported authorization path.Step 2: Configure credible.toml
Create assertions/credible.toml to declare the protected contracts and their assertions:
Each contract address must be unique within the configuration. See the pcl Reference for all available fields.
Declare the complete policy set for the replacement release, including policies you want to retain. Omitting a contract or assertion proposes its removal as part of that release; it does not remove an assertion individually from the active release. Review the full diff before signing. Changes take effect after deployment approval and the State Oracle delay.
Step 3: Apply Your Assertions
Create a release on the platform:--yes to skip the confirmation prompt:
pcl apply automatically builds your project. You can also run pcl build separately to check for compilation errors before applying.Step 4: Review and Deploy in the Platform
Open the release under Releases in your project and follow Review and Deploy Policies. The release becomes active after an authorized manager signs the deployment and the State Oracle delay expires.Troubleshooting
Authentication Issues
Apply Issues
Next Steps
Review and Deploy Policies
Complete deployment in the platform
pcl Reference
Full command reference
Testing Assertions
Test before deployment
Troubleshooting
Common issues and solutions

