def. Restaking Network. consists of a following weighted bipartite graph: where:

  • : total stake by validater
  • : partial stake by validator on service
  • def. Atomic network is when validators can only stake to one service, and stake fully
  • def. Restaking network is any non-atomic network.
  • ! services include the base Ethereum network, since they have the same slashing mechanism as far as we’re concerned def.1. Restaking Degree of validator is the ratio of their total stake they used up in staking.
  • Intuition. ¶Restaking degree of 1.5 means the validator over-staked by 150%.
  • def. Prize per unit threshold (=total stake required to secure a service) is prize per difficulty.

Cryptoeconomic Security Game

  1. Each validator chooses amount to allocate to attack on a service
  2. def.2. Attcked Services. an attack may include multiple services, and those that are mounted a successful attack is in the set of attacked services.
  1. def. Validator cost and Total cost

def.3. Modified Strong Nash Equilibrium.

def.4. Restaking Network Cryptoeconomic Security. Restaking network is cryptoeconomically secure iff attack , where attacked services , is the MSNE.

def.5. Attack Profitabilty. is profitable iff

def.6. Restaking Network Cryptoeconomic -Robustness. is -budget robust if an adversry is willing to spend up budget to take town services using attack , but the MSNE is where ..6

def.7. -costly Attack has and

Byzantine Service

def. Byzantine Service is one that, due to ¶bug in the code accidentally slashes all of its stakers (or, forced to do so by an adversary) def. Base Service. Some services (like the Ethereum base network) we deem un-failable because that’s too catastrophic to fathom. Adversary can thus choose to fail services taking from following subsets:

Example of adversary slashing a byzantine service.

  1. Adversary chooses , set of services that are byzantine
  2. Adversary fails them, slashing all stakes to that service. Staker’s new stakes are
  1. Other services may lose stake too, due to validator not having enough stake

Example.

  1. Validator has 5 units, (over-)staked to 3 services
  2. Adversary fails first service, slashing 3 units from the validator
  3. Validator now has no longer enough to stake 3 units on service 2

def.8. -robust network is robust for all the network is -budget robust.

EigenLayer’s Weak Security

thm. Atomic Network is cryptoeconomically secure if the cost for misbehavior is:

and also for all validaators in

problem: we don’t want to slash the whole stake. That’s a bit too harsh, and it may also affect stakes to other services less secure as we saw above.

Searching for Attacks is NP-Complete

prop.4. Determining whether a restaking network has a profitiable, allocation-indivisible AND allocation-divisible attack is NP-complete. corr.2. Checking if restaking network is fully secure, i.e. has no allocation-individsible attack is co-NP-complete.

WB in a Symmetric Network?

def.9. Symmetric Network. is symmetric iff:

  1. All validators have equal total stake
  2. Stake of two validators to any service is same,
  3. All attack threshold are same

def.10.

Improvement

Q. from the application’s perspective, let’s try requiring a ceiling for restaking degree of a potential validator wanting to restake

  • services can dynammically join, then design
    • maybe consider adversaries, who dynamically add services
      • ¶ if the code is committee, and committee is evil ¶ malicious/backdoor in code ¶if rewards are given to validators