Closed mfinestone closed 5 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 1000000.0 LRC attached to it as part of the Loopring fund.
Issue Status: 1. Open 2. Cancelled
Work has been started.
These users each claimed they can complete the work by 2 years, 4 months ago. Please review their action plans below:
1) kris30pl has started work.
i want recive something i work and nothing 2) evertonmelo has started work.
I found an incompatibility between dependencies. I'll report it as an "issue." 3) reslake has started work.
0x71C7656EC7ab88b098defB751B7401B5f6d8976F 4) wew0011001 has started work.
I can help in security bug and i need most of financial. 5) davidbanu has started work.
Would love to take part in this bug bounty... 6) maskerwind has started work.
find and submit bugs find and submit bugs find and submit bugs find and submit bugs
Learn more on the Gitcoin Issue Details page.
Just FYI, i don't think we have permissions to set labels / add to projects
Just FYI, i don't think we have permissions to set labels / add to projects
That's fine without adding project/labels.
Is it still active?
@k06a The end date of the bug bounty is October 13.
According to my stats, only 1 participant submitted 1 issue for upgrading npm packages, which is not a bug at all. The other participants have no output.
Issue Status: 1. Open 2. Cancelled
The funding of 1000000.0 LRC (45940.0 USD @ $0.05/LRC) attached to this issue has been cancelled by the bounty submitter
Loopring has allocated up to 1,000,000 LRC for those who identify significant security issues in Loopring Protocol 3.0.
Background
Loopring is an orderbook-based DEX protocol. The 3.0 version scales by migrating most storage and computation off the Ethereum blockchain. User balances and order trading histories are maintained as part of an off-chain Merkle tree per DEX.
Requests, such as deposits, withdrawals, order cancellation, and trade settlements, are processed as batches to update the Merkle tree. For each batch, the DEX operators only need to publish a 32 bytes post-processing Merkle tree root to Ethereum - and then, asynchronously, provide a Zero-Knowledge proof to verify user balances and order trading histories have been updated strictly by the rules enforced by the protocol.
Thanks to SNARKs, Loopring can settle up to 660 trades per second. If the on-chain data-availability feature is enabled, Loopring can still settle 200 trades per second. We expect to implement a more efficient data compression solution to offer even higher throughput.
Features
The current beta release, v3beta2, supports the following features:
Bounty Rules
Performance enhancement suggestions are welcomed but do not qualify for bounties. We have many existing ideas on how to improve the throughput and/or lower the cost. That said, if your idea is truly inspiring and eventually gets adopted, we may still grant you some tokens at our discretion.
This bounty program is set up only for the Smart Contracts in v3beta2, circuits excluded. Bugs found in other versions don't qualify. The Design Doc is something you must read to understand the overall design and solidity code.
How to participate
Thanks! Looking forward to the community's help. Happy hunting!
Important Update:
When you identified a bug, please check if it has already been fixed on the master branch. If so, the bug is not valid for claiming a reward.