Yokefellow
ETH: —
YES: —
USDC: —
YES: —
USDC: —
Profile
Yokefellow is looking for partners interested in joining and creating new ways to enjoy web3 experiences!
← Back to home

Yokefellow - Blog

NFTs, Rights, and Redemption

By jhinjuju | Jun 15, 2026 | Last edited Jun 26, 2026 | 7 min read

A practical guide to what NFTs can mean on Yokefellow, how rights are tied to buckets and offerings, and why redemption depends on the actual terms of the path.

type: guideguidenftsrightsredemptionclaimsaccess
Yokefellow logo
Yokefellow
NFTs, Rights, and Redemption cover image

NFTs, Rights, and Redemption

NFTs on Yokefellow are not only pictures, collectibles, or profile items.

An NFT can be the carrier for something a user may receive through a bucket or offering. That thing might be access, proof, status, participation ability, a product claim, a redemption path, a role, a permission, a digital item, or another defined right.

This guide explains the basic idea.

The simple version

On Yokefellow, the NFT is often the carrier.

The right is what the user may actually receive, use, access, prove, or redeem.

NFT = the object held by the user
Right = what that object may mean or allow
Redemption = the process of using or claiming what the right gives

Those three things are connected, but they are not the same thing.

Why Yokefellow uses rights language

Yokefellow uses the word right because users should understand what they may receive before they participate.

A right can mean different things depending on the bucket and offering.

It may be:

  • access to something
  • proof of participation
  • entry into a path
  • status inside a bucket or app
  • permission to use a tool
  • permission to post, manage, or control something
  • a claim on a product or service
  • a ticket-like object
  • a badge or record
  • a redeemable output
  • a digital item
  • a role or work-related permission

The point is not to make every NFT sound bigger than it is.

The point is to describe what it actually does.

The bucket gives context

An NFT or right should not be understood by name alone.

The bucket matters because the bucket explains the initiative, the terms, the operator, the participation path, and the place where the right belongs.

The same kind of NFT could mean one thing in one bucket and something different in another.

For example:

A ticket in one bucket may mean entry.
A ticket in another bucket may mean participation in a selection process.
A badge in one bucket may mean proof.
A badge in another bucket may unlock access.

The bucket gives the object its context.

The offering explains the path

An offering is the structured way a bucket makes participation available.

An offering may be a purchase, request, application, grant, earned path, or another configured path.

That matters because not every NFT is received the same way.

Some outputs may be bought.

Some may be earned.

Some may require review.

Some may depend on a selection process.

Some may be granted by an operator.

Some may come later through a queue or fulfillment step.

The offering tells the user what path they are entering.

NFTs are not all the same

Users should not assume every NFT on Yokefellow means the same thing.

One NFT may be transferable.

Another may be locked.

One may be redeemable.

Another may only be proof.

One may be used inside a bucket.

Another may be used inside an app.

One may expire.

Another may last longer.

One may be consumed when used.

Another may stay in the wallet after use.

The NFT standard is only the carrier. The real meaning comes from the bucket, offering, rights structure, metadata, and rules attached to it.

Common kinds of rights

Yokefellow can support many kinds of rights.

Some common examples include:

  • access rights
  • participation rights
  • reward rights
  • proof rights
  • status rights
  • decor or display rights
  • control or authority rights
  • product claim rights
  • redemption rights
  • tool-use rights
  • role-based rights

Not every bucket will use all of these.

A serious bucket should explain what kind of right is being offered and what limits apply.

Redemption

Redemption is when a user uses a right or claims what the right allows.

That may be simple or complex depending on the bucket.

For example, redemption might mean:

  • claiming access
  • receiving a product
  • using an entry
  • consuming a ticket
  • receiving a service
  • proving eligibility
  • unlocking a feature
  • using an app-layer permission
  • having an operator fulfill something manually

Redemption should be explained by the bucket or offering before the user acts.

Redemption can have conditions

A right may be real and still have limits.

A redemption path may depend on:

  • time windows
  • user eligibility
  • supply limits
  • review
  • operator action
  • location
  • identity or wallet checks
  • whether the NFT has already been used
  • whether the NFT is still transferable
  • whether the bucket is still active
  • whether the output has expired
  • whether the required information was submitted

A right is stronger when its limits are clear.

Transferability matters

Some NFTs may be transferable.

Some may not be.

Transferability should never be assumed.

If an NFT is transferable, a holder may be able to send it or sell it depending on the rules and available surfaces.

If an NFT is not transferable, it may be locked to the holder or designed only for that wallet.

Even when an NFT is transferable, the right does not automatically become broader than the original bucket terms.

The buyer or receiver gets the object subject to the actual rules attached to it.

Burnable or consumable NFTs

Some NFTs may be burned or consumed as part of use.

That means the NFT may be destroyed, marked used, depleted, or changed when the holder redeems it or uses it in another path.

For example:

Unused = still available
Redeemed = already used
Burned = consumed or destroyed
Expired = no longer usable

This depends on the design of the NFT and the bucket.

Do not assume an NFT can be used forever unless the bucket says that.

Metadata matters

NFT metadata can help explain what the NFT is, what it belongs to, what class it is, what image or description it has, and sometimes what state it is in.

Metadata may show things like:

  • name
  • image
  • description
  • issuing bucket
  • class or output type
  • attributes
  • use state
  • redemption state
  • limits or conditions

Metadata is important, but it should not be read alone.

The bucket and offering still matter.

Proof and public records

NFTs can help make outcomes easier to track.

A bucket may use NFTs, posts, receipts, updates, and activity records to show what happened.

Proof may include:

  • the bucket page
  • the offering terms
  • activity records
  • transaction records
  • NFT mint records
  • redemption updates
  • receipts
  • closeout posts

The goal is for participation to leave a readable record instead of disappearing into private explanation.

What an NFT does not guarantee

Holding an NFT does not automatically mean every possible benefit is guaranteed.

An NFT does not automatically mean:

  • ownership of Yokefellow
  • ownership of the issuing bucket
  • unlimited platform rights
  • permanent access
  • guaranteed resale value
  • guaranteed redemption without conditions
  • guaranteed operator performance
  • that the right applies outside its stated scope

The actual meaning depends on the bucket, offering, right, metadata, and posted terms.

Before participating in a path that may issue an NFT or right, check:

  • what bucket the path belongs to
  • what the offering says
  • whether the path is purchase, request, earned, application, or grant
  • what the NFT or right actually means
  • whether redemption is available
  • what the redemption process requires
  • whether the NFT is transferable
  • whether it can expire
  • whether it can be burned or consumed
  • whether fulfillment is instant, delayed, queued, or manual
  • what proof or receipt will exist later

The more valuable or important the right is, the more carefully the user should read the path.

The earlier guides explain how users get started, add YES, understand deposits, and use the market.

This guide explains what users may receive through participation.

The larger flow looks like this:

Wallet
→ YES
→ personal bucket or public bucket
→ offering or participation path
→ output, NFT, right, proof, or redemption

Not every path uses every step, but this is the basic shape.

Current guides

Read next:

More guides will be added as Yokefellow fills out.

Comments

Discuss this post with your Yokefellow profile.

0 comments
UN
Unknown
Your profile will appear beside your comment.
Loading comments...