code.vegaprotocol.io/vega@v0.79.0/core/integration/features/rewards/0056-REWA-106.feature (about) 1 Feature: Team Rewards 2 3 Background: 4 5 # Initialise the network 6 Given time is updated to "2023-01-01T00:00:00Z" 7 And the average block duration is "1" 8 And the following network parameters are set: 9 | name | value | 10 | market.fee.factors.makerFee | 0.001 | 11 | network.markPriceUpdateMaximumFrequency | 0s | 12 | market.auction.minimumDuration | 1 | 13 | validators.epoch.length | 60s | 14 | limits.markets.maxPeggedOrders | 4 | 15 | referralProgram.minStakedVegaTokens | 0 | 16 17 # Initialise the markets 18 And the following assets are registered: 19 | id | decimal places | quantum | 20 | USD-1-10 | 1 | 10 | 21 And the markets: 22 | id | quote name | asset | risk model | margin calculator | auction duration | fees | price monitoring | data source config | linear slippage factor | quadratic slippage factor | sla params | decimal places | position decimal places | 23 | ETH/USD-1-10 | ETH | USD-1-10 | default-log-normal-risk-model | default-margin-calculator | 1 | default-none | default-none | default-eth-for-future | 1e-3 | 0 | default-futures | 0 | 0 | 24 25 # Initialise the parties 26 Given the parties deposit on asset's general account the following amount: 27 | party | asset | amount | 28 | lpprov | USD-1-10 | 10000000000 | 29 | aux1 | USD-1-10 | 10000000 | 30 | aux2 | USD-1-10 | 10000000 | 31 | aux3 | USD-1-10 | 10000000000 | 32 | a3c024b4e23230c89884a54a813b1ecb4cb0f827a38641c66eeca466da6b2ddf | USD-1-10 | 10000000000 | 33 34 # Exit opening auctions 35 Given the parties submit the following liquidity provision: 36 | id | party | market id | commitment amount | fee | lp type | 37 | lp1 | lpprov | ETH/USD-1-10 | 1000000 | 0.01 | submission | 38 And the parties place the following pegged iceberg orders: 39 | party | market id | peak size | minimum visible size | side | pegged reference | volume | offset | 40 | lpprov | ETH/USD-1-10 | 5000 | 1000 | buy | BID | 10000 | 1 | 41 | lpprov | ETH/USD-1-10 | 5000 | 1000 | sell | ASK | 10000 | 1 | 42 When the parties place the following orders: 43 | party | market id | side | volume | price | resulting trades | type | tif | 44 | aux1 | ETH/USD-1-10 | buy | 1 | 990 | 0 | TYPE_LIMIT | TIF_GTC | 45 | aux1 | ETH/USD-1-10 | buy | 1 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 46 | aux2 | ETH/USD-1-10 | sell | 1 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 47 | aux2 | ETH/USD-1-10 | sell | 1 | 1100 | 0 | TYPE_LIMIT | TIF_GTC | 48 And the opening auction period ends for market "ETH/USD-1-10" 49 When the network moves ahead "1" blocks 50 And the trading mode should be "TRADING_MODE_CONTINUOUS" for the market "ETH/USD-1-10" 51 52 # Create the teams 53 Given the following teams with referees are created: 54 | referrer | prefix | code | team name | referees | balance | asset | 55 | referrer1 | ref1 | referral-code-1 | team1 | 20 | 10000000 | USD-1-10 | 56 | referrer2 | ref2 | referral-code-2 | team2 | 10 | 10000000 | USD-1-10 | 57 58 @TeamStep 59 Scenario: 0056-REWA-106 the top N % determines the rewards 60 61 Given the parties submit the following recurring transfers: 62 | id | from | from_account_type | to | to_account_type | entity_scope | teams | ntop | asset | amount | start_epoch | end_epoch | factor | metric | metric_asset | markets | 63 | 1 | a3c024b4e23230c89884a54a813b1ecb4cb0f827a38641c66eeca466da6b2ddf | ACCOUNT_TYPE_GENERAL | 0000000000000000000000000000000000000000000000000000000000000000 | ACCOUNT_TYPE_REWARD_MAKER_PAID_FEES | TEAMS | team1,team2 | 0.2 | USD-1-10 | 10000 | 1 | | 1 | DISPATCH_METRIC_MAKER_FEES_PAID | USD-1-10 | ETH/USD-1-10 | 64 ## Bunch of orders: 65 # Team1: 20, 10, 10, 10, 1 (out of 20) 66 # Team2: 21, 19, 10, 5 (out of 10) 67 # TopN 0.2 should be based on 50/4 and 40/2 -> 12.5 and 20 68 # This is then divided between 5 parties in team1, 4 in team2 respectively, 69 # so team1 parties receive 12.5/5 (or 2.5), whereas team2 referees receive 20/4 (or 5) 70 # We expect to see the vesting account balances of team2 to be 2x those of team1 71 And the parties place the following orders: 72 | party | market id | side | volume | price | resulting trades | type | tif | 73 | aux1 | ETH/USD-1-10 | sell | 10 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 74 | ref1-0001 | ETH/USD-1-10 | buy | 10 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 75 | aux3 | ETH/USD-1-10 | sell | 10 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 76 | ref1-0002 | ETH/USD-1-10 | buy | 10 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 77 | aux3 | ETH/USD-1-10 | sell | 10 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 78 | ref1-0003 | ETH/USD-1-10 | buy | 10 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 79 | aux3 | ETH/USD-1-10 | sell | 20 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 80 | ref1-0004 | ETH/USD-1-10 | buy | 20 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 81 | aux3 | ETH/USD-1-10 | sell | 1 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 82 | ref1-0005 | ETH/USD-1-10 | buy | 1 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 83 | aux1 | ETH/USD-1-10 | sell | 21 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 84 | ref2-0001 | ETH/USD-1-10 | buy | 21 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 85 | aux1 | ETH/USD-1-10 | sell | 5 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 86 | ref2-0002 | ETH/USD-1-10 | buy | 5 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 87 | aux1 | ETH/USD-1-10 | sell | 19 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 88 | ref2-0003 | ETH/USD-1-10 | buy | 19 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 89 | aux1 | ETH/USD-1-10 | sell | 10 | 1000 | 0 | TYPE_LIMIT | TIF_GTC | 90 | ref2-0004 | ETH/USD-1-10 | buy | 10 | 1000 | 1 | TYPE_LIMIT | TIF_GTC | 91 When the network moves ahead "1" epochs 92 Then parties should have the following vesting account balances: 93 | party | asset | balance | 94 | ref1-0001 | USD-1-10 | 769 | 95 | ref1-0002 | USD-1-10 | 769 | 96 | ref1-0003 | USD-1-10 | 769 | 97 | ref1-0004 | USD-1-10 | 769 | 98 | ref1-0005 | USD-1-10 | 769 | 99 | ref1-0006 | USD-1-10 | 0 | 100 | ref2-0001 | USD-1-10 | 1538 | 101 | ref2-0002 | USD-1-10 | 1538 | 102 | ref2-0003 | USD-1-10 | 1538 | 103 | ref2-0004 | USD-1-10 | 1538 | 104 | ref2-0005 | USD-1-10 | 0 | 105 #And "ref1-0002" should have vesting account balance of "0" for asset "USD-1-10"