WINR Protocol
- Completed (2)
Project Information
Description
The WINR Protocol pioneers the transition of e-gaming to web3 by providing smart contract tools, a liquidity engine, and an incentive framework to builders. View their documentation here.
-
Commissioned
12 Feb 2023
Completed
12 Mar 2023
Contracts Audited
Vesting 0x6Ed34c4D56B82A76e6540B7Cc2d35000873E1dd6 Winr 0xD77B108d4f6cefaa0Cae9506A934e825BEccA46E VestedWinr 0x63097e97ba51b64547cf1f4ba154495d7af74582 DateTime Dependency RoleBasedAccessControl Not used Governable Not used When using this protocol, the main risks you want to look out for are:
1. Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
2. Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.View Audit Report
IssuesRisk SummaryFound Resolved Partially Resolved Acknowledged
(no change made)High
0 – – – Medium
1 1 – – Low
10 8 1 1 Informational
15 14 1 – Total 26 23 2 1 When using this protocol, the main risks you want to look out for are:
- Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
- Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.
-
Commissioned
12 Feb 2023
Completed
26 Apr 2023
Contracts Audited
GensisWLPStaking 0xc885b641CB11CE2B38a7C28b79318C4B89cf04f9 When using this protocol, the main risks you want to look out for are:
1. Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
2. Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.View Audit Report
IssuesRisk SummaryTH Found Resolved Partially Resolved Acknowledged
(no change made)High
5 5 – – Medium
0 – – – Low
4 3 – 1 Informational
3 1 1 1 Total 12 9 1 2 When using this protocol, the main risks you want to look out for are:
- Ensuring that the contracts you are interacting with matches the one we audited. This can be done by comparing the addresses with the one present in the contracts page in our audit.
- Our audits only cover code-related risks. Users will have to do their own due diligence on other aspects of the protocol such as the reputation of the team, the protocol’s tokenomics, and other aspects of the project that might be relevant.