September Demo

[jaybuidl]

Goal

1. To demonstrate the functioning of the v2 court for the resolution of a dispute originating from a new Tag Registry on Arbitrum, and the associated cost savings.
2. To demonstrate the new user experience offered by the new front-end.

Scenario

• John, Joe and Jimmy stake some PNK, hoping to be drawn as jurors.
• Tom wants to tag some contracts, he uses the Tags Registry on Arbitrum to submit several tags.
• Charles disagrees with a tag and challenges it.
• A dispute is created: John, Joe and Jimmy are likely drawn
• Tom and Charles submit evidence to support their claims.
• The dispute resolves (keep the appeal period short for the demo).
• John, Joe and Jimmy get rewarded or penalized for their voting.
• The tag registry enforces the court decision

Scope

Arbitrator

PNK staking ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Staking #256
• Court Actions Bot #247 (delayed stakes)

Dispute creation ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84

Dispute appeal ❓

⚠️ Arbitrable frontend needs changes.

• Smart contracts
• Subgraph for the court on Arbitrum #84

Juror drawing ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Staking #256
• Court Actions Bot #247
• Court Notification Service (backend) #248 "you have been drawn"

Evidence submission ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Evidence Display & Submission tab #259
• Court Notification Service (backend) #248 "New evidence submitted for a dispute"
• Data: bot for evidence pinning on IPFS #254

Juror voting ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Binary voting tab #260
• Verdict (summary) #274
• Voting History #275
• Court Actions Bot #247
• Court Notification Service (backend) #248 "time to vote"

Juror commit/reveal voting ❌

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Court Front-End #250
• Court Actions Bot #247
• Court Notification Service (backend) #248 "time to commit (or reveal) your vote"

Phases automation ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Court Actions Bot #247

Dispute periods automation ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Court Actions Bot #247
• Court Notification Service (backend) #248 "dispute has entered phase X"

Token and ETH redistribution ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Profile #263
• Stats + Gamification #264
• Court Actions Bot #247
• Court Notification Service (backend) #248 "you have won/lost some PNK and ETH"

Ruling execution ✅

• Smart contracts
• Subgraph for the court on Arbitrum #84
• Court Actions Bot #247

Others

• PolicyRegistry migration and deployment #283
• Populate the Policy Registry (scripting) #290
• Populate the Subcourts with the same hierarchy and parameters as V1 (scripting) #294

---

Arbitrable

Curate Tag Registry (plan A) ✅

• Deployment on Arbitrum Rinkeby tcr#62
• Deployment to Arbitrum Rinkeby gtcr-subgraph#16
• Deployment on Arbitrum Rinkeby gtcr-injected-uis#6
• Support for Arbitrum Rinkeby gtcr#255
• Support for the arbitrator v2 gtcr#256
• Support for Curate on Arbitrum Rinkeby gtcr-action-bot#19

Features:

• Submission of a new tag ✅
• Challenge of a pending tag ✅
• Execution of the arbitrator's ruling ✅
• Appeal ❌

Dispute Resolver (plan B) ✅

• Dispute Resolver arbitrable proxy migrated to v2 #96
• Support for dispute creation on the court v2 on Arbitrum dispute-resolver#125

---

Fast Bridge❓

⚠️ Likely not enough time to bot it, demo it later.

• Smart contracts
• feat: Subgraph for the Fast Bridge Sender (Arbitrum Rinkeby) #219
• feat: Subgraph for the VeaOutbox vea#35

Fast Bridge Automation

Either one of these:

• Validator CLI - Implementation A (Typescript) vea#41
• Simple Fast Bridge Frontend

Features

• Dispute creation from L1
• Ruling execution to L1