Contest proposal: Free TON wallet as a Chrome extension
- Submission: 01 March, 2021 - 23:59 UTC 21 March, 2021
- Voting: 21 March, 2021 - 23:59 UTC 28 March, 2021
Mobile apps are used by many and existing wallets (well, some are not just wallets) in Free TON cover this market pretty good. There is still plenty of room for desktop applications. And this contest aims to cover one of the options of working with your tokens on desktop computers - Chrome extensions.
Wallet as an extension is not just a wallet, it’s a communicator that lets the user connect with web-sites. You want to easily buy something in the eshop? Planning to spend some time rolling dice? Want to post some messages on the forum that supports login with your wallet address? All in all, a properly built extension gives numerous options to introduce blockchain to the day-to-day Internet.
To offer the community handy wallet-as-extension to be used on desktop computers. All the code should be fully open-sourced to offer all the interested parties in joining forces on building the best Chrome extension to be used in Free TON.
- Browser: Chrome
- Language: English with translation-friendly architecture
- Mainnet and testnet support
- Creating and using existing wallets
- Contract support: TON Surf contracts, others as a plus
- Multi-account support
- Security: private and public keys are stored locally only
- Sending tokens upon confirmation only
Interface for Free TON blockchain to communicate with websites through the extension:
- Deploy of the contract
- Call contract methods with user’s keys
- Ability to send tokens from contract of user wallet with specified sum, payload and bounce
- Current net request, address, pubkey and balance
- All the methods that use the user’s secret key must ask for confirmation.
Any additional features - a plus!
Submission format and requirements
- GitHub repository
- Open-source license
- Original code - no more than 10% of other contestants’ works
- Submissions with failing builds/tests/samples will be rejected
- Code quality
- Overall extension design
- The juror must have a solid understanding of the described technology to provide a score and feedback. If not, the juror should choose to ‘Abstain’.
- Jurors or whose team(s) intend to participate in this contest by providing submissions lose their right to vote in this contest.
- Each juror will vote by rating each submission on a scale of 1 to 10 or can choose to reject it if it does not meet requirements or vote ‘Abstain’ if they feel unqualified to judge.
- Jurors must provide feedback on submissions or lose their reward.
- The Jury will reject duplicate, sub-par, incomplete, or inappropriate submissions.
1st place………… 120 000 TON
2nd place………… 70 000 TON
3rd place………… 30 000 TON
4-5th place……… 10 000 TON
Total prize amount: 230 000 TON
Rewards distribution model
- Winners receive 10 000 TON of their rewards when contest results are evaluated
- Remaining amount is distributed within a 6 month period in equal parts on a monthly basis
- To receive all 6 distributions, the solution should be supported for 6 months:
- The code should be updated within a reasonable timeframe - 1 month maximum
- Major GitHub Issues should be resolved within a reasonable timeframe - 1 month maximum
An amount equal to 5% of the total sum of all total tokens awarded to contest winners will be distributed among jurors who vote and provide feedback. This percentage will be awarded on the following basis:
- The percentage of tokens awarded to the jury will be distributed based on the number of votes each juror casts. For example, if one juror votes 50 times and another juror votes 5 times, the juror who votes 50 times will get 10 times more tokens than the juror who votes 5 times.
- Feedback is mandatory to collect any rewards.
- Jury rewards are distributed in full upon the end of voting regardless of the long term outcome.