👤LGE for Devs

This page is being updated with the latest implementations

Overview

Use LGE when you want to launch with community-provided liquidity instead of funding the whole liquidity pool yourself.

The event creates vested LP-based claims for participants after the presale ends.

Step 1 — Deploy the LGE

Configure these LGE settings carefully:

• Tokens for LGE — the amount of SD tokens committed to the event. Using 100% creates the strongest alignment.

• Rate — the number of SD tokens per BNB/ETH. This affects the launch price.

• Max buy — the maximum contribution per wallet.

• Start date and time — when the event begins.

• Duration — how long the event stays open.

• Vesting delay — time between claim windows.

• Vesting rate — percentage unlocked in each claim window.

• Backing share — percentage of raised value sent to asset-backing. A common target is 50%.

• Dev share — percentage of vested LP allocated to the project owner.

• FEG share — share allocated to the SD/FEG side versus the SD/BNB or SD/ETH side.

• SAFU tag

The LGE receives the SAFU label when:

• At least 98% of supply is deposited

• Dev share is 10% or less

After reviewing the settings:

1. Click Approve

2. Confirm the approval transaction

3. Click Deploy

4. Confirm deployment

Edit the LGE before it activates

Before the start time, you can still edit the LGE from the token dashboard using Edit LGE.

Once the event is live, the settings can no longer be changed.

Configure a whitelist

Before launch, you can enable a whitelist.

Whitelisted wallets get first access to the event. The general public stays blocked until all whitelisted wallets have entered, or until you remove wallets from the whitelist or disable it.

Each whitelisted wallet still follows the same max buy rule as everyone else.

Step 2 — End the LGE and launch the project

If you do not open trading within 72 hours after the LGE ends, participants can start recovering their funds.

If funds later fall below softcap because users exit, you can still launch with the remaining non-zero amount.

The presale can end in three ways:

Hardcap is reached

If hardcap is reached, the event ends immediately.

You then open trading manually through the UI. The system creates the liquidity pools automatically. After that, you or any participant can enable share claims.

The event ends at softcap

If time expires and softcap is met, anyone can use Force end presale.

The system creates the liquidity pools automatically. After that, enable shares so participants can begin claiming on schedule.

The event ends below softcap

If the timer ends below softcap, the event moves to Failed.

Participants can then use Abort presale and Exit presale to recover wrapped BNB/ETH.

Special conditions

Special cases:

• If hardcap or softcap is reached but trading is not opened within 72 hours, participants can start withdrawing.

• If users exit and funds fall below softcap but stay above zero, you can still launch with the remaining amount.

• If everyone exits and the pool reaches zero, you can later relaunch with new settings.

• If softcap is not reached, you can abort and create a new LGE.

Example

Example:

• Hardcap = 1000 BNB

• Backing share = 35%

• FEG share = 30%

• Dev share = 5%

Calculation:

1. 350 BNB goes to backing

2. 650 BNB remains for LP

3. 195 BNB goes to the SD/FEG side

4. 455 BNB goes to the SD/BNB side

5. A 5% dev share gives:

   • 22.75 BNB worth of vested SD/BNB LP

   • 9.75 BNB worth of vested SD/FEG LP

Dev share

The dev share can go up to 50% of total raised value.

It follows the same vesting schedule as participant claims, with one exception:

The first dev claim can be larger.

Formula:

amt * (51 - devshare) / 10

Where amt is the normal first unlocked share.