Everything You Need to Know About PB
This site is hosted on IPFS, fully decentralized and censorship-resistant. You can also browse the IPFS copy.
Important Notice: Read Before Connecting Your Wallet
By interacting with the Perpetual Bitcoin (PB) protocol, you acknowledge and agree to the following terms. If you do not accept these terms in full, you should not proceed.
PB is a finished, immutable 21 million supply protocol with price-based unlocks that settle into USDL. When market price reaches your specific checkpoints, ⅓ of your remaining locked position is automatically settled into USDL. No roadmap, no promises, just deterministic on-chain rules. If you want the shortest plain-English intro first, read PB in 60 Seconds.
The 21M number is a reference to Bitcoin's "total supply," a proven model of fixed scarcity. However, PB is unique in its unlock mechanism. We're not copying Bitcoin's success; we're building on its philosophy with new mechanics.
PB is deployed on PulseChain, a high-speed, EVM-compatible blockchain. We chose PulseChain for its low transaction costs and growing ecosystem.
PB is a utility token on a decentralized protocol. There is no company, no team, no issuer, and no counterparty, just you and the smart contract. No one promises you returns. There is no yield, no staking reward, no APY, and no dividend. When unlocks happen, your locked position settles into USDL under the protocol rules, normally through internal netting and, if needed, through the AMM fallback path. It is still the value of your own tokens, not someone else's money. PB does not represent equity, debt, or earnings.
That said, consult a lawyer for your jurisdiction, regulations vary globally.
PB is a fully autonomous protocol. No admin. No upgradeability. The team that built it has no special control or governance rights. Everyone is equal.
No. PB has no governance, no DAO, and no voting. All protocol logic is hard-coded and immutable. This removes bureaucracy and ensures fair, deterministic execution.
PB is built around one core rule: no outside party should be able to interfere with the system. If the stable asset inside the protocol has freeze, blacklist, pause, or admin controls, then PB is not truly trustless.
USDL has no blacklist. No freeze. No admin pause. It is the only dollar-pegged (ish) stablecoin on PulseChain that matches PB's trustless design. That is why PB uses USDL for purchases, unlock payouts, and the canonical LP pair.
Presale offers 555 blocks at a fixed cost of 555.5 USDL per block. When you buy, you receive a PBIOU NFT (ERC-721, non-transferable) representing your block purchase. The PBIOU records your block number, entry price, and buyer address on-chain.
At launch, the LaunchConverter contract converts your PBIOU into a real PBt position:
it calculates your PB amount (555.5 / entryPrice), allocates your tokens through the vault
(3.69% liquid + 96.31% locked PBc), mints your PBt tracker, and burns the PBIOU. Conversion happens
in batches and is handled automatically.
The PB you receive per block depends on your block’s entry price. Early blocks get more PB (~15,054 PB at block #1) while later blocks get less (~10,379 PB at block #555). Entry prices range from 0.0369 → 0.05352 USDL/PB and determine your unlock thresholds.
During presale: minimum is 1 block (555.5 USDL) and maximum is 5 blocks per address (enforced on-chain). Purchase price is fixed per block, while entry prices vary by block for unlock timing.
After mainnet launch: that presale cap no longer applies. Live vault buys are not capped by the protocol in the same way.
You can "shield" a purchase by providing a recipient address when calling the buy flow (the Dapp uses the Vault's recipient parameter). This lets you buy and send in a single on‑chain transaction, useful for gifting, custodial transfers, or directly routing purchases into recovery/inheritance workflows (PBr / PBi). Shielding is simply a user pattern: the buy mints the PBt for the specified recipient so no additional move is needed.
PB is fully on-chain and decentralized. You'll need a crypto wallet (e.g., Internet Money, OKX, MetaMask, Trust Wallet) connected to PulseChain. No KYC, no usernames, no middlemen.
No. All purchases are final. Once you participate, you get a PBt tracker NFT recording your purchase, entry price, and unlock schedule. This is by design. It ensures commitment and prevents gaming.
Each block gets its own entry price and its own unlock schedule, so yes, buying multiple blocks lets you build a ladder instead of relying on one single entry. If you want the strategy side of that, see Investment & Strategy below.
Each block has an entry price on a fixed curve. Block #1 = 0.0369 USDL/PB, Block #555 = 0.05352 USDL/PB. Linear interpolation fills in between. Early blocks = lower entry price = lower unlock thresholds. Purchase price remains fixed at 555.5 USDL per block.
PBc (Perpetual Bitcoin Claim) is a non-transferable ERC-20 token issued when you buy PB. It represents your locked allocation and is tied to your wallet. You cannot sell it or transfer it. It only settles into USDL when price reaches the next checkpoint.
Each checkpoint does two things: the trigger price is set by your entry price, and when that trigger is reached, 1/3 (one-third) of your remaining locked amount settles into USDL.
Trigger prices follow the formula: checkpoint_n = entryPrice × (1.5555^n)
Example: If your entry price is $0.04, then the first checkpoints are:
If you have 10,000 locked PB, the unlock sequence would look like this:
Unlocks continue until only dust remains. Every 55.55% price increase (×1.5555 multiplier) triggers another checkpoint where ⅓ of your remaining locked amount unlocks.
Since each unlock releases only ⅓, the remaining balance decreases geometrically. Eventually, the locked amount drops below 15 Satoshi (dust threshold), at which point the vault automatically sells the entire remainder to your wallet. Your tokens stay locked until those rule-based settlements occur. That is intentional: the design keeps remaining exposure under the same price-based rules instead of unlocking everything on a calendar.
No. PBc is non-transferable by design. You cannot sell, gift, or delegate it. Only the vault can move it during unlock settlement.
Yes. Use the PB Dapp to view your PBc balance, PBt positions, entry prices, current checkpoint, and next unlock threshold.
Unlocks are settled through convergent netting inside each buy transaction. When the next buyer calls buyPBDirect():
Settlements are automatic and claimless: you do not need to submit a transaction or pay gas to receive USDL, proceeds are transferred directly to your payout address when an unlock is settled.
What if a buy is smaller than the unlock? The vault handles this with a NET SELL path:
it reduces to a single unlock (K=1), uses the buyer's USDL for part of the payout, and sells vault PB on the
AMM to cover the shortfall. You still get paid in full. As a final fallback, anyone can call
executeUnlock(pbtId) permissionlessly to force this unlock to settle via AMM sell.
The vault is an autonomous smart contract that:
During the Distribution Phase, 36.9% of each buy's net USDL is paired with vault excess PB and added to the AMM pool. This serves two purposes:
All PB purchases route through the vault's buyPBDirect() function, not a raw AMM swap.
This is necessary for two reasons:
buyPBDirect()
keeps the entire flow in one clean, predictable call.In short: the vault is the exchange interface. It calls PulseX internally (63.1% AMM buy) after netting and LP are handled, so you still get AMM-priced PB, just with fair rules enforced.
Yes. PB is a standard ERC-20 token. You can sell (or transfer) your liquid PB on PulseX or any DEX at any time, no vault interaction required. The split and netting mechanics only apply to buying.
At genesis, effectively all of it. The full 21 million PB starts under immutable vault control, not in any human wallet. No person has a key to a private treasury or team allocation.
As users buy in, only 3.69% of each allocation becomes immediately liquid. The other 96.31% stays locked as PBc until future price checkpoints trigger settlement. So even after distribution begins, most of the system's supply remains contract-governed rather than freely circulating.
The initial LP is seeded with presale proceeds (USDL) paired with vault PB at a launch price of 0.05555 USDL per PB. The exact pool size depends on how much USDL the presale raises.
Completely. All vault operations are on-chain and auditable. You can see every unlock, every swap, every LP addition in real time using a blockchain explorer.
You control your slippage tolerance. On the AMM, you can set a minimum amount out to avoid excessive slips. For large sales, the vault's LP additions over time should reduce slippage.
No. PB is not a time-lock protocol, it is a value-lock protocol. PBc is already force-held by the contract: it is non-transferable, only the vault can move it, and that only happens when a price checkpoint is reached.
One thing to know: executeUnlock() is permissionless. Once price hits your trigger,
anyone can call it, and during normal buys the vault batches up to 500 unlocks automatically.
You cannot opt out or delay an eligible unlock. When it fires, your PBc is converted to USDL and sent to your
payout address. This is by design: the protocol does not let you keep a value-locked position past its trigger.
If you want to re-lock later, you can reinvest that USDL into a fresh buy
(via buyPBDirect()) or VLock any liquid PB you hold to get a new locked position.
See the VLock question below.
The vault has a voluntaryLock(pbAmount) function that lets you send liquid PB back
into the vault in exchange for PBc + a new PBt position, exactly as if you had just bought it.
Your PB goes back into the vault, you receive the equivalent PBc (locked), and a fresh PBt tracker is minted
with unlock thresholds based on the current spot price.
Why would you do this?
buyPBDirect() to get a new split (3.69% liquid + 96.31% locked PBt), then VLock
your leftover liquid PB to lock that too at the current spot price.How it works:
voluntaryLock(pbAmount) from the PB Dapp or directly on-chainThink of it as re-entering the protocol on your own terms. You trade short-term liquidity for structured, price-gated unlocks, plus a cut of LP fees as a thank-you for deepening the vault.
Bitcoin is proven sound money but remains fundamentally illiquid. PB takes Bitcoin's fixed-supply principle and adds dynamic vault-driven liquidity expansion. As price rises, the vault automatically deepens pools, solving the chicken-and-egg problem of low liquidity. You get Bitcoin's scarcity with crypto-native market depth. If you want the broader design-tradeoff framing behind choices like this, read WHY.
HEX introduced staking and time-locked vesting, but vesting schedules create predictable dump pressure when tokens "unlock on a calendar" regardless of price. PB eliminates both staking and time-based cliffs. Unlocks are triggered only by price proof (55.55% increases = 1.5555× multiplier), and the vault pre-deepens pools before users get tokens, preventing the panic-dump cycle that plagues fixed-schedule protocols.
Yes. All contracts have been professionally audited. The full audit report covers all 15 attack vectors, contract immutability verification, and whitepaper consistency checks.
No. The contracts are intended to remain immutable after deployment, with no pause functions and no upgrade path. If you want the hard constraints listed without interpretation, read Immutable Rules.
Bugs are discovered during audits and fixed before deployment. After deployment, bugs cannot be "patched" because the code is immutable. This is a feature, not a bug.
Crypto regulations vary by jurisdiction. In some countries, tokens may be classified as securities. Please consult legal counsel before investing.
If you lose access to your wallet and haven't configured recovery or inheritance, your PBc and unlocked PB are permanently inaccessible. Always secure your private keys.
However, PB has built-in Recovery and Inheritance functions on each PBt NFT. These must be set up in advance, they cannot be configured after you lose access. See the question below for details.
PB includes dual-factor succession planning to protect against wallet loss or incapacitation:
⚠️ These must be configured while you still have access to your wallet. Recovery and inheritance cannot be set after you lose your keys.
Important Edge Cases:
setInheritanceAddress() for the first time.These mechanisms ensure secure, one-way succession while preventing abuse or manipulation after activation.
Note: If you made a recovery address typo, use the PBi (inheritance) to correct it, as recovery cannot be modified once configured.
Yes. If demand doesn't materialize, price may stay flat or fall, preventing unlocks. This is the core risk of PB. Only buy if you believe in organic price appreciation.
Enter a dollar amount to see the estimated PB split, locked PBc, and unlock ladder. Prices come from the presale entry curve.
| Tier | Trigger Price | Multiplier | PBc Unlocked | USDL Payout | Remaining PBc |
|---|
The core rule is simple: outstanding PBc can never exceed the PB held by the vault.
In other words, the backing condition is always vaultPBBalance ≥ totalOutstandingPBc.
During the distribution phase, LP additions only happen if there is still PB above the backing line. If excess PB falls to zero, LP contributions stop automatically and the system remains at minimum 1:1 collateralization.
So the backing logic does not depend on presale math or a specific launch scenario. It depends on one invariant enforced by the vault: PBc outstanding can never be greater than PB held in reserve.
PB uses convergent netting, so every call to buyPBDirect() automatically settles
eligible unlocks for other users. The buyer pays the gas for the entire transaction. The easiest way to think about it is
Pay It Forward: your buy settles older unlocks, and future buys later settle yours.
The Gas Flow:
vault.buyPBDirect(usdlAmount, minPBOut)executeUnlock(pbtId) permissionlessly to force-settle via AMM sellGas Costs (at current PLS prices):
| Scenario | Gas Used | Cost @ $0.000011 PLS | Cost @ $1.00 PLS |
|---|---|---|---|
| Buy only (no unlocks) | ~231K gas | $0.000025 | $0.23 |
| Buy + 1 unlock triggered | ~469K gas | $0.000052 | $0.47 |
| Buy + 5 unlocks triggered | ~1,421K gas | $0.000156 | $1.42 (1.42% on $100 buy) |
| Buy + 10 unlocks | ~2,611K gas | $0.000287 | $2.61 (2.61% on $100 buy) |
| Buy + 500 unlocks (max) | ~125,000K gas | $0.01375 | $125 (theoretical max) |
Why This Model?
executeUnlock() is permissionless, anyone can trigger it as a fallbackFail-Safe: If PLS price rises significantly (e.g., $10+), network gas prices would likely adjust downward to compensate. Additionally, anyone can donate PLS to the vault address if community support is needed. The system is designed to work at any price point.
PBc is a non-transferable ERC-20 token. Each PBc balance is tied to your wallet and tracked alongside PBt entry prices, allowing precise checkpoint and redemption logic.
Price is derived from the on-chain AMM spot price of the PB/USDL canonical pair via getReserves().
No external oracles. No off-chain data feeds. Pure on-chain logic. (on PulseX only) The 96.31% lock ratio makes spot-price
manipulation economically impossible (see security section below).
PB's main defense is the 96.31% lock ratio. Any attacker trying to move price with a large buy gets only 3.69% liquid PB immediately, while the other 96.31% is locked as PBc under the same rules as everyone else.
Example: a $300K attacker buy would leave only about $11,070 immediately liquid and about $288,930 locked as PBc. That does not stop price from moving, but it does break the normal short-term extraction path.
The key point is simple: attacking PB with buy-side capital means voluntarily locking most of your own capital inside the protocol.
Yes. PB can be integrated into wallets, dashboards, bots, portfolio tools, and custom frontends. Once deployed, the contract address and ABI will be public.
The key rule is that buys must still route through buyPBDirect() on the Vault.
That is where the protocol enforces the PB / PBc split, unlock settlement, LP contribution, and netting logic.
Your app can change the user experience, but it must not bypass the vault buy path.
In practice:
buyPBDirect()So yes, custom integrations are fully compatible with the protocol, as long as the buy path respects the vault rules.
Yes. After mainnet launch, the contracts will be publicly readable and auditable by anyone. They will be visible on PulseChain Scan and available for independent review.
Early blocks (#1-100) have lower entry prices on the curve, so lower 1.5555× unlock thresholds. Purchase price is fixed per block, but entry prices still affect unlock timing. All blocks follow identical rules no special treatment.
The main reason to split any larger allocation is to build a ladder instead of relying on one single entry.
A ladder matters because separate entries create separate unlock profiles. Instead of concentrating everything into one line item, you create a more flexible payout structure over time. In practice, a ladder lets you combine:
The strongest reason to do this is not cosmetic, it is structural: laddering gives you staggered checkpoints, staggered unlocks, and less dependence on one exact entry level.
You're free to do so. Any liquid PB can be paired with other assets and added to liquidity pools. The protocol doesn't restrict this. Just be aware: only liquid PB can be used for LP, locked PBc cannot be added to pools. And only the canonical PB/USDL pair on PulseX affects the vault's price feed and unlock triggers. LP on other pairs or DEXs won't influence unlocks.
Yes, but automated, on-chain, and you never have to decide when to sell.
Traditional DCA out means you manually sell a portion of your holdings at regular intervals, hoping to average a good exit price. The problem? Timing, discipline, and emotion. Most people either sell too early, too late, or panic-dump everything at once.
PB's unlock mechanism is price-triggered DCA out built into the protocol:
The key difference: traditional DCA out reduces your position and you're done. PB's unlock decay (⅔ remaining each tier) means some exposure can remain after each settlement. You are not forced fully out by a single vesting event. You take profit at milestones while the remaining position stays subject to the same rules.
Think of it as rule-based profit-taking with remaining locked exposure. The protocol handles the sell-side settlement for you at predefined price checkpoints, so emotion and timing discretion are removed.
Use the cards below to click any published address to copy it, open it on the official block explorer, add the correct PulseChain network to MetaMask, and import PB or PBc directly into your wallet. If you want the canonical trust and verification hub, use the Trust Center.
Chain ID 369 • Production network
Only published addresses are shown as copyable. Empty slots remain clearly marked until the deployment is finalized and verified.
Chain ID 943 • Public testing network
These values come from the live site config used by the test dapp and are intended for wallet import, explorer verification, and manual contract interaction.
If the objections are handled, continue into the presale page. If not, step back one page and re-check the mechanism.