alto-io/nft-minter

Mint non-fungible tokens via a web server

nft-minter's Issues

[nft-minter by OP Games] : Add support for NFT tokens minted on NEAR Protocol

[nft-minter by OPGames]: Add support for NFT tokens minted on NEAR Protocol

Prize Bounty

Up to $3000 USD in NEAR (with matching grants)
One grand prize and two runner up prizes

Challenge Description

nft-minter is an open-source framework for minting NFTs, currently using IPFS and the Ethereum blockchain. We would love for it to be built upon by hackers so it will eventually become blockchain agnostic.

The challenge is to provide an option to users of nft-minter to mint their tokens on NEAR protocol instead of on the Ethereum blockchain, in the most developer friendly way possible.

The first step is probably to create an npm script similar to yarn contract:deploy:rinkeby that will deploy the contracts on NEAR instead of Ethereum. Once done, hackers should then update the frontend on packages/client to allow developers to create and mint the tokens via the web form.

This could be a stretch goal for the challenge, but we envision the ideal flow to be as simple as just changing an variable in the .env files. For example, adding a "blockchain=near" .env variable will automatically deploy the contract to the desired blockchain.

Submission Requirements

Hackers should create a pull request for this challenge, tagging this issue for reference. The completed submission should include the updated code (backend and frontend) and an updated README.md file discussing how to use nft-minter for NEAR tokens.

The application must be (1) the original work of the individual participant or the participating team; (2) third-party technology used by the individual participant or the participating team must be subject to valid perpetual, irrevocable licenses.

By submitting an application, the individual participant and each member of a participating team, jointly and severally, represent and warrant that the application, and all components thereof, will not violate any rights of any person or entity, including without limitation, any copyright, trademark, patent or other intellectual property rights, or violate any applicable national, federal, state, or local laws, regulations, or policies, including those relating to export control.

Judging Criteria

1. Robustness and completeness of solution
2. Developer experience (the more documented and the less steps for developers needed, the better)
3. Potential reusability across blockchains (how well the solution is able to abstract away blockchain specific code)

Helpful References

NEAR NFT discussions

• https://gov.near.org/t/nft-standard-discussion/853/14
• https://github.com/Mintbase/near-nft-standards/blob/main/ERC721_reference.md#rust-equivalent
• near/NEPs#171

Other Links

• Opensea erc1155 format used by nft-minter: https://github.com/ProjectOpenSea/opensea-erc1155
• Example deployment: http://nft-minter.herokuapp.com/
• Observable Article: https://observablehq.com/@polats/web-3-0-explorable-3-nfts-game-items-with-real-world-value

Winner Announcement Date

April 9th 10am PST

More Info

For questions, please comment on this issue. For more long-form discussions, we can also use Github Discussions.

Token creation error: cannot estimate gas; transaction may fail or may require manual gas limit

I get this error when I try to create a new token. It happens on http://nft-minter.herokuapp.com/ as well as on my local deployment.

How to reproduce

• Open minter frontend
• Create new token: Happens with both the contract owner address or personal wallet address.

Error message

cannot estimate gas; transaction may fail or may require manual gas limit (error={"code":-32000,"message":"execution reverted"}, method="estimateGas", transaction={"from":"0x549deAF2d8819B49Bae0C4d43Da90D65dCBF29C9","to":"0xd7E37BBA4eF7e2f11d12df84D9635fe5c4b91255","data":"0xe38e3b24000000000000000000000000243566e830705ce95b09ae66705c8b291b3333100000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"}, code=UNPREDICTABLE_GAS_LIMIT, version=providers/5.0.24)

Current environment

• Google chrome 89.0.4389.90
• Metamask 9.2.0

Permanent metadata storage support: please add

Could the devs of this please integrate automatic Arweave.org data upload in addition to IPFS?
See rationale at https://keepyourNFT.com