> For the complete documentation index, see [llms.txt](https://docs.geode.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geode.fi/key-concepts/future-of-geode/further-decentralization/supporting-eip-4788-draft.md). # Supporting EIP-4788 (DRAFT) #### EIP-4788 vs EIP-4895 (WIP) (CFI for Shanghai Update) There are currently two possible methods suggested for Withdrawal Operations on the Beacon Chain. 4788, is a version that supports trustless withdrawals from Smart Contracts living in the Execution Layer. This provides ease to the staking pools, however it is not going to be live soon. 4895, is a version that only allows withdrawals when Operator triggers. This is not so trustless as there is no way to enforce the validator. However, currently this is the version to be implemented. #### Geode supports withdrawals with EIP 4895 and will support EIP-4788 when it is ready. * Operator withdraws remotely with a key, without any limits other than validator timeline stated when it is created. * Funds emerges within "**withdrawalContract**" of the Pool, without triggering the fallback. Since it is not trustless to handle all this operation, currently we are optimizing it further and preparing for the EIP-4788. However, it is not coming soon. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.geode.fi/key-concepts/future-of-geode/further-decentralization/supporting-eip-4788-draft.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.