Pith. sign in

REVIEW 5 major objections 5 minor 6 references

Rugsafe: A multichain protocol for recovering from and defending against Rug Pulls

T0 review · 5 major / 5 minor · reviewed 2026-08-06 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗ Review JSON

Pith's one-line read The paper claims that victims of a rug pull can deposit their collapsed tokens in multichain vaults and receive 'anticoins' whose value rises as the token falls, converting a total loss into a hedge, a tradable asset, and a stream of…

desk verdict A sprawling DeFi design sketch whose central inverse-log peg is asserted, not enforced, and whose own equations contradict each other. read the letter →

arxiv 2507.06423 v1 pith:RERL2YWD submitted 2025-07-08 cs.CR cs.CEcs.ETcs.GT

Jovonni L. Pharr , Jahanzeb M. Hussain This is my paper · ORCID
classification cs.CRcs.CEcs.ETcs.GT
keywords rugpullanticoininverselogarithmicpegmultichainvaultDeFirecoverytokenburningrewardsdetectiondecentralizedinsurance
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

Rugsafe is a multichain protocol built around a single economic promise: a rug pull—a token's collapse to near-worthlessness—should not have to be a total loss. The paper's device is the 'anticoin': a victim deposits the collapsed token $C_r$ into a vault and receives a 1:1 anticoin $C_a$ whose value is set by the inverse logarithmic peg $C_a(t) = \log(C_r(0)/C_r(t))$, so the anticoin rises as the rugged token falls. Around that peg the paper assembles a full recovery economy—anticoins tradable on a protocol DEX, usable as perpetual-futures collateral, or burnable for native Rugsafe tokens whose supply tightens as more tokens get rugged—plus front-running-style rug detection, whale penalties, and bonding-based insurance. A sympathetic reader would care because, if the peg holds, victims gain a hedge, a tradable asset, and an incentive to keep participating instead of walking away with nothing.

What carries the argument

The load-bearing object is the inverse logarithmic peg identity $C_a(t) = \log(C_r(0)/C_r(t))$, which fixes the anticoin's value as a function of the rugged token's price path from vault creation. It does three jobs at once: it makes the anticoin a receipt whose value is anchored to a common reference point for all holders; it converts price decline into anticoin appreciation, creating the claimed hedge; and its unbounded, tapering shape lets the protocol claim stability without hard limits or resets, unlike earlier linear inverse pegs that froze at bounds. The second piece of machinery is the vault itself, which mints $C_a$ 1:1 against deposited $C_r$ and can issue the receipt as a fungible token, an NFT, or a refungible token depending on a parameter $\tau$. Finally, the native token supply rule $R_{\mathrm{supply}} \propto 1/\log(\sum C_r)$ ties the protocol's scarcity to the total volume of rugged tokens, which the paper claims keeps the ecosystem stable as rug events accumulate.

What would settle it

Deploy a Rugsafe vault on a testnet for a token that has already collapsed and record the anticoin's traded price every block alongside $C_a(t) = \log(C_r(0)/C_r(t))$; if the anticoin persistently trades away from the formula—especially if its market capitalization ever exceeds what the vault could ever pay out—then the asserted inverse peg is not being enforced by the AMM, and the hedge the protocol promises does not exist.

Watch

Extended reading notes

Core claim

The paper's central claim is that an inverse logarithmic peg can turn a collapsed token into the substrate of a recovery economy. When a user deposits $C_r$ into a vault $V_c$, the protocol mints an equal quantity of $C_a$, which is at once a receipt for the deposit and a tradable asset whose value follows $C_a(t) = \log(C_r(0)/C_r(t))$; as $C_r$ falls toward zero, $C_a$ grows without bound, so a victim's position hedges further decline instead of tracking it. The paper presents the log shape as 'soft theoretical bounds': the value tapers at the extremes, unlike earlier linear inverse pegs that froze and reset at hard limits. The anticoin can be held, traded, used as collateral, or burned, with burning paying the larger reward in native tokens $R$, and $R$'s supply is regulated inversely to the total value of rugged tokens via $R_{\mathrm{supply}} \propto 1/\log(\sum C_r)$. In the abstract the authors state the aim as 'a secure multichain system for recovering assets and transforming rugged tokens into opportunities and rewards.'

Load-bearing premise

The load-bearing premise is that market participants will actually pay the formula price for anticoins—$C_a(t) = \log(C_r(0)/C_r(t))$—since the paper names no reserve, collateral pool, arbitrage loop, or redemption right that would force the market price to track the formula.

Editorial extensions

If this is right

  • Rug-pull victims can deposit worthless tokens and hold an anticoin whose value rises logarithmically as the underlying token falls, hedging against further decline instead of riding it to zero.
  • Burning an anticoin permanently surrenders the claim on the underlying rugged token and pays out more native $R$ tokens than a mere deposit, so the protocol rewards full exit over waiting.
  • As more tokens get rugged, the native token's supply shrinks ($R_{\mathrm{supply}} \propto 1/\log(\sum C_r)$), so the protocol's own token becomes scarcer exactly when distress is highest.
  • The protocol DEX claims to enforce the peg by continuously repricing anticoin swaps, and perpetual futures with asymmetric funding rates give near-worthless tokens a secondary market with liquidity-provider incentives.
  • Non-linear, cumulative whale penalties make it more expensive to withdraw large holdings or to split them across sybil accounts, deterring the behavior that would otherwise destroy a post-rug ecosystem.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • The paper never specifies who pays for the hedge: Section 5 calls $C_a$ 'purely market-driven' while Section 11.1.1 says the DEX 'ensures' the peg, so the enforcement mechanism is left as collective belief in the formula rather than any reserve, arbitrage loop, or redemption right.
  • A direct test follows from the paper's own equations: deploy a vault for an already-collapsed token and compare the traded anticoin price with $\log(C_r(0)/C_r(t))$; a persistent divergence would mean the AMM alone cannot hold the peg.
  • The rug-detection strategy in Section 12 assumes the protocol can outbid the same MEV bots that compete for transaction ordering, so a congested-chain experiment would show whether the claimed 'detection window' is wide enough in practice.
  • The bonding-and-challenge apparatus from the insurance section could be turned on peg risk itself, giving anticoin holders a way to insure against the exact event—peg failure—that would leave their recovery asset worthless.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

5 major / 5 minor

Summary. The paper describes Rugsafe, a multichain protocol intended to let victims of cryptocurrency rug pulls deposit the collapsed token Cr into a vault Vc, receive an anticoin Ca as a 1:1 receipt, and obtain a native token R whose supply is inversely related to the total value of rugged tokens. The claimed core innovation is an "inverse logarithmic peg" Ca(t)=log(Cr(0)/Cr(t)), which allegedly provides a hedge and mitigates volatility. The manuscript also specifies whale-withdrawal penalties, rewards for burning Ca, a rugproof token-issuance bonding mechanism, a DEX and perpetual-futures suite, rug-detection methods, and decentralized insurance. No implementation, formal proof, or simulation is provided.

Significance. The problem addressed, user losses from rug pulls in DeFi, is important and timely, and the paper usefully organizes a taxonomy of rug-pull types and proposes a broad set of incentive mechanisms. Some peripheral components, such as the cumulative sybil penalty in Section 8, are internally coherent and correctly derived. The claimed result, however, would be significant only if the inverse peg and the supply-regulation mechanism were economically sound. Since those are the load-bearing parts of the protocol, and since they are asserted rather than derived or enforced, the contribution in its current form is a high-level protocol sketch rather than a substantiated design. The paper's own statement in Section 5 that Ca is "purely market-driven" is in direct tension with the claimed DEX-enforced peg in Section 11.1.1, and this undermines the central hedge and reward claims.

major comments (5)
  1. [§3, §3.2, Eqs. (1) and Ca(t)=log(Cr(0)/Cr(t))] The protocol defines Ca inconsistently. Section 3 states Ca = Cr (Eq. 1), a 1:1 quantity of tokens minted against deposited rugged tokens, while Section 3.2 defines Ca(t) = log(Cr(0)/Cr(t)), which is a price-like quantity that is zero at vault creation and can be negative when Cr(t) > Cr(0). These two definitions cannot both hold. This inconsistency is load-bearing because the abstract and Section 3.1 use the inverse logarithmic relationship to claim that Ca provides a hedge and mitigates volatility, and Section 6 uses the same relationship to compute the market potential of the Ca ecosystem. The paper must specify whether Ca is a token quantity, a price target, or an index, and then use that one definition consistently throughout.
  2. [§5 and §11.1.1] Section 11.1.1 says the DEX/AMM "ensures that the inverse peg remains intact" by automatically adjusting the price of anticoins, but Section 5 states that Ca tokens remain "purely market-driven assets" whose value is "dictated by market conditions" and that the protocol enforces no burning or minting of Ca. An AMM quote price is the ratio of reserves; it cannot be set to an external formula such as log(Cr(0)/Cr(t)) unless the protocol stands ready to buy or sell Ca at that price with committed capital. No reserve pool, collateral requirement, insurer, counterparty, or arbitrage condition is specified anywhere in the manuscript. Without such a mechanism, the central hedge promise, the vault-receipt valuation, and the burning-reward economics have no operational foundation.
  3. [§4, Eq. (2)] The supply rule R_supply ∝ 1/log(Σ Cr) is asserted without derivation. The paper does not define what "total value of rugged tokens" means, does not justify the logarithmic form, and does not explain how a reduction in token supply translates into a higher token value. The same issue affects the burn rate Rβ ∝ 1/log(Σ RCv), which is introduced with a new undefined quantity Σ RCv. Consequently, the claimed scarcity and stability properties of R are not supported by any model of demand or price formation.
  4. [§6.1] The statement ∂R/∂Ca < 0 is presented as the mathematical justification that burning Ca increases the value of R. But the supply model of Section 4 makes R's supply a function of rugged-token value Σ Cr, not of the circulating supply of Ca. The derivative does not follow from the preceding equations, and no substitute model is given. This step is load-bearing because the entire reward structure for burning Ca is based on it.
  5. [Overall] The paper provides no formal specification, machine-checked proof, or simulation of the core dynamics. Claims such as "ensuring stability and mitigating volatility" in Section 3.1 are qualitative; the reader cannot verify that the mechanisms terminate, that incentives are aligned, or that the peg is even approximately sustainable. Given that the central mechanism is an economic claim about what market participants will do with Ca, the absence of any model of agent behavior or any numerical evaluation is a substantive gap, not a presentation issue.
minor comments (5)
  1. [§1 and §3] The symbol R is used both for the Rugsafe native token and for the receipt in Section 1 and Section 3, which makes the notation confusing.
  2. [§4] Section 4 contains an apparent copy-paste error: the formula labeled Rβ = g(ϵ, blocks) uses the burn symbol for the minting rate, which should presumably be Rmint.
  3. [§2.2.3] The claim that liquidity withdrawal under a constant-product AMM increases the rug token's price is not correct; removing both sides of the pool does not move the price, whereas swapping rug tokens for the paired asset does, so the intended point should be restated.
  4. [§3.1, §4, §8] Figures 1 through 4 are referenced in the text but are not present in the manuscript, which makes the visual claims about the peg and penalties impossible to verify.
  5. [§11.2.2] The funding-rate formula can be negative when N_short exceeds N_long, and the text does not explain how negative funding rates are paid or capped.

Circularity Check

3 steps flagged · score 8.0 of 10

The inverse logarithmic peg and the burn-to-increase-R relationship are stipulated by definition and then presented as protocol properties, forcing the central hedge claim.

  1. self definitional [Section 3.2, 'Inverse Logarithmic Pegging as Soft Theoretical Bounds']
    "Ca(t) = log( Cr(0)/Cr(t) ) ... This relationship ensures that all Ca holders share a uniform reference point."

    The formula Ca(t)=log(Cr(0)/Cr(t)) is introduced as the definition of the anticoin's value. The paper then states that this relationship 'ensures' proportional response and stability, and uses it as the basis for the hedge. No reserve pool, collateral requirement, or arbitrage mechanism is specified that would make the market price of Ca track the formula; the hedge is therefore the input assumption restated as a result.

  2. self definitional [Section 6.1, 'User Commitment and Signal to the Ecosystem']
    "The act of burning Ca tokens strengthens this relationship by increasing the scarcity of Ca and consequently affecting the value of R. ... ∂R/∂Ca < 0. This partial derivative indicates that as the circulating supply of Ca decreases (through burning), the value of R is expected to increase."

    Section 4 defines R supply as Rsupply ∝ 1/log(sum Cr), with no dependence on Ca. The derivative ∂R/∂Ca<0 asserted in Section 6.1 does not follow from that model; it is a separate assumption inserted to justify burn rewards. The claimed increase in R value from burning Ca is thus loaded into the assumption rather than derived.

1 more flagged steps
  1. self definitional [Section 11.1.1, 'Enforcement of the Logarithmic Inverse Peg']
    "By automatically adjusting the price of anticoins as rugged token prices fluctuate, the DEX ensures that the inverse peg remains intact, providing users with a reliable way to hedge against further declines in rugged token value."

    The DEX 'enforcement' simply reasserts the peg from Section 3.2. An AMM cannot set an arbitrary price independently of its reserves; Section 5 states Ca is 'purely market-driven' and that the protocol enforces no burning or minting of Ca. So the reliable hedge is an asserted property, not a derived one.

full rationale

The paper's auxiliary mechanisms (vaults, rewards, insurance, rug detection) are independent design proposals and are not circular. However, the central economic claim—that depositing rugged tokens yields an anticoin hedge that secures recovery—rests on the inverse logarithmic peg Ca(t)=log(Cr(0)/Cr(t)). That equation is presented as a definition/design constraint, not derived from any market or collateral mechanism. Section 5 explicitly says Ca is purely market-driven and the protocol enforces no supply changes, which is inconsistent with Section 11.1.1's claim that the DEX/AMM ensures the inverse peg remains intact. No reserve or arbitrage mechanism is specified. The burn-reward calculus ∂R/∂Ca<0 likewise contradicts the Section 4 supply rule, which contains no Ca term. Thus two of the load-bearing 'results' reduce by construction to assumptions. Because the central hedged-recovery claim is forced by the peg's definition, the score is 8. There are no load-bearing self-citations.

Assumptions & free parameters 10 free parameters · 5 assumptions · 3 invented entities

The protocol's central claims rest on several unverified economic assumptions: that the inverse log peg can be enforced by market behavior without a specified backstop, that liquidity removal exposes a detectable window, and that burning anticoins increases the native token's value even though the supply equation does not depend on anticoin supply. All quantitative parameters are unspecified, and the 'equations' for the peg and supply are stated as design definitions rather than derived results.

free parameters (10)
  • Whale penalty scaling exponent λ = unspecified, λ > 1
    Section 8 defines P(Ca) ∝ (H_Ca)^λ and claims nonlinear penalty growth; no value or calibration is given and no game-theoretic justification beyond the assumption that whales should be penalized more.
  • Penalty rate γ = unspecified (example 10%)
    Section 8.0.5 defines one-time withdrawal penalty P = H_total × γ; the rate is arbitrary and not derived.
  • Incremental sybil penalty Δγ = unspecified
    Section 8.0.6 adds an incremental penalty per split withdrawal; no value, bound, or empirical basis is given.
  • Funding rate base constant α = unspecified
    Section 11.2.2 funding rate formula F_rate = α × (1 - N_short/(N_long + N_short)); α is a hand-picked constant.
  • Minimum liquidity threshold L_min = unspecified
    Section 11.2.2 scales funding rates by (1 + L_min/L_pool); L_min is arbitrary.
  • Block emission rate ε = unspecified
    Section 4 defines R_mint = ε × b; ε is a parameter said to be adjustable by governance.
  • Burn-rate function parameter β_burn = unspecified
    Section 4 defines burn rate R_β = f(1/log(Σ Cv), β_burn); β_burn is not specified or calibrated.
  • Vault reward parameters ω and θ = unspecified, θ > ω such that burn reward exceeds deposit reward
    Section 9 defines deposit reward R_ω = f(Cr, ω) and burn reward R_burn = g(Ca, θ); both are set at vault creation without formulas or values.
  • Bond and slashing percentages (x%, y%, z%, w%, α%, γ%) = unspecified
    Sections 10 and 13 define issuer, claim, dispute, and join bonds as percentages of issued tokens or insured value, with slashing factors; none are specified.
  • Minimum vote deposit z = unspecified
    Section 10.0.2 requires δ_vote ≥ z; z is a protocol parameter without a value.
assumptions (5)
  • domain assumption Liquidity removal is gradual enough to leave a detectable window for front-running, sandwiching, or back-running.
    Section 12 states 'liquidity is not removed instantly, but rather over a short period, providing a critical window for intervention.' If a rugged token's liquidity can be drained in one atomic transaction, the detection and mitigation strategies collapse.
  • ad hoc to paper The inverse logarithmic peg can be enforced by a DEX/AMM without an explicit arbitrage mechanism, reserve, or counterparty.
    Section 11.1.1 asserts the DEX 'ensures that the inverse peg remains intact' via the AMM price formula, but no mechanism is described that makes market price equal to log(Cr(0)/Cr(t)).
  • ad hoc to paper Burning anticoin tokens increases the value of the native Rugsafe token.
    Section 6.1 asserts ∂R/∂Ca < 0, but the R supply rule in Section 4 depends on Σ Cr and block emissions, not on the circulating supply of Ca; the derivative is an assumption rather than a consequence.
  • domain assumption Vaults can serve as reliable cross-chain oracles for the existence and volume of rugged tokens.
    Section 7 claims vaults act as decentralized oracles in real time; cross-chain oracle security, data availability, and manipulation resistance are not analyzed.
  • domain assumption The protocol can execute front-running, sandwich, and back-running transactions without being front-run or preempted.
    Section 12.6 describes dynamic gas and transaction-fee settings as countermeasures, but no consensus-level or mempool-level priority is proven.
invented entities (3)
  • Anticoin (Ca)
    purpose: Serves as a 1:1 receipt for deposited rugged tokens and as an inversely logarithmically pegged hedge that is supposed to rise in value as the rugged token falls.
    Section 3 introduces Ca. No token is deployed, no market exists, and no reserve or arbitrage mechanism backs the claimed peg, so there is no falsifiable handle outside the paper.
  • Rugsafe native token (R)
    purpose: Protocol token with supply supposedly regulated by the total value of rugged tokens and by block emissions; used to reward deposits and burns.
    Section 4 and 9 describe R, but no issuance, economic model, or deployed implementation exists.
  • Vault (Vc) with central vault registry
    purpose: Holds deposited rugged tokens, issues Ca receipts, and acts as an oracle across blockchains.
    Section 3 describes vaults and a registry per blockchain; no cross-chain implementation or security model is given.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Rugsafe: A multichain protocol for recovering from and defending against Rug Pulls." pith.science (2026). https://pith.science/paper/RERL2YWD

@misc{pith2026250706423,
  author       = {Pith},
  title        = {Pith review of: Rugsafe: A multichain protocol for recovering from and defending against Rug Pulls},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/RERL2YWD}},
  note         = {Machine review of arXiv:2507.06423}
}
read the original abstract

Rugsafe introduces a comprehensive protocol aimed at mitigating the risks of rug pulls in the cryptocurrency ecosystem. By utilizing cryptographic security measures and economic incentives, the protocol provides a secure multichain system for recovering assets and transforming rugged tokens into opportunities and rewards. Foundational to Rugsafe are specialized vaults where rugged tokens can be securely deposited, and anticoin tokens are issued as receipts. These anticoins are designed to be inversely pegged to the price movement of the underlying rugged token. Users can utilize these anticoins within the ecosystem or choose to burn them, further securing the protocol and earning additional rewards. The supply of the native Rugsafe token is dynamically adjusted based on the volume, value, and activity of rugged tokens, ensuring stability and resilience. By depositing rugged tokens into a vault on several chains, and by burning anticoins, users receive incentives on the RugSafe chain. This protocol's vaults are designed to work in heterogenous blockchain ecosystems, offering a practical and effective solution to one of the most significant challenges in the cryptocurrency market.

Figures

Figures reproduced from arXiv: 2507.06423 by the authors.

Figure 1
Figure 1. The plotted relationship between the price of a rugged token ( [PITH_FULL_IMAGE:figures/full_fig_p007_1.png] view at source ↗
Figure 2
Figure 2. The logarithmic relationship between the theoretical supply of Rugsafe [PITH_FULL_IMAGE:figures/full_fig_p008_2.png] view at source ↗
Figure 3
Figure 3. the impact of the whale penalty mechanism based on varying scaling [PITH_FULL_IMAGE:figures/full_fig_p014_3.png] view at source ↗
Figures from the paper (1 more)
Figure 4
Figure 4. Figure 4: the impact of the cumulative penalty mechanism on sybil attack [PITH_FULL_IMAGE:figures/full_fig_p015_4.png]

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

6 extracted references · 6 canonical work pages

  1. [1]

    DeFi Deception – Uncovering the Prevalence of Rugpulls in Cryptocurrency Projects

    Agarwal, S., Atondo-Siuz, G., Ordekian, M., Hutchings, A., Mariconti, E., Vasek, M. DeFi Deception – Uncovering the Prevalence of Rugpulls in Cryptocurrency Projects. 2023, Financial Cryptography and Data Security (FC), University College London

    work page 2023

  2. [2]

    A Deep Dive into NFT Rug Pulls

    Huang, J., He, N., Ma, K., Xiao, J., Wang, H. A Deep Dive into NFT Rug Pulls. 2023, arXiv:2305.06108 [cs.CR], https://doi.org/10.48550/arXiv.2305.06108

    work page Pith review arXiv doi:10.48550/arxiv.2305.06108 2023

  3. [3]

    On the Involvement of Bots in Promote-Hit-and-Run Scams – The Case of 28 Rug Pulls

    Janetzko, D., Krauß, J., Haase, F., Rath, O. On the Involvement of Bots in Promote-Hit-and-Run Scams – The Case of 28 Rug Pulls. 2023, 5th Int’l Conference on Advanced Research Methods and Analytics (CARMA 2023)

    work page 2023

  4. [4]

    CRPWarner: Warning the Risk of Contract-related Rug Pull in DeFi Smart Contracts

    Lin, Z., Chen, J., Zheng, Z., Wu, J., Zhang, W., Wang, Y. CRPWarner: Warning the Risk of Contract-related Rug Pull in DeFi Smart Contracts. 2024, arXiv:2403.01425 [cs.SE], https://doi.org/10.48550/arXiv.2403.01425

    work page Pith review arXiv doi:10.48550/arxiv.2403.01425 2024

  5. [5]

    RPHunter: Unveiling Rug Pull Schemes in Crypto Token via Code-and-Transaction Fusion Analysis

    Wu, H., Wang, H., Li, S., Wu, Y., Fan, M., Jin, W., Zhao, Y., Liu, T. RPHunter: Unveiling Rug Pull Schemes in Crypto Token via Code-and- Transaction Fusion Analysis. 2025, arXiv:2506.18398 [cs.CR], https://doi.org/10.48550/arXiv.2506.18398

    work page Pith review arXiv doi:10.48550/arxiv.2506.18398 2025

  6. [6]

    Stop Pulling my Rug: Exposing Rug Pull Risks in Crypto Token to Investors

    Zhou, Y., Chen, Y., Yan, Z., Sun, J., Ma, F., Jiang, Y. Stop Pulling my Rug: Exposing Rug Pull Risks in Crypto Token to Investors. 2022, BNRist, Tsinghua University 29

    work page 2022

Pith tools

Reviewed August 6, 2026 · model on record in the stance chip above.