Hashink is a dapp for fans to request and purchase autographs from their stars and allow them to sign and send them digitally by using NFT technology.
- Signers will be spotlighted for an X amount of time
- Only one signer at a time
- VIPs will sign through our backend and their private keys will be hardcoded for this launch version
- No account creation for now
- 10%-100% proceeds will go to hardcoded account for charity
- User may uplaod picture to sign on top of
- VIP will sign on top of picture canvas
- Signer Signup form [email, price, avatar, signature]
- magic.link (?)
- Minimum backend to store celebrity image, their autograph, etc
- Requester metamask connect
- Users can request an autograph.
- Celeb can sign an autograph.
- User can view their autograph's gallery.
- User and celeb payments work through their wallets.
- Requests and celebrities (critical data like price or response time) stored on-chain.
- Should come back to this at some point.
- “Celeb” profiles created manually
- Users can request an autographed photo.
- Celebs and users can pay with FIAT (Circle integration)
- What token are we using? (I thinking using USDC and DAI would be best, otherwise we can consider using something like DePay)
- Search function
- Filtering
- Setup Python bot to ‘@’ signers
- Layer 2 (?)
- User reviews
- 2 eth accounts, user + celeb
- Eth transactions between them using the hashink contract as an escrow
- Pages and features:
- Home page
- ranking
- celebs marketplace
- create account
- Celeb: connect twitter + upload [signature+name+etc]
- User gallery
- List of hashink NFTs
- Share capabilities
- Autograph request
- Form with basic input
- Backend feature: users request/receipt notification system (!)
- Autograph canvas
- Scribble thing
- Background Image placement
- Send button
- Profile page
- add/edit eth account
- Home page
- Smart Contracts: Solidity + HardHat
- Query layer: The Graph
- Frontend: React + TypeScript (Next.js for fullstack capabilities)
- Backend: When needed, resort to Python
- Framework: flask vs django?
- Database. PostgreSQL
- External Storage: Pinata
- Authentication: Magic
- Hosting: Heroku
Question: What are we going to store on-chain and off-chain?
Question: Where are we going to deploy our product?
Question: Are we going to use different environments and different development branches?
- ERC-721
- EIP-2981
- ERC-20
- Cameo
- Nifty.ink
Royalties are tricky because we have to either;
- implement our own royalty system and marketplace (current best solution)
- implement zora or another protocol’s system
- wait for the ERC20-royalty standard to be ready
Existing platforms that have royalties implemented:
- Rarible:
- Zora:
- Opensea:
Existing non-marketplace projects that have royalties implemented are:
*Mintable *…?
Currently, a range of marketplaces (Rarible, OpenSea, Zora,...) offer their own system for royalties (where any secondary sale that is made, the creator gets X% back of that sale), although, none of them work on any marketplace outside of their own. It exists the EIP-2981 (NFT Royalties Standard) which is a standardized way to handle royalty payments for ERC-721 tokens, but it’s only a proposal and it’s not approved yet.
Question: Royalties implementation?
What technical solution are we going to apply to offer payment of royalties on our product?
- Develop our own system for royalties. This gives us a lot of flexibility but forces us to develop a marketplace where users can sell their NFTs. It also implies that if the NFTs are sold on other marketplaces, the creators will not receive the royalty.
- Implement the EIP-2981 standard in our ERC-721 contract. This also implies developing a marketplace since this standard is not yet supported in any marketplace since it has not been approved. It also has the problem that if the NFT is sold on another marketplace, the creator will not receive the royalty payment.
- Perform the mint of the token in another marketplace such as Zora or Rarible. This implies that the token will not be created in our contract. It is also not a cross-marketplace solution.
Question: Do we want to charge a fee on secondary sales?
This decision may affect the previous point. If we want to charge a fee in secondary sales, the solution of performing the mint of the token in another marketplace does not serve us since we will not have control of the transfers.
Question: Do signers need to sign up?
Question: How are we going to verify the authenticity of celebrity accounts?
The idea is for the celebrity to publish their Ethereum address on their official Twitter account. But this process can have security problems if your profile is hacked.
Question: What currency are we going to use to pay for the autographs?
Options: ETH or a stablecoin like USDC. If we use ether, the balance will be stored in our contract. If we use a token, the balance will be stored in the token’s contract. If we use USDC we will be more prepared to integrate with Circle Protocol since it uses USDC to send payments to bank accounts.
Ideally a user should not have to pay funds to request an autograph. Is there no way to escrow the funds? Use an oracle service if we have to (not exactly sure how this would work though). It immediately shuts a lot of consumers out.
Signing an autograph on a phone is hard to personalize given the size of available space...
Stars can create many generic autographs (one at a time) and store them in their hashink web account. Later, fans may insta-buy these autographs without going through he waiting period. These autographs could be less expensive.
Celebs may record a video on top of which they sign their autograph.
Multiple signers, one NFT. The NFT is either;
- minted once all signatures have been received or;
- A new NFT is minted each time an additional signer is added
Being able to add a autograph on top of an existing NFT’s picture. Of course this won’t edit or modify the original NFT, but will mint a new one.
This section defines our User Stories. This collection is going to define our product.
- Celebrity POV
- A celeb wants to register to sell autographs.
- A celeb wants to view pending requests.
- A celeb wants to sign a pending request.
- A celeb wants to get paid once an autograph is signed.
- A celeb wants to be notified when a request is created.
- A celeb wants to update his profile.
- User POV
- A user wants to register to request autographs.
- A user wants to see celebrities available to sign with price and response time.
- A user wants to request an autograph.
- A user wants to request an autograph with a photo.
- A user wants to see his pending requests to be signed.
- A user wants to remove a request and get the money back.
- A user wants to be notified when a request is signed.
- A user wants to see his autograph gallery.
- A user wants to sell an autograph.