# zkServerless Framework & x86 Verifiable Compute Engine

**URL:** <https://forum.eigenlayer.xyz/t/zkserverless-framework-x86-verifiable-compute-engine/6429>\
**Category:** AVS Research\
**Created:** [June 2, 2023, 5:08am UTC](https://forum.eigenlayer.xyz/t/zkserverless-framework-x86-verifiable-compute-engine/6429 "2023-06-02T05:08:39Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![0xtokidoki](https://avatars.discourse-cdn.com/v4/letter/0/2acd7d/32.png) [@0xtokidoki](https://forum.eigenlayer.xyz/u/0xtokidoki)\
**Post date:** [June 4, 2023, 8:39am UTC](https://forum.eigenlayer.xyz/t/zkserverless-framework-x86-verifiable-compute-engine/6429/9 "2023-06-04T08:39:32Z")

</div>

2/  
Node Operator will be able to spin up a node via a user-friendly GUI, removing the technical ability requirement.

3/

- Resource consumption: We can make sure the AVS don’t take over compute required by running ETH nodes. This is done so on our networking layer
- Malicious AVS: we want to make sure the AVS software don’t attack the host machine
- Privacy: we want to make sure that it’s hard to peak inside the avs to maintain a degree of privacy

4/  
Throughput is improved as both the node operators and compute consumption scale proportionally. The economic follows the free-market supply and demand equilibrium. But a waitlist mechanism may be adopted to put a hard cap on the number of nodes based on current demand, or alternatively the restaking requirements may be dynamically adjusted to ensure the number of qualified validators make economic sense.

5/  
The partnership provide additional security to the restakers by avoiding unintended slashing, and full transparency to operators for delegation, enhancing control and trust in restaking activities.

---

_[View the full topic](https://forum.eigenlayer.xyz/t/zkserverless-framework-x86-verifiable-compute-engine/6429)._
