ssing2/meta-pool

NEAR protocol Meta Staking Pool, tokenized stake, liquid unstake, stNEAR, $META

Meta Staking Pool

Overview

What is Meta-Pool and other non-Technical Documentation

CLICK HERE

Technical Documentation

Technical Notes

Repositories

This is the Smart Contract repository. The Web App UI is at https://github.com/Narwallets/metastaking-webapp

Change Log

0.1.0

• Initial version based on core-contracts/lockup and core-contracts/staking-pool
• Deposit, withdraw
• Distributed stake/unstake
• NEAR/stNEAR liquidity pool, Add/Remove liquidity
• META Minting with rewards

1.0.0

• Full functionality
• Simplified user flow
• Desk check testing https://github.com/Narwallets/sc-desk-check-parser

TO DO & Help needed

Smart Contract

• Deposit/withdraw
• Buy stNEAR/Stake
• Sell stNEAR/immediate unstake
• Classic unstake-wait-finish-unstake
• User trip-meter, measure rewards
• distribute staking/unstaking
• retrieve unstaked and ready
• NEAR/stNEAR Liquidity Pool, Add/Remove liquidity
• clearing mechanism on stake to restore liquidity in the NSLP
• act as a NEP-xxx MULTI-FUN-TOK (multi-token contract). Implement for NEAR, stNEAR and META
• Dividends-pool stNEAR/META
• Staking-loans to whitelisted validators
• Emergency Staking (from the nslp) to whitelisted validators

Test

• Simulation tests
• Fuzzy Testing

Staking pool list

• List selected staking pools, getting weight, staked & unstaked
• add a staking pool, set weight

Governing

• Mint and distribute META with rewards
• Phase II - Governing DAO

Infrastructure

• External cron to call distribute()
• compute remaining epoch time
• whitelist pools before adding them

Expansions

• USDNEAR MVP: Create a collateral-based stablecoin similar to Compound's DAI, using NEAR & stNEAR as collateral

Testing

Besides We are doing a simple ad-hoc fuzzy test for metapool. The test generates random operations. We have a list of "invariants" the contract must satisfy to guarantee the internal accounting is consistent. We use a seeded random generator to create "operations" against the metapool (deposit, liquid-unstake, delayed-unstake, add-liquidity, remove-liquidity, end-of-epoch, compute-rewards, retrieve-funds-from-pools) in any order and amount. After each successful operation we check the contract invariants again. This is our way to tests unprepared operations combinations and make sure the internal accounting remains consistent

This is he core .rs fuzzy source https://github.com/Narwallets/meta-pool/blob/master/metapool/tests/sim/simulation_fuzzy.rs, you can navigate up from there to see what it is doing.