You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indexer : apps/nestjs-indexer for indexer and saved in DB
and packages/indexer-prisma for the schema prisma
Backend endpoints to render data:
apps/backend
Add to schema token_launch attrs: threshold_liquidity as a String?
To finish UI:
Add a claimed button when is_liq_raised.
Slider remain to buy in quote amount:
when threshold_liq ok in backend: add a slide/step for the liq raised to threshold (how many percent done or remain before launch)
Indexer:
Fix CreateLaunch indexer and token_launch model: add Threshold liquidity and Bonding type required in the launch model and to display in the UI
better total price calculation: based on init_supply and liq_raised to get the price at a point of time (after each buy or sell)
indexer: token-launch.indexer.ts, add the threshold_liquidity and bonding_type in the model and saved it
token-launch.indexer.ts : Fix owner_address
indexer: liquidity-added.indexer.ts: uncomment the code of tx check (not useful) and fix the indexer to add is_liquidity_raised
Check calcul after sell: total_token_holded looks having an issue
Summary of TODO by Event of indexer:
CreateToken:
Threshold to add in model
Add correct bonding curve string based on enum number: 0 Linear, 1 Exponential
Buy and Sell:
Verify amount owned by user at each buy and sell.
check total amount holded
[ ]add init pool supply
[ ]check liquidity raised value= can't be negative
LiquidityAdded to LiquidityCreated:
Change the LiquidityCreated
Change the boolean of token_launch of is_liq_raised to true
Batch call all of share user to claim_coin_for_friend so user don't need to do it
create indexer: claim-token.indexer.ts: TokenClaimed event, check the amount and the user and update the share_user with amount claimed and amount_owned and if it's still claimable
Check holders endpoints in backend
Check if others endpoints of the indexer/backend are ok
Cron to maybe claim for user directly after a liquidity launched
Bonus:
Think, check and do (fixed if needed, add others things if needed, LFG)
Graph endpoints based on buy and sell (price can be calculate using bonding curve, the liq raised
The text was updated successfully, but these errors were encountered:
Description
Indexer : apps/nestjs-indexer for indexer and saved in DB
and packages/indexer-prisma for the schema prisma
Backend endpoints to render data:
apps/backend
Add to schema token_launch attrs: threshold_liquidity as a String?
To finish UI:
Add a claimed button when is_liq_raised.
Slider remain to buy in quote amount:
when threshold_liq ok in backend: add a slide/step for the liq raised to threshold (how many percent done or remain before launch)
Indexer:
Fix CreateLaunch indexer and token_launch model: add Threshold liquidity and Bonding type required in the launch model and to display in the UI
better total price calculation: based on init_supply and liq_raised to get the price at a point of time (after each buy or sell)
indexer: token-launch.indexer.ts, add the threshold_liquidity and bonding_type in the model and saved it
token-launch.indexer.ts : Fix owner_address
indexer: liquidity-added.indexer.ts: uncomment the code of tx check (not useful) and fix the indexer to add is_liquidity_raised
Check calcul after sell: total_token_holded looks having an issue
Summary of TODO by Event of indexer:
CreateToken:
Threshold to add in model
Add correct bonding curve string based on enum number: 0 Linear, 1 Exponential
Buy and Sell:
Verify amount owned by user at each buy and sell.
check total amount holded
[ ]add init pool supply
[ ]check liquidity raised value= can't be negative
LiquidityAdded to LiquidityCreated:
Change the LiquidityCreated
Change the boolean of token_launch of is_liq_raised to true
Batch call all of share user to claim_coin_for_friend so user don't need to do it
create indexer: claim-token.indexer.ts: TokenClaimed event, check the amount and the user and update the share_user with amount claimed and amount_owned and if it's still claimable
Check holders endpoints in backend
Check if others endpoints of the indexer/backend are ok
Cron to maybe claim for user directly after a liquidity launched
Bonus:
The text was updated successfully, but these errors were encountered: