Why REF cannot enter the Mining Pool Reference Circuits can help Builders learn and build But they cannot become part of a Mining Netlist Recursive references can increase Area without matching real Burn in the current layer BEM measures real Work

How Design Commitment protects Builders Builders can submit a Design Commitment before Tape Out It creates a verifiable commitment before the Design is revealed Seeing a Netlist is not enough to take the Design Slot Commit first Then build openly

BEM is not first to submit forever Each Task and Processor continuously compares valid Designs by Design Cost A correct lower cost Design can become the new Optimal First Optimization continues

How Design Quality works BEM compares the Builder Design Cost with the Task Reference Cost A better correct Design can earn higher Design Quality Quality has a ceiling and a floor Extreme results cannot grow without limit

Critical Path Depth is the longest Combinational Path in a Circuit A longer path means greater delay And it affects Design Cost BEM measures both scale and speed

Fewer Gates do not always mean lower Design Cost BEM considers Recursive Area And the longest Combinational Path A smaller Circuit with a deeper path may not be the more efficient Design

Every BEM Task has an official Reference Implementation It is synthesized and verified Its Reference Cost is fixed when the Task is created Builders do not need to copy it The challenge is to build a correct and better Design

Creating a Circuit in BEM requires a permanent Transistor Burn It is not a temporary stake It is not a cost that can be withdrawn Burn puts Design Work on chain Mining Work becomes verifiable

What PoD Mining mines BEM does not ask you to contribute hash calculations alone You submit a Circuit Design It completes a task Passes verification And turns real Burn and Design Quality into measurable Work Design Verify Mine That is Proof of Design

How Area works Area measures the scale of a Circuit A = g + 6s Example A Circuit has 10 recursive Elements It has 2 LATCH Its Area is 10 + 6 × 2 = 22 LATCH has greater weight It stores State as well as logic

Why Reference Burn is not counted again Imagine you use an existing Circuit That Circuit already Burned 100 components in the past Your new Design only Burns 7 components BEM counts your 7 It does not count the old 100 again References can help you build They cannot repeat past Work

BEM first looks at the components you actually Burn b* = n + m Example You Burn 5 NAND You Burn 2 LATCH Your Burn Work is 5 + 2 = 7 Those 7 units are real Work from your current Design

$BEM is deeply saddened by this security incident When the frontend users see no longer matches the content they actually sign, even the most complete approval process can be deceived $BEM is the first Proof of Design Mining Example based on TapeOut We are not a custodial service or security audit institution, and we cannot promise to prevent every attack But $BEM has always believed that key On Chain actions must be built on a verifiable foundation

BEM is built through Work Every Circuit starts with a Design Every Design starts with a Builder

Build from NAND Store state with LATCH Create the Circuit Prove the Design Turn Work into Mining

The BEM Mining flow Connect your wallet Read the available Circuits Arm the Mining position Start with a live check Mine BEM Claim your rewards

If Design contribution became too small Optimization would barely matter BEM keeps the Design component linear

Why does BEM not compress Burn Cost Because splitting the same amount of burn into many pieces could otherwise drain the Mining pool

Keep building！！

What happens when someone finds a better Design The Task remains open A new Design can replace the current optimal Design The strictly smaller C takes the optimal slot The previous Design keeps its burn But loses the Design premium