Skip to content

Dynamic Blocks: Fast When Quiet, No Backlog at Peaks

Dynamic blocks explained: fixed-size blocks build backlogs on busy days. Hyper 0X lets each L2 grow and shrink its blocks with demand, so payments never queue.

Buckleson logoBuckleson Engineering4 min read

How it works

Fixed blocks queue salary-day payments, dynamic blocks grow with the peak

Without Hyper 0X

Salaries late, while spare compute sits idle

  1. BankSalary-day peak
  2. Fixed blocksSame cap every block
  3. BacklogPayments wait in line
  4. EmployeesSome salaries late
  1. 1On salary day, thousands of payroll payments arrive at once.
  2. 2Every block has the same fixed cap, on quiet days and busy days.
  3. 3A backlog forms at once, even though the network had spare compute.
  4. 4Some salaries arrive late.

With Hyper 0X

Peak absorbed, no backlog builds

  1. BankSalary-day peak
  2. Payroll L2Own block settings
  3. Dynamic blocksGrow toward the maximum
  4. Seal ruleSize target or time limit
  5. EmployeesPaid with no backlog
  1. 1The payroll L2 sets a minimum block size, a maximum block size and a time limit.
  2. 2When the salary payments arrive, blocks grow toward the maximum.
  3. 3A block seals when it reaches its size target or when the time limit runs out.
  4. 4Dynamic blocks add no compute, but they remove the bottleneck of a fixed block size.

Dynamic blocks change size with demand. On Hyper 0X, a block seals when it reaches its size target or when a time limit runs out, whichever comes first. To seal a block means to close it and add it to the chain. Quiet periods get small blocks that seal quickly. Busy periods get larger blocks, so a sudden peak does not turn into a queue.

What goes wrong with fixed-size blocks?

Most blockchains use fixed-size blocks. That works on an average day, but traffic is rarely average. Think of a bank that runs payroll on its own L2, a private blockchain for one application. On salary day, thousands of payments arrive in a few minutes. With a fixed cap, a backlog forms at once, and some salaries arrive late. This happens even though the network had spare compute a moment earlier.

How do dynamic blocks work?

Each L2 on Hyper 0X sets three values: a minimum block size, a maximum block size and a time limit. When the network is quiet, small blocks seal on the time limit, so waits stay short. When load suddenly increases, blocks grow toward the maximum, and the backlog never builds.

What is the honest limit?

Dynamic blocks do not add compute. They remove the artificial bottleneck of a fixed block size. So the network uses the capacity that you have when you need it.

Why one L2 per workload helps

Every customer runs their own L2, so a payroll peak at one bank never slows down the workload of another institution. Each L2 sets its own block settings, policies and bridges. All of them settle to one shared record on Hyper 0X. Read more in private L2 vs public blockchain.

Frequently asked questions

What are dynamic blocks?

They are blocks whose size follows demand. A block seals when it reaches its size target or when a time limit runs out, whichever comes first. So quiet periods get small, quick blocks, and busy periods get larger ones.

Do dynamic blocks add capacity?

No. They remove the artificial bottleneck of a fixed block size. So the network uses the compute that you already have when you need it.