anchor-protocol / anchor-basset-contracts Goto Github PK

A list of the things we think we want to do, maybe not quite ready for work, but high likelihood of being worked on.

This is the staging area where specs should get fleshed out.

No limit on the list size, but we should reconsider if it gets long.

┆Issue is synchronized with this Trello card by Unito
┆Attachments: Backlog.png

Currently, the ClaimReward implementation does not work as we expected. We need to adapt it to CosmWasm.
We have to pass the functionalities of the handle_reward to the reward contracts. The reward contract is supposed to handle computing global_index and user's_index and reward distribution.

┆Issue is synchronized with this Trello card by Unito

To handle ReportSlashing, we need to provide an algorithm.

┆Issue is synchronized with this Trello card by Unito

Some things that may be added.
Activity Name:
Description:
Expected completion by:
Members Related:

┆Issue is synchronized with this Trello card by Unito

Describe the bug
The update_global_index handler fails if there are tokens with unknown exchange rates on the anchor_basset_reward contract balance:

{"error":"rpc error: code = InvalidArgument desc = failed to execute message; message index: 0: dispatch: dispatch: ibc/0471F1C4E7AFD3F07702BEF6DC365268D64570F7C1FDC98EA6098DD6DE59817B: no price registered with oracle: invalid request"}

To Reproduce
For the current mainnet: send any IBC token to the reward contract and try to execute update_global_index.

Context & versions
0.2.0
0.1.0

(if applicable) suggested solution
The solution is to handle only the tokens with known exchange rates.

Some things that may be added.
Activity Name:
Description:
Expected completion by:
Members Related:

┆Issue is synchronized with this Trello card by Unito

┆Issue is synchronized with this Trello card by Unito

┆Issue is synchronized with this Trello card by Unito

┆Issue is synchronized with this Trello card by Unito

Provide a little background information:

┆Issue is synchronized with this Trello card by Unito

┆Issue is synchronized with this Trello card by Unito

It is better to avoid unwrap in a production code.

Just replace it with ?. Maybe worth to fix it in moving to cosmwasm 0.14 version

Same here:

Activity Name:
Description:
Expected completion by:
Members Related:

┆Issue is synchronized with this Trello card by Unito

Attach designs conveniently using Power-ups for design tools like Figma or Invision

┆Issue is synchronized with this Trello card by Unito

Some things that may be added.
Activity Name:
Description:
Expected completion by:
Members Related:

┆Issue is synchronized with this Trello card by Unito

Currently, we only consider one validator for unbonding which is chosen randomly. We need to devise a plan for the time that the required unbonding amount is more than each validator's delegated amount. In this case, we must pick two or more validators and send an Undelegate message to them.

┆Issue is synchronized with this Trello card by Unito

Currently, we do not consider the possibility of having a slashing event during the unbonding period. An accurate implementation should consider slashing event during the unbonding period and consider the new exchange_rate after slashing event.

┆Issue is synchronized with this Trello card by Unito

• Remove ./artifacts
• Move artifacts to GitHub release materials

This list is for items in code review.

When a task has gotten approval, it moves off to Testing.

If there are too many cards here, we should break off from other tasks to get code review done.

┆Issue is synchronized with this Trello card by Unito
┆Attachments: Code Review.png

┆Issue is synchronized with this Trello card by Unito

┆Issue is synchronized with this Trello card by Unito
┆Attachments: Design.png

┆Issue is synchronized with this Trello card by Unito

┆Issue is synchronized with this Trello card by Unito

Cards come here after being code reviewed, and we're in a place for QA and fixing things QA finds. Design review also happens at this stage.

If we have too many cards here, we should throw a flag and figure out whether we're building things that take too many passes of QA, or if we're bottlenecked on QA time.

┆Issue is synchronized with this Trello card by Unito
┆Attachments: Verifying.png

Create a Trello manual for Terrans

┆Issue is synchronized with this Trello card by Unito
┆Attachments: Trello Plan

We shipped it to production!

┆Issue is synchronized with this Trello card by Unito
┆Attachments: done.png | Done.png

These are the things that folks are working on.

All our engineers should have at least one item in this state.

If there are too few things here, they should be pulled off Todo.

When doing is done, cards move to Code Review.

┆Issue is synchronized with this Trello card by Unito
┆Attachments: Doing.png

Currently, InitBurn and FinishBurn works with a structure similar to <EpocId, <HumanAddr, Uint128>>. Using this structure like this adds a level of complexity while handling the FinishBurn message.
The solution is using a structure like this:
<HumanAddr, <EpocId, Uint128>>.

┆Issue is synchronized with this Trello card by Unito

This is a list of things that are good to pull off to work on, prioritized.

If there are too few items here, we should swarm against getting tasks ready for work.

┆Issue is synchronized with this Trello card by Unito
┆Attachments: To-Do.png

┆Issue is synchronized with this Trello card by Unito

The contract schema files are not updated. We need to update schema files for each struct.

┆Issue is synchronized with this Trello card by Unito