SUBMISSION

Submit work for assessment

One public url - the contract reads what is there at the moment it runs, and grades the bytes it read.

PUBLIC URL OF REAL WORK

no assessment fee · three prompts and one page render, inside one transaction · nothing is issued if the url cannot be read

STUDIO TESTNET charges nothing for anything, so the receipt you get here is not a measurement of what three prompts and one page render cost on a live network.

INSIDE ONE NON DETERMINISTIC BLOCK

pass one

Extraction - rubric blind

waiting

pass two

Grading, criterion by criterion

waiting

pass three

Grading again, criteria reversed

waiting

consensus

Validators rerun all three and must match exactly

waiting

finality

The credential record is written

waiting

WHAT IT WILL BE GRADED AGAINST · V1

00correctness of the mechanism · 0 to 5

01handling of failure paths · 0 to 5

02readability and structure · 0 to 5

03gas and storage awareness · 0 to 5

04documentation of intent · 0 to 5

READ THE FULL RUBRIC →

WHAT WILL BE READ

The page at the url, rendered as text inside the transaction - nothing behind a login, and nothing that changes after the read. The node fetches it, not your browser, so a url that only resolves on your own machine is refused before anything is spent.

LINK TO THE WORK, NOT TO A PAGE ABOUT IT

A repository landing page renders as its README, and a README is not the code - it will be graded as the prose it is. Link the source itself: a raw file, a directory listing that shows content, a rendered document.

WHAT IS STORED

A level, the url, a hash of exactly the bytes that were graded, how many bytes those were, and one flag: whether the work addressed the assessor. Nothing else, and no per-criterion score - every field stored is one that every validator computed independently and matched exactly.

IF THE LEVEL CANNOT AGREE

No credential is issued, and the transaction fails with the reason. A missing credential is recoverable; a wrong one follows someone around.

SUBMITTING THE SAME WORK TWICE

Improving and resubmitting is the intended path - both attempts stay on your page and the higher level is what a consumer reads. The same bytes from a different address is a different thing, and flags both records rather than issuing quietly.

WHAT TO PAIR IT WITH

A short live task. The credential settles the reading that does not scale, so twenty minutes of real work is left to settle authorship and pace - and it is a far better twenty minutes once the standard is already known.