customEditor.json Info-Block Compliance for Community Devs Publishing
Audit / Issue Found
The Gunbot core team specified a required shape for the info block of every
strategy in customEditor.json so the GUI can publish them as Community Devs
without distributing source files. The required shape:
- description (non-empty)
- category = "Community Devs"
- license = the seven-item standard array
- exchangeBlacklist = []
- market = "spot" or "futures"
- buyMethod = "custom"
- sellMethod = "custom"
- hardcode block with BUY_METHOD, SELL_METHOD, a unique boolean identifier per strategy, and IS_MARGIN_STRAT. No STRAT_FILENAME field.
Before the patch
A standardiser script was prepared to fix any deviation from this shape: filling missing fields, removing any STRAT_FILENAME, replacing the strategy filename hint with a unique boolean ID, and normalising field order.
After the patch
The standardiser ran across all thirty-four strategies and reported zero edits required. Every strategy is already in the exact compliant shape. A separate independent audit then re-checked every required field across every strategy and confirmed zero issues. All thirty-four unique boolean IDs are present with no duplicates.
The work to reach this state was done across the earlier audit rounds; this round verified the state and produced the final compliance check that the core team can use to certify publication.
Per-strategy unique boolean IDs (matching the .js file stem in lowercase):
Spot strategies: inventorybalancer, hawkesmm, glostenmilgrom, kalmangrid, rollmodelmm, harrisscalpmm, meanrevoscillator, cointegrationpairs, priceactionpro, mixerspot, moonphasesspot, vwapmm, emabouncemm, bbsqueeze, rsimeanrevmm, twapscalpermm, keltnerchannel, stochmeanrevmm, macdmomentummm, ccimeanrevmm, atrchannelmm, williamspctrmm, donchianmm, supertrendmm, ichimokumm, parabolicsarmm, adxtrendmm, obvmomentummm.
Futures strategies: queuereactivemm, ofiflashmm, cartajaimicromm, micropricemm, mixerfutures, moonphasesfutures.
Bottom line
customEditor.json passes the Community Devs publishing spec. The file can be handed to the Gunbot core team as-is. The package zip and folder were refreshed to ensure the snapshot reflects the verified state.