Skip to content

Ceto-Labs/non-fungible-token

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

34 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Introduction

WIP

Our goal for this project is to develop a non-fungible token standard (Compatible with ERC721 and ERC1155 standards) which leverages the unique properties of the IC and enables builders to create entire experiences from a single contract. Our approach is guided by the following exploratory questions: What can be an NFT? What can it be used for? Who can access it? How and where is it accessed? What properties does it have - can they change? Who can change them?What are the external interfaces that must be provided?

Combined with our actual development of the nft exchange, we will gradually improve all interfaces. Hope that more people will give us various feedbacks, we will realize a perfect nft standard as soon as possible.

Development Status - Early Alpha

Notes:

  • 8/26/2021. Fork from no-fungible-token,The support for NFT class is completed, and NFT based on ERC721 and ERC1155 standards can be created.

Standard interfaces

//Exchange interface 
//the amount of single NFT
supply(id : Text) -> async (Nat);

//Query all NFTs owned by an address
balanceOf(p : Principal, id : Text) -> async Nat;

//Batch authorization to agents
authorize(authorizeRequest : NftTypes.AuthorizeRequest) -> async NftTypes.AuthorizeResult;

//Batch transferFrom NFT
transferFrom(transferRequest : NftTypes.TransferRequest) -> async NftTypes.TransferResult;

//Query all authorization information of the owner of nft
getAuthorized(owner : Principal, id : Text) : async [NftTypes.AuthorizeInfo];

// Data interface
//mint erc1155 standard type NFT
//return Nft ID
mint(egg : NftTypes.NftEgg) -> async Text;

//Get NFT raw data
nft(id : Text) -> async NftTypes.NftResult;

//Destroy NFT
burn(id : Text, amount : Nat) -> async NftTypes.BurnResult;


Features

  • 🟢 - Ready
  • 🟠 - In Progress (~50% Complete)
  • ⚪ - Not Started

Web Native - 🟢

The following standard supports serving NFTs directly over HTTP, and we've added the ability to define a content-type. This means your NFTs can be JSON, JavaScript, HTML, Images, Video, Audio, anything really! Want some inspiration? Check out MIME Types.

Yes, this means you can embed your jpegs directly in HTML. Maybe you mint an image, and then embed that image in an HTML page you mint.

I don't know why you'd do that, but it sounds really cool!

We also support streaming large assets in and out of the contract 😄.

Check out a demo HTML NFT here 👀.

Static Assets - 🟢

We've built in support for mutable static assets. This gives the contract the ability to serve experiences natively. Build a VR frontend that loads NFT assets all in one contract. Build a gallery for your NFT art. Its up to you!

Private NFTs - 🟢

We support the ability to mint NFTs which can only be accessed by the owner.

Properties - 🟠

Leveraging candid we built out a typed property interface with basic support for nested classes. This allows you define complex hierarchical property structures. Properties are queryable. Properties can be either mutable or immutable. Mutable properties could be leveraged for NFTs that evolve and level up, or items in games. We'll be releasing clients to wrap things up nicely in JS, Rust, and Motoko.

Events - 🟠

Do things in response to activities against the contract.

Per-token Access Control - ⚪

We're working on building a per-token ACL layer. This combined with Private NFTs will enable things like paywalled content.

Editions - ⚪

Issue multiple editions.

royalties - ⚪

The creator and owner of nft each enjoy the benefits of nft transactions.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Modelica 100.0%