tksventures / smart-contracts

smart-contracts

smart-contracts's Issues

Waves Address Registration List Contract

Problem

Collecting a list of addresses that have proven ownership and an on-chain data source is only possible with a smart contract

Solution

• Build a ride smart contract address-list with a single function that adds the caller's address to a list.
• Write a simple front end tool that calls this function with Waves Keeper.

Ethereum Mint-and-Burnable Token Supply Smart Contract

Problem

We need a smart contract that is compatible with the Ethereum protocol that will create a token supply we can use within our Mint-and-Burn Protocol for CLPPS

Solution

Write a smart contract with these features:

• ERC-20 compliant token
• Mintable
• Burnable
• Written in Solidity v0.6.x+

Additional Context

• Parent issue dependent on this issue being resolved: https://github.com/tksventures/ecosystem/issues/137

Timelock Utility

Problem

To interact with the smart contract, like set a lock schedule for tokens, it requires the token holder to call functions on the smart contract manually either through scripts or a cli. This can lead to security issues and possibly more room for error.

Solution

• Build a serverless page that uses Waves Keeper to interact w/the smart contract
  • Allow for deposit, withdraw, and timelock to be called with inputs for each parameter
  • Display information about the current state of the contract

Update README

Please update the README so the project has a public description

Smart Contract Design (RIDE): MV Corporate Vesting of New Asset

Describe the solution you'd like
We will be issuing a new Waves asset for our ecosystem token (tokes) in conjunction with our IEO. Undistributed tokens will be subject to a vesting schedule, locked in an auditable smart contract. Specific numbers are yet to be determined, but the contract should be capable of the following:

• Lock and secure tokens not distributed during IEO period
• Produce the following vesting schedule:
  • No release of tokens for 6 months
  • Over the period of 2 years (24 months), 1/24th of remaining tokens will be made available to MV
  • First vesting occurs at the end of 6 months, or otherwise considered day 1 of month 7. Each subsequent vesting should occur at the beginning of the following month

Additional context

1. These contracts should be open source, and available for distribution to other teams utilizing waves/RIDE.

2. Request security review from waves team after contract is developed

3. Determine if Waves would be willing to reward us with a grant for this feature development.