GoPlus × OpenFour: From Royalty, an Extra Security Check for the Next-Gen of Launch Mechanisms On Four.meme, every launch mode began as someone's idea. Four.meme has now released OpenFour: developers can design their own launch mechanisms, and once a mechanism is listed, projects across the community can use it. OpenFour and GoPlus are launching the OpenFour × GoPlus Ecosystem Incentive Program, with a total prize pool of up to $500,000, to call for the next generation of launch mechanisms. GoPlus will provide a free token security audit for selected mechanisms, helping developers find common contract risks earlier. 1. What this program is OpenFour is a modular issuance engine from Four.meme that opens the protocol layer to external developers, teams, and the community. Built on Four.meme's launch infrastructure on BNB Chain, anyone can create their own token issuance model, including bonding curve rules, trading logic, incentives, and revenue distribution. The official site positions it as "The Meme Launchpad OS." The protocol layer is made up of Core, Registry, FeeRouter, and Modules. Developers can combine six contract modules to build a mechanism: Token, Vault, Curve, Trade, Migration, and CustomData. Parameters can also be rendered directly into an interface, so there is no need to build your own frontend. This Ecosystem Incentive Program encourages work in directions including, but not limited to: Royalty vaults and revenue distribution Custom bonding curves and trading logic New migration paths and incentive models New combinations of OpenFour modules, or combinations with protocols such as Binance Agent ID Selected mechanisms can receive: A free security audit, provided by GoPlus A one-time reward of $2,000 when the mechanism is listed A fee share of up to 50% Official promotion and integration support The call for new mechanisms also helps developers make those mechanisms more solid. 2. Royalty: an on-chain royalty framework for every token What is Royalty? Four.meme's featured release this time is Royalty, an on-chain royalty framework officially upgraded from GoPlus Skill Royalty. In August 2026, Four.meme announced: "GoPlus Skill Royalty has been officially upgraded to Royalty." In the words of Four.meme's documentation: "Royalty is an on-chain royalty framework under the OpenFour engine, designed to give projects, developers, creators, and communities a more flexible way to manage and distribute on-chain value." It is bound to each token, automatically collects trading tax, and distributes it according to the rules. The allocation ratios and rules are defined independently by each mode. How it works It takes four steps: a user trades the token → trading fees are generated → Royalty collects them automatically → the rules of the selected Royalty mode are executed. What modes are available? Royalty currently supports five modes: Code Royalty: "Code is Asset." Upgraded from the earlier Skill Royalty mode, it extends the royalty mechanism from specific Skill scenarios to a wider range of code repositories, and connects developers' code contributions to the on-chain Royalty mechanism. Open-source developers, protocol and application developers, AI / Agent developers, and developer communities can all use it. X Verified Royalty: After verification, that X account is bound to an EVM address used to receive and manage royalty proceeds. The binding is set at creation. Ecosystem Buyback Royalty: The project specifies the contract address of a target token. A designated portion of the fees generated by trading is used to buy that token, then applied to a preset ecosystem use, such as a token burn or ecosystem incentives. In official terms: "Trading activity in one token can continuously provide value support for another designated ecosystem asset." Unverified Royalty: Developers can create their own Royalty Template and open it for other projects to use. Custom Royalty: The project sets a custom proceeds address. Proceeds can go to a creator wallet, a community wallet, a project treasury, an ecosystem fund, or another designated address. Incentives for authors of open templates. When a project uses a qualifying Unverified Royalty Template, 6% of each applicable tax goes to the template author's wallet, and 94% enters the Royalty Vault actually used by that token. Where the royalties go is itself part of the mechanism design. OpenFour puts it this way: "Who receives the royalties is part of the design." Four.meme's documentation states that Royalty will continue to expand along two directions: more assets, and more royalty mechanisms. 3. What GoPlus provides: AI audits and Token Self-Check GoPlus DeepScan runs AI audits and Token Self-Check before a project goes live, and continuous security monitoring after launch. It includes three modules: AI contract audits: It uses AI to scan contract source code, permission management, and business logic in depth, find code-level vulnerabilities and business-logic flaws, and output a structured audit report that includes a security score, key findings, issue details, and remediation suggestions. Token Self-Check: a fast token check before launch, with results typically ready in 10 to 30 minutes, that identifies common high-risk characteristics. Continuous security monitoring: Based on real-time attack events and threat intelligence (contract vulnerabilities, oracles, cross-chain bridges, third-party protocols, and more), it helps project teams and developers analyze risks quickly and provides targeted self-check plugins. This supports ongoing security monitoring and risk response, and addresses the "audit as the finish line" problem in Web3 projects. Of these, Token Self-Check is the easiest place to start. What it checks: common token risks such as honeypots, malicious minting, blacklist mechanisms, abnormal buy/sell taxes and trading taxes, owner permissions, and trading restrictions. Tokens that use Royalty are tax tokens, so tax settings and permissions are especially worth a look. How to use it: Open deepscan.gopluslabs.io, choose Token Self-Check, and submit the token information you want to check. What you get: a token security score and risk level, plus a checklist of results that shows which items passed, which need attention, and a risk note for each item. Teams can use this to decide what still needs to be rechecked before launch. 4. How the security tools support developers before and after launch We suggest that developers break security work into three steps: Self-check before launch. Token Self-Check can already be run during development, to screen first for common issues such as honeypots, minting, blacklists, abnormal tax rates, and owner permissions. Teams can also walk through the security checklist in the OpenFour documentation item by item. Examples include: initialization can only be executed once, fee bps must have a cap, conditions should be revalidated at migration, do not trust hookData, and the Vault should use SafeERC20. A free security audit after selection. Every OpenFour mechanism goes through review before it is listed, and third-party submissions need to include audit or testing materials. Mechanisms selected for this program can receive a free token security audit from GoPlus. The specific audit scope follows the arrangements made after selection. Keep watching after launch. After a contract is live, new vulnerabilities can still be disclosed and external dependencies can change. DeepScan's continuous security monitoring can trigger a re-review and alerts when these situations appear. For traders and wallets, the GoPlus Token Security API can also identify tokens launched via four.meme and detect common token risks. What we can do is point out common risks early, so developers can go live with clearer information.