-
Notifications
You must be signed in to change notification settings - Fork 18
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
What is the correct Policy? #510
Comments
The format in your signatory.yaml file would be
You can choose from the policy list for the rest: So you might choose:
|
Thanks, so something like this should work to allow baker duties, delegation and staking transactions only.
|
signatory is "closed by default" so there is no 'deny' block. also, if you have 'unstake' you might want 'finalize_unstake' as well. Finally, note as well that |
Thanks, the following example now is it correct? tezos:
tz1ExamplePublicKeyHash:
log_payloads: true
allow:
block:
preattestation:
attestation:
unstake:
finalize_unstake:
generic:
- transaction
- reveal
- delegation
- drain_delegate |
That should work. |
Dear Signatory Team,
I appreciate your help to share the correct policy to allow backer duties, voting, delegating, staking and unstaking and block transaction (ie: draining funds from consensus key). Thank you!
The text was updated successfully, but these errors were encountered: