Contributor Transactions
Project contributor transactions - task commitment and completion
Contributor Transactions
Project contributors can commit to and complete tasks. Contributors must meet the project's prerequisite requirements (typically holding credentials from specified courses).
Available Transactions
| Transaction | Description |
|---|---|
| Task Commit | Enroll in project and commit to a task |
| Credential Claim | Claim credential by burning contributor state |
Contributor Role
Contributors are users who work on project tasks. To become a contributor:
- Meet Prerequisites: Hold the required course credentials
- Commit to Task: Use task-commit to enroll and commit in one transaction
- Submit Evidence: Provide
task_infoas proof of work - Await Decision: Managers assess the submission
Key Concepts
Prerequisites via contributor_state_id
Projects define prerequisites using contributor_state_id - a policy ID representing the credential a contributor must hold. This is a compact way to verify course completion without listing individual SLT hashes.
First Enrollment Mints Token
When a contributor commits to their first task in a project, the transaction mints a contributor-state token. Subsequent commits update this token rather than minting new ones.
Global State Credential
Upon enrollment, the project credential is added to the contributor's global state credentials map. This enables cross-project credential verification.
See Also
- Tasks Manage - How managers create tasks
- Project Create - How projects are created