NASDANK Docs
Open app
Protocol/Liquidity and locks

Liquidity and locks

NASDANK custodies locked liquidity. That makes the locker the single most consequential contract in the system, so what it can and cannot do is written out here in full.

The lock is permanent, on every tier

Pro · V3 and Custom · V4
LockPermanent
Can principal ever be withdrawn?No. There is no function.
Can the position be transferred out?No
Can liquidity be decreased?No
Who can collect fees?Anyone. Proceeds go to the fixed recipients.
Creators earn fees, never principal

This is the entire deal, on both tiers. Your supply is in the pool forever; what you earn is a share of the trading fees it generates. There is no launch type on NASDANK whose liquidity comes back on a timer, and no setting that makes one.

What the locker cannot do

These are the properties the locker is built to hold. They are worth reading as a checklist, because they are exactly what you should verify yourself before trusting any locker — ours included.

  • No withdraw path. There is no function that returns principal, decreases liquidity, or burns the position for its underlying.
  • No transfer path. There is no function that sends the position NFT anywhere. It arrives and it stays.
  • No owner powers. There is no owner who can move funds, change recipients, or pause collection.
  • No upgradeability. No proxy, no implementation slot, no way to introduce a withdraw function later.
  • No arbitrary call. No delegatecall, no call with caller-supplied data, no multicall that could be pointed at the position manager.
  • No selfdestruct.
  • No dangling approvals. The locker does not hold standing approvals that another contract could draw against.

The only externally callable function that touches value is fee collection, and it always splits to the two recipients that were fixed at launch.

Verifying a lock yourself

Do not take a website's word for it — including this one. Three checks, in order of how much they tell you:

  1. Who owns the position?Read ownerOf(tokenId) on the position manager. It should be the locker address the launch event named, not a wallet.
  2. What can that locker do?Read the verified source on the explorer. Look for any function that calls decreaseLiquidity, transferFrom, safeTransferFrom or burn on the position manager. If there is one, the lock is conditional and you need to know on what.
  3. Is it upgradeable?Check for a proxy. A locker behind a proxy is only as permanent as whoever controls the proxy admin.
Reading the owner of a Pro position
import { createPublicClient, http, parseAbi } from  3 ;

const client = createPublicClient({ transport: http( 4 0x73991a25C818Bf1f1128dEAaB1492D45638DE0D3 5 function ownerOf(uint256) view returns (address) 6 ownerOf",
   1 
  args: [689248n],
});
 2 

Why the position can still earn while locked

A locked position is a normal Uniswap position in every respect except custody. It accrues fees from trading exactly as any other position would. Collecting those fees does not touch principal — collect on a Uniswap position withdraws only the accrued fee amounts, never the liquidity itself. That is what makes "locked forever, still earning" a coherent design rather than a contradiction.

What is not guaranteed by the lock

A locked LP guarantees that the liquidity stays in the pool. It does not guarantee anything about price, and it is worth being blunt about what it cannot do:

  • It does not stop the price falling. A pool with permanent liquidity can still trade to near zero if everyone sells.
  • It does not stop the creator selling a dev-buy bag they bought at launch.
  • It does not make a Custom coin's holder rewards safe. Those depend on whatever reward token was chosen and can go to zero independently. See Holder rewards.
  • It does not apply to a coin's pair token. If you launched against a custom pair token, that token's own risks are yours.

Read Risk disclosures for the full list.

© NASDANK Not affiliated with Robinhood Markets, Inc. Risk disclosures nasdank.fun