Conversation
✅ Deploy Preview for taco-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for taco-nft-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| https://raw.githubusercontent.com/nucypher/taco-web/signing-epic/packages/taco/schema-docs/condition-schema.json | ||
|
|
||
| 2. Human-readable schema reference: | ||
| https://github.com/nucypher/taco-web/blob/signing-epic/packages/taco/schema-docs/condition-schemas.md |
There was a problem hiding this comment.
We should think about what branch is best to reference in order to be the most evergreen. This currently uses signing-epic but eventually that branch will be merged into epic-v0.7.x and then into main - #657.
We can probably leave as is, and have a follow-up PR to update the reference when applicable.
Just pointing this out to remind us.
| - After the `:`, the name must match /^[a-zA-Z_][a-zA-Z0-9_]*$/ (letters, digits, underscores only). | ||
| - No dots, dashes, hyphens, or spaces. `:user-address`, `:user.address`, `:1first` are all INVALID. | ||
| - Case-sensitive: `:userAddress` ≠ `:useraddress`. | ||
| - Built-in variables you do NOT need to define yourself: `:userAddress` (requester's wallet), `:message` (signed message), `:signature` (signature being verified), `:jwtToken` (JWT being validated), `:signingConditionObject` (UserOperation in threshold signing). |
There was a problem hiding this comment.
We probably need to be a little clearer here - see nucypher/taco-docs#12 (comment).
| ## Q&A | ||
|
|
||
| **Q: Can I test conditions before deploying?** | ||
| A: Yes. Use the [TACo Playground](https://playground.taco.build/) to simulate decryption with your condition and test requesters' data. |
There was a problem hiding this comment.
We'll need to bring the TACo Playground up to date.
| A: Yes. Any context variable (starting with `:`) is valid. You supply its value at decryption time. Tell the LLM: "Use a context variable `:myCustomVar` and I will supply its value at runtime." | ||
|
|
||
| **Q: Are there limits on condition complexity?** | ||
| A: CompoundCondition max 5 operands, max 2 nesting depth. SequentialCondition handles 2–20 steps. If you need more: compound → operand1 (SequentialCondition), operand2 (SequentialCondition), etc. |
There was a problem hiding this comment.
|
Very cool - nice work. You'll also need to rebase over |
2 participants
Type of PR:
Required reviews:
What this does:
Issues fixed/closed:
Why it's needed:
Notes for reviewers:
Depends on nucypher/taco-docs#12, so don't merge it before.