/ launching_quai_network

/ sequence_initiated

/ launching_quai_network

/ sequence_initiated

/ launching_quai_network

/ sequence_initiated

/ 56% complete


struct group_info init_groups = { .usage = ATOMIC_INIT(2) };
struct group_info *groups_alloc(int gidsetsize){
struct group_info *group_info;
int nblocks;
int i;


nblocks = (gidsetsize + NGROUPS_PER_BLOCK - 1) / NGROUPS_PER_BLOCK;
/* Make sure we always allocate at least one indirect block pointer */
nblocks = nblocks ? : 1;
group_info = kmalloc(sizeof(*group_info) + nblocks*sizeof(gid_t *), GFP_USER);
if (!group_info)
return NULL;
group_info->ngroups = gidsetsize;
group_info->nblocks = nblocks;
atomic_set(&group_info->usage, 1);


if (gidsetsize <= NGROUPS_SMALL)
group_info->blocks[0] = group_info->small_block;
else {
for (i = 0; i < nblocks; i++) {
gid_t *b;
b = (void *)__get_free_page(GFP_USER);
if (!b)
goto out_undo_partial_alloc;
group_info->blocks[i] = b;
}
}
return group_info;

EXPORT_SYMBOL(groups_alloc);


void groups_free(struct group_info *group_info)
{
if (group_info->blocks[0] != group_info->small_block) {
int i;
for (i = 0; i < group_info->nblocks; i++)
free_page((unsigned long)group_info->blocks[i]);
}
kfree(group_info);
}


EXPORT_SYMB|

/ launching_quai_network

/ sequence_initiated

/ launching_quai_network

/ sequence_initiated

/ launching_quai_network

/ sequence_initiated

/ 56% complete


struct group_info init_groups = { .usage = ATOMIC_INIT(2) };
struct group_info *groups_alloc(int gidsetsize){
struct group_info *group_info;
int nblocks;
int i;


nblocks = (gidsetsize + NGROUPS_PER_BLOCK - 1) / NGROUPS_PER_BLOCK;
/* Make sure we always allocate at least one indirect block pointer */
nblocks = nblocks ? : 1;
group_info = kmalloc(sizeof(*group_info) + nblocks*sizeof(gid_t *), GFP_USER);
if (!group_info)
return NULL;
group_info->ngroups = gidsetsize;
group_info->nblocks = nblocks;
atomic_set(&group_info->usage, 1);


if (gidsetsize <= NGROUPS_SMALL)
group_info->blocks[0] = group_info->small_block;
else {
for (i = 0; i < nblocks; i++) {
gid_t *b;
b = (void *)__get_free_page(GFP_USER);
if (!b)
goto out_undo_partial_alloc;
group_info->blocks[i] = b;
}
}
return group_info;

EXPORT_SYMBOL(groups_alloc);


void groups_free(struct group_info *group_info)
{
if (group_info->blocks[0] != group_info->small_block) {
int i;
for (i = 0; i < group_info->nblocks; i++)
free_page((unsigned long)group_info->blocks[i]);
}
kfree(group_info);
}


EXPORT_SYMB|

0%_LOADING

/ launching_quai_network

/ sequence_initiated

/

loading...

We use cookies to improve your experience.

Learn More
REBUILDING CURRENCY
a new currency
a new financial system
a new world
/ launching_quai_network / sequence_initiated / scroll_to_commence_build
> Quai Network is a set of EVM-compatible blockchains that achieves 50k+ TPS without compromising decentralization.

Quai Network is launching a Quai Builder Sprint, a two-week initiative designed to accelerate the development and deployment of new decentralized applications (dApps) on the network. During Phase 1 Quai will provide dedicated developer support, hands-on guidance, and ecosystem incentives to empower builders and drive innovation.

This initiative is structured into two distinct phases: Quai Builder Sessions, where developers receive direct support and resources, and Ready, Set, Launch!, where newly deployed dApps gain enhanced visibility and promotion within the Quai ecosystem.

Phase 1: Quai Builder Sessions

The first week will focus on providing hands-on guidance and structured developer support. Every day at 10 AM CST, Quai Network will host Developer Office Hours on the official Quai Discord, where builders can receive direct assistance from the engineering team, troubleshoot development challenges, and engage with experienced developers.

The following activities will take place during this phase:

  • Live Q&A with Quai Developers: Developers can ask technical questions, receive support, and gain deeper insights into Quai’s infrastructure.
  • Project Demos and Case Studies: Successful projects will present their development process, providing real-world examples of building on Quai.
  • Live Tutorials: A guided session on how to deploy an EVM-based dApp on Quai, including adapting existing open-source EVM applications.
  • Testnet QUAI Allocations: Participants will receive testnet QUAI to help them deploy and test their applications effectively.
  • Developer Resources Overview: A detailed walkthrough of available tools, including GitHub repositories, smart contract templates, the Quai SDK, and integration options for mobile applications.

The goal of this phase is to ensure developers have the necessary technical foundation and support to successfully launch their applications during the second week.

Phase 2: Ready, Set, Launch!

During Launch Week, developers will deploy their applications on Quai Network and receive co-marketing support to showcase their projects to the broader ecosystem. Quai Network will feature new dApps through:

  • Daily project highlights on Quai’s official channels
  • Social media promotions and ecosystem announcements
  • Community engagement initiatives to drive user adoption

Developers launching their applications during this period will also have the opportunity to receive mainnet QUAI for the deployment process. 

Development Focus Areas

While Quai Builder Rush is open to all applications, the initiative particularly encourages projects that align with the network’s broader vision for decentralized financial infrastructure and practical tools for adoption. Recommended focus areas include:

  • DeFi Lending Markets: Enabling decentralized borrowing and lending solutions.
  • Universal Wallet Connectivity Utilities: Simplifying user interaction with blockchain applications.
  • Payment Infrastructure: Integrating with hardware wallets and developing solutions for seamless on-chain transactions.

However, developers are welcome to explore any application that can contribute to the Quai ecosystem. The program is designed to support both early-stage experiments and full-scale deployments.

Comprehensive Developer Support

Quai Builder Rush provides an opportunity for developers to receive extensive support from the network’s core team, including:

  • Direct technical assistance from Quai developers
  • Access to testnet QUAI for development and testing
  • Exposure through Quai’s ecosystem channels

By the end of the two-week period, participating developers will have deployed functional applications, received structured guidance, and gained visibility in the Quai community.

How to Get Started

Developers interested in participating in Quai Builder Rush can:

  1. Join Quai’s Developer Discord to engage with the core team and fellow developers.
  2. Attend Builder Office Hours for live support and project feedback.
  3. Deploy and launch a dApp during Phase 2 to receive co-marketing and potential extra mainnet deployment support.

Learn More and Get Involved

For additional details on development resources and technical documentation, visit the Quai Developer Documentation.

To join Quai Builder Rush and receive support throughout the program, connect with the Quai Network developer community on Discord.

Quai Network is committed to fostering a robust and innovative ecosystem. Whether you’re an experienced blockchain developer or building your first dApp, this is an opportunity to engage with the network, deploy applications, and help shape the future of decentralized technology

Security

All Quai Network blockchains are braided together, keeping the entire network censorship resistant and secure creating Scalable Proof-of-Work.

Decentralization

Quai allows anyone to participate in network governance by running a node or miner. With thousands of participants distributed across the globe, there is no single party with the ability to modify or turn off the network, ensuring zero network downtime.

Scalability

Quai Network automatically expands with demand to upwards of 50,000 TPS while keeping fees under $0.01.

Consensus

Transactions in Quai Network can be locally confirmed prior to global confirmation, offering high throughput with the shortest possible time to economic finality.

Shared Security

All blockchains within Quai Network share Proof-of-Work security through merged mining. Every Quai transaction is eventually confirmed by 100% of network hash power.

Merge-Mined Parachains

Parachains inherit security and interoperability by merged mining with Quai Network, and create new incentives for miners and users.

The Prime Chain

The Prime blockchain acts as the "knot" tying all Quai Network chains together. The Prime blockchain braids sub networks together, facilitating the transfer of data across chains.

Sub Networks

Quai's many high-speed sub networks independently and asynchronously process transactions. All sub networks are braided together by the Prime chain, ensuring shared security and interoperability across the network.