givenchy bless

老外因一张"Unsafe"图不敢买 $SZR ，看来很多人还是不懂HOOK啊，这其实是自动扫描工具的误报。 看这张图:红字标 "Unsafe",它下面白纸黑字写着"完全不可变的 hybrid hook,写死 1% 费,对交易逻辑和用户资金无任何 admin 控制"。既然无 admin 控制、不可变,哪来的 unsafe。推特上问的最多的问题我总结了一下。官推 @SazareProtocol 创始人开发者 @Furyoku0x1 ，现在 $SZR 自己运行不依赖任何人，开发者一旦发布代码就没有任何权限对这个币有权限操作了这就是Hook。 有几个问题我可以回答： 1 $SZR 能无限增发,稀释持有人？ 不是这么理解的。mint 权限在hook合约中,但扫描器只扫了 token 合约、读不到 hook 内部合约:hook 里写死了 10 亿枚发行硬顶,且每一笔 mint 都要过地板价不能下降,否则 revert校验，这是被锁死的。现在链上铸了约 4.3亿 / 10 亿,链上可查也可以去官网查。 2 $SZR 能烧掉任何人的币? burn 确实是 hook 调,但只在你自己主动发起赎回/迁移时触发,把你交回的币烧掉换 WETH 给你。没有任何函数能烧掉你钱包里、你没授权的币。 3 $SZR 的流动性只有 $20K太薄? SZR 合约永久禁止任何人添加流动性,这是写死在代码里的。看 hook 的 beforeAddLiquidity 函数,你加池子会被HOOK合约拦截。 源码函数： function beforeAddLiquidity(...) external view override onlyManager returns (bytes4) { revert LiquidityForbidden(); } 任何人包括项目方想加 LP,交易 100% 被回滚,没有例外。所以 SZR 的深度不以传统 LP 形式存在,DexScreener 扫描不到真的池子。真正的LP是锁在 hook 金库里的 222 WETH约$40万,以"地板储备 + 交易带"形式提供,全链上可查。禁止加 LP 等于没人能撤池跑路, 拿 $20K 说它薄,是没找对地方看。 4 既然不能加池子那 $20K是怎么来的？ 那 $20K 既不是项目方现在手动加的 LP,合约禁止加 LP,也不是合约写死的固定值，它是 hook 金库里、当前暴露在交易带(band)最前排的那层动态深度,起点是初始化时注入的种子储备,之后由每笔交易的机制自动增减。它是"活的",不是谁手动摆上去的,也不是写死的常量。 你完全可以自己在链上验而且代码都是开源的: 合约无 owner、无 setter、不可升级，真实 WETH 储备 222 枚,和账面记账分毫不差 扫描器的问题它只能识别权限在谁手里读不懂这个权限被 hook 内部的硬规则锁死。SZR 是把权限收进一个不可变、无后门的 hook合约里面了。 Scared off from buying $SZR by one "Unsafe" image — turns out a lot of people still don't understand Hooks. This is actually a false positive from an automated scanner. Look at the image: it flags "Unsafe" in red, yet right below it states in black and white — "fully immutable hybrid hook, hardcoded 1% fee, no admin controls over swap logic or trader funds." No admin controls, immutable — so where's the "unsafe"? I've rounded up the questions asked most often on Twitter. Official account @SazareProtocol, founder/dev @Furyoku0x1. Right now $SZR runs on its own and depends on no one — once the dev shipped the code, they no longer have any privileges over this token whatsoever. That's what a Hook is. Here are a few questions I can answer: 1. Can $SZR mint unlimited tokens and dilute holders? That's not how it works. The mint permission sits in the hook contract, but the scanner only scanned the token contract and can't read inside the hook: the hook has a hardcoded 1B issuance hard cap, and every single mint must pass a "floor price cannot drop, else revert" check — it's locked down. On-chain, ~430M of 1B has been minted so far — verifiable on-chain and on the official site. 2. Can $SZR burn anyone's tokens? Burn is indeed hook-called, but it only fires when YOU actively initiate a redemption/migration — burning the tokens you hand back in exchange for WETH. No function can burn unapproved tokens sitting in your wallet. 3. Is $SZR's liquidity only $20K — too thin? The SZR contract permanently forbids anyone from adding liquidity — it's hardcoded. Look at the hook's beforeAddLiquidity function; adding to the pool gets intercepted by the hook contract. Source function: function beforeAddLiquidity(...) external view override onlyManager returns (bytes4) { revert LiquidityForbidden(); } Anyone, project team included, trying to add LP gets their transaction reverted 100%, no exception. So SZR's depth doesn't exist as traditional LP — DexScreener can't scan the real pool. The real liquidity is locked in the hook vault: 222 WETH (~$400K), provided as "floor reserve + trading band," all verifiable on-chain. No LP allowed means no one can pull the pool and rug. Citing $20K to call it thin is just looking in the wrong place. 4. If you can't add to the pool, where did that $20K come from? That $20K is neither manually-added LP by the team (the contract forbids adding LP), nor a hardcoded fixed value. It's the front-of-book dynamic depth currently exposed in the trading band within the hook vault — it originates from the seed reserve injected at initialization, then automatically increases and decreases with each trade. It's "alive," not something manually placed there, and not a hardcoded constant. You can verify it all on-chain yourself, and the code is fully open source: No owner, no setter, non-upgradeable — and the real WETH reserve of 222 matches the on-chain ledger to the wei. The scanner's problem: it can only identify who holds a permission — it can't read that this permission is locked down by the hard rules inside the hook. SZR has concentrated permissions inside an immutable, backdoor-free hook contract.