Flow blockchain is cool. Start leveraging it now with Rarible Protocol!
If you’re looking for alternatives to the Ethereum blockchain, there are plenty of different options. One of them is Flow, a blockchain developed by the CryptoKitties and Dapper creators. It was built with scalability in mind and was tailored for intense blockchain usage. In this article, we will walk through Flow features in more detail, talk about what makes it unique, and explore the creation of NFTs on the Flow blockchain using Rarible Protocol.
List of contents:
- What is the Flow Blockchain?
- Flow contracts on Rarible Protocol
- How to create NFTs on Flow using Multichain SDK
What is the Flow Blockchain
Speaking in marketing terms, Flow is “a fast, decentralized, and developer-friendly blockchain, designed as the foundation for a new generation of games, apps, and the digital assets that power them.” To be honest, after researching it for a while, it does appear so. Let’s break it down a little, and highlight all the pros.
There are 4 main reasons why Flow is considered unique, often referenced as the “Four Pillars”, which are:
- Multirole architecture
- Resource-oriented programming
- Developer ergonomics
- Consumer onboarding
We’ll now break down each pillar, so you can get a better understanding of Flow blockchain.
On Flow, instead of every node managing everything around transactions processes (like storing the entire state), the dev team had them split into pipelines. What that means in practice is that the work is split into a few different parts, which allows the blockchain to scale dramatically.
What resources mean, in this context, is a new way of representing asset ownership. Thanks to Cadence (which is the native language of Flow’s smart contracts) “developers can create uniquely durable digital artifacts where ownership is tracked by the language itself, enabling a powerful new category of applications” (source).
By developer ergonomics, Flow means: developer-friendly smart contracts creation. Additionally, smart contracts on Flow are upgradable. On Flow, you are allowed to deploy a contract to mainnet in its “beta state”, allowing the authors to incrementally update the code. Users are alerted about the status of the contract and are able to choose if they want to trust it now, or only after it’s finalized.
Flow puts a lot of effort on consumers. For example, ETH transactions contain very little information about the transaction itself. You just trust it, which is not ideal. On Flow, you get detailed transaction info and guarantees about what transactions can and cannot do.
In my honest opinion, Flow does sound pretty neat. Now it’s time to dive into how we can take advantage of it with Rarible Protocol.
Flow contracts on Rarible Protocol
As mentioned in the introduction, I will also provide the contracts Rarible Protocol distribute on Flow. There are four of them at the time of writing.
- RaribleFee: fee manager that holds the rates and addresses fees.
- LicensedNFT: contract interface adds royalties to NFT. You can implement this LicensedNFT on your contract (along with NFT), and your royalties will be distributed when trading on Rarible.
- RaribleNFT: the Rarible NFT contract that implements the Flow NFT standard is equivalent to ERC-721 or ERC-1155 on Ethereum.
- RaribleOrder: marketplace contract is the wrapper for the standard NFTStorefront, handling market orders.
Smart Contracts Addresses
Another important thing is the address of the Smart Contract that we want to use. Currently, Rarible has 4 contracts deployed, you can see them below. If you want to copy or read them, you can find all the information here.
We need those addresses because, in the Multichain SDK (which used to be called Union SDK), we’re referencing entities like collection ID, token ID by Union Addresses, which consists of blockchain name and address after colon, like this:
(yes, contract addresses on Flow look funny 🤡)
How can you create NFTs on Flow using the Multichain SDK?
You can follow the project template that I’ve created.
Everything is already set up to save you trouble and time. We won’t cover every detail as I already did in past articles, so if you are interested in further explanations, please refer to:
The hardest part about using the Multichain SDK is setting it up, but we’ve already done that for you on the GitHub template. Now, I’ll walk you through the Flow-specific aspects of the process.
Which wallet should we use for Flow?
The first important question is, which wallet can we use for Flow? Unfortunately, you can’t access it from Metamask. According to official Flow suggestions, there are two options:
In this example, we’ll be using Blocto (which is also referenced as FCL). Create a new account, and let’s get started.
Finally! It’s time for the coding part. 🥳 I will be your guide, and hopefully, make this process super easy.
- Choose FCL as the desired wallet in _app.tsx
When it comes to working with the Multichain SDK, there are two things that have to be right in order for the rest to work.
- Network environment,
- Union address
A network environment is needed for sending and signing transactions. You can treat it just like a login functionality. Multichain addresses, on the other hand, are needed because we’re interacting with a few blockchains using one code base. So the code needs to know which blockchain (first part of the Multichain Address) and which entity (second part of the Multichain Address) we want to interact with. Values on “desired wallets” will translate to buttons on the frontend (you can style them on an sdk-wallet-connector file using the Options function), which allows users to connect with chosen blockchains.
2. Prepare Mint
Get information about the way you can mint a token. Information such as:
- is lazy minting supported?
- is multiple minting supported?
- is the provided collection address valid?
Remember that you can always check what’s inside a response just by consoling it out. At the end of the function, we’re storing the values which we’re interested in, within useState hooks.
In this step, we’re submitting the response that we got in step #2. The best way to do it (for me, at least), is to store it in the useState hook 🪝. In order to successfully mint an NFT, we also need URI, lazymint, and supply. One more thing I wanna cover in greater detail is URI.
First things first, in order to successfully display an image on Rarible, the URI has to be in the following format:
The second thing is that the URI should point to a metadata object like the one shown below.
If you want to check out what’s under your URI on IPFS, you have to merge https://rarible.mypinata.cloud/ipfs/ with your hash. That’s it! 😎
In this article, we’ve walked through the process of creating NFTs with Multichain SDK, talked about how the Flow blockchain works and what makes it unique, and covered what is the proper way to store the URI.
If you have any further questions, we are always ready to help you! Join our discord, and we will provide the support you need!
Rarible DAO discord: https://discord.com/invite/zqsZsEWBbN
Consider subscribing to our weekly newsletter: https://www.getrevue.co/profile/raribleprotocol
My personal contact information:
Discord: Szymon From Poland#6093
Happy coding, amigos!