Search…
⌃K
🔊

Scalability

HyperMint can sustain the following throughput, measured in requests per second. Higher throughput can be achieved in coordination with the HyperMint team.

Throughput Limits

Request Type
Contract Type
Throughput
Client SDK Get Contract
ERC721, ERC1155
30,000 requests per second
Client SDK Get Token
ERC721, ERC1155
10,000 requests per second
Client SDK Authorise Buy
ERC721
2,500 requests per second
MoonPay Integration Mints
ERC721, ERC1155
1,250 requests per second
API Mint Requests
ERC721, ERC1155
1,500 requests per second
API Get Mint Status
ERC721, ERC1155
2,000 requests per second
API Get Allocated Mints
ERC721, ERC1155
1,000 requests per second

Mint Creation Throughput Limits

When mints are submitted through the API or through the MoonPay integration, they are queued and sent to the network. This process of sending from the queue to the network scales independently of the requests to the HyperMint platform.
Network
Contract Type
Throughput
Ethereum
ERC721
10 mints per second
Ethereum
ERC1155
15 mints per second
Polygon
ERC721
50 mints per second
Polygon
ERC1155
70 mints per second
If mints are delivered to HyperMint faster than this, they will be queued and processed in the order they are received.

Methodology

HyperMint regularly tests our platform to see how well it scales under demand. We pay particular attention to the minting process as that receives the most load during viral moments. Every two weeks we test and review a full suite of simulated scenarios that cover our entire system. We're constantly improving our scalability and the numbers in this section are updated regularly.
HyperMint carries out scale testing across the same APIs that you and your end users use. We test on a full-scale replica of production and we use a blockchain testnet -never an emulator!- to maximize accuracy. We only test with large contracts with many tokens and many mints. Most of our scenarios are measured across a million requests, to a contract with a million mints. The slowest actions are measured across at least ten thousand requests.
Many of these requests represent requests to perform on-chain actions, like minting. We report the number of requests we can queue up for later processing each second. Actual on-chain actions tend to lag behind based on the performance of the chain.

Feedback

Something not quite right, unclear or can't find what you are looking for? Please let us know at [email protected] and we will get back to you as soon as we can.