Type Alias Nft 

pub type Nft = Singleton<NftInfo>;

Contains all information needed to spend the outer puzzles of NFT coins. The NftInfo is used to construct the puzzle, but the Proof is needed for the solution.

The only thing missing to create a valid coin spend is the inner puzzle and solution. However, this is handled separately to provide as much flexibility as possible.

This type should contain all of the information you need to store in a database for later. As long as you can figure out what puzzle the p2 puzzle hash corresponds to and spend it, you have enough information to spend the NFT coin.

Aliased Type

pub struct Nft {
    pub coin: Coin,
    pub proof: Proof,
    pub info: NftInfo,
}

Fields

coin: Coin

The coin that this Singleton represents. Its puzzle hash should match the singleton outer puzzle hash.

proof: Proof

The proof is needed by the singleton puzzle to prove that this coin is a legitimate singleton. It’s typically obtained by looking up and parsing the parent coin.

Note that while the proof will be a LineageProof for most coins, for the first singleton in the lineage it will be an EveProof instead. However, the eve coin is typically unhinted and spent in the same transaction as it was created, so this is not relevant for database storage or syncing unspent coins.

info: NftInfo

The information needed to construct the outer puzzle.

Implementations

impl Nft

pub fn child( &self, p2_puzzle_hash: Bytes32, current_owner: Option<Bytes32>, metadata: HashedPtr, amount: u64, ) -> Nft

Creates a new Nft that represents a child of this one.

pub fn spend( &self, ctx: &mut SpendContext, inner_spend: Spend, ) -> Result<Self, DriverError>

Spends this NFT coin with the provided inner spend. The spend is added to the SpendContext for convenience.

pub fn spend_with<I>( &self, ctx: &mut SpendContext, inner: &I, conditions: Conditions, ) -> Result<Self, DriverError>

where I: SpendWithConditions,

Spends this NFT coin with a Layer that supports SpendWithConditions. This is a building block for built in spend methods, but can also be used to spend NFTs with conditions more easily.

However, if you need full flexibility of the inner spend, you can use Nft::spend instead.

pub fn transfer_with_metadata<I>( self, ctx: &mut SpendContext, inner: &I, p2_puzzle_hash: Bytes32, metadata_update: Spend, extra_conditions: Conditions, ) -> Result<Nft, DriverError>

where I: SpendWithConditions,

Transfers this NFT coin to a new p2 puzzle hash and runs the metadata updater with the provided spend.

This spend requires a Layer that supports SpendWithConditions. If it doesn’t, you can use Nft::spend_with instead.

pub fn transfer<I>( self, ctx: &mut SpendContext, inner: &I, p2_puzzle_hash: Bytes32, extra_conditions: Conditions, ) -> Result<Nft, DriverError>

where I: SpendWithConditions,

Transfers this NFT coin to a new p2 puzzle hash.

This spend requires a Layer that supports SpendWithConditions. If it doesn’t, you can use Nft::spend_with instead.

pub fn lock_settlement<I>( self, ctx: &mut SpendContext, inner: &I, trade_prices: Vec<TradePrice>, extra_conditions: Conditions, ) -> Result<Nft, DriverError>

where I: SpendWithConditions,

Transfers this NFT coin to the settlement puzzle hash and runs the transfer program to remove the assigned owner and reveal the trade prices for the offer.

This spend requires a Layer that supports SpendWithConditions. If it doesn’t, you can use Nft::spend_with instead.

pub fn unlock_settlement( self, ctx: &mut SpendContext, notarized_payments: Vec<NotarizedPayment>, ) -> Result<Nft, DriverError>

Spends this NFT with the settlement puzzle as its inner puzzle, with the provided notarized payments. This only works if the NFT has been locked in an offer already.

pub fn assign_owner<I>( self, ctx: &mut SpendContext, inner: &I, p2_puzzle_hash: Bytes32, transfer_condition: TransferNft, extra_conditions: Conditions, ) -> Result<(Conditions, Nft), DriverError>

where I: SpendWithConditions,

Transfers this NFT coin to a new p2 puzzle hash and runs the transfer program.

This will return the conditions that must be emitted by the singleton you’re assigning the NFT to. The singleton must be spent in the same spend bundle as the NFT spend and emit these conditions.

However, if the NFT is being unassigned, there is no singleton spend and the conditions are empty.

This spend requires a Layer that supports SpendWithConditions. If it doesn’t, you can use Nft::spend_with instead.

pub fn parse_child( allocator: &mut Allocator, parent_coin: Coin, parent_puzzle: Puzzle, parent_solution: NodePtr, ) -> Result<Option<Self>, DriverError>

Parses the child of an Nft from the parent coin spend.

This can be used to construct a valid spendable Nft for a hinted coin. You simply need to look up the parent coin’s spend, parse the child, and ensure it matches the hinted coin.

This will automatically run the transfer program or metadata updater, if they are revealed in the p2 spend’s output conditions. This way the returned Nft will have the correct owner (if present) and metadata.

pub fn parse( allocator: &Allocator, coin: Coin, puzzle: Puzzle, solution: NodePtr, ) -> Result<Option<(Self, Puzzle, NodePtr)>, DriverError>

Parses an Nft and its p2 spend from a coin spend.

If the puzzle is not an NFT, this will return None instead of an error. However, if the puzzle should have been an NFT but had a parsing error, this will return an error.

Trait Implementations

impl AddAsset for Nft

fn add(self, spends: &mut Spends)

impl Asset for Nft

fn coin_id(&self) -> Bytes32

fn full_puzzle_hash(&self) -> Bytes32

fn p2_puzzle_hash(&self) -> Bytes32

fn amount(&self) -> u64

fn constraints(&self) -> OutputConstraints

impl SingletonAsset for Nft

type ChildInfo = ChildNftInfo

fn default_child_info(_asset: &Self, spend_kind: &SpendKind) -> Self::ChildInfo

fn needs_additional_spend(child_info: &Self::ChildInfo) -> bool

fn finalize( ctx: &mut SpendContext, singleton: &mut SingletonSpend<Self>, intermediate_puzzle_hash: Bytes32, change_puzzle_hash: Bytes32, ) -> Result<Option<SingletonSpend<Self>>, DriverError>