Compensation Scheme

Preamble

The Crosswise compensation scheme is a compromise that aims to be as fair as possible, prudent, yet practical. It is utilitarian in principle and therefore aims to provide the greatest benefit to the greatest number of people. The overall timeline errs on the side of caution.

Guiding our approach to fairness, is the assumption that the exploit was an unexpected and unfortunate event for everyone. Although many attempted to game and otherwise take advantage of the situation, we only penalize clear cases of abuse and treat the remainder as actions taken in distress. Thus our aim is to ensure nobody wins nor loses as a result of the exploit.

Our approach to ascertaining entitlements is limited by what we can do technically and the amount of time and resources we can reasonably dedicate to this task.

A snapshot is an accurate, yet necessarily blunt tool when it comes to evaluating entitlements. Nonetheless a return to a state prior or near the event is the only equitable basis for compensation, as it is accurate and comprehensive.

Dip buyers and sellers have been taken into consideration, as well as users that moved or sold liquidity.

Following the community vote that ended 27th April, the compensation scheme aims to re-instate the CRSS token amount users held prior to exploit. In cases where there is no direct equivalence, the price at time of exploit will be used to assess overall entitlement. The overall intention is for users to see their holdings reinstated to the time prior to exploit. As such nobody should lose nor benefit from the exploit. All compensation will be distributed in CRSS token.

Transparency & Reproducibility

Each and every step can be recreated by running the scripts provided in our compensation Github repository (https://github.com/crosswise-finance/crosswise-snapshot). No data was tampered with, every piece of information except dip buyers and sellers was taken directly from the blockchain or by using BSC Pro API service, ensuring 100% accuracy, precision and reproducibility of results. Dip buyers and sellers data was gathered from an external source which records and stores this information. As we are uncertain whether this external source data source is 100% secured against tampering, we will disclose it as soon as we restart the emission.

Distribution & Mechanics

• Compensation will be distributed via a Compensation Pool (CP).

• Only users that were affected by the exploit will have access to the CP.

• Users entitlements will be automatically added to the contract.

• For transparency and audit-ability users will be able to query the any wallet's compensation entitlement.

• Compensation has its own fixed emission amount of 0.35 CRSS per Block.

• Compensation is progressively paid out in proportion to your overall share of the CP.

• Similar to our regular pools, when claiming compensation, users will have the option to vest compensation over 5 months or pay the 25% Instant Claim fee.

• Compensation will take a total of one and a half years (1.5036666) for those that decide to vest throughout.

• Compensation will take a total of one year and 1 month (1.0870) for users that use the instant claim option throughout.

Example: How Is Compensation Paid Out? The compensation will be coming from block emissions. Meaning that as each block is mined, CRSS will be mined too.

Depending on how much CRSS you are entitled to, you get bits into your account as the emissions occur.

The compensation is spread over a year. Meaning that by the end of about a year, your entire entitlement would have been emitted.

As the compensation tokens are emitted and accumulate in your account, you are expected to claim them. At the point of claiming, you can either vest for 5 months or claim immediately by paying a fee of 25%. If you don't vest, and you are claiming 100 CRSS, you will only receive 75 CRSS. If you vest, at the end of 5 months, you will receive the 100 in full.

If you have 2400 tokens in compensation, that's about 200 CRSS emitted per month. If you claim monthly, you can vest 200 monthly or instant claim and get 150 CRSS.

You can claim daily. That's about 7 CRSS every day. Vest it or claim instantly by paying 25% tax.

Definitions

Reference Block (RB)

In our case the block chosen is the last block 14465247 prior to the first exploit transaction, which occurred at block number 14465248.

NAME	BLOCK	BLOCK TIME	CRSS PRICE IN BUSD
Reference	14465247	Jan 18 2022 06:07:59 AM UTC	1.2605653314300524
First Exploit	14465248	Jan 18 2022 06:08:02 AM UTC	0.5028251059642918

Block Before Exploit (BBE)

The block just prior to the first exploit transaction is block 14465247.

Price Before Exploit (PBE)

The CRSS token price just prior to the first exploit transaction. The price at BBE 14465247 was 1.2605653314300524 BUSD and derived from the CRSS-BUSD pool state, which contained 121004.672023137878940045 CRSS and 152534.294493431617799855 BUSD at the time. We therefore divide 152534.294493431617799855 by 121004.672023137878940045 to obtain 1.2605653314300524 BUSD

Blanket Compensation (BO)

This is the main component of the compensation scheme and includes everyone automatically, but excludes Illegitimate Claimants (ICs) and Project Wallets & Contracts (PWCs). Liquidity pair contracts will be compensated in order to restart the protocol with sufficient liquidity.

Illegitimate Claimants (ICs)

These are the attacker wallets and contracts, which we will exclude in order to prevent compensating them.

Project Wallets & Contracts (PWCs)

This includes the dev wallet and old contracts.

TYPE	ADDRESS
Dev Wallet	0x2A479056FaC97b62806cc740B11774E6598B1649
CRSS (Presale)	0x0999ba9aEA33DcA5B615fFc9F8f88D260eAB74F1
CRSS (V1)	0x55eCCd64324d35CB56F3d3e5b1544a9D18489f71
CRSS (V1.1)	0x99FEFBC5cA74cc740395D65D384EDD52Cb3088Bb
CRSS-Router	0x8B6e0Aa1E9363765Ea106fa42Fc665C691443b63
CRSS-Masterchef	0x70873211CB64c1D4EC027Ea63A399A7d07c4085B
xCRSS	0x27DF46ddd86D9b7afe3ED550941638172eB2e623
CRSS-BNB	0xb5d85cA38a9CbE63156a02650884D92A6e736DDC
CRSS-BUSD	0xB9B09264779733B8657b9B86970E3DB74561c237
BNB-BUSD	0x290E1ad05b4D906B1E65B41e689FC842C9962825
USDT-BUSD	0xef5be81A2B5441ff817Dc3C15FEF0950DD88b9bD
BNB-ETH	0x8151D70B5806E3C957d9deB8bbB01352482a4741
BNB-BTCB	0x9Ba0DcE71930E6593aB34A1EBc71C5CebEffDeAF
BNB-CAKE	0x0458498C2cCbBe4731048751896A052e2a5CC041
BNB-ADA	0xDE0356A496a8d492431b808c758ed5075Dd85040
BNB-DOT	0xCB7Ad3af3aE8d6A04ac8ECA9a77a95B2a72B06DE
BNB-LINK	0x278D7d1834E008864cfB247704cF34a171F39a2C
CRSS-USDT	0x21d398F619a7A97e0CAb6443fd76Ef702B6dCE8D
CRSS-LINK	0x16ff408bcdce1521db8edfecd7bcbb91689e5043
CRSS-DOT	0x206b9efc52a4e7ffa5a06165c8f975d84dbee6fc
CRSS-ADA	0x2c52ea643b861e8c1f9ebff52bc46cbfc102a6ff
CRSS-CAKE	0xcd2915cf8a4121e8efab77024eee8af4cd50afca
CRSS-BTCB	0xd313d1c6320e909e53467c239944edaf456328ae
CRSS-ETH	0xe04708a3d712162b2e08c2ecc35eb5c99139c526
BNB-USDT	0xfE04537629a3c94d74143f09633ade1d1127128d

Dip Buyers Compensation (DBC)

This component intends to provide some compensation for users that “bought the dip”, perhaps unaware of what had happened.

Compensation Pool (CP)

Users will be provided with compensation tokens to stake in the Compensation Pool in order to receive their CRSS compensation.

1. Baseline Snapshot

Our Baseline Snapshot (BS) provides us with with every holders holdings just prior to exploit. The aim is to re-instate the exact CRSS token amount. LP token value is calculated using the CRSS PBE of 1.26 BUSD.

Scope & Eligibility

Amounts held in CRSS and xCRSS, or LP tokens in their wallet or our farms and pools prior to exploit:

TOKEN	LOCATION	CONTRACT
CRSS (PRE-SALE)	Pre-sale Round 1	0xad3f5a4526fbed82a865d1baef14153488f86487
	Pre-sale Round 2	0x3DC2b7E5dc5274C2d603342E73D1d0A9DE96796A
	User Wallet
CRSS (V1.0)	User Wallet
CRSS (V1.1)	User Wallet
	Pools
xCRSS	User Wallet
NON-CRSS LP	User Wallet
	Farms
CRSS LP	User Wallet
	Farms

Baseline Snapshot Calculation

A more in-depth technical description of each step is available in the Snapshot Methodology.

Wallet Compensation

1. We use Binance Pro API’s “Get Historical BEP-20 Token Account Balance by ContractAddress & BlockNo” request to get BEP20 balances of all 2398 addresses in block 14465247 for all 15 tokens in scope.

Note to those who will want to run the scripts for themselves, this one takes 5h+ per timestamp as each run includes 35970 requests, with BSC API cap for Historical BEP20 at 2 requests/sec

BSC Pro API reference :https://docs.bscscan.com/api-endpoints/tokens

1. We record each different token type in wallet and their respective amounts for every user, then convert all LP tokens values to Equivalent Value In CRSS and add it to user CRSS/v1/v11 and xCRSS holdings to get TotalWalletCRSSAmount .

LPtoCRSS *= LP tokenAmount * LPtokenPrice / CRSStokenPrice

TotalWalletCRSSAmount = CRSSamount + CRSSv1Amount + CRSSv11Amount + XCRSS + LP1toCRSS + LP2toCRSS + LP3toCRSS + LP4toCRSS + LP5toCRSS + LP6toCRSS + LP7toCRSS + LP8toCRSS + LP9toCRSS + LP10toCRSS + LP11toCRSS + LP12toCRSS

USER WALLET BALANCES BEFORE EXPLOIT

ADDRESSES	1162
TOTAL CRSS TO BE REFUNDED	267157.7715691107
ADDRESSES WITH OVER 10000 CRSS	3
ADDRESSES WITH OVER 1000 CRSS	38
ADDRESSES WITH OVER 100 CRSS	252

Possible Token Types

1. CRSS/CRSSv1/CRSSv11

2. XCRSS

3. CRSS-BNB

4. CRSS-BUSD

5. BNB-BTCB

6. CRSS-USDC

7. BNB-ADA

8. BNB-BUSD

9. BNB-CAKE

10. BNB-DOT

11. BNB-ETH

12. BNB-LINK

Masterchef Staking & LP Farm Compensation

Using the deployed Masterchef smart contract, we collected all transactions logs filtered by deposit, withdraw and emergency withdraw function topic and all BEP20 token transfers from BNBChain, between block of its creation (14280384) to BBE (14465247).

There were a total of 11 different tokens involved in staking and farming, which were identified by checking each token address that participated in deposit or withdraw function calls.

We first separated token transfers by ingoing and outgoing, we extracted hashes from transaction logs, and then filtered token transfers with these hashes, which left us with only withdraw, deposit and emergency deposit token transfers.

These hash filtered ingoing and outgoing token transfers were then calculated for each user address. The token type is identified, and all ingoing (deposit) transfers are added up per token type. The same is done for all outgoing (withdraw) transfers for each token type, and the sums deducted from their respective deposit balances. Each token’s PBE was accounted for and used to convert to CRSS in order to get total TotalWalletCRSSAmount .

LPtoCRSS *= LP tokenAmount * LPtokenPrice / CRSStokenPrice

TotalWalletCRSSAmount = CRSSv11Amount + LP1toCRSS + LP2toCRSS + LP3toCRSS + LP4toCRSS + LP5toCRSS + LP6toCRSS + LP7toCRSS + LP8toCRSS + LP9toCRSS + LP10toCRSS

Out of the 12 possible LP tokens, only the 10 for which at least one transaction was recorded, were included.

A much more detailed description of the system behind staking compensation can be found in Compensation Methodology.

TOKEN	PBE
1 CRSS, CRSSV1, CRSSV1.1, XCRSS	1.2605653314300524 BUSD
1 CRSS-BNB	49.0989412475227 BUSD ($49.138220400520716)
1 CRSS-BUSD	2.2636182137109717 BUSD ($2.2654291082819404)
1 BNB-ADA	54.46800811397548 BUSD ($54.51158252046665)
1 BNB-BTCB	8901.826454288857 BUSD ($8908.947915452287)
1 BNB-BUSD	43.50208854030589 BUSD ($43.46731468855505)
1 BNB-CAKE	145.21530799063586 BUSD ($145.33148023702836)
1 BNB-DOT	218.63006958282182 BUSD ($218.80497363848806)
1 BNB-ETH	2447.916877692636 BUSD ($2449.8752111947897)
1 BNB-LINK	210.6534966967243 BUSD ($210.82201949408164)
1 USDC-BUSD	2.0000609617849574 BUSD ($2.0016610105543853)
1 CRSS-USDC	2.243276691477553 BUSD ($2.2450713128307345)

These prices were derived by collecting historic LP token supplies and their respective token balances BBE, which were calculated and merged into total pool value in BUSD. Total pool value in BUSD for each LP token was divided by its respective LP token supply, to get their PBE.

ADDRESSES	702
TOTAL CRSS TO BE REFUNDED	1602893.952216537

RECONSTRUCTED AMOUNTS LOCKED IN STAKING AND FARMS

Presale Compensation

This part was the simplest of all, done similarly to Staking Compensation, by reading blockchain information stored inside the two deployed presale smart contracts with Web3

1. We ran all the relevant view functions, most important being totalRewardAmount() and totalWithdrawedAmount(), for all addresses involved in the presale, which were stored inside the contracts.

2. We calculated CRSS owed for each user by deducting totalWithdrawedAmount() from user’s totalRewardAmount() to get total CRSS amount left inside the two smart contracts, all withdrawn amounts were covered in other parts of the compensation.

3. Any withdraws made from either of the two presale contracts after first exploit were added back to user’s presale compensation

The simplest way to independently check whether the presale component of your compensation is correct, is to head over to BSCScan, and run userDetail() view function with your address as input.

Presale Round 1: 0xAd3f5A4526fbEd82A865d1BaeF14153488f86487

Presale Round 2: 0x3DC2b7E5dc5274C2d603342E73D1d0A9DE96796A

PRESALE 1 ENTITLEMENT

PRESALE 2 ENTITLEMENT

	PRESALE ROUND 1	PRESALE ROUND 2
ADDRESSES	1082	647
TOTAL CRSS	2999999.5707433973	999999.8375834356
TOTAL WITHDRAWN	981171.6635363961	95796.43293209284
TOTAL CRSS OWED	2033890.536206996	906359.9760799137

2. Post-Exploit Swaps

This part of the compensation scheme is intended to make adjustments for holders that “bought the dip”, but also those that sold their CRSS.

Cut-Off Time for Eligibility

The eligible time frame has been set in reference to the timing of our communications detailed below. Given the confusion at the time, we have decided to consider transactions eligible all the way until the end of day on the 18th Jan 2022. Those that persisted in trading CRSS after this cut-off will not be compensated For those amounts.

DATE	COMMUNICATION	TELEGRAM	DISCORD
18 Jan 2022	“Exploit/Attack”	6:43 AM UTC	7:20 AM UTC
18 Jan 2022	“Stop Buying”	7:43 AM UTC	8:12 AM UTC
18 Jan 2022	“Trading Halted”	9:17 AM UTC	9:18 AM UTC

Dip Buyers Calculation

Timeframe

BUY CRSS	TOE to 24:00:00 UTC on 18th Jan 2022
SELL CRSS	TOE to last CRSS swap recorded on 22nd Mar 2022

Part A: Calculate the “Dip Buyers Balance” (DBB)

Here we assess the amounts of dip buys eligible for compensation.

1. We collected all CRSS Buy and Sell Amounts in USD we could find from an external source, which should include all CRSS pairs on our DEX, as well as PancakeSwap, Biswap and Apeswap. There is some room for inaccuracy here as the data could not be retrieved from a 100% reliable source, like a blockchain, but the vast majority of all dip buys and sells will be included.

2. sum up all CRSS Buys Amounts in USD per wallet and convert to CRSS Buys BUSD Price achieved at the time of swap. - from exploit to end of 18th

3. Collect all CRSS Sells Amounts in USD per wallet and convert to CRSS Sells BUSD Price achieved at the time of swap. - from exploit until last ever TX

4. Calculate total BUSD paid/earned per wallet

5. Calculate Dip Buyers total CRSS entitled by converting total BUSD value to CRSS using the PBE.

Part B: Applying the “Haircut”

Here we apply a 30% haircut to the entitlement to enhance sustainability.

1. Select only the wallets with a positive Dip Buyers total CRSS

2. Apply a 30% haircut only to wallets with positive balance multiplying by 0.7 to get the Dip Buyers CRSS Net Entitlement

Part C: Carrying Forward Negative Balances

The above calculations will result in numerous wallets with negative balances, as some people sold more than they bought during the dip.

1. Select only the wallets with negative Dip Buyers Balance

2. Save seperately as Dip Buyers Negative Balance Adjustment

3. Keep for use when calculating BC

Please note that due to limitations on data availability we were unable to include users that bought less than 99.39$ worth of CRSS between BBE and 7:35AM UTC. If you fall into this category, please send us a bug report with your transaction hash(s), and we will add them to your entitlement manually.

DIP BUYS TO BE COMPENSATED IN USD	77901.32610517349
DIP SELLS AMOUNT IN USD	380907.20302561787

DIP BUYS AND SELLS

3. Manual Adjustments

Hacked Wallet Replacements

Over the months, a number of users got in touch claiming they had fallen victim to wallet phishing attacks. Given that due to the exploit we had this extraordinary opportunity to help and were also eager to avoid distributing CRSS to hackers that would sell the token instantly, we offered users the opportunity to replace their hacked wallets.

In practice it is impossible to ascertain if a wallet has suffered such an attack, so instead we relied on a strong disincentive to prevent fraudulent claims. Users opted in to forgoing 50% of their entitlements, which is returned to the protocol and sent to the Marketing Wallet: 0x10E5Bd7DdE3894a1f99bc24ADeE4674772f3a3EA

Given the inherent dangers of allowing anonymous users to replace a given wallet, all wallet ownership was cross checked with presale submissions. Of the 30 unique submissions, only 8 provided a valid replacement wallet from the outset and 1 user later submitted a correction, and verified ownership via a micro transaction. All the other wallets were part of the presale and thus did not require further verification. 2 wallets had instead suffered a failed token conversion and are dealt with separately below.

These addresses, alongside their corresponding replacement addresses, are listed below. The script used to make these adjustments is manualAdjustments.js in the Github repository.

Included Wallets

ORIGINAL WALLET	REPLACEMENT WALLET	VERIFICATION
0x8aC458588444e4018ddB58b7F3080496F7986947	0x926C3b1271d07594B11C8FB28C99683801736300	Pre-sale
0x6d7ED0DA2ACaa2a047630Ea1741537b6f2181806	0x91E321BEddA63F8E04235a417828cB075B23b111	Pre-sale
0x60a69d2f9327543f7916f3974479F02EE561873E	0xBAa9B7B74DF9d446198d2e3C08f71Ad34539fC4D	Pre-sale
0x3355e761f7b3ba2c08aE0CE7b6C821122040ef0A	0x30a9BdF6c028242a26F99270168217E8a2B1145F	Pre-sale
0xd6b09f1d6b1f35c2ff09651c221663bce4993204	0x6740353b66F823C9d30AE96fc32566C3160804A3	Pre-sale
0xeBA0DB97eC85ef23049Af7E1270D7240DF4Bb59f	0xa622216e4Cf0f7A59c93c18B82bB5011ed5B9F51	Pre-sale
0xB8CE3fC4D0a60e9e28973D42435daC211b273b87	0x25747761965f2710FdA9851636F722268925c1A0	Pre-sale
0x9FF251fD3363632626E96CE5ccC82CEe6C80A732	0xe3fdc3fee7ea3c05aaba89c7d65b5351da400164	0xef4a6b734d86eb4de4b213a1b3f1e264b11fa8b6c15d8a53c438019311c6f549
0x975ab1f920059615dDbF3d08fa68962e10926295	0xbb3940aB8cf809f8cdc24080b838B95622eA9c89	Pre-sale

Users that failed to provide a replacement address or provided the same address as their original address, or an incompatible address were unfortunately not included in this process:

Excluded Wallets

ORIGINAL WALLET	REPLACEMENT WALLET
0xad95ea143748557b99dd5a54274551ef5eaf27d4	?
0xAEa3B43960c564A438e51C8Cc4867B6edC67BfE4	?
x4c9da991A9a91c161f3c194d617eD7016CDA611e	?
0x132a63728138d4C633F5E8375935594370308f05	0x132a63728138d4C633F5E8375935594370308f05
0xBBB73Aa47c398F35A7366A5864E2c873B9Cad1A7	0xBBB73Aa47c398F35A7366A5864E2c873B9Cad1A7
0xF0d22c98bb362AB8c38aE4098Ba9088C988ff52C	0xF0d22c98bb362AB8c38aE4098Ba9088C988ff52C
0xefcC5406D1354d668a25A418629Cd83c2d185aEA	0xefcC5406D1354d668a25A418629Cd83c2d185aEA
0x213Efa63571F3Bf3d4e4c457BB27ba09f730d596	0x213Efa63571F3Bf3d4e4c457BB27ba09f730d596
0x4f5B25AdB17E7BD4c48fbEDd7Bda4444072a14bd	?
0x5c335424d73BD1Ef1512106716063D2803744641	bnb1kznjq9aw5tkt36g0pdwum33h5wjx8undr5lgns
0x5DdB1F871CdF065D6AEFD467E895C1710BE263E5	0x5DdB1F871CdF065D6AEFD467E895C1710BE263E5
0xD055dd9B13945397618E17D73cd636b6C9A77D82	0xD055dd9B13945397618E17D73cd636b6C9A77D82
0xaBdBA2E2b22c036efDa11CD4c5388d15209eb425	0xaBdBA2E2b22c036efDa11CD4c5388d15209eb425
0x499E75E925Cd25a1aa4204548E8E2412501fDA4c	0x499E75E925Cd25a1aa4204548E8E2412501fDA4c
0x22057c79E4a9f2856a97C90b8A5D73B5fa14BA6c	0x22057c79E4a9f2856a97C90b8A5D73B5fa14BA6c
0xbD29a8BF1DA9EF93baD3be8AB5194b7344c2CD5E	0xbD29a8BF1DA9EF93baD3be8AB5194b7344c2CD5E
0x991b479aB68DE87B52c81cAea7D32c8D641e249b	0x991b479aB68DE87B52c81cAea7D32c8D641e249b
0xF84df2195382C3b6A08b841511300b6218873085	0xF84df2195382C3b6A08b841511300b6218873085

Failed V1 to V1.1 Token Conversions

Two users erroneously submitted their wallet for the Hacked Wallet Replacement Program. In fact these users experienced a loss of funds due to failed conversion of CRSS V1 to CRSS V1.1 after the exploiter had already minted max supply. This meant the contract couldn’t mint the required V1.1 tokens for them in exchange. These users will see their lost amount of CRSS added to their entitlement in full.

ACCOUNT	CRSS AMOUNT	TX HASH
0x4D473bC97aDF3B6bd48F28a80a495964Bd67e13b	105	0x17528c722e9cd2bc15bac51be6004056a8dbdedad4b8ecd94003a06adfd84f35
0x7BE73921626702D045B69E47bA029572b5d0f768	948.518	0xe48179a6f0994b7f252e2c359466bc47751222e9d2e4f7c126be72dbc7badbb2

Personal Debt Collateral

One user was in another business relationship with a member of the team. Due his outstanding debt he has agreed to his CRSS entitlement to be transferred to his creditor, until his debt is paid in full. A binding legal agreement was signed and is available upon request.

ORIGINAL WALLET	REPLACEMENT WALLET
0x2C61569026CA8DA02911fd991d2FF695C435D031	0xc1Aaf375DdDdE66Fa45794B63260A2E7a8BdeAbA

Extracting Residual Contract Value

In order to ensure we don’t distribute compensation to our old contracts, we exclude any that hold tokens. All recovered balances will be allocated to the new dev wallet to be used for liquidity.

DESCRIPTION	CONTRACT
CRSS V1.1 Token Contract	0x99fefbc5ca74cc740395d65d384edd52cb3088bb
CRSS-BNB Pair Contract	0xb5d85cA38a9CbE63156a02650884D92A6e736DDC
CRSS-BUSD Pair Contract	0xB9B09264779733B8657b9B86970E3DB74561c237
CRSS-USDC Pair Contract	0x21d398F619a7A97e0CAb6443fd76Ef702B6dCE8D
CRSS-BNB PancakeSwap Pair Contract	0x9cbed1220E01F457772cEe3AAd8B94A142fc975F
CRSS-BNB Biswap Pair Contract	0x73C02124d38538146aE2D807a3F119A0fAd3209c

Post Consultation Adjustments

Our community of users was given a week starting from Monday 26th September until Tuesday 4th October 2022 to report any discrepancies between expected and actual entitlements.

Overall only 1 legitimate issue was found. In addition there were 2 late submission to the Hacked Wallet Replacement Program, as well as 1 correction. Every user received an email and/or Dirrect Message in Telegram or Discord, with a short explanation. All changes resulting from this consultation have been added below:

ACTION	REASON	VERIFICATION
REPLACED 0x84d9dbd0fb282f3884bb663fe4febbceb046440b WITH 0xc5DD37bcfb33a3Cc03b909038400E5Bf5CbbeFFB	Hacked Wallet Replacement - late submission	0x120295f40a0c77ceae62f98c5625ff4999757bb66d7418ca303408e9321d81cd
REPLACED 0xCDE6F2942734b7895C1F2424724A563199076B3d WITH 0x270AE84f36Eb11f205A4D42F764C12443470f683	Hacked Wallet Replacement - late submission	seed provided and verified
REPLACED 0xD3137741763cc0eeAD8cf7b3BCF9e895B61BfB51 WITH 0xF3DC05E6E11E37530d4612182EFB397e491bD8B1	Hacked Wallet Replacement - previoiusly submitted but excluded	none required as part of presale
ADDED 59.22 CRSS TO 0xD4105c56dCd0497B3b220Eb2Fc88022465717a2f CRSS OWED	User performed dip buy that was below the threshold of data retention of our data source.	none required as part of presale

Exceptional Handling of Project Wallet

The old “Dev” wallet will be replaced. It will receive instant compensation to ensure sufficient liquidity, without having to mint more tokens for launch.

ORIGINAL WALLET	REPLACEMENT WALLET
0x2A479056FaC97b62806cc740B11774E6598B1649	0xb96235f423Fb407b5f9c3A227de86B2A5057A656

Excluding Attacker Wallets

All known attacker wallets will be excluded from the compensation scheme.

ADDRESS	TRANSACTION HASH	CONTRACT
0xeE608a79adaF1C4Fc1415092896D58471Ef28480	0x43034be028cfb73d0b47f7961b97cd3a828a7cc47d3831a247ad90682627df46
0x748346113b6d61870aa0961c6d3fb38742fc5089	0xd02e444d0ef7ff063e3c2cecceba67eae832acf3f9cf817733af9139145f479b
	0x5142704d825b32b724cb868c694d683a0d1b1835c08d2beb62638d9714fbdea1
	0x5689ce511bfa5fe6c2fa1c7db1efec1463684c6241ccd35b1dc60231f361897a
	0xf6dac23c1ca72a826007804effbbeb073e13100370b33f18c65dad92bdb00d98
0x530B338261F8686e49403D1b5264E7a1E169F06b	0xd02e444d0ef7ff063e3c2cecceba67eae832acf3f9cf817733af9139145f479b	Yes
0x5aa2b981463D35724676aC7Fd399d3043a3F4299	0x43034be028cfb73d0b47f7961b97cd3a828a7cc47d3831a247ad90682627df46	Yes
0xfD3002cE12D81c4e5F62B97F3c72f18122291A65	0x5bc5cdcbd01e2f567b134d9fed75e924811a74b199b300f40aaf1b543b10f1e2
0x22216a348647a297089970dfad28064baBF01495	0x5bc5cdcbd01e2f567b134d9fed75e924811a74b199b300f40aaf1b543b10f1e2
0xCd35552932af41714480f436Ac8cbA2F14890CdE	0x4e5212778eabb652cfd6e5e78e109b493e1e010ba98bdab788a99bb71202f4e1
0x16d8DF4E23a21e54CdB9E32cc878Df9f5d48d44E	0xd5507c29e94d2d03718177f5a5b7e8fe1b808ecb6e03f21171e3c62ab954fc9e
0x2d515004a2D8D93ACFcEe39E157BCF4290b73809	0x643a7db5db24c665e8cd014e831913891457c993cb3a33b81727d8e2006acadd
0x9618Ce1Cf75F0D9090325Ba4C26a0e782F4Ea7Ad	0xb908a5c5eab1b1799e6d9e142495d363aa686c8f03ea20bcefeccdc7e4a526a0
0xdC945BeA36371D3c72E5E7FB2e07D20D178FE751	0xb908a5c5eab1b1799e6d9e142495d363aa686c8f03ea20bcefeccdc7e4a526a0	Yes
0x4c4a3c0f7bbc623ed9d694b4616da8722c8f210c	0x13faee56649821d7a01703309d8bc6cd53ad22ec6de1f9e696c9137f559e6bdd	Yes
0xc24f9D5C5D53AA69B2911dB8b2cDA3528d03b71e	0xd55ba30dcd2e0efd8e6c1c04fc50bbc699fc1f02e2cf5104e67287356ebe4671
0x60Ac04C1019558ca8536fA314AEAe9e6e1a2ae67	0xb7d110ad35d0d1bb3e38d4e8a1572aaf62a000ecfb97b02d57c9a2c845fe124a

Bonus sCRSS

In order to thank our community and also remedy some dissatisfaction that is likely to arise from a necessarily imperfect solution, we have decided to airdrop a modest amount of our upcoming stakeholder/governance token, sCRSS, to holders that held CRSS prior to exploit. This is not intended as part and parcel of the compensation, but rather as a small gesture of gratitude for the support that many in our community have shown during these testing times. Distribution will happen once sCRSS is launched.

Total Compensation

UNIQUE ADDRESSES INCLUDED	3186
TOTAL CRSS TO BE COMPENSATED	5111110.238318922 (liquidity reserves included)
AVERAGE CRSS COMPENSATION AMOUNT	1498.7720231388303
MEDIAN CRSS COMPENSATION AMOUNT (only included addresses with 1 or more CRSS)	333.8418619
ADDRESSES WITH MORE THAN 10k CRSS COMPENSATION	82
ADDRESSES WITH MORE THAN 1k CRSS COMPENSATION	627
ADDRESSES WITH MORE THAN 100 CRSS COMPENSATION	1500

Lookup Total Compensation Entitlement

Your entitlement is broken down into the various "locations" where you may have held tokens, as defined in Scope & Eligibility. "Total CRSS Owed" is the total tokens you will receive as part of compensation.

We have removed the last 5 characters of all wallet addresses to preserve privacy. When searching for your wallet in the list, please ensure you have deleted at least the last 5 characters or you won't find your wallet!

TOTAL PRELIMINARY COMPENSATION ENTITLEMENTS

FINAL COMPENSATION ENTITLEMENTS