JVault
Docs EN
Docs EN
  • Introduction
  • Tokenomics
  • Staking V2
    • General information
    • Unstake periods
    • Info for pool creators
      • Pool creation and adding rewards
      • Fees
      • FAQ
    • Info for stakers
      • JVault responsibility
      • Staking process
      • Unlocking tokens and rewards claim
      • FAQ
  • Launchpad
    • Launchpad info
    • Different types of presales
    • Reliability Score
    • Info for projects
      • Launching tokensale
      • Fees
      • The end of tokensale
      • Referral system
      • Whitelists
      • Verification of projects
    • Info for tokensale participants
      • Buying tokens without Whitelist
      • Buying tokens with Whitelist
      • Token and referral cashback claim
  • Locker
    • Locker info
    • Token locking process
    • FAQ
  • Staking V1 (DEPRICATED)
    • General information
    • Types of staking pools
    • Info for pool creators
      • Pool creation
      • Fees
      • FAQ
    • Info for stakers
      • JVault warranties
      • Staking
      • Token unlock and rewards claim
Powered by GitBook
On this page
  • What is Reliability Score?
  • What does the Reliability Score depend on?
  • Calculation method
  • How to increase Reliability Score?
  1. Launchpad

Reliability Score

PreviousDifferent types of presalesNextInfo for projects

Last updated 10 months ago

What is Reliability Score?

Reliability Score is a tokensale evalluation system based on guarantees for investors. Reliability Score shows how much the minimum price of a token after listing can differ from the purchase price at the presale, assuming that all tokens in circulation are immediately sold on DEX. The smaller the difference, the higher the score.

What does the Reliability Score depend on?

The Reliability Score of a project is influenced by the following parameters:

  1. Base purchase price on tokensale (without taking into account any discounts)

  2. Minimum purchase price (including all possible discounts from and )

  3. Soft Cap (minimum amount of raised funds at which the presale will be successfully completed)

  4. Amount of initial liquidity supplied automatically and initial ratio of tokens and TONs in the pool

  5. The number of tokens unlocked in the (deducted from the circulating supply)

  6. Number and size of unlocked presale tokens

Calculation method

Score=111 ∗ min_guaranteed_price / base_priceScore = 111\ *\ min\_guaranteed\_price\ /\ base\_price Score=111 ∗ min_guaranteed_price / base_price

Where base_pricebase\_pricebase_price is the base purchase price on tokensale, and min_guaranteed_pricemin\_guaranteed\_pricemin_guaranteed_price is the weighted average price for each token unlock (in case of using vesting) at which each investor can be guaranteed to sell purchased tokens on DEX.

When calculating min_guaranteed_pricemin\_guaranteed\_pricemin_guaranteed_price , it is assumed that:

  1. The number of TONs raised will be equal to Soft Cap, and all tokens will be sold at the lowest possible price, taking into account all discounts and cashbacks (for existing tokensales that have already collected Soft Cap, it is assumed that the number of TONs raised so far will be the final one)

  2. The liquidity will only be added once (immediately, after the end of the sale), and no token purchases will be made on DEX

  3. The investor for whom min_guaranteed_pricemin\_guaranteed\_pricemin_guaranteed_price is calculated will sell unlocked tokens exactly one hour after each vesting cycle

More detailed formula
# base_price — base sale price excluding discounts
# min_price — minimum price including all possible discounts and cashbacks
# soft_cap — minimum number of attracted TONs, upon reaching which the presale can be successfully completed

# current_collected_ton — current number of TON raised
# current_sold_jettons — current number of tokens sold

# allocated_jettons — total number of tokens allocated for tokensale (tokens for sales and for liquidity)
# liquidity_part_jetton — share of tokens that will be added to liquidity after the end of the sale
# liquidity_part_ton — a share of the collected TONs, which will be added to liquidity after the sale is over

# first_unlock_time — time of the first unlocking of tokens purchased at the sale
# first_unlock_size — share of tokens that will be available at first unlocking
# vesting_cycles_number — number of unlocks of presale tokens, excluding the first one
# vesting_cycle_length — unlock interval

# total_supply — total number of mined tokens
# locked_jettons(time) — number of tokens blocked in Loker and other sales of Launchpad 
#                        (tokens from the current sale are not counted). Depends on time.

if current_collected_ton < soft_cap:
    min_sold_jettons = current_sold_jettons + (soft_cap - current_collected_ton) / min_price
    ton_liquidity = soft_cap * liquidity_part_ton 
else:
    min_sold_jettons = current_sold_jettons
    ton_liquidity = current_collected_ton
jetton_liquidity = min_sold_jettons * liquidity_part_jetton / (1 - self.liquidity_part_jetton)
    

k = jetton_liquidity * ton_liquidity  # coefficient, which remains constant in classical AMM
        
sell_time = first_unlock_time + 60 * 60 - 1  # the time of the first sale by a hypothetical investor
    
unlocked_jettons = total_supply - allocated_jettons + min_sold_jettons * first_unlock_size
guaranteed_price = (k / (jetton_liquidity + unlocked_jettons - locked_jettons(sell_time)) ** 2) * first_unlock_size

if vesting_cycles_number:
    # size of all subsequent unlocks in linear vesting
    unlock_size = (1 - first_unlock_size) / vesting_cycles_number  
    
    for _ in range(self.cycles_number):
        sell_time += vesting_cycle_length
        unlocked_jettons += min_sold_jettons * unlock_size
        guaranteed_price += (k / (jetton_liquidity + unlocked_jettons - locked_jettons(sell_time)) ** 2) * unlock_size

reliability_score = round(max(min((guaranteed_price / base_price) / 0.9, 1), 0) * 100, 2)

How to increase Reliability Score?

Reliability Score depends largely on the parameters that you set up when creating a tokensale. To increase the Reliability Score, you can use the following recommendations:

  • Increase the percentage of TONs that will be added to initial liquidity Since the Reliability Score calculation assumes that liquidity will only be added once, the score is directly dependent on this parameter.

  • Don't set referral and whitelist discounts too high When calculating the initial ratio of tokens to TON in the liquidity pool, the lowest possible sale price is used including all discounts, so it is important not to over reward referrals and whitelist owners.

  • Do not allow too much difference in the amount between Soft Cap and Hard Cap It is often difficult to predict the amount of investment raised, but if Soft Cap differs from Hard Cap by several times, it can negatively impact the Reliability Score.

  • Increase the number of vesting cycles Increasing the number of vesting cycles has a positive impact on the Reliability Score, as a smooth, even unlocking of assets ensures that there are no large sales at the start of trading.

  • Reduce the percentage of tokens that will be added to initial liquidity The lower the ratio of tokens that will be added to liquidity to tokens allocated for sale at the sale, the higher the listing price will be. This will increase the Reliability Score, but only if the tokens to be sold are vested.

After each token unlock (in both and ), all holders will immediately sell all tokens available to them

Lock the tokens in according to your tokenomics Locking tokens will create a guarantee that they will not be sold on DEX, hence it will increase the Reliability Score.

the referral system
WL SBT
Locker
Locker
Launchpad
JVault Locker