Before beginning work on the bounty, you must submit a proposal. Only if your proposal is accepted will you be able to claim the reward of the bounty. In particular for this bounty you need to detail the testing you will use other than unit testing.
There should be at most 1 week between proposal is accepted and you start working on the bounty. It should take you at most 1 month to complete the bounty.
Description
For this bounty you will need to rewrite the whitelist contract into AssemblyScript making sure that they have the same API.
Context
With the new addition of includeBytes function in AssemblyScript, near-sdk-as should have enough parity with near-sdk-rs that the core smart contracts should be able to be written in AS. The trickiest part of the contracts are the cross contract calls. Rust provides a high level abstraction for working with promises. For an example for batch promise calls in AS see the sdk's repo here.
NEAR Bounty Terms
Before beginning work on the bounty, you must submit a proposal. Only if your proposal is accepted will you be able to claim the reward of the bounty. In particular for this bounty you need to detail the testing you will use other than unit testing.
There should be at most 1 week between proposal is accepted and you start working on the bounty. It should take you at most 1 month to complete the bounty.
Description
For this bounty you will need to rewrite the whitelist contract into AssemblyScript making sure that they have the same API.
Context
With the new addition of
includeBytesfunction in AssemblyScript, near-sdk-as should have enough parity with near-sdk-rs that the core smart contracts should be able to be written in AS. The trickiest part of the contracts are the cross contract calls. Rust provides a high level abstraction for working with promises. For an example for batch promise calls in AS see the sdk's repo here.Relevant repos or issues
Core Contracts
API
Same as rust contracts.
Acceptance Criteria
Bounty
200 DAI