Whitepaper

Memesly Whitepaper

What Memesly is, what it is built out of, and where to check every number in it, because a whitepaper nobody can verify is just a long advertisement.

Last updated August 18, 2026 · Questions:

This is a whitepaper for a project whose entire premise is that memecoin whitepapers are nonsense. So there is no token velocity equation, no four quadrant market map, no invented advisory board and no paragraph about disrupting anything. There is a description of what was built, the numbers it was built with, and instructions for checking those numbers without asking us.

Memesly is three things, and they arrived in this order: a satirical parody of a subscription creator platform where 185 real memecoins have profiles, then a memecoin, then a launchpad. The parody came first and the rest grew out of it. That order is unusual and it is also the only structurally interesting thing about the project, so it is stated up front rather than reverse engineered into a mission.

The joke only works if the boring parts are real, so the boring parts are real. Live market data, published burn transactions, an open configuration file with a comment on every value explaining why it is that value. You are welcome to dislike the jokes. The numbers you can go and verify, which is the point of putting them where you can reach them.

Nothing in this document is a promise, a forecast, or financial advice. The last two sections say so at greater length, and that part is not a joke.

#What Memesly is

Three separate things share one brand, and blurring them together would be the easiest way to mislead somebody by accident, so here they are apart.

  • The parody, a send up of a subscription creator platform. 185 memecoins have creator profiles, bios, hobbies, subscription prices, posts and direct messages that answer back. The personalities are invented. The market data next to them is live and real.
  • $MEMESLY, a memecoin on Solana. It is a token about memecoins. It has no revenue behind it, no yield, no claim on anything, and no intrinsic value.
  • The launchpad, built on a third party audited bonding curve program. It is live on Solana mainnet, it charges a real fee in real SOL, and the tokens it mints are permanent.

All three sit on one domain, memesly.io. They were split across two for a while and memesly.io now forwards there, so an old link still lands in the right place.

The parody was built first, on its own, as a joke about the fact that memes have been doing unpaid labor since roughly 2009 while every other kind of creator on the internet got a platform and a subscribe button. The token came after the site. The launchpad came after the token, and only because a site that already ranks memecoins every day is an unusual place to put a launch button.

That is the shape of it. Everywhere else, a launchpad is a launch button hoping to grow an audience. Here it is an audience that grew a launch button. We are not claiming that makes the tokens better. It makes the discovery problem different, and discovery is the part of this market nobody has solved.

#How to check everything in this document

This is the most useful section here, which is why it is near the front instead of buried in an appendix. Every category of claim in this whitepaper is checkable, and here is where each one is checkable from.

What you want to verifyWhere it can be verified
Every launchpad parameterlaunchpad/config/memesly.config.mjs, and the inspector script, which prints what the config does and fails loudly if any value has drifted
That a token really launched herethe pool account's config address on chain, never the mint address ending in meme
$MEMESLY supply, and both burnsthe mint account on any Solana explorer, plus the two burn signatures published further down
That a launched token is immutableits mint account: the mint authority and the metadata update authority are both null
That graduated liquidity is lockedthe graduated token's pool position, where no withdrawable share exists to be withdrawn
What a trade actually cost youthe transaction itself, read against the fees page
The market cap on any creator profilethe public chart each profile links to, which is the same feed the profile is drawn from
How many launched tokens graduatethe graduates scoreboard, which publishes the denominator next to the numerator

Two rules follow from that table. First, where this site and the chain disagree, the chain is right and we are wrong; write to with the transaction signature and we will fix the page. Second, nothing here asks you to trust a screenshot, a dashboard we control, or a sentence beginning with the words we can confirm.

A mint address ending in meme proves nothing at all. Four characters of vanity address costs anybody about two minutes of grinding. The only check that cannot be faked is which config a pool belongs to, and that is on chain.

#What problem this solves

Mostly none. This is a joke that got built properly, and dressing that up as a market inefficiency would be the first dishonest sentence in the document.

There is no unmet need for a parody creator platform. Nobody was waiting for another memecoin. The world had launchpads before it had this one and will have them afterward. If you are looking for the paragraph where a joke website is reframed as infrastructure for the creator economy, it is not here, because it would be untrue and it would be embarrassing.

There are, however, a handful of places where real work went in and the result is genuinely better than the default. Those are worth naming precisely, because a vague claim of innovation is worthless and a specific one can be checked.

  • Launched tokens are immutable from creation. No mint authority, no metadata update authority, enforced by the program rather than by us promising not to use them.
  • All migrated liquidity is permanently locked. Not mostly, not for a period, and not by our choice: there is no withdrawable portion for anyone to withdraw.
  • The trading fee starts at 5% and decays to 1% over two minutes, which taxes launch block bots and costs an ordinary buyer nothing.
  • The creator's share of trading fees is 0.40% of volume for as long as the token trades on the curve.
  • Nothing is skimmed at migration, so a graduating token keeps the full depth it earned.
  • The launchpad publishes its graduation rate with the denominator attached. Every launchpad knows that number and none of them puts it on a page, for the obvious reason.
None of that is new cryptography or a new curve. It is a set of parameter choices, each made on the safe side, written down in one open file with the reasoning attached. The contribution is the reasoning being public, not the math being clever.

#The site, and how the ranking works

The roster holds 185 tokens: 184 other people's, plus Memesly itself. Every one of them has a profile page written as if the coin were a creator with a subscription tier and a content schedule.

The ranking is not curated, sold or negotiated. The page ranks the whole roster by live market cap in your own browser, every time it loads, and shows the top 100. The rest sit in the Cooking section, which is exactly the same ranking one screen further down. If one of them climbs, it moves up on the next page load, without anyone editing anything.

  • Market data comes from public DEX endpoints, fetched by your browser, not by a server of ours.
  • Every token is pinned by contract address rather than ticker, because a ticker search returns scam clones and several of them outrank the real token on apparent liquidity.
  • The chain battle page scores chains on combined market cap, momentum and volume, and publishes the weights on the page, because an unexplained score on a leaderboard is indistinguishable from a rigged one.
  • Nobody pays to appear, to rank higher, or to be described kindly.

The data can be wrong. It is delayed sometimes, thin for small pairs, and occasionally missing altogether. Where a token has no standard pair to read, the profile says no DEX feed instead of inventing a number. The holder count is labeled as wallets trading in 24 hours, because that is what the public API actually returns and calling it holders would be a small lie told a hundred and eighty five times.

Being ranked here is not an endorsement, an audit, or a signal that a token is safe. It means a public API reported a market cap. That is the entire qualification.

#Which parts are fiction

All of them except the numbers. This matters enough to have its own section rather than a line in a footer.

  • Every profile, bio, hobby, post, subscription price and direct message is invented comedy. No token project wrote any of it and none of them is involved.
  • The subscribe and tip buttons are cosmetic. There is no payment form anywhere on the site and there never was one.
  • The age gate is a parody of an adult site interstitial. There is no adult content on the site.
  • The rug meter on each profile is a joke scored from real liquidity and volume inputs, and it says so on the page.
  • The direct messages are a keyword engine with hand written personalities. Nobody is on the other end.

Memesly is not affiliated with, endorsed by or connected to any subscription platform it parodies, or to any token, project or person depicted on the site. The tokens are real. The characters wearing them are not.

#$MEMESLY

A memecoin on Solana, launched on a public bonding curve like everything else in this category, on the same terms as everybody else who bought it.

The tokenValue
NetworkSolana
Contract6ZC5kpZf9kLfxwMc4QVZfGJksTLrZQUTmKJCDaaopump
StandardSPL token, 6 decimals
Supply at launch1,000,000,000
Burned by the project401,126,231.78
Burned by holders54,479,274.35
Supply now544,394,493.87

There was no presale, no private round, no seed allocation, and no group chat that got a better price for being early. There is no team vesting schedule, because there is no team allocation to vest. There is no buy tax, no sell tax, no reflections, no staking and no revenue share, which is partly a design preference and partly the difference between a memecoin and a security.

AllocationTokensShare of the original supply
Circulating435,229,826.9543.5230%
Airdrop reserve88,058,000.308.8058%
Marketing and operations21,106,666.622.1107%
Burned455,605,506.1345.5606%
Original supply1,000,000,000100%

Shares are of the original billion, and the token column adds to it exactly. The percentages are each rounded to four places on their own, so reading down that column gets you 100.0001% rather than 100%, which is rounding and not a missing allocation. Unrounded, the marketing and operations allocation is 2.110666662% of the original supply and 3.877090394% of what is left.

Burned supply cannot be reissued and there is no mint function waiting to surprise anyone later. Supply moves in one direction only, and the direction is down.

#The burns, and the airdrop

401,126,231.78 tokens have been destroyed across three burns, all out of project wallets rather than out of the market, so nothing anybody bought was touched. Here are the signatures, which are the only part of a burn announcement that means anything.

  • Burn one, 201,000,000 tokens, out of marketing and operations. Signature 4PTGZnRizDAoFUP93dHigE477ozVGAjpyzQXdtcA5Vy3QT1BKvDPgYAze6VJAiV1uTPbHF44dxaUSgL3Drs9sk1e
  • Burn two, 100,126,231.78 tokens, out of marketing and operations. Signature 531vDtAgbosd1QC6YNsWYLGRL6Ux73PnWVprUrHxWcQyv3CQ7gLvfPTRSemnF2XjdPcfyVudiXnaL38RRQyKXwDb
  • Burn three, 100,000,000 tokens, out of the airdrop reserve. Signature bg8hGuph1We21CaYEPpttJuHTzUAdCA7V3vMsX3aipj3LSThPiLmQxwjqmQG2wePgjkWdkFVTEcJkoPmNQFqbAs

Take the current supply off the original billion and you get 455,605,506.13 rather than the 401,126,231.78 above. The difference, 54,479,274.35 tokens, was burned by holders out of their own wallets. We did not do it, we cannot hand you a signature for it, and we do not count it as ours. It is gone either way, which is why the supply on Solscan is lower than our own receipts would explain.

The airdrop reserve started at 200,000,000 tokens sitting in its own wallet, 7LoxN8DhDwwLvkuPaQGagzV4Zx8PPAbxEzVJum8kGr3V, with nothing else in it. 11,941,999.70 has gone out so far, 100,000,000 was burned rather than distributed in burn three above, and 88,058,000.30 is still there. The airdrop is smaller than it was originally meant to be, and the wallet history says so whether this document does or not. Watching that balance is a better source than any announcement we could write, and it is available to you at the same moment it is available to us.

There is nothing to claim, farm, sign or connect a wallet for. Tokens land in wallets. Anybody running a claim site, a checker or a form is not us, and the second they ask you to connect something you already know that.

Marketing and operations is 21,106,666.62 tokens, held across several project wallets rather than one, so a single balance will not match the total. 31,662,646.10 has already been spent and is out in the market now, which is precisely why the circulating figure moved up by the same amount. That allocation shrinks as it is used and never grows. The first two burns came out of the primary wallet, so you can read that address straight off either of those transactions above.

#The launchpad, and what it runs on

Memesly's launchpad is a configuration of Meteora's Dynamic Bonding Curve program, a deployed Solana program built so that third parties can run their own launchpads on it. The mainnet program is dbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqN. It is not our code and it has been audited by people who do that for a living.

That was a deliberate choice and the reasoning is worth stating plainly, because the alternative sounds more impressive. Writing our own bonding curve program means an Anchor build, a queue for an audit slot, an audit, fixes, a re-review and a public beta: realistically ten to twenty three weeks and twenty to sixty thousand dollars, at the end of which we would personally own the most dangerous two thousand lines in the building. Shipping an unaudited curve that holds other people's SOL is the single most expensive mistake available to us, so we did not take it.

  • What we control: the curve parameters, the fee schedule, the vesting, the migration target, the supply tiers, the site, and our share of the fees.
  • What we do not control: the math of the pool, the program fee, and the program's roadmap.
  • What nobody controls: an existing config, including us. There is no instruction in the program that edits one.

Every parameter lives in one file, launchpad/config/memesly.config.mjs, which the config creation scripts, the inspector and the launch API all read from, so there is never a version of these numbers that exists only in somebody's terminal history. Each value carries a comment saying why it is that value. The house rule is that a value with no comment has not actually been decided and does not ship.

A config is immutable from creation, forever, for every token ever launched under it. That cuts both ways and we prefer the cut: nobody can raise the fees, redirect the migration or unlock the liquidity later, including us, including someone who steals a key from us.

#Picking a supply, and why it changes nothing

A creator picks the total supply of their token from eight options. This is the one cosmetic choice on the launchpad and it is offered because creators genuinely care about unit price, which is a good enough reason.

Total supplyNote
500,000,000highest unit price
950,000,000the default, and ours
1,000,000,000the common choice in the space
1,500,000,000
2,000,000,000
5,000,000,000
1,000,000,000,000
2,000,000,000,000lowest unit price

Supply is baked into the curve itself and a config cannot be edited, so the picker is not a runtime setting. It is eight separate configs, created once, each holding one supply forever. Everything else about them is identical on purpose: same graduation threshold, same 20% seeding the pool, same 2% creator allocation, same fee schedule, same vesting.

Which means the thing somebody will otherwise assume is wrong. Picking a supply does not change the economics. Every tier opens at a 27.94 SOL market cap and graduates at a 425 SOL market cap, roughly 15.2 times the opening price, whichever one you pick. A 500M token simply costs ten times what a 5B token costs at the same market cap. It is a choice about how many zeros are in the price and nothing else.

The inspector asserts that the market caps are identical across every tier, and the website's build fails if the picker and the on chain configs disagree about which tiers exist. Both checks exist so the supply picker cannot quietly become a pricing lever.

#Immutable tokens

Every token launched here has no mint authority and no metadata update authority, from the moment it is created. Not revoked afterward as a gesture, not held by a multisig that promises restraint: set to immutable in the config, enforced by the program, applied to every token launched under it.

  • Nobody can print more supply. Not the creator, not Memesly, not a compromised key.
  • Nobody can swap out a token's name or image after it gets attention, which is the bait and switch that keeps working because people check a token once.
  • The same property means a typo in a ticker is permanent. That is the cost, it is real, and the trade is obviously worth it.

There is one way a revoked metadata authority can be quietly undone, and closing it took more work than setting the flag did. If a token's metadata URI points at a document the creator can edit later, the name and picture can still change, and the on chain flag becomes decoration. So the launch API only accepts a metadata URI that this server issued, records which ones it issued, and refuses anything else.

Uploaded images get the same treatment for the same reason. The size cap is enforced while reading rather than after, the format is decided by decoding the bytes rather than trusting the filename, SVG is refused outright because it is a document format that executes script, dimensions are capped so a decompression bomb is refused rather than allocated, and every accepted image is re-encoded, which means an appended archive or a polyglot header does not survive contact.

Tokens are classic SPL rather than Token2022. Token2022 has better features and worse support: some wallets, aggregators and analytics tools still handle it badly. A launchpad's token standard is not the place to be early.

#Graduation, migration and locked liquidity

A token graduates when 85 SOL has accumulated on its curve. This happens automatically, which is the important half of the sentence: nobody presses a button, so nobody can decline to press it, delay it, or press it for a friend first.

  • 80% of the supply sells on the curve.
  • 20% seeds the pool at graduation.
  • 0% is held back for the platform. A launchpad that keeps a slice of every token it launches has a sell wall in every one of its own charts.
  • Liquidity migrates to a DAMM v2 pool at the 0.25% fee tier, which is the rate traders already expect on a graduated pool.

All of the migrated liquidity is then permanently locked by the program. The configuration splits it fifty fifty between the platform and the creator, and both of those halves are the permanently locked kind. The two withdrawable lines are set to zero, so the total that anyone can ever pull out of a graduated Memesly token is zero.

That is worth being precise about, because every launchpad says something reassuring here. This is not a promise not to pull liquidity. It is the absence of an instruction that could pull it. Neither we nor the creator can withdraw it, and the reason is not restraint, it is that the capability does not exist. We do still claim trading fees from the locked position, forever, which is how the locked position pays for itself.

The inspector refuses to pass and the config creation script refuses to send if the withdrawable percentage is ever anything other than zero. That check is in the repository and it is the one assertion in the project that is not negotiable.

#The creator's 2%

A creator pays 0.1 SOL at creation, or half that paying in $MEMESLY, and receives 2% of their token's supply, but only if the token graduates. The vesting escrow is created at graduation and not before, so a token that never fills its curve produces no escrow and pays its creator nothing at all.

  • Half of the 2% unlocks at graduation.
  • The other half unlocks eight hours later.
  • The schedule is keyed to the program's own curve completion timestamp, so until graduation is an exact moment rather than a date somebody guessed.
  • The escrow itself is created in a third party locker program, funded out of unsold supply.

Under 2% of tokens graduate anywhere in this market. So this is not a grant and it should not be read as one. It is a payout for finishing the curve, and the creation fee is what somebody pays for the chance at it. The expected value of launching fifty tokens before breakfast is, deliberately, negative.

What the vesting is not: a lock on tokens a creator bought on their own curve. The program vests an allocation carved from supply and cannot reach swap output, and in fact nothing can lock a purchase until graduation, because only the program knows when graduation happens. A creator can buy their own token like anyone else, at the same price, paying the same 5% in the first second, and that purchase is not locked. Every token page on the launchpad says exactly that.

#Fees

Every fee is set in the on chain configuration rather than in the website, which means the site cannot quote one number while the program charges another. The fees page carries the same figures and is the canonical version.

Launching a tokenAmountWhere it goes
Paid in SOL0.1 SOLMemesly, less the program's 10% share
Paid in $MEMESLY0.025 SOL plus 0.025 SOL worth of $MEMESLY, so half the priceThe SOL as above. The $MEMESLY is burned and nobody receives it.

The SOL part of either fee is the bonding curve program's own pool creation fee, charged by the program rather than by our website. That distinction matters: a fee collected by our own code could be skipped by anybody who built the transaction themselves, and they would still get the creator allocation, because the vesting lives in the config. This one cannot be skipped. It is also why a $MEMESLY launch still costs some SOL: the program charges that fee on every launch whatever the creator paid with, so the discount is a second set of configurations carrying a smaller fee rather than a switch anybody can flip.

Trading on the curveFee on the trade
First second5.0%
Falling linearly over 120 seconds5.0% down to 1.0%
After two minutes, and forever after1.0%
Who receives the 1%Share of the trade
The token's creator0.40%
Memesly0.40%
The bonding curve program0.20%

The creator's 0.40% is paid automatically for as long as the token trades on the curve. It is not something we hand out and not something we can withhold, because the split lives in an immutable config account rather than in a policy we could quietly change later.

Nothing at all is taken at migration, by us or by the creator. Every basis point skimmed there comes straight out of the liquidity a graduated token launches with, at the exact moment it can least afford thin depth. We earn on trading and on the locked position instead.

  • There is a volatility surcharge on top of the base fee, capped by the program at 20% of the base fee.
  • Fees accrue in SOL only, never in the launched token, so Memesly never ends up holding a position in a coin it launched and never has to sell into somebody's chart.
  • Solana network fees, priority fees and account rent are real, and they are not ours. We do not set, receive or control any of them.
  • Any other interface reaching the same contracts sets its own fees on top. On our own site, the fees above are the only ones we add.

#Why the fee starts at 5%

The decaying fee is the one parameter here that is doing real work rather than being set conservatively, so it deserves its own explanation.

A bot buying in the launch block pays 5%. A person who read the page, opened their wallet and decided pays 1%. The gap closes linearly over 120 seconds in two second steps, and it costs an ordinary buyer nothing, because an ordinary buyer is not there in the first two minutes.

  • The alternative in the same program taxes by order size instead of by time. That punishes one large honest buyer exactly as hard as one large sniper, so it is the wrong tool.
  • The schedule runs on wall clock time rather than slots. Slot times drift with network conditions, and a slot based fee schedule is a fee schedule of uncertain length.
  • The creator's first swap is not exempt. Exempting it would let a creator front run their own launch at 1% while everybody else paid 5%.
This does not stop sniping and we are not claiming it does. Every launchpad tries, nobody wins, and fair launch tooling moves the edge rather than removing it. A five times tax on the first two minutes is the cheapest honest protection available, which is a much smaller claim than the one usually made here.

#Paying the launch fee in $MEMESLY

A creator can pay the launch fee in $MEMESLY instead of SOL and pay 50% less for doing so. It is charged in two parts, and the split is the interesting part of this section.

Paying in $MEMESLYAmountWhere it goes
The program's creation fee0.025 SOLMemesly, less the program's 10% share
The burn0.025 SOL worth of $MEMESLYDestroyed. Nobody receives it.
Total0.05 SOL of valueHalf of what a launch paid in SOL costs

The reason it is split rather than burned in full is that the bonding curve program charges its own creation fee, in SOL, on every launch, whatever the creator paid with. No setting waives it and no setting converts it into tokens. So a $MEMESLY launch runs against a second set of configurations where that fee is 0.025 SOL rather than 0.1 SOL, and the remaining 0.025 SOL of value is paid in tokens and burned. There are sixteen immutable configurations in total: eight supply tiers, twice.

That arrangement is deliberate on both sides. Memesly receives SOL at creation on every launch, graduated or not, which matters more than it sounds: under 2% of tokens graduate anywhere, so for most launches the creation fee is the only revenue there will ever be. And real tokens still leave supply on every discounted launch, which is the point of the option existing at all.

The discount is the entire reason the option exists. Charging the same either way gives nobody a reason to switch, and an unused payment method is not a demand sink, it is a second code path to maintain. The burned amount is priced from the live market at the moment of launch rather than fixed in tokens, because a fixed token amount looks tidy in an announcement and then drifts until it is either meaningless or absurd.

A burn is used rather than a treasury, and the reason is verification rather than ideology.

  • A burn is checkable without trusting anybody. Supply went down, the transaction says by how much, and there is no claim about an address to evaluate.
  • A treasury is a promise with a private key attached to it. It requires an ongoing commitment about what will never be sold, made by people who could change their minds, and held in something that can be stolen.
  • A burn requires no future good behavior from us. It has already happened, it cannot be undone, and it does not depend on this project still existing next year.

One implementation detail, because it is the kind of thing that gets glossed over. The burn cannot be a program parameter, since the program only knows how to charge SOL, so it rides as our own instruction in the same transaction as the pool creation. Same signature, same atomicity: if the pool creation fails, nothing is burned, and if the burn fails, no token is created. A burn that landed while the launch failed would take somebody's tokens and give them nothing, and no instruction anywhere undoes it. The affordability check happens before any of it, so a creator who cannot cover the burn is told so rather than handed a transaction that cannot succeed.

We are not making $MEMESLY the currency every trade routes through, and the reason is that the pool is not deep enough for it. There is a published threshold for revisiting that, roughly $100,000 of pool liquidity, so a thousand dollar buy costs under 2% slippage. Writing the number down in advance is the point, since the temptation to switch it on early will arrive exactly when the chart is green and judgment is at its worst.

#Security, and the risk that is left

The program holding the money is a third party's and it has been audited. Our own code sits in front of it, and with the curve audited, the largest remaining risk on a launchpad is not the curve. It is a website serving somebody a malicious transaction.

  • The server never holds a key and never signs for a user. Writes return an unsigned transaction and the browser signs it in the user's own wallet. It is the only arrangement in which a compromised server cannot drain anyone.
  • Signing in is a message signature, never a transaction. The nonce is issued by the server, single use, five minute life, and the message names the domain and the purpose in words the user reads in their wallet.
  • Sessions are opaque random tokens hashed at rest rather than signed tokens, so there is no signing key to leak, and disconnecting the wallet ends the session.
  • The wallet library is vendored into the repository with a published hash rather than loaded from a CDN, because a compromised CDN in the signing path is the most likely way a launchpad loses other people's money.
  • Uploads are validated by decoding them and re-encoded before storage.
  • We never take custody of anything, at any point, and we have no technical ability to move assets out of anyone's wallet.

The launchpad code went through a line by line security review on 17 August 2026, conducted by reading it and then by attacking it with real payloads through a real browser, a fake Solana RPC serving correctly encoded pool accounts, and a suite that plays the attacker. It found two critical issues, five high, four medium, and three identifiers that were called but never defined. Everything found was fixed, and each fix has a test that fails when the fix is removed, which is the difference between a fix and a claim.

That review was ours. It was thorough and it is written up finding by finding, and it is still not the same thing as an external audit of our own code. We have not had one, and the launchpad went live on mainnet without it. That is a real gap and it is written down here rather than left for somebody to discover. The program holding the money is audited by people who do that for a living. The code sitting in front of it was reviewed by the people who wrote it.

The residual risks, named rather than implied, because a security section with no open items is a marketing document.

  • The guard that refuses private network addresses in metadata fetches does not stop DNS rebinding. A hostname that resolves publicly at check time and privately at fetch time gets through.
  • A third party swap widget is loaded from a CDN without subresource integrity. It is currently only on pages with no wallet bar, which is a separation nothing enforces.
  • The fee claimer address was fixed at the moment the mainnet configs were created and can never be changed. Whatever holds that address receives every lamport of launchpad fee revenue for as long as these configs exist, and the program has no instruction that points it somewhere else.
  • The launch API is a single deployment. If it is unreachable, launches fail; if it were ever compromised, it could return a transaction that is not the one the interface described. Your wallet showing you what you are about to sign is the last real check on that, and it is the one check we cannot perform for you.
  • All of this now runs against real money. The same code was exercised for weeks in a place where a mistake cost nothing, and that place is gone. A defect that used to produce a worthless test token now produces a real one, on a real chain, that nobody can recall.
  • No system is perfectly secure, a session token lives in your browser, and a wallet is only as safe as the device holding it, which is a problem no website can solve for you.
The most likely way somebody loses money to the word Memesly is not a bug in any of this. It is a fake site or a direct message. We never send the first message, and the only wallet prompt we will ever show you is one you started yourself.

#What we will never do

Short list, absolute language, and it is absolute on purpose. Everything here is something we could technically do and have decided not to, which makes it worth writing down where it can be held against us.

  • No presale, no private round, no seed allocation, and no better price for being early to a group chat.
  • No allocation sales, ever. Nobody can buy a share of a launch or a share of the platform from us.
  • No queue positions, no paid early access, no head start. When something opens, it opens for everybody at the same moment.
  • No paid placement in the ranking. The order is live market cap and nothing else.
  • We never send the first direct message. Anyone messaging you first about a presale, an allocation or a claim is not us.
  • We never ask for a seed phrase, and never ask you to connect a wallet in order to claim anything.
  • No hidden wallets. Project wallets are published and the burns name the wallet they came from.
  • No price promises, no return promises, no listing promises, no market cap targets presented as plans.
If somebody offers you any of the above in our name, they are lying. Report it to , and do not click anything first to check.

#Roadmap, honestly

The launchpad is live on Solana mainnet at memesly.io. It spent its build on a test network behind a password, where nothing anybody did cost or earned a thing, and that period is over. Real SOL, real tokens, and no way to reverse either of them.

The mainnet configs exist and the launchpad is open, which is where the previous version of this list ended. What is left, in rough order, without dates.

  • An external security review of our own code. It has not happened, the launchpad went live without it, and the security section says so at greater length.
  • A lawyer in the relevant jurisdictions. A launchpad taking a fee is a different regulatory posture from a parody site with a memecoin, and the legal pages are accurate descriptions of how the system works rather than documents anyone qualified has signed off.
  • An indexer, before the current program account scan gets slow enough to matter.
  • Graduated tokens getting full creator pages alongside the parody profiles, rather than the client rendered token page they get today.

No dates are attached to any of it, and that is a policy rather than an oversight. A date on a crypto roadmap is a marketing asset that costs nothing to publish and everything to miss, and the honest estimate on most of these items has a two week spread on it. We would rather look slow than dishonest.

The one public date this project has ever committed to was a reveal, not a launch, and that was the deliberate version of the same policy: nothing that holds anybody's SOL gets scheduled against a countdown clock.

A roadmap item here is done when you can check it on chain, not when it is announced. Development updates are posted in the Telegram channel, which is where they actually happen and where you can ask a question and get an answer.

#Risks

The rest of this site is a joke. This section is not, and the risk disclaimer says all of it at greater length.

MEMECOINS ARE AMONG THE RISKIEST ASSETS A RETAIL BUYER CAN TOUCH. THE NORMAL OUTCOME IS THAT THEY GO TO ZERO. NEVER SPEND MONEY YOU NEED FOR RENT, FOOD, MEDICINE, DEBT, OR ANYONE WHO DEPENDS ON YOU.

  • Total loss is the ordinary result, not the worst case. Most memecoins lose nearly everything within weeks and plenty manage it within hours.
  • $MEMESLY has no intrinsic value, no revenue behind it, no yield, no claim on anything, and no roadmap beyond jokes.
  • Thin markets amplify everything. One sell can erase a day, and the price you see is not always the price you get.
  • A token launched here is not vetted, endorsed or reviewed by us. Anybody can launch anything, and the safety parameters in this document constrain the contract, not the person using it.
  • Immutable tokens and locked liquidity remove specific failure modes. They do not make a token good, and a carefully configured token with no buyers is worth exactly as much as a badly configured one with no buyers.
  • Smart contracts can have bugs, including audited ones, including this one.
  • Market data on this site can be delayed, thin, wrong or missing, and every profile links to the chart it came from so you can check rather than assume.
  • The regulatory picture around launchpads and tokens is unsettled and can change in ways that affect availability with no notice.
  • Impersonation is the most common way people actually lose money here, and it does not require any bug in anything we built.
  • You are responsible for every transaction you sign. Nobody can reverse one, including us, including the people who wrote the program.

If any of that comes as a surprise, that is a useful signal, and the correct response to it is not to buy anything today.

#Disclaimer

This document describes how a website, a token and a launchpad work. It is written to be understood rather than to be impressive, and it is not legal, financial, investment or tax advice. If something in it matters to you, take it to somebody qualified in your own jurisdiction.

Questions, corrections and anything where this document and the chain disagree: .

THIS WHITEPAPER IS NOT AN OFFER TO SELL OR A SOLICITATION TO BUY ANY ASSET, AND IT IS NOT INVESTMENT ADVICE OR A RECOMMENDATION OF ANY KIND. $MEMESLY IS A MEMECOIN WITH NO INTRINSIC VALUE, NO EXPECTATION OF FINANCIAL RETURN, NO REVENUE, NO PROFIT SHARE AND NO CLAIM ON ANY ASSET OR ENTITY. NOBODY HERE PROMISES THAT IT OR ANY TOKEN LAUNCHED THROUGH THE LAUNCHPAD WILL HOLD VALUE, GAIN VALUE, OR CONTINUE TO EXIST. TOTAL LOSS IS THE NORMAL OUTCOME. NEVER SPEND MORE THAN YOU CAN AFFORD TO LOSE ENTIRELY.

This is not legal advice, and we are not your lawyer. It is a description of how this site works, written to be understood rather than to be impressive. If something here matters to you, take it to somebody qualified in your own jurisdiction.

Questions about this document go to .