[{"data":1,"prerenderedAt":124},["ShallowReactive",2],{"\u002Fblog\u002F2021-11-23-launching-a-token-while-the-audit-is-still-running":3},{"id":4,"title":5,"archiveType":6,"body":7,"category":108,"contextDate":109,"cover":110,"coverAlt":111,"date":112,"description":113,"extension":114,"featured":115,"historicalDate":112,"historicalLabel":109,"meta":116,"navigation":117,"path":118,"publishedDate":109,"seo":119,"stem":120,"thumbnail":109,"workPeriod":121,"writtenDate":122,"__hash__":123},"blogs\u002Fblog\u002F2021-11-23-launching-a-token-while-the-audit-is-still-running.md","Launching a token while the audit is still running","retrospective",{"type":8,"value":9,"toc":99},"minimark",[10,14,25,28,33,36,39,43,46,69,72,76,79,82,86,89,93,96],[11,12,13],"p",{},"November 2021 was the month Playermon's token, PYM, went live. The pre-IDO ran on 3 November. The launchpad IDOs followed on 18 and 19 November. In late November came the token generation event, with trading on MEXC and Quickswap.",[11,15,16,17,24],{},"Through all of it, the smart contract audit by CertiK was still in progress. When a host in the Romich AMA on 23 November asked whether we had audit certificates, I answered: \"Our audit is on-going by Certik and we would expect it to be released from them.\" On 30 November our Telegram channel said the same thing in its own words: the contract was ",[18,19,23],"a",{"href":20,"rel":21},"https:\u002F\u002Ft.me\u002Fplayermon\u002F594",[22],"nofollow","under assessment, with the audit in process",".",[11,26,27],{},"This post is about that gap, and what I think a team owes holders while it lasts.",[29,30,32],"h2",{"id":31},"what-an-audit-is-and-what-it-is-not","What an audit is, and what it is not",[11,34,35],{},"I had finished the smart contract work before I became CEO, so I knew what the contract was meant to do. That is exactly why an outside review matters. The author of a contract reads it with the intention in mind, and an auditor reads it without one.",[11,37,38],{},"An audit is still a review of particular code at a particular time. It does not cover the website people use to reach the contract, the keys of the people who deploy it, or the fake token with the same name that someone deploys an hour later. A launch can be undermined in any of those places with a perfectly reviewed contract underneath. So while the report was pending, the useful question was not \"are we safe?\" but \"which of the other risks can we reduce ourselves?\"",[29,40,42],{"id":41},"what-we-could-control-in-the-gap","What we could control in the gap",[11,44,45],{},"Some of the answers were procedural.",[47,48,49,57,63],"ul",{},[50,51,52,56],"li",{},[53,54,55],"strong",{},"One address, published by us."," Before trading opened, our Telegram channel posted the contract address of PYM, and the claim notice repeated it. On a public chain, anyone can deploy a token called PYM. The address is the only identifier that settles which one is ours.",[50,58,59,62],{},[53,60,61],{},"A quiet channel during the sale."," For the pre-IDO, the team muted the Telegram channels so that only official admins and moderators could post. Sales attract impersonators offering \"help\" and fake links, and a muted channel gives them nowhere to speak.",[50,64,65,68],{},[53,66,67],{},"Holdings in players' own wallets."," In the AMA on Polygon's Telegram on 3 November, I explained that tokens and NFTs sit in each player's own decentralised wallet, and that game logins would use two-factor authentication. I also said the uncomfortable part: if a player leaks their mnemonic, no project can protect those funds.",[11,70,71],{},"One design answer from that same AMA matters here too. For players who use NFTs owned by investors, we were working on access control where the owner sets the share of rewards that goes to the player. The split is enforced by the system, not by trusting the owner to pay out later.",[29,73,75],{"id":74},"a-late-claim-page","A late claim page",[11,77,78],{},"On the day of the token generation event, the page for claiming tokens did not open on time. The team posted that the tech team was still working on it, and when the page went live, the notice apologised for \"the delay due to late technical issue\".",[11,80,81],{},"Nobody enjoys apologising on launch day. But the alternative is worse. A delay costs people patience. A claim process that pays the wrong amounts, or sends people to the wrong place, can cost them tokens, and a transfer on a public chain cannot be called back. When something is not right at the last minute, I would rather hold a step back and explain the wait than push it through to keep a timestamp.",[29,83,85],{"id":84},"monitoring-after-the-audit","Monitoring after the audit",[11,87,88],{},"In the same Romich answer I said that CertiK Skynet would be enabled \"to ensure that even after the Audit, the system is able to prevent future bugs or flaw\". That sentence claims more than monitoring can deliver. Monitoring watches a deployed contract and the activity around it, and it can raise an alarm sooner than a community would. It does not change the code. What it buys is time to respond, and that time is only useful if someone is ready to act on the alarm.",[29,90,92],{"id":91},"what-i-think-holders-are-owed","What I think holders are owed",[11,94,95],{},"Launching before a report is published is a decision, and it should be stated as one. Holders were entitled to know that the audit was in progress rather than finished, which auditor was doing it, and where to check its status. They were also entitled to the plain warnings: use only the published address, ignore direct messages offering help, and never share a seed phrase.",[11,97,98],{},"At the end of November, the audit was still running. Until the report is published, the accurate description of the contract is that it is under assessment, and that is how we described it.",{"title":100,"searchDepth":101,"depth":101,"links":102},"",2,[103,104,105,106,107],{"id":31,"depth":101,"text":32},{"id":41,"depth":101,"text":42},{"id":74,"depth":101,"text":75},{"id":84,"depth":101,"text":85},{"id":91,"depth":101,"text":92},"Security",null,"\u002Fimg\u002Fblog-covers\u002F2021-11-23-launching-a-token-while-the-audit-is-still-running.webp","A token on a launch pad while a magnifying glass on a stand still examines it.","2021-11-23","November 2021: Playermon's token went live while its CertiK audit was still in progress. What I told AMAs, what we could control in the gap, and why a late claim page beats a rushed one.","md",false,{},true,"\u002Fblog\u002F2021-11-23-launching-a-token-while-the-audit-is-still-running",{"title":5,"description":113},"blog\u002F2021-11-23-launching-a-token-while-the-audit-is-still-running","2021","2026-11-07","Q9A3ZJ2VXuUQxjk-SyVzcu02dTU8JZYht26s9XCSZck",1794838285790]