Explore ways to split Court into multiple contracts about aragon-court HOT 3 CLOSED

Related comment: #6 (comment)

from aragon-court.

Update on this. Right now is an important issue, as the contract exceeds the maximum size allowed by EIP-170.
I have explored several strategies to reduce its size, right now what seems to make more sense and be more effective is to split Commit-Reveal voting (bbranch split_voting) and SumTree (branch split_sumtree).

I attach here some tools I have used for analyzing this.

• Function calls graph generated wih surya:
• Disassembled bytecode generated with ethervm and with some function entry points sprinkled.
• Spreadsheet with estimations of most functions size.

Court_analysis.tar.gz

Right now the current size came down from more than 26k to ~21.5k bytes, so it's under EIP requirement but there's no much margin left.

npx truffle compile > /dev/null && cat build/contracts/Court.json | jq '.bytecode' | wc -m | xargs -I {} echo "{} / 2 - 1" | bc
21524

from aragon-court.

Closing this since we already implemented many paths to split the old Court logic in different contracts.

from aragon-court.