feature-sh / smart-contract

FEATURE 🏗️ smart contract ♦︎

FEATURE

Getting Started

cp .env-sample .env
npx hardhat test test/feature.js
npx hardhat test test/feature-erc20.js

Deploy

Feature

npx hardhat run scripts/feature-deploy.js --network <network>

Centralized Arbitrator

npx hardhat run scripts/centralized-appealable-arbitrator-deploy.js --network <network>

Etherscan Verification

npx hardhat clean
npx hardhat verify --network <network> <smart contract address> <Argument1...>

Run Test with event logs

npx hardhat test --logs

smart-contract's Issues

Add protocol to deploy to the README

Explain the different steps to deploy the smart contract FEATURE to a chain like :

• change chain constants
• execute initialize function...

Explain this works in a file like ./DEPLOY.md .

Change token ERC20Mock with FeatureToken

$feat with 500 FEAT rewards (xdai)

Add smart contract deployed addresses comment

In https://github.com/feature-sh/smart-contract/blob/main/contracts/Feature.sol and https://github.com/feature-sh/smart-contract/blob/main/contracts/FeatureERC20.sol, add deployed addresses (gnosischain, polygon, arbitrum one, mumbai, goerli) with this format * @deployments: [<network 1>: <smart contract address 1>, <network 2>: <smart contract address 2>, ...] .

Exemple:@deployments: [gnosischain: 0x3a6Cf1a7DD424f300df1c519156c71CAD1947Fbb].

$feat sell 10k this month for 100 ALA (goerli)

specs

Deploy smart contract version 2.4.1 Arbitrum network

Redolve xith tasks:

• Fund the Manager Feature account to deploy smart-contract Feature/FeatureERC20 v2.4.1.

$CI: add Github Action workflow to run the tests 30XDAI (xdai)

See Github Actions .

test: add assertion for a multiple claim on the same deal

Add this assertion: Should give the amount of the first claimer who claim in multiple successful claims.

Create a scenario with 2 claimers, then the first claimer will get the reward.

Create t to add the XDai courts

See specs on https://forum.kleros.io/t/kip-development-courts-on-xdai/735/17

Add smart contract deployed addresses comment

In https://github.com/feature-sh/smart-contract/blob/main/contracts/Feature.sol and https://github.com/feature-sh/smart-contract/blob/main/contracts/FeatureERC20.sol, add deployed addresses (gnosischain, polygon, arbitrum one, mumbai, goerli) with this format * @deployments: [<network 1>: <smart contract address 1>, <network 2>: <smart contract address 2>...] .

Exemple:@deployments: [gnosischain: 0x3a6Cf1a7DD424f300df1c519156c71CAD1947Fbb].

Arbitration test with Kleros inconclusive

Since the referee's draw is carried out by Kleros, the simulations remain correct but do not cover all scenarios.
Here are the tx statements concerning the two arbitrations carried out with Kleros:

Dispute Kleros 140

Smart-contract FeatureERC20

• https://gnosisscan.io/address/0x62b286a93d6f720a654745a3451f71cf71481b81
  Github:
• #31
  Transaction: 324
• https://gnosisscan.io/tx/0xcbe5ede439b5d387a797bba02b7a1c32568902a255c76513b12fbd0b87c68018
  Claim: 217
• https://gnosisscan.io/tx/0xc7b93c777ef00c463961143c9a75f98481c658eb21b1fb7184d85623f5dffa5a
  Challenge: 140
• https://gnosisscan.io/tx/0x139ce74682117f34f331eec531e899959704247a3f28ba743bb86b7fccecbd23
  ✅ Payment Kleros: Dispute 140 (challenger win)
• https://gnosisscan.io/tx/0xd77160821763f0f74f62da952600dcd14c739dbaa6dbef8c9b0726b4e8d76a54

-> TRANSFER  30 xDAI From 0x9c1da9a04925bdfdedf0f6421bc7eea8305f9002 To  0x4dff727fd5002dad7e028c6987c394f1913c2137
-> TRANSFER  30.0001 xDAI From 0x62b286a93d6f720a654745a3451f71cf71481b81 To  0x06255fa39ebd18796ecccc17db8153ef58dba0a8

✅ Payment:

• https://gnosisscan.io/tx/0x2f39d04ec352978f3b66bff5f4c9a72624fc7764d94e5e9a70c1244498ba385f

Dispute Kleros 143

Smart-contract FeatureERC20:

• https://gnosisscan.io/address/0xce9260c08272fa39c9af1307cd079dc5636bee01
  Github:
• #34
  Transaction: 7
• https://gnosisscan.io/tx/0xc5aeb84a0128062d2f8934830fec8127ff3158c2d14054979f55f09ae0fddc39
  Claim: 5
• https://gnosisscan.io/tx/0xc05540d5019915d1933da2c103f5d264935c7611c94e7295c37529090bea3011
  Challenge: 143
• https://gnosisscan.io/tx/0xd77043717fb77c74cf8e17fe3ed6245478ebdacccc8256eb127ecab32e667ac8
  ✅ Payment Kleros: Dispute 143
• https://gnosisscan.io/tx/0x7cd2e9084e6bee4e267d77f6fc2f5121164683dad97d00852cec8303b7b53bf6

-> Although one or more Error Occurred [Out of gas] Contract Execution Completed
-> TRANSFER  30.0001 xDAI From 0xce9260c08272fa39c9af1307cd079dc5636bee01 To  0x06255fa39ebd18796ecccc17db8153ef58dba0a8

❌Payment:

• https://gnosisscan.io/tx/0xdee2d2374ffff50c96949c55113d9607c24a9ae90de722e339903269bada6f21

Also an error occurred during a payment, its origin has not been determined, and the court's rendering is not fully understood:

Try to explain the origin of the problem and demonstrate the validity of the arbitration with the use of the FeatureERC20 smart-contract.

Add smart contract deployed addresses comment

In https://github.com/feature-sh/smart-contract/blob/main/contracts/Feature.sol and https://github.com/feature-sh/smart-contract/blob/main/contracts/FeatureERC20.sol, add deployed addresses (gnosischain, polygon, arbitrum one, mumbai, goerli) with this format * @deployments: [<network 1>: <smart contract address 1>, <network 2>: <smart contract address 2>, ...] .

Exemple:@deployments: [gnosischain: 0x3a6Cf1a7DD424f300df1c519156c71CAD1947Fbb].

Deploy smart contract version `2.4.1`

Changes

• #36

Networks

Mainnets

• Gnosis chain
• Polygon
• [ ] Arbitrum
• Celo
• Binance

Testnets

• [ ] Goerli
• Sepolia
• Mumbai
• Alfajores

Mainnets (dev mode)

• Gnosis chain
• Polygon
• [ ] Arbitrum
• Celo
• Binance

Add smart contract deployed addresses comment

In https://github.com/feature-sh/smart-contract/blob/main/contracts/Feature.sol and https://github.com/feature-sh/smart-contract/blob/main/contracts/FeatureERC20.sol, add deployed addresses (gnosischain, polygon, arbitrum one, mumbai, goerli) with this format * @deployments: [<network 1>: <smart contract address 1>, <network 2>: <smart contract address 2>...] .

Exemple:@deployments: [gnosischain: 0x3a6Cf1a7DD424f300df1c519156c71CAD1947Fbb].

Add smart contract deployed addresses comment

In https://github.com/feature-sh/smart-contract/blob/main/contracts/Feature.sol and https://github.com/feature-sh/smart-contract/blob/main/contracts/FeatureERC20.sol, add deployed addresses (gnosischain, polygon, arbitrum one, mumbai, goerli) with this format * @deployments: [<network 1>: <smart contract address 1>, <network 2>: <smart contract address 2>, ...] .

Exemple:@deployments: [gnosischain: 0x3a6Cf1a7DD424f300df1c519156c71CAD1947Fbb].

$feat: add a simple CentralizedArbitrator ERC20 without appeal 50XDAI (Xdai)

Check the difference between feature.sol and featureERC20.sol to add tokens of the CentralizedArbitrator.sol.

Add tests.

feat: add meta evidence in the Transaction struct

It's bad in term of gas but easier to handle, audit and debug in particular for the logic relative to the RPC provider.

Note: Gas optimisation is not a priority because we use a L2.

Feat: complete the smart-contract with a user's proof of work for a claim WIP

To migrate data from clever-cloud to aws (production), the public sql schema will change to the feature schema.

The change of host, db and schema should happen for the beginning of the v2 release.

Older versions will be deployed with branches in their respective repo marked with tags.

Here are the dependencies to build v2:

with feature schema
- dapp pr#148 https://github.com/feature-sh/app/pull/148
- bot pr#193 https://github.com/feature-sh/bot/pull/193
- dashboard pr#610 https://github.com/feature-sh/dashboard/pull/610
- premium-subscription-monitor pr#3 https://github.com/feature-sh/premium-subscription-monitor/pull/3
- monitor-block -> ok

with smart-contract v2
- smart-contract pr#24 https://github.com/feature-sh/smart-contract/pull/24 (without feature schema)
- dapp pr#147 https://github.com/feature-sh/app/pull/147 (without feature schema)
- bot pr#197 https://github.com/feature-sh/bot/pull/197 (with feature schema)

refacto: clean indentation of the smart contracts

By convention, the interval of solidity is 4 spaces.

See OpenZepplin smart contract as reference: OZ .

Fix: deployments of version 2.1.0 of Feature and FeatureERC20 smart contracts

See the modifications of smart contracts:

• #32
  See the modifications of Monitor:
• https://github.com/feature-sh/monitor/pull/314
  See the modifications of Monitor-blocks:
• https://github.com/feature-sh/monitor-block/commit/689bd9d939260fbfad1ea90e39aa54f0c066f7a1

Mainnet

• Update on the Gnosis Chain.
• Update on the Polygon.
• Update on the Arbitrum One.
• Update Dune Analytics for Gnosis Chain.

Testnet

• Update on the Goerli.
• Update on the Mumbai.

Bot

• Update all production environment variables on Testnet networks.
• Update all development environment variables on Mainnet networks.

Monitors v2 or Monitors-block

• Update all production environment variables on Testnet networks.
• Update all development environment variables on Mainnet networks.

feat: deploy the new contract on Gnosis Chain

Add smart contract deployed addresses comment

In https://github.com/feature-sh/smart-contract/blob/main/contracts/Feature.sol and https://github.com/feature-sh/smart-contract/blob/main/contracts/FeatureERC20.sol, add deployed addresses (gnosischain, polygon, arbitrum one, mumbai, goerli) with this format * @deployments: [<network 1>: <smart contract address 1>, <network 2>: <smart contract address 2>, ...] .

Exemple:@deployments: [gnosischain: 0x3a6Cf1a7DD424f300df1c519156c71CAD1947Fbb].