Flow technical research\u00a0paper<\/a>.<\/p>\nCollections<\/h4>\n
Composed of an ordered lists of one or more hashes of signed transactions, Collections enables the network to optimize the overall network transactional payload.<\/p>\n
Flow Collections, source: Flow\u00a0docs<\/em><\/p>\nObservation<\/strong>: By requiring collection nodes to store transaction payload, Flow creates a built-in data availability layer optimizing data transfer speed. Indeed, while on one hand, collections enable lightweight consensus nodes to agree on transactions orders without storing those, it also enable execution nodes to quickly query transactional payload to advance the network\u00a0state.<\/p>\nCadence<\/h4>\n
Inspired by Libra\u2019s Diem, Cadence is a resource-oriented programming language specifically developed to create secure and scalable smart contracts.<\/p>\n
Key features of\u00a0Cadence<\/strong>:<\/p>\nResource-Oriented programming<\/strong>: Cadence treats digital assets as resources ensuring they cannot be duplicated, lost or access without authorization. Additionally, it ties resources to specific accounts, enforcing ownership rules at the language\u00a0level.Capacity-based security<\/strong>: Access to resource is controlled through explicitly granted capabilities which act as permissions reducing vulnerabilities from unintended access.Strong static typing<\/strong>: The language enforces type safety, minimizing runtime errors and improving code reliability.Developer-friendly design<\/strong>: Inspired by Swift, Kotlin and Rust, Cadence emphasizes readability and ease of use. Additionally, tools like the Flow emulator and Visual Studio Code extensions streamline development.<\/p>\nAdvantages over traditional smart contract languages:<\/strong><\/p>\nEnhanced security<\/strong>: Resources and capabilities prevent common exploits like reentrancy attacks, a significant improvement over Ethereum\u2019s Solidity.Upgradeable contracts<\/strong>: Flow allows smart contracts to enter a \u00ab\u00a0beta state\u00a0\u00bb enabling updates before finalization a rare feature in blockchain ecosystems.<\/p>\nCore Contracts<\/h4>\n
All network core functionalities in Flow are implemented through a suite of dedicated Cadence smart contracts called core contracts:<\/p>\n
Fungible token<\/strong>: Implements the Flow fungible token standard.Flow token:<\/strong> Defines the $FLOW\u00a0tokenFlow Fees:<\/strong> Act as treasury vault for all network collected feesService account:<\/strong> Tracks transactions fees, deployment permissions and provides convenient tooling for $FLOW token operations.Staking table:<\/strong> Manage staked nodes, delegation and\u00a0rewards.Epoch contract:<\/strong> Manage epoch phases and emitting service\u00a0events.<\/p>\nAccounts<\/h4>\n
A Flow account can be conceptualise as a record in the chain state holding the following information:<\/p>\n
AddressBalanceCodeStorage<\/p>\n
Address<\/strong><\/p>\nUnlike Bitcoin and Ethereum, Flow addresses are not derived from cryptographic public keys. Instead, each Flow address is assigned by the Flow protocol using an on-chain deterministic sequence.<\/p>\n
Note<\/strong>: This decoupling is a unique advantage of Flow, allowing for multiple public keys to be associated with one account or for a single public key to be used across several accounts.<\/p>\nBalance<\/strong><\/p>\nEach Flow account created on Mainnet own by default a Flow vault holding a balance satisfying the FungibleToken standard. This balance is also used to pay for transaction and storage\u00a0fees.<\/p>\n
Note<\/strong>: A minimum account reservation of 0.001 $FLOW must be held into any accounts at all times to cover the storage cost of the account (~100kB of data) and ensure that most account won\u2019t run out of storage capacity if anyone deposits anything like an NFT to the\u00a0account.<\/p>\nContracts<\/strong><\/p>\nAn account can optionally store multiple Cadence contracts. The code is stored as human-readable UTF-8 encoded string which makes it easy for anyone to inspect\u00a0it.<\/p>\n
Storage<\/strong><\/p>\nEach Flow account has an associated storage capacity. The account storage used is the byte size of all the data stored in the account\u2019s storage.<\/p>\n
Note<\/strong>: An account storage capacity is directly tied to the balance of Flow tokens of the\u00a0account.<\/p>\nAccount Keys<\/strong><\/p>\nFlow accounts can be configured with multiple public keys that are used to control access. During the account creation, public keys can be provided to interact later on with the account. Additionally, account keys can be added, removed or revoked by sending a transaction which is radically different from blockchains like Ethereum where each account is tied to a single public\/private key\u00a0pair.<\/p>\n
Note<\/strong>: Upon account creation, each account key is being assigned a weight knowing that a transaction has to exhibit a total signature weight greater than or equal to 1000 to be\u00a0valid.<\/p>\nFlow key account schema, source: Flow\u00a0docs<\/p>\n
Observation<\/strong>: Through this account key design, Flow is implementing a built-in multi-sig functionallity for each\u00a0account.<\/p>\nTransaction processing<\/h3>\nTransaction status<\/h4>\n
Similarly to block status, the transaction status represents the state of a transaction on the Flow blockchain and usually follows the below timeline:<\/p>\n
Unkown<\/strong>: the transaction has not yet been seen by the section of the network the user is communicating with through the Access node\u00a0API.Pending<\/strong>: The transaction has been received by a collection node but has not yet been finalised in a\u00a0blockFinalised<\/strong>: The consensus nodes have included the transaction in a block but it has not been executed by execution nodes.Executed<\/strong>: Execution nodes have produced a result for the transactionSealed<\/strong>: The verification nodes have verified and agreed on the result of the transaction and the consensus node has included the seal in the latest\u00a0block.Expired<\/strong>: The transaction was submitted past its expiration block\u00a0height.Flow transaction status, source: Flow\u00a0docs<\/p>\nTransaction finality<\/h4>\n
In the dominant PoS environment, there are three key finality\u00a0stages:<\/p>\n
Preliminary result:<\/strong> Initial answer from the network not ensuring and not linked to any economic penalties (i.e. slashing) if the information provided is\u00a0false.Soft economic finality:<\/strong> The answer provided is backed by cryptographic proof. Additionally, if the informant is deceptive, this latter is facing severe economic repercussion or slashing.Hard economic finality:<\/strong> The provided answer either holds true or the entire blockchain require a\u00a0restart.<\/p>\nOn its end, thanks to its novel network design, Flow is able to fully bypass the preliminary stage to directly reach soft finality in less than 6 seconds and hard finality in about 14\u00a0seconds.<\/p>\n
Transaction finality flow, source: Flow\u00a0Docs<\/em><\/p>\nChain comparison<\/h4>\nTransaction result<\/h4>\n
Once a transaction, is executed, its result is available onchain, providing users details on its success state or any errors encountered during execution. Additionally it also includes all events the transaction might have\u00a0emitted.<\/p>\n
Successful transaction schema, source: Flow\u00a0docs<\/em><\/p>\nNetwork roles<\/h3>\n
Unlike in most other blockchain networks, not all Flow nodes are equals. Indeed, due to the network multi-roles architecture, Flow nodes all specialise and fulfill a specific role in the operation of the\u00a0network.<\/p>\n
Flow node roles, source: Flow\u00a0docs<\/em><\/p>\nCollection node<\/h4>\n
Collection nodes are bandwidth-optimised nodes divided by the protocol into several cooperating clusters. Their first tasks is to manage the transaction pool and collect well-formed transactions to propose to Consensus nodes. Technically speaking, each nodes cluster collect transactions assigned pseudo-randomly by the network, assemble them into collections and submit a collection guarantee signed by a super-majority of the cluster to the Consensus nodes.<\/p>\n
Collection node processing flow:<\/strong><\/p>\nStep 1<\/strong>: A collection node sees a well-formed transactionStep 2<\/strong>: The collection node hashes the text of that transactionStep 3<\/strong>: It signs the transaction to indicate its validity and commit to its storage until its final processing by the\u00a0network.<\/p>\nNote<\/strong>: Collections nodes are required to stake a minimum of 250,000 $FLOW to be confirmed as active node operators.<\/p>\nConsensus node<\/h4>\n
Consensus nodes form and propose blocks in a manner similar to traditionally-structured proof of stake blockchains, using the Hotstuff consensus algorithm to create a globally consistent chain of blocks. Consensus nodes validate that the signed collection hashes submitted to them by Collection nodes were, in fact, signed by the required majority of Collection nodes before assembling the transactions into blocks and finalise them through voting. As such, Consensus nodes act as checkpoints against Collection nodes and held those accountable by verifying that a critical number of Collection nodes reviewed and signed the transmitted transactions. Currently, Consensus nodes are required to stake a minimum of 500,000 $FLOW tokens to be confirmed as a node operator.<\/p>\n
The network currently supports approximately 100 active consensus node operators.<\/em><\/p>\nNote<\/strong>: Flow choses the HotStuff algorithm due to its inherent flexibility enabling to add new participants throughout time.<\/p>\nExecution node<\/h4>\n
Most resource-intensive nodes on the Flow network, Execution nodes are responsible for executing transactions and maintaining the execution state as well as responding to any queries related to it. From a technical standpoint, Execution nodes are computing the outputs of the blocks provided by Consensus nodes while also ensuring the bulk of the network improvement in terms of scale and efficiency through hardware optimisation.<\/p>\n
Transaction execution flow:<\/strong><\/p>\nStep 1:<\/strong> An execution node receive a proposed block from the consensus nodes.Step2:<\/strong> Using the hash of the transaction contained in the transmitted block, the execution node query the transaction payload from Collection nodesStep 3:<\/strong> The execution node compute the new network state based on the transmitted transactionsStep 4:<\/strong> Once all co-adjacent execution nodes have finished to compute the new network state all execution nodes outputs are revealed to avoid spoofing.Step 5:<\/strong> Execution nodes are emitting an execution receipt<\/p>\nNote<\/strong>: Execution nodes are required to stake a minimum of 1,250,000 FLOW to become confirmed node operators.<\/p>\nVerification<\/h4>\n
Verification nodes are responsible for confirming the correctness of the work done by Execution nodes. Individual Verification nodes only check a small amount of the total computation but collectively check every computation many times in parallel.<\/p>\n
Verification Flow:<\/strong><\/p>\nStep 1:<\/strong> A sortition algorithm assigned a chunk of the execution receipt to each validatorStep 2:<\/strong> Validators verify the deterministic execution process by comparing their compiled state and the one transmitted by execution nodesStep 3:<\/strong> If everything is valid, Validators issue to the network a result approval enabling the network to seal the block and assert hard finality for those transactions.<\/p>\nNote:<\/strong> Verification nodes are required to stake a minimum of 135,000 $FLOW to become a confirmed node operator.<\/p>\nAccess node<\/h4>\n
Access nodes act as a proxy to the Flow network. Their main role is to route transactions to the correct Collection nodes or route state queries to Execution nodes.<\/p>\n
Note<\/strong>: Access nodes are required to stake 100 $FLOW to become a confirmed node operator.<\/p>\nObserver node<\/h4>\n
An observer node provides locally accessible, continuously updated, verified copy of the block data. It serves the Access API but unlike an access node, an observer node does not need to be staked, and anyone can run it without being added to the approved list of\u00a0nodes.<\/p>\n
Flow Technical Features<\/h3>\nAccount abstraction<\/h4>\n
Through its account model, Flow provides native support for key use-cases empowering developers to deliver mainstream-ready user experiences enabled by account abstractions.<\/p>\n
Multi-sig transactions<\/strong>: Native support for multi-sig transactions since all accounts are defined as smart contracts.Sponsored transactions<\/strong>: Built-in 3 roles support for transactions providing a native support for sponsored transactions.Bundled transactions:<\/strong> Protocol-level support for transaction bundling across multiple contracts into a single transaction thanks to Cadence explicit separation of contracts and transactions.Account recovery<\/strong>: Native support for account recovery and cycling of keys helping users regain access to account in a secure\u00a0manner.Multi-factor authentication:<\/strong> Native support for multi-factor authentication as developers can easily implement these security mechanism for their users using\u00a0Cadence.<\/p>\nStorage<\/h4>\n
Flow storage model aims to ensure data availability without continuously charging fees for storage while also preventing abuses that could burden the network\u2019s storage resources. To this end, each Flow account has an associated storage used. The account\u2019s storage used is the byte size of all the data stored in the account\u2019s storage. Accounts also have a storage capacity directly tied to the amount of Flow tokens an account has which can be used without any additional cost.<\/p>\n
Note<\/strong>: Currently, the amount required to store 100MB in an account storage is 1\u00a0$FLOW.<\/p>\nScripts<\/h4>\n
Flow scripts are executable Cadence code scripts providing a light-weight method to query execution state in a read-only manner. Unlike Flow transactions, a script is not signed and does not require any transaction fees.<\/p>\n
Note<\/strong>: Scripts are currently executed either on Access nodes or directly on Execution nodes depending on Access nodes configurations.<\/p>\nFlow EVM<\/h4>\n
Introduced as part of of the Crescendo upgrade, the Flow EVM allows Ethereum developers to deploy their decentralised applications on the Flow blockchain with minimal code\u00a0changes.<\/p>\n
Flow EVM key features:<\/strong><\/p>\nEVM equivalence:<\/strong> Flow EVM achieves full EVM equivalence, enabling seamless migration of Ethereum-based projects to\u00a0Flow.Developer-friendly:<\/strong> Ethereum developers can use familiar tools and languages (like Solidity) without learning a new programming languageInteroperability: <\/strong>The Flow EVM bridge allows for the atomic movement of both fungible and non-fungible tokens between Cadence and EVM environmentsPerformance:<\/strong> Flow maintains fast block times (as low as 0.8 seconds), even with EVM compatibility, ensuring quick transaction processing<\/p>\nNative onchain randomness<\/h4>\n
Flow\u2019s on-chain randomness delivers immediate random values within smart contracts and bypass the latency and complexity of oracle integrations. Thus, using this feature, developers can easily obtain robust randomness within a single line of Cadence code and streamline the development process of complex decentralised applications.<\/p>\n
On-chain randomness use-cases:<\/strong><\/p>\nGaming<\/strong>: Integrates fairness and unpredictability into gameplay, enhancing user engagement without\u00a0delays.NFTs<\/strong>: Facilitates the creation of uniquely randomized traits in NFTs quickly, adding to their rarity and\u00a0value.Lotteries & Draws<\/strong>: Offers instant and verifiably fair random selection for lotteries, solidifying trust in real-time.DeFi Protocols<\/strong>: Enables rapid and innovative random reward systems within decentralized finance.DAOs<\/strong>: Assists in unbiased voting and task assignments through immediate randomness.<\/p>\nEcosystem<\/h3>\nNetwork State<\/h3>\n
Despite a small year on year (YoY) increase in terms of network activity of 6.73%, we can observe that similarly to other alternative layer 1 networks, Flow faced some challenges to attract new users atop its ecosystem throughout Q4.<\/p>\n
Active network users, source:\u00a0Flowscan<\/em><\/p>\nRegarding development activity, the recent Crescendo upgrade, introducing full EVM compatibility, successfully sparked a significant surge in contract deployment throughout the past quarter. Nonetheless, it remains to be seen, if this initial surge of interest from developers convert into further decentralisation application development due to the rapid decrease of daily contracts deployed towards the end of\u00a0Q4.<\/p>\n
Daily contracts deployed, source:\u00a0Flowscan<\/em><\/p>\nNetwork accounts creations on their end, still appear to be mostly reliant on hackathon events implying that overall the ecosystem still lack real user traction and do not benefits from notable ecosystem features like Base that would create significant excitment among crypto-native users.<\/p>\n
Flow daily account creation, souce:\u00a0Flowscan<\/em><\/p>\nEcosystem State<\/h3>\n
While still remaining relatively low by comparison with other alt-layer 1 networks, Flow TVL shown a record growth of more than 75% mostly led by the mainnet launch of numerous new projects leveraging the recent Crescendo upgrade across multiple categories (AI, Gaming, DeFi, RWA,\u00a0\u2026)<\/p>\n
Q4 Flow USD TVL, source: DefiLlama<\/em><\/p>\nAdditionally, this newly found EVM-based activity on Flow, also represents a new sizeable network revenue source thanks to the exploding transactional activity induced by those new protocols as shows the more than 800% YoY increase in fees perceived by the network over the second half of the\u00a0year.<\/p>\n
Flow daily network fees, source:\u00a0Flowscan<\/em><\/p>\nDeFi<\/h3>\n
Led by the increasingly favorable environment provided by the network for DeFi traders and the recent increase in ETH-based liquidity following the Crescendo upgrade, Flow DeFi ecosystem significantly expanded both in terms of TVL and available applications over the past\u00a0quarter.<\/p>\n
Across Q4 \u201924, numerous new projects launched across multiple categories:<\/p>\n
Gaming<\/strong>: Sudocat,\u00a0CapshaAI<\/strong>: DevDockSports<\/strong>: Jump.Trade, AiSportsDeFi<\/strong>: MORE, Kittypunch, Trado, ANKR, Pump.FlowNFTs<\/strong>: FlowFun,\u00a0MintifyReal World Assets<\/strong>:\u00a0Beezie<\/p>\nNew infrastructures facilitating the onboarding of new-users into Flow ecosystem also went live over the past\u00a0quarter:<\/p>\n
Alchemy,MoonpayGelatoThirdweb\u2026<\/p>\n
Additionally, Flow also deployed a new community incentive program aimed at supporting its nascent DeFi ecosystem through the unlocking of prizes, giveaways and exclusive offers for active DeFi\u00a0users.<\/p>\n
NFTs<\/h3>\n
While several new projects are currently trying to leverage the recent Crescendo upgrade to propose a new type of immersive NFT based experience, the bulk of NFT volume and interest still remain centered around CryptoKitties and a few large NFT sports-based collections backed by US mainstream sport corporations (NBA topshot, NFL All Day\u00a0, UFC Strike,\u00a0\u2026).<\/p>\n
Latest Technical upgrade<\/h3>\nCrescendo Upgrade<\/h4>\n
Deployed to Flow mainnet on Wednesday, September 4th 2024, the Crescendo upgrade introduced full EVM equivalence alongside major stability upgrades and performance improvements:<\/p>\n
Key Crescendo benefits:<\/strong><\/p>\nFull EVM equivalence allowing any Solidity smart contract to be ported over to the Flow\u00a0networkBlock time of less than 1s versus an industry average of\u00a06s.Improved transaction success rate and reduction in memory usage for managing blockchain state<\/p>\n
Recent Developments<\/h3>\n
The Flow Rewards Store is now live. Users can earn points for the Flow Rewards Store by interacting with various applications on Flow, and they can spend these points on exclusive experiences, real-life items, and onchain\u00a0items.Over Q4, Flow jumped in developer usage and mindshare. Additionally, the Flow World Tour hosted a record-breaking number of builders, as well as conversations with the co-founders of Ethereum (Vitalik Buterin) and Metamask (Dan\u00a0Finlay).The latest telegram integration built on Flow, CryptoKitties: ALL THE ZEN! reached over 150,000 players last November.<\/p>\n
Tokenomics<\/h3>\nGeneral metrics (11\/02\/2024)<\/h4>\nTokenomic design<\/h3>\n
From a tokenomic design standpoint, the network is built around a new Cadence token interface model, called Flow fungible Token Interface<\/a>, leveraging the network account model. More specifically, at the protocol level this new token standard is integrated through the $FLOW native token ensuring the following tokenomic utility functions:<\/p>\nCommodity<\/strong>: $FLOW provide a built-in mechanism to exchange and store value while acting as a reserve currency for the overall network ecosystem.Security<\/strong>: $FLOW enables various value-based security mechanisms (slashing,\u00a0\u2026)Governance<\/strong>: Token-gated governance model ensuring community alignment on governance votes<\/p>\nFlow Fee\u00a0model<\/h3>\n
Transaction fees are the cost paid in $FLOW by a user or an application for a transaction to be included in the Flow blockchain. Fees are necessary to both ensure the network security and provide monetary incentive for active node operators to run the\u00a0network.<\/p>\n
Note<\/strong>: Similarly to other blockchain, in Flow transaction fees are paid regardless of whether a transaction succeeds or\u00a0fails.<\/p>\nFee structure<\/h4>\n
Each transaction fee consists of three components:<\/p>\n
Execution feeInclusion feeNetwork surge\u00a0factorFee Structure, source: Flow\u00a0docs<\/p>\n
Execution Fee<\/strong><\/p>\nThe execution effort for a transaction is determined by the code path the transaction takes and the actions it does. The actions that have an associated execution effort cost can be separated into four broad\u00a0buckets:<\/p>\n
Normal lines of cadence, loops, or function\u00a0callsReading data from storage, charged per byte\u00a0readWriting data to storage, charged per byte\u00a0writtenAccount creation<\/p>\n
Inclusion Fee<\/strong><\/p>\nThe inclusion effort of a transaction represents the work needed\u00a0for:<\/p>\n
Including the transaction in a\u00a0blockTransporting the transaction information from node to\u00a0nodeVerifying transaction signatures<\/p>\n
Note<\/strong>: For now, the inclusion effort is set to 1.0 and the inclusion effort cost is fixed to 0.000001\u00a0$FLOW.<\/p>\nSurge Factor<\/strong>
In the future, a network surge factor will be applied when the network is busy due to an increased influx of transactions required to be processed or a decrease in the ability to process transactions. Right now, the network surge is fixed to\u00a01.0.<\/p>\nNote<\/strong>: Currently, both the inclusion fee and surge factor don\u2019t represent any significant Flow\u00a0fees.<\/p>\nRewards Distribution<\/h3>\n
The rewards distribution schedule in Flow is designed to ensure there is enough liquid supply of $FLOW available in the ecosystem to empower a wide array of use cases and promote fair and diverse participation in the Flow ecosystem. Technically speaking, the total staking reward amount paid upon is known and fixed per epoch and paid directly to network participants by the central pool gathering all transaction fees paid since the last reward payments.<\/p>\n
Note<\/strong>: If the pool happens to be depleted, the protocol is authorised to mint new tokens to cover its lack of treasury.<\/p>\nNetwork expected reward\u00a0schedule<\/strong><\/p>\nIndividual Reward Calculation<\/h4>\n
Each user gets a percentage of the total rewards during each epoch that is proportional to their percentage of the tokens staked by all participants.<\/p>\n
The full reward calculation on a per-user basis is equal\u00a0to:<\/p>\n
New Reward(user) = Tr * (Sn \/\u00a0St)<\/strong><\/p>\nwhere:<\/p>\n
Tr<\/strong> = Total staking rewards to be paid out during the current epoch. (See table\u00a0above)Sn<\/strong> = Amount of FLOW Staked by the target user for the current Epoch. (Different for each\u00a0staker)St<\/strong> = Sum of all the FLOW staked by all the participants in the network. (Changes every\u00a0epoch)<\/p>\nNote<\/strong>: Rewards for delegators are calculated in the exact same way that rewards for node operators are calculated, at the difference that 8% of the calculated reward amount is given to the node operator being delegated to.<\/p>\nFlow value accrual mechanisms<\/h3>\n
In terms of value accrual mechanisms, Flow is showcasing a pretty common set of value accrual mechanisms for active network participants.<\/p>\n
Reward Reduction<\/strong><\/p>\nCurrent network penalty for node operators subject to liveness issues, the reward reduction process naturally lead to a lesser network inflation for any given epoch inducing as such a scarcity impact on the expected $FLOW circulating supply potentially benefiting token holders through price appreciation.<\/p>\n
Staking<\/strong><\/p>\nThe important node staking requirements for node operators structurally reduce the amount of $FLOW available on the market for extended period of time leading to price appreciation for existing token holders due to the decrease token velocity inside the network ecosystem.<\/p>\n
Network inflation<\/strong><\/p>\nFor active participants actively ensuring the network security the network inflation represents another additional form of value accrual mechanism enabling them to accrue interest on their capital at the expense of passive token\u00a0holders.<\/p>\n
Slashing [not\u00a0live]<\/strong><\/p>\nWhile not being currently live on the network, the future slashing mechanism will without a doubt create a significant liquidity sink in the overall network economic model and create additional scarcity pressure on the protocol native token supply if similar to other comparative alternative layer 1 networks, this slashing mechanism is backed by a burning mechanism.<\/p>\n
Initial token distribution<\/h3>\n
Upon the genesis block creation in June 2020, 1.25 billion $FLOW were issued and allocated as\u00a0follows:<\/p>\n
Large Backers<\/strong>:\u00a011.1%Small Backers<\/strong>:\u00a08.9%Community Sales<\/strong>:\u00a010%Development Team<\/strong>: 18% allocated to the development team through a pool following a vesting unlock of 3\u00a0years.Dapper Labs<\/strong>: 20% intented to be hold as part of a long-term treasury helping the long-term development of the protocol.Ecosystem Development<\/strong>: 32% aimed at bootstrapping the development of the protocol ecosystem and network\u00a0effectFlow Initial token allocation, source: Flow\u00a0blog<\/p>\nProtocol Fundings<\/h3>\n
Seed round <\/em><\/strong>(source: Cryptorank)<\/em><\/p>\nDate: N\/APrice: $0.1Amount raised:\u00a0$13.9M<\/p>\n
Private Round <\/strong>(source: Cryptorank)<\/em><\/p>\nDate: N\/APrice: $0.1Amount raised:\u00a0$11.10M<\/p>\n
ICO <\/em><\/strong>(source: Cryptorank)<\/em><\/p>\nDate: 22\/09\/2020\u201302\/10\/2020Price: $0.1Amount raised:\u00a0$9M<\/p>\n
Undisclosed round <\/em><\/strong>(source: Cryptorank)<\/em><\/p>\nDate: 10\/05\/2022Price: N\/AAmount raised:\u00a0$725MInvestors: a16z, Dapper Labs, DCG, Greenfield Capital<\/p>\n
Team<\/h3>\n
Roham Gharegozlou<\/strong>, Co-founder & CEO at Dapper\u00a0Labs<\/p>\n