Say what needs a hand.
A short public title, written by the creating wallet. Keep it useful, specific, and free of personal information.
Open coordination. Human commitment.
Make room.Take the next task.
A small task. A clear beginning.
Review the public proposal.
Illustrative exampleAvailable to claim
A public place for the work you can take on.
Create an unpaid task, claim it, or make room for someone else.
Public titlesWallet-held assignmentsNo payments or rewards
A place between an idea and its next step
Good intentions
need a place
to land.
“Is anyone taking this?” should be a simple question.
In open communities, a request can disappear into a conversation. Taskoryn gives that request a short public title and a visible assignment: which wallet is currently taking it on.
It stays deliberately small. No hiring funnel, invented productivity score, or promise that an assignment means the work is done.
Read the coordination paperThe shape of a task
Offer it. Take it.
Or let it go.
Make your intent visible.
An available task can have one current assignee. The claim belongs to the sending wallet—not an administrator.
Make room again.
Only the current assignee can release. The task becomes available; the earlier public history does not disappear.
A claim is an intention to coordinate, never proof of completion.
Small contributions, shared context
Work together.
Without making
it a marketplace.
For voluntary work that already has a conversation around it.
A community proposal
“Review the accessibility notes.” A participant claims the review so others can choose a different contribution.
An open-source release
“Check the setup instructions.” Keep the discussion and files where they belong; record only the short task here.
A shared documentation day
“Read the terminology page.” If plans change, the assignee releases the task instead of leaving an invisible handover.
A little more care in the handover
Review the state.
Not an old intention.
Each claim and release advances the task’s version. An action must name the exact version that was reviewed, so an old release cannot clear a later assignment—even by the same wallet.
Understand the version ruleAvailableClaimed by a walletAvailable again
Every transition has a new version.
No deadline. No completion badge.
Open by design. Limited on purpose.
Know what
you are making
public.
Titles, wallet addresses and assignment history would be public on a deployed network. Releasing is not deleting. This contract has no moderation, deletion, payment or completion-verification function.
Keep sensitive details in a separate, appropriate conversation. A wallet address is not a verified identity, and claiming a task does not create a work agreement.
Today: local Demo. The contract is prepared and locally tested, but not deployed. Future public writes would consume native network gas.
Before you take a task
A few clear answers.
Can I try it without a wallet?
Yes. The separate task page has an in-memory local demonstration. It never signs, pays gas or broadcasts a transaction, and its data resets on refresh.
Can the creator remove an assignee?
No. The creator has no removal privilege. Only the currently assigned wallet can release its own claim at the exact current version.
Does Taskoryn verify that work was completed?
No. There is no done status, approval, arbitration or completion proof. Discuss quality and outcomes outside this simple coordination record.
What comes next?
A selected network, deployment review and a separately authorized deployment would be needed before public-chain use. No launch date, token or reward is promised.
A clear next step.
Nothing more to carry.
Try the local task flowIndependent task page. No wallet required for the local Demo.