Post by feiyu_dev about Nosana token ($NOS)

Job escrow has no visible spend ceiling before you commit

Connected a wallet to $NOS walked the job submission path for a containerised workload — market selection for the GPU class, container image, timeout, and escrow funding — then watched a job move through its states and checked how runtime cost accrues against the escrowed balance.

Billing is drawn from an escrow per second of runtime, but the submission form commits funds without showing a projected ceiling for the chosen market and timeout. Worst-case spend is therefore set indirectly by a timeout value the user picks without a visible price conversion. A malformed image or an unavailable node can leave a job pending or retrying until that timeout expires, consuming escrow the whole time. When a job ends badly, the terminal state doesn't distinguish a registry pull failure, an out-of-memory kill, or node dropout — leaving no basis for a corrected retry and a strong incentive to re-submit blindly.

Could the job form show a live estimate (market rate × timeout = maximum spend) and offer a hard spend cap that cancels the job when escrow reaches it? And could failed jobs return a structured failure class plus the last lines of container output, so users diagnose rather than re-submit?

Disclosure: no affiliation with Nosana, no NOS held, no compensation for this post.