An ecosystem of immutable vault tokens with a floor that only rises

TL;DR

PulseStrategy is a family of ownerless smart contracts. Each one holds a single yield-bearing asset in a vault and issues its own token against it.

The rule that defines the entire system:

The amount of backing behind each token can never go down.

Not "shouldn't." Not "is unlikely to." Cannot — there is no function in any of these contracts that lowers it. Every mint adds proportionally more assets than tokens. Every redemption leaves value behind. Nobody can pause it, upgrade it, drain it, or change the rules, because no owner exists.

Every round trip through the system leaves ~4.3% behind for the people who did nothing but hold. Traders churn; holders collect.

You are not asked to trust a team. You are asked to read a contract.

1. The problem

Crypto has no shortage of upside. What it lacks is a floor.

Almost every token can go to zero, because almost every token's value is a story about the future. When the story weakens, there's nothing underneath. The protocols that did promise floors mostly died the same way: they funded the promise with emissions, needed constant new deposits to honor it, and had an admin key that could — and eventually did — change the terms.

The mechanisms that failed weren't floors. They were narratives with a treasury attached.

2. The ethos

PulseStrategy was designed backwards from one question: what can a holder be certain of?

Not "what returns can we advertise" — what can be proven, by anyone, by reading code that can never change?

The answer turned out to be small but solid: a redemption right against a pool of real assets, where the assets-per-token ratio only ever ratchets upward. That's it. That's the whole promise. Everything else in this document is a consequence of it, or an honest admission of what it doesn't cover.

This forced three design decisions that most projects avoid:

No admin. No owner, no multisig, no pause switch, no upgrade path, no governance. Not because governance is bad, but because a floor that someone can move isn't a floor. The cost is real: bugs are permanent, parameters can never be tuned, and nobody can rescue anything. We accept that cost, because the alternative undermines the only thing being promised.

No emissions, no reserved supply, no team allocation. 100% of every vault token that will ever exist is minted by the public through one formula, at a price anyone can compute. There is no pre-mine to explain away and no inflation schedule to outrun.

No hidden mechanics. Every fee is disclosed in this document and visible on-chain. The one place value leaves the system — a 0.5% protocol fee — is stated plainly below rather than buried.

The result is a token that does not promise to make you rich. It promises that its floor rises, that the floor is real, and that nobody can take it away. In a market that mostly sells the opposite trade, that's the differentiator.

3. How a vault works

Every vault in the family is the same machine with a different asset inside. It has exactly two functions.

Mint — the ceiling

Deposit the vault's asset, receive vault tokens priced at backing + 4.5%.

That 4.5% premium doesn't go to a founder. 4.0 points stay in the vault, which means the vault gains proportionally more assets than the tokens it just issued — so every mint raises the floor for everyone who already held. The remaining 0.5 points are the protocol fee (§9).

Minting is capped: see §6.

Hold — the ratchet

Nothing to do. Backing-per-token only rises. Three streams feed it:

1. Mint premiums — every new minter pays above backing, and the excess stays behind
2. Redemption fees — every exit leaves 0.5% for the people who stayed
3. The underlying asset's own yield — vPLS accrues PulseChain staking rewards; HTTs pull toward HEX parity as their stakes mature

Plus donations: anyone can send the vault asset directly to a vault contract at any time. It raises backing for all holders instantly, and it is not restricted by the mint quota.

Redeem — the floor

Burn your vault tokens, receive your exact pro-rata share of the vault, minus a 0.5% fee that stays in the vault for remaining holders.

Redemption is never gated, never paused, never quota-limited, never delayed. The mint side of the system breathes; the exit does not. A floor with conditions attached is not a floor.

Last-redeemer waiver: if you redeem 100% of the outstanding supply, the 0.5% fee is waived and you take the entire vault. No assets are ever stranded in a fully-redeemed vault.

4. The ratchet, precisely

The invariant, stated formally:

For any operation of these contracts, vaultBalance / totalSupply after ≥ vaultBalance / totalSupply before.

Why it holds, case by case:

There is no fifth case. No admin function, no rescue function, no fee-change function, no upgrade hook exists to create one.

Worked example — the genesis mint. Vault is empty. You deposit 104.5 units of the asset:

• You receive 100 vault tokens (104.5 ÷ 1.045)
• 0.5 units go to the protocol fee
• The vault holds 104.0
• Backing per token = 1.04 — above 1.0 from the very first transaction

Worked example — you profit from the next person. Continuing above: a second minter deposits 104.5. Vault holds 208.0, supply is ~195.6, backing rises to ~1.0632. Your original 100 tokens now redeem for ~105.8 units gross (~105.3 after fee) — more than the 104.5 you put in. Their premium became your gain. Then when you exit, your 0.5% fee becomes the next holder's gain.

5. Two paths to a rising floor

There are two ways the ratchet turns, and they are wildly different in power. Understanding which one matters is the difference between an honest pitch and a fantasy.

Path one: growth (weak)

If people mint and hold, the vault grows — but so does supply. Each mint adds 10.4% to the vault while adding 10% to supply. The net gain per unit of growth is small, and it obeys a strict law:

B ∝ V^(1/26) — backing grows logarithmically with vault size.

Every order of magnitude of vault growth buys only about +9.5% backing. To double backing through growth alone, the vault would have to grow 67 million times (2²⁶). That is not a realistic path, and we will not pretend otherwise.

At full saturation — every epoch's quota filled, everyone holding — backing grows about +0.36% per epoch ≈ +21% per year. That's a ceiling, not a forecast, and it can't persist: the quota compounds in absolute size, so sustained saturation eventually demands more of the asset than exists.

Path two: churn (strong)

Now consider capital that enters and leaves. Supply returns to where it started, so there is no dilution — the fees are pure transfer.

Every round trip through the vault leaves ~4.3% of its size behind, permanently, for the people who did nothing but hold.

The difference is dramatic:

A 1M-asset vault doubles its backing after roughly 25M of cumulative round-trip volume — no growth required, just traffic. Volume is the one thing crypto reliably produces.

Why churn beats growth: a growth-minter pays the premium and then stays — their tokens dilute the very gain they funded. Capital that cycles through pays and leaves, taking zero supply with it. Pure transfer, no dilution. That single distinction is why one path needs 2× and the other needs 67 million×.

So the honest summary of this system:

The mint premium is a steady ratchet, not a doubling machine. Churn is the engine. The underlying asset's own yield is the multiplier.

Realistic expectations: mint premiums contribute perhaps +20–40% in asset terms over a vault's life. Churn can do far more, given years and real volume. And underneath both, vPLS accrues PLS staking rewards and HTTs pull toward HEX parity — that layer never has an idle week.

6. The epoch quota

Each 7-day epoch, total minting is capped at 10% of the supply that existed at the epoch's first mint. When the quota fills, mint() reverts until the next epoch opens.

The genesis epoch — while supply is zero — is uncapped, so the vault can bootstrap. This is the only window in a vault's life when entry can never be quota-blocked.

Why throttle at all?

• Scarcity creates the event. Exhausted quota means new demand must go to the DEX, where nothing caps the price. When the next epoch opens, arbitrageurs race to mint at backing+4.5% and sell into the elevated market — filling the vault. Weekly rhythm, permanently.
• It's deterministic. No oracle, no randomness, no admin switch. block.timestamp / 7 days. Anyone can predict it; nobody can manipulate it.
• It's a percentage, not a fixed number. The quota grows with the vault. Sustained demand makes each epoch's capacity larger — the throttle relaxes exactly as the system matures.
• It suppresses runaway premiums. Every epoch, fresh supply enters and pulls price back toward backing. This is deliberate: a token trading far above its floor has a distant floor, and the floor is the product. We chose holder protection over chart optics.

7. Arbitrage — the engine

This is how the vault fills. Understanding it is worth the two minutes.

Each vault contract is its own market maker, quoting two permanent prices:

CEILING  →  mint()    at  backing × 1.045   (infinite ask, quota-limited)
FLOOR    →  redeem()  at  backing × 0.995   (infinite bid, never limited)

Between them sits a ~5% band. The market price does whatever it wants inside that band. But the moment it steps outside, a risk-free trade appears:

Price above the ceiling → mint from the contract, sell on the DEX, pocket the difference. Vault gains 4.0% of the mint. Backing rises. Supply rises, pushing price back down.

Price below the floor → buy cheap on the DEX, redeem at the contract, pocket the difference. Vault keeps the 0.5% fee. Backing rises. Supply burns, pushing price back up.

Notice what happens in both directions: the vault gets fed and holders get richer. Every time price leaves the band, someone profits by pushing it back — and pays the vault for the privilege.

This is the elegant part. Arbitrageurs aren't a threat to be defended against; they're unpaid employees. They need no incentive program, no emissions, no partnership — just a profitable trade. Their self-interest is the mechanism.

Who actually pays?

It's worth being precise here, because the honest answer is better than the cynical one.

The arbitrageurs don't lose. They never mint-then-redeem — that trade loses ~4.8% and nobody takes it deliberately. They mint and sell, or buy and redeem, capturing the DEX spread. They walk away profitable every time.

So the vault's ~4.3% comes from the counterparty who traded outside the band — the buyer who paid above the ceiling, or the seller who dumped below the floor. The arbitrageur is just the pipe connecting that impatience to your vault.

The vault taxes impatience, not participation. Anyone who wants immediacy badly enough to trade outside the band pays for it — and that payment lands with the people who simply held.

And minters don't have to lose either. You pay backing + 4.5% and exit at backing − 0.5%, so you break even once backing rises 5.03%:

After that, every further epoch is pure profit in asset terms. The 4.5% isn't a punishment — it's a time-preference toll. Pay it, wait out the ratchet, keep everything after. Mint if you believe activity will follow; if you don't, buy on the DEX instead and let someone else pay the toll.

Even the buyer who paid above the ceiling isn't a mark: they bought conviction and immediacy, and the floor then rises toward their entry.

Nobody has to lose for holders to win. Patient capital gets paid by impatient capital — and impatient capital still gets what it came for.

And the ordinary buyer who never mints, never arbs, and just holds? They're the beneficiary. The mint race happening above their heads is what funds their rising floor.

For arbitrageurs specifically

• Both legs are permissionless and atomic-friendly. No allowlist, no delay, no KYC.
• previewMint() and previewRedeem() are view functions — simulate before you commit.
• Both mint() and redeem() take a slippage parameter (minTokensOut / minAssetOut). Use it.
• The quota resets on a fixed 7-day boundary — timeToNextEpoch() tells you exactly when the ceiling reopens. Epoch open is the most contested moment in each vault's week.
• mintQuotaRemaining() tells you how much room is left before the ceiling closes.
• The HEX vaults have an unusually clean loop: HTT ↔ HEX liquidity already exists, so both arb legs complete through an established pool.

8. Liquidity providing

Providing liquidity to a PulseStrategy pool is structurally different from LPing a normal token pair, and it's worth being precise about why — and about what it doesn't fix.

The normal LP problem: impermanent loss comes from price wandering. In a standard pair, price can go anywhere — 10x up, 90% down — and the AMM mechanically sells you the winner and buys the loser the whole way. The further price travels from where you entered, the worse it gets. There is no natural stopping point.

Why these pools are different: the vault contract enforces boundaries the market cannot cross for long.

• Price can't sustainably fall below the floor — arbitrageurs will buy your cheap inventory out of the pool and redeem it against the vault
• Price can't sustainably run above the ceiling — arbitrageurs mint fresh supply and sell it into your pool

So instead of a random walk across an unbounded range, you're LPing an asset that mean-reverts inside a ~5% band around a ratchet that only moves one way. Bounded divergence means bounded impermanent loss. And crucially, unlike a normal pair whose "fair value" can collapse, the band itself is anchored to a backing figure that structurally rises.

The honest caveats:

• This reduces IL; it does not eliminate it. Within the band, and during the moments before arbitrage closes a gap, you still take the standard LP tradeoff.
• The floor is denominated in the vault asset, not dollars. A PLSstr floor is measured in vPLS. If PLS collapses in USD terms, so does the USD value of everything — pool included. This system protects against token-vs-asset risk. It does nothing about asset-vs-world risk.
• Thin pools are volatile pools. Early on, depth is small and price swings hard inside the band.
• Fees are the point. Your compensation is the trading fees generated by all that arbitrage traffic — and this design manufactures arbitrage traffic on a weekly schedule.

The dashboard displays a trailing realized fee APR per pool once one exists: a backward-looking measurement of fees actually earned, not a projection, not a promise, and it excludes impermanent loss. We'd rather show you a real number that might be unimpressive than an advertised number that isn't real.

9. Fees, in full

There are exactly two, and one destination outside the vault.

There is no transfer tax. Moving tokens between wallets, into a pool, or through a DEX costs nothing. The vault tokens are plain, fully-composable ERC20s.

The protocol fee is carved out of the premium minters already pay — it is not added on top. A minter pays 4.5% whether or not the fee exists; the fee only determines whether the last 0.5 points sit in the vault or fund the protocol. Because the vault still nets 4.0%, every mint remains accretive, and the core invariant is untouched.

It funds hosting, development, and future vaults. It is hardcoded, immutable, and publicly auditable — each vault exposes totalProtocolFees and emits a ProtocolFeePaid event on every mint. You can verify exactly what it has taken, forever.

Protocol fee address: 0x3E5a5764EBd24d8142638366d4c5674D86c2EC64

Launched vaults (§13) use the same 4.5% mint premium and 0.5% redeem fee, but split the premium 3.5% vault / 0.5% protocol / 0.5% creator, and charge a one-time 10,000 PLS create fee to the same protocol address. The core family above is unchanged.

10. The vault family

One codebase — the HEXstr contracts are logically identical to each other, and share their core with PLSstr. Same economics everywhere in this family: 4.5% mint / 0.5% redeem / 7-day epochs / 10% quota / no admin. The Launcher (§13) deploys copies of the same machine against a short allowlist. Those are user-launched vaults — same floor, different fee split and a decaying quota — not the Core family in this section.

PLSstr — PulseStrategy

Yield underneath: vPLS is value-accruing. The vault's vPLS balance doesn't grow on its own — instead, each vPLS becomes redeemable for more PLS over time as Vouch's validators earn staking rewards. So PLSstr compounds on two independent layers: backing-per-token ratchets up in vPLS terms from premiums and fees, while every vPLS underneath grows in PLS terms. The second layer never has an "unfilled epoch" — it accrues through dead weeks, bear markets, everything.

HEXstr-3000 → 7000 — HEXStrategy

Dated vaults backed by Actuator Finance HTTs — liquid, tradeable claims on staked HEX, redeemable 1:1 for HEX at their redemption day.

All HTTs are 8-decimal (HEX-denominated); the vault tokens mirror that automatically.

Yield underneath: an HTT trades at a discount to HEX before maturity, and that discount closes as its redemption day approaches — a scheduled pull toward par. So a HEXstr vault ratchets in HTT terms from premiums and fees, while each HTT underneath climbs toward 1 HEX. Together the maturities form a HEX yield curve: longer-dated vaults carry a bigger discount and a longer runway; shorter-dated ones converge sooner.

11. What is guaranteed, and what is not

The credibility of everything above depends on being equally clear about both.

Guaranteed by the contract

• Backing-per-token never decreases from any operation of these contracts
• No owner, no admin, no upgrade path, no pause switch — verifiable in the ABI
• Redemption is always open — no gate, no quota, no delay, no discretion
• No transfer tax, no reserved supply, no team allocation, no emissions
• 100% of supply is publicly minted through one formula, forever
• Every fee is on-chain and countable (totalProtocolFees, events)

Not guaranteed — read carefully

• Market price. Nothing forces the market to value a vault token above its floor. It can sit at the floor indefinitely. The floor rises; the price is the market's business.
• The underlying asset's value. Your floor is denominated in vPLS or HTT — not in dollars. If PLS or HEX falls in USD terms, so does your position. This system reduces the risk of the token relative to its asset. It does nothing about the asset itself.
• The layers below. PLSstr's entire backing is a claim on the Vouch liquid staking protocol. HEXstr's backing sits on a deeper tower: HEX → Hedron/HSIs → Actuator Finance → this vault. A failure, exploit, or depeg at any of those layers impairs backing even though this contract's math holds perfectly. Minters carry that risk in full.
• PulseChain itself. All six vaults live there and inherit its risks entirely.
• Your entry cost. A round trip costs ~5% (4.5% premium + 0.5% exit fee). You start below your own floor and need subsequent activity or asset yield to clear it. Early entrants benefit most from later activity; the last person to touch a vault eats their own premium.
• Smart contract risk. These contracts have not received a paid third-party audit. They are small, deliberately simple, publicly readable, and immutable — which means anyone can verify them, and nobody can fix them. A bug would be permanent. Read the code, or don't deposit.
• Quota griefing. Someone can mint an epoch's full quota and immediately redeem to block others, at a cost of ~5% of the quota value. It's expensive, self-limiting, and the cost lands in the vault — but it's possible.

Nothing here is financial advice. Verify every contract yourself before depositing.

12. Governance

There is none, and there never will be.

No token votes. No DAO. No parameter changes. No treasury to allocate. No roadmap that can alter the terms you agreed to when you minted.

The contracts are finished. That's not a stage of development — it's the product.

13. The Launcher

The vaults in §10 are the PulseStrategy Core family — ownerless vaults PulseStrategy deploys (PLSstr and the HEXstr maturities). More Core HEXstr vaults may be added as HEX maturities come into range. They are a separate list from anything created here.

Anyone can deploy the same machine against a short allowlist of PulseChain assets, from pulsestrategy369.com/launch. That is the permissionless vault launcher.

What you get. A LaunchVault contract. Same invariant: backing-per-token cannot fall. Same two functions: mint and redeem. Same 7-day epochs. Same no-owner, no-pause, no-upgrade. The factory has no admin either — it is a list and a deploy function, nothing else.

Not a pump launch. Nothing here seeds a pool, locks LP, or "graduates." You get a vault contract. If you want a market, you add PulseX liquidity yourself. The board on the launcher ranks vault TVL plus whatever PulseX depth it can see.

What is different from the core family

The creator fee. 0.5% of each mint goes to the wallet that called createVault and paid the 10,000 PLS. It is hardcoded. The creator cannot change it, pause it, or take anything else. They get the same thing a holder gets, plus that 0.5% stream, and nothing more.

The on-chain list is the index. Frontends enumerate vaults(i) / allVaults() or listen to VaultCreated. A hosted JSON file is only a cache — the chain is the source.

The guarantee in §11 applies to launched vaults in their own asset. Same as the family: the floor is real in the backing token, the market price is not guaranteed, and the layers below the asset are not this contract's problem.

Quick start

1. Go to the vaults dapp (or run your own copy — see below)
2. Tap Connect → Browser wallet or WalletConnect
3. Pick a vault from the switcher (PLSstr, or any HEXstr maturity)
4. Get the vault's asset — vPLS via Vouch, HTTs via Actuator Finance or a DEX
5. Mint with it, or just buy the vault token on the DEX and hold

To create a new vault against PLSX, PLSstr, PRVX, WPLS, INC or pDAI, use the launcher instead — see How to launch a vault. That costs a fixed 10,000 PLS.

Reading the dashboard

How to mint

1. Select the vault, make sure you're on the Mint tab
2. Enter an amount (or hit MAX)
3. Check the preview: how many tokens you'll receive, and the 4.5% premium you're paying
4. Tap Approve — one transaction, lets the vault take your asset
5. Tap Mint — a second transaction

What you're paying: backing + 4.5%. You are immediately ~4.5% below your own redemption value, and that's not a trick — it's the toll that funds everyone else's floor, including yours when the next person mints. Mint if you believe activity will follow. Otherwise just buy on the DEX.

If mint reverts with "quota exhausted": that's the ceiling doing its job. Buy on the DEX, or wait for the epoch timer.

How to redeem

1. Redeem tab
2. Enter an amount (or MAX)
3. Check the preview: assets out, and the 0.5% fee left behind
4. Tap Redeem — one transaction, no approval needed

You get your exact pro-rata share of the vault minus 0.5%. This always works. No quota, no pause, no delay — regardless of market conditions, epoch state, or anything else.

Redeeming 100% of the supply? The fee is waived and you take the whole vault.

How to launch a vault

This is the permissionless factory in §13. You pay 10,000 PLS and mint at least 10 of the backing asset in the same transaction. After that the contract is yours — ownerless — and the token is already in your wallet.

1. Compile LaunchVaultFactory.sol in Remix at 0.8.29, optimizer on, EVM Version = shanghai — not cancun/prague. PulseChain has no MCOPY opcode. A cancun factory deploys, then every createVault reverts and burns gas. Deploy that factory on PulseChain (369) and paste it into the launcher.
2. Go to the launcher (or run your own copy — see below)
3. Tap Connect → Browser wallet or WalletConnect, on PulseChain
4. Name it (1–32 characters) and pick a ticker (1–12)
5. Pick a backing asset from the six: PLSX, PLSstr, PRVX, WPLS, INC, pDAI
6. Pick the epoch mint cap: 5% or 10% of supply per 7-day epoch
7. Enter the first mint — at least 10 of the backing asset. You choose how much; more seed means more supply at launch. Name and ticker must be unique. The rest of that 7-day epoch stays uncapped (same as PLSstr); the 5%/10% cap starts at the next epoch.
8. Tap Launch vault · 10,000 PLS + first mint. If the factory needs approval, the first signature is the token approve; the second is the create.
9. Your wallet will show 10,000 PLS plus the backing-asset mint plus gas. Confirm only if that's what you intend.
10. When it lands, the vault address is shown on the launcher in a Vault live card — copy it, open it, or jump to PulseScan. It is also in the VaultCreated event of your transaction. This page remembers it on that device. Then add PulseX liquidity yourself if you want a market.
11. Paste the address into PulseVerify and read the source before you, or anyone else, deposits.

If it reverts: the factory requires exactly 10,000 PLS and at least 10 of the backing asset. Short PLS, extra PLS, or a seed under 10 all fail. Name and ticker must be unique (ASCII case-insensitive) and fit the length limits, and the asset must be one of the six. Approve the factory for the seed first. If the explorer shows the inner CREATE failed with invalid opcode: MCOPY, the factory was compiled for cancun — do not retry it. Recompile at EVM Version shanghai and deploy a new factory.

What you are not buying: a seeded pool, locked LP, a "graduation," or any admin rights over the vault. The 10,000 PLS is a spam deterrent paid to the protocol, not a deposit into the vault.

For HEXstr holders — the redemption day

Each HEXstr vault has a hard date (see §10). Around and before it:

1. Redeem HEXstr at the vault → receive HTTs
2. Redeem HTTs at Actuator Finance → receive HEX

Don't sleep past it. After maturity, HTT liquidity thins as everyone exits, and Actuator's 1:1 redemption operates within its own window. The vault will hold matured HTTs forever if you let it — it can't convert them for you.

For liquidity providers

The pools section shows every known pool per vault, with live depth and a trailing realized fee APR.

Why LP here: arbitrage traffic is manufactured by the design — every band crossing routes through your pool. And your inventory risk is bounded, because price mean-reverts inside a ~5% band around a rising floor instead of wandering freely (§8).

Two practical notes: don't LP your entire position (LPing caps your upside on the LP'd portion when price runs), and remember the bounded-IL argument is about token vs. asset — it says nothing about the asset's own price.

Running PulseStrategy locally

The PulseStrategy front-ends — the vaults dapp, the PulseVerify explorer, the market desk, and the launcher — are single HTML files. No server, no backend, no build step, no database. Each one reads PulseChain directly from your browser using public RPC endpoints.

That is not a technical curiosity. It is the point. A protocol whose contracts are immutable and ownerless should not depend on a website that someone can take down. Anyone can download any of those files, keep it, share it, inspect it, and run it years from now — and it will keep working as long as PulseChain does.

Download and verify

Every page here can be downloaded from its footer. The dapp pages — vaults, PulseVerify, and the launcher — also show the file's SHA-256 hash, because those pages connect a wallet and build transactions, so a tampered copy could do real damage. Before trusting a copy you got from anywhere other than pulsestrategy369.com, compare its hash against the one published on our X account and GitHub. Matching hashes mean the file is byte-for-byte the one we published. This matters precisely because we encourage redistribution: the hash is what makes a copied file trustworthy without trusting whoever copied it.

What works with no setup at all

On every device, in every browser, straight from a downloaded file:

• Live backing-per-token, supply, vault holdings, and epoch quota
• Market price and premium/discount versus backing
• The full PulseVerify explorer: blocks, transactions, addresses, token holdings, DEX prices, Sourcify verification status, Pulse Check safety scans, contract reads
• Custom RPC — including your own node, so no third party sees what you look up

Reading the chain never requires a wallet. If all you want is to verify what the protocol is doing, you are already done.

Connecting a wallet to a local copy

Minting and redeeming require a wallet signature, and this is the one area where running from a file behaves differently than running from a website. Browsers isolate local files for security: a file has no web address, and both wallet extensions and WalletConnect use the web address to decide whether to trust a page.

There are three working paths.

Desktop — browser wallet (simplest)

Browser extensions are blocked from local files until you allow it:

1. Open chrome://extensions (or brave://extensions)
2. Find your wallet — MetaMask, Rabby, etc.
3. Click Details
4. Switch on Allow access to file URLs

Reload the page and connect with the browser-wallet option.

Android — a file manager that serves over http

Most Android file managers hand the page to your browser as a content:// document, which WalletConnect will not accept because it is not a web address. A file manager that serves files over a local http address solves this. Cx File Explorer does — it is free on the official Google Play store:

play.google.com/store/apps/details?id=com.cxinventor.file.explorer

Open the downloaded file with it, and its Open-with list will show HTTP beside Chrome and Brave. Pick one of those and WalletConnect works normally.

The page is served from 127.0.0.1 — the loopback address, meaning your device talking to itself. Nothing is exposed to your network or the internet; the file manager simply hands the page to your browser through a local pipe rather than as a raw file.

iPhone

iOS does not allow an equivalent app, so a downloaded copy on iOS is for reading only — which still covers backing, supply, prices, verification and every safety check. To connect a wallet on iOS, use the hosted pages at pulsestrategy369.com.

Either platform — run a local web server

Users comfortable with a terminal can serve the folder and get every feature, including WalletConnect, with no other configuration:

python -m http.server 8000
# then open http://localhost:8000/vaults.html

localhost is a legitimate web address, so wallets treat the page as they would any site.

Why this matters: if pulsestrategy369.com ever goes down, is censored, or has its DNS hijacked, your local copy still works and cannot be tampered with. The contract has no admin key; now the interface has no mandatory middleman. Verify your copy of either dapp page against the SHA-256 hash shown in its footer and cross-checked against the one published on GitHub or @pulsestrategy — a compromised server can fake the page, but it can't fake a hash you got somewhere else.

FAQ

Can the team rug this?
There is no mechanism to. No owner, no admin function, no upgrade path, no privileged supply. Read the verified source — that's the point. The one thing the founder gets is the same thing you get: tokens minted through the public formula, plus a disclosed 0.5% protocol fee, publicly counted on-chain.

Why would backing ever go down?
From these contracts, it can't. From the layers below — a Vouch failure, an Actuator failure, a HEX or PulseChain event — it can. That's the honest boundary of the guarantee.

What if nobody uses it?
Then backing grows only from asset yield, and the token trades at its floor. You'd hold roughly what you'd hold anyway, minus your entry cost. That's the downside case: dull, not catastrophic — which is the entire point of the design.

Do traders lose so holders can win?
No. Arbitrageurs profit on every trade — they mint and sell, or buy and redeem, capturing the spread. Minters break even once backing rises ~5% (roughly 3 months at healthy activity) and profit after. The system taxes impatience — trading outside the band, or exiting before the ratchet catches up — not participation. See §7.

Why is the mint premium so high?
Because it's the ratchet. Every point of premium is a point that lands in the vault, permanently, for holders. It's a toll on entry that pays existing holders — and if you don't want to pay it, don't mint: buy on the DEX from an arbitrageur who did.

Which vault should I use?
PLSstr if you want PLS exposure with a perpetual vault and staking yield underneath. A HEXstr if you want HEX exposure with a scheduled pull-to-par — longer maturities carry a bigger discount and a longer life; shorter ones converge sooner but expire sooner. Match the maturity to your own horizon, and put the redemption day in your calendar.

Is it audited?
No paid third-party audit. The contracts are small, simple, immutable, and fully public. Verify them yourself, and size your position accordingly.

Can anyone launch a vault?
Yes. The factory is permissionless. You pick a name, a ticker, one of six allowlisted assets, and 5% or 10% epoch cap, pay a fixed 10,000 PLS, and mint at least 10 of the backing asset in the same transaction. After that the vault has no owner — including you — and you already hold the token. See §13.

Does the 10,000 PLS go into the vault?
No. It is a create fee, paid to the protocol address. The backing that goes into the vault is the first mint — at least 10 of the chosen asset — in the same transaction. That mint is what you hold.

Do launched vaults have the same floor?
Yes, in their own asset. Backing-per-token cannot fall from any operation of a LaunchVault. The 4.5% mint premium is split 3.5 / 0.5 / 0.5 (vault / protocol / creator) instead of 4.0 / 0.5. Genesis week is uncapped; after that the quota is 5% or 10% and decays to 1%. Same redemption: always open, 0.5% left behind. Names and tickers are unique on the factory.

Source and this whitepaper live at github.com/PulseStrategy369/PulseStrategy.

Contracts

All on PulseChain. Verify every address on the block explorer before you interact with it — and never trust an address from a screenshot, a DM, or a link.

Liquidity pools

Launcher

The factory address is shown in the footer of pulsestrategy369.com/launch once deployed. Until then it is empty — do not send PLS to an address from a screenshot. Each launched vault is its own contract; the factory is only the index and the deploy function.

Launch fee: 10,000 PLS, paid to the protocol address below, required exactly — extra or short reverts. Plus a bootstrap mint of at least 10 whole tokens of the chosen backing asset.

Protocol fee: 0x3E5a5764EBd24d8142638366d4c5674D86c2EC64

↑ back to top