Shelflife

Open

NEAR Hackathon 2026

About

Only 6 of 168 NEAR token contracts have a source link that works and points to one exact version of the code. One “source” link is literally <xxx>/<xxx>. Built Shelflife at NEAR HACKATHON to check yours @NEARProtocol #NEARHackathon

Media

Played from X. Open the post (0:45) (opens in a new tab)

From the builder’s post on X. Images and video are streamed from X’s servers, not copied.

Links

Launch post on X: x.com/Savage27z/status/2118225862168649899?a=cWR9MkkqB8MWz0SLjP0&s=20 (opens in a new tab)
Repository: github.com/Savage27z/Shelflife (opens in a new tab)
Hackathon listing: nearhackathon.com#submissions (opens in a new tab)All submissions: the source has no per-project page

Discussion · 0 comments

Each comment is signed by its author on NEAR

Checking your wallet…

No comments yet. Start the discussion.

Comments are public rows on nearhunt.near under comment/3dfb2344…. Only the author can delete one, because only they can write their own row. NEAR Hunt hides a comment that breaks the comment policy.

On-chain record

This page is a view. The data lives on NEAR mainnet.

Account: nearhunt.near
Key: project/3dfb2344-8015-43d8-9389-9cf36bd8fbc2
Schema: nearhunt/project/1
Written at block: 223,703,532 (opens in a new tab)
Record updated: 9 Nov 2026, 02:22 UTC
Comments: 0 signed keys

What am I looking at?

“View JSON” opens this row in the public FastData KV API, read only from rows that nearhunt.near wrote itself. “Written at block” opens the block on Pikespeak.

Upvoted by

No upvotes yet.

Similar projects

Built this project?

Sign in with GitHub to show that you control Savage27z/Shelflife. NEAR Hunt asks for no permissions beyond your public profile and publishes only your GitHub username here.

If the description, repository, links or a contact shown here are wrong or missing, request a correction (opens in a new tab) and it is fixed in a reviewed change. Records are never deleted from the chain.