Files
logos-execution-zone/lez/sequencer/core
Marvin Jones 200b60b09e docs(lee): correct the chain-called Deploy limitation's root cause
The AccountId migration (marvin/program-as-account-3-1) fixed dispatch
locating a Deploy-created PDA-addressed program, but that was never
what blocked this test: the forwarder exhausts its 32M public-execution
cycle budget just carrying the target bytecode through its own
instruction_data before dispatch's addressing even matters. Chain-called
Deploy needs a mechanism where bytecode reaches Deploy without being
copied through an intermediary guest's interpreted execution, deferred
to a future PR. Deploy as the top-level entry point, natively emitting
its own follow-up chained calls after deploying, is the supported
pattern today.
2026-08-14 17:07:39 -04:00
..
2026-08-07 18:30:14 +02:00