home.social

#nxk — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nxk, aggregated by home.social.

fetched live
  1. Telegram setup finalized for launch:

     

    Priority: Channel first (official announcements), Group second (community chat). Cross-linked both, streamlined permissions, and kept member approval OFF for smoother onboarding.

    #NXK #W3Rooster #Crypto #Web3 #Blockchain

     

  2. Launch tuning update:
    earlyBps set to 3000 (30%) instead of 1500.A 30% early window provides a smoother launch phase and reduces excessive restriction in the first blocks.
    Balanced protection > over-tight limits.#NXK #W3Rooster #Crypto #Web3 #Blockchain

  3. Rechecked contract optics, ownership model, liquidity sizing, and launch limits. Adjusted launch protections for smoother 2 ETH / 300K NXK start.

    Goal: clean bytecode, clean optics, controlled launch.
    #NXK #W3Rooster #Crypto #Web3 #Blockchain

  4. Adjusted launch protections accordingly:
    • maxBuyPerBlock = 60,000 NXK• earlyBps = 15%• maxBuyGlobal = 20,000 NXK• maxWalletGlobal = 80,000 NXK
    Goal: smoother launch, lower chaos, controlled distribution.#NXK #W3Rooster #Crypto #Web3 #Blockchain

  5. Deploy.ts update: removed setExcludedFromMaxWallet for SAFE_GOVERNANCE.
    Owner privileges should not bypass wallet limits unless strictly necessary — reducing unnecessary exemptions improves trust and optics.
    #NXK #W3Rooster #Crypto #Web3 #Blockchain

  6. We added a configurable slippage safety limit in our liquidity tooling to prevent bad-price execution during LP actions.#NXK #W3Rooster #Crypto #Web3 #Blockchain

  7. NXKToken.sol update: maxBuyPerBlockLocked removed to reduce complexity and avoid unnecessary launch-time restrictions.#NXK #W3Rooster #Crypto #Web3 #Blockchain

  8. We’re mapping every admin function to the correct modifier (Timelock-only, Guardian during launch, etc.) and enforcing 3 hard rules in code: • emergency window only • loosen-only changes • one-way guardian lock after launch

    #NXK #W3Rooster #Crypto #Web3 #Blockchain

  9. Focus remains on safety, transparency, and clean exchange optics.

    #NXK

  10. Launch planning update: startTrading will execute simultaneously with transferring ownership to the Timelock, while a time-limited Safe Guardian remains available to react to any launch-phase misbehavior.

    Hashtags #NXK #W3Rooster #Crypto #Web3 #Blockchain #TokenLaunch

  11. NexaKing website update: footer social links corrected and now properly pointing to X and Telegram.

    #W3Rooster #NXK #Web3 #Crypto

  12. From the first tradable block, NXK has no EOA admin control — launch/config actions are executed via Safe multisig batches, and ownership is transferred to the Timelock at the trading start moment.#W3Rooster #NXK #Crypto #Blockchain

  13. We’re keeping pauseTradingForBlocks() for NXK token strictly as a launch-only emergency safeguard. It applies only to primary-pair buys, never to sells or wallet-to-wallet transfers, and expires automatically after the first blocks.

    #NXK #Nexaking #blockchain #crypto

  14. – NXKToken.sol: setSnipeBlockCount function reviewed/updated again

    #NXK #Nexaking

  15. GitHub monthly reports for the NXK token (Nexaking) have launched for November.2025, December.2025, January.2026

    #NXK #Nexaking

  16. NXK = no EOA admin control.Every contract role is managed by Safe multisig wallets, not single wallets.#NXK #W3Rooster #Crypto #Blockchain

  17. SAFE_LP_TAX was excluded from maxwallet, but not from maxFee and maxBuy.

    #NXK #w3rooster

  18. Ask helper was corrected in NXK deploy.ts

    #NXK

  19. Staking has been removed from NXK’s goals.
    We will not implement staking for NXK.
    #w3rooster #nxk #crypto #blockchain