@Balcore_AI Testnet is going to be a little late. I spoke with our lead Developer today while he was preparing the contracts for deployment on Fuji, Avalanche’s C-Chain testnet. He found that the compiled contract bytecode is over the EVM’s 24,576-byte deployment limit and not slightly over. So we’re cleaning it up properly before pushing anything on-chain. That limit exists for a reason. Every node has to load and execute deployed contracts, so one oversized contract should not create costs for the entire network. We could look for a chain with a larger limit, but that would be the wrong decision. Build within 24KB and Balcore can remain portable across EVM chains. Build around one chain’s exceptions and you quietly lock the protocol into that environment. For a liquidity operating system designed for tokenized assets, portability matters.
There is also a real engineering tradeoff: optimize aggressively for smaller bytecode and runtime gas may increase; optimize only for gas and the contract may stay too large. My lead developer is closest to the code, so he has the room to make that call correctly. You partition, optimize, or remove what does not belong.
My job as founder is simple: Allow time and take the time. A delayed testnet costs us a little time. A rushed contract holding other people’s capital can cost trust that never comes back. We’ll share the updated timeline once the cleanup is complete. Mainnet performance remains the proof.
Be the Market Maker. There is no escape🔺
