The Taskoryn paper

A small protocol
for taking a task.

What is recorded, who may change it, and what a public assignment cannot prove.

Purpose

Coordination, not a promise.

Taskoryn is for voluntary collaborators who need a small public answer to “which wallet is currently taking this task?”. It records intent, without trying to manage work or price it.

A creator writes a short title. Any wallet may claim an available task, including its creator. Only its current assignee may release. Outcomes and private discussion stay outside this protocol.

The public record

A title. A creator.
A current assignee.

Title
1–160 UTF-8 bytes, with a visible byte beyond ASCII whitespace. The title cannot be edited or deleted through this contract.
Creator
The transaction sender who created the task. Creation does not confer eviction, approval or administrative rights.
Assignee
One current wallet, or no wallet when available. This is not a verified person or a completion certificate.
Version
Starts at one and advances with every successful claim or release. IDs are positive, monotonically increasing and never recycled.
Versioned handovers

The reviewed state matters.

Claim and release calls include an expected version. A stale version reverts rather than changing a later assignment. This also prevents an old release from clearing a new claim by the same wallet.

Review, then act.

The frontend clears its review when input, mode, account, network or connection changes. A successful transaction requires a matching receipt and exact Created, Claimed or Released event—not just a transaction hash.

Authority & limits

No one gets
a hidden override.

There is no owner, administrator, upgrade proxy, moderation or delete path. A creator cannot evict someone else. One wallet may hold multiple tasks; unhelpful or abusive tasks are possible.

No compensation, escrow, rewards, employment, deadline enforcement, work execution, acceptance review, arbitration or completion verification is included. All writes are nonpayable, although a public network would charge native gas.

Do not publish personal details, credentials or sensitive work. Releasing an assignment does not erase history. The application cannot promise that a public record is true or appropriate.

Current state & next steps

Prepared locally.
Not deployed.

This Demo includes project-specific Solidity source, local tests and an unsigned deployment preview. It has no public deployment address, chosen network or live explorer link. The local browser demonstration is not a blockchain result.

Public use requires reviewing network compatibility, deployment inputs, bytecode, gas and signer controls, followed by separate deployment authorization. No private key belongs in this website. Changes to business rules require a new contract address and an explicit migration; old public history remains.

Local checks are not an independent security audit or proof of browser-wallet execution. No public launch timing is promised.