Share of 7,100 UNI: Bitget Opens BGBTC PoolX Locks at 18:00 SGT

The window lasts five days

The published start and finish are both at 18:00 in UTC+8, which is also Singapore Time. From October 29 at 18:00 SGT to November 3 at 18:00 SGT is five days, or 120 hours. This is a calculation from the notice's two timestamps, rather than a separately advertised duration. An account holder deciding whether to lock tokens needs both ends of that window.

The announcement identifies the lock asset as BGBTC and the distributed asset as UNI. Those labels describe different sides of the event: BGBTC is the quantity entered in the allocation formula, while UNI is the unit of the distribution. The notice does not describe depositing UNI as the qualifying action. Match the asset names on the event screen before considering any instruction.

Source: the Bitget PoolX announcement, article 12560603899050, opened for this report. Odaily's report also gives the total allocation, maximum and timetable. It does not include all of the official notice's eligibility and release provisions.

For readers comparing this event with other exchange activity, the NexuAlpha activity page provides an internal starting point. The Bitget profile is the relevant venue page. Keep the event's exact asset, dates and formula together when comparing it with another offer; a different lock asset or distribution method answers a different question.

How the proportional formula changes the reader's calculation

Bitget states the allocation formula as the user's locked BGBTC divided by the total BGBTC locked by all qualifying users, multiplied by the corresponding allocation. That makes the denominator essential. Knowing your own proposed lock amount and the event's headline UNI total is insufficient to calculate a fixed personal distribution.

Written with variables, the formula is: personal UNI allocation = personal qualifying BGBTC ÷ total qualifying BGBTC × corresponding UNI allocation. A larger denominator reduces the fraction for the same personal amount. A smaller denominator increases it. This follows directly from the division in the published formula; it is a way to read the terms, rather than a forecast of participation.

SponsoredBitget

Partner rebate share60%Up to

Check regional eligibility and account terms

→Enter the code when you sign up: nexu888

Sign up on Bitget →Codenexu888Copied

A hypothetical example shows the difference. If a qualifying lock were 1 BGBTC and the applicable qualifying total were 1,000 BGBTC, the fraction would be 1 ÷ 1,000 = 0.1%. Applying the stated 7,100 UNI total gives 7.1 UNI. These BGBTC inputs are selected only to demonstrate the arithmetic. Neither the announcement nor Odaily reports a live qualifying total of 1,000 BGBTC.

If that hypothetical denominator became 2,000 BGBTC while the same 1 BGBTC numerator remained, the fraction would be 0.05%, giving 3.55 UNI when applied to 7,100. The reader's lock has stayed unchanged between the examples. The denominator alone explains the difference. Neither result is a quote of the amount that a participant will receive.

The official page does not provide a current total of qualifying locks in the text opened for this report. It also does not provide an individual UNI allocation for a specified participant. A screenshot or calculation that omits the denominator cannot establish a personal amount from these terms. When reviewing an event estimate, record the qualifying total and the time attached to it alongside the personal lock amount.

The 30 BGBTC cap limits the lock

The maximum of 30 BGBTC is a lock limit. It does not give a per-user UNI entitlement. The 0.0001 BGBTC figure is the minimum lock, also expressed in the input asset. Keep these limits in BGBTC when checking the event conditions; the 7,100 figure belongs in the UNI allocation column.

A participant considering an amount between those two limits still needs to read the eligibility conditions. An amount within the range answers the size question. It does not, by itself, answer whether that account qualifies. The official notice makes identity verification a requirement and separately excludes specified account types.

There is no verified BGBTC or UNI market price in the two event sources used here. This report therefore does not convert either lock limit into dollars or attach a dollar value to the distribution. Readers preparing a comparison should keep any separately obtained market quote, its timestamp and its asset distinct from the event's fixed token quantities.

The five-day event window also does not supply an annualized return. A percentage calculation would need a supported valuation and the actual allocation basis. Reading the token amounts as though they were a quoted annual rate would change what the announcement says. The useful comparison in this document is the published lock range and proportional allocation.

Identity verification and excluded accounts

The notice says participants must complete identity verification to be eligible for the distribution. It states that subaccounts, institutional users and market makers cannot participate. Those exclusions matter before any calculation: an estimate based on an account that does not qualify is missing a stated condition of the event.

For an existing Bitget account, inspect whether the event is available to that account and whether its verification status satisfies the published requirement. The article does not establish country-specific availability. The official text opened here does not provide a country-by-country list or a document checklist for verification, so neither is inferred from the presence of the event announcement.

The terms also say Bitget can disqualify users and confiscate distributions for fraud, using multiple accounts to collect allocations, or other violations. Review the account being used against those restrictions. The formula's reference to qualifying users should be read together with these conditions, rather than treated as a promise to every address or account holding BGBTC.

The official notice reserves the ability to change the terms or cancel the event. Keep the version of the event conditions shown when making a decision and review any later event update. The point to check is whether the amount, eligibility or timing has changed, rather than assuming every field remains fixed after the first announcement.

Where the locked tokens are scheduled to return

Bitget says locked tokens will be released to the spot account within five minutes after the event ends. With the stated finish at November 3, 18:00 SGT, that describes a release window ending at 18:05 SGT on November 3 if the published timetable is unchanged. The five-minute interval comes from the official terms; the clock conversion is simple addition.

The notice gives a different destination when automatic Earn is enabled: funds are then deposited automatically into the Earn account. An account holder reviewing the release should therefore check that setting before deciding which balance to inspect. Looking only at the spot balance can miss the destination expressly named for that configuration.

This paragraph concerns the release of the locked tokens. It does not establish a separate UNI distribution timestamp. The opened announcement's release clause should not be repurposed into a claim that UNI necessarily arrives in the same five-minute interval. Review the distribution record separately from the returned lock asset.

Keep the lock record, its amount and the destination setting together when reconciling balances. At the end of the published window, compare the released BGBTC with the lock record and inspect the account named by the setting. For UNI, compare the actual credited amount with the event's distribution record rather than the hypothetical calculations above.

How to check the event before acting

An existing eligible holder can begin with the event's asset labels, its minimum and maximum, and the verification requirement. Then read the allocation formula and locate any qualifying-total figure supplied by the event interface. Finally, check the stated finish and the release destination associated with automatic Earn. These checks follow the specific terms in this announcement.

For venue context, return to the Bitget information page. For a comparison with other dated offers, use the activity listings and compare each offer's own conditions. A headline allocation provides one input; the account restrictions and the denominator determine how useful that input is for an individual reader.

The next event-specific evidence to examine is the qualifying lock total, any amended terms, and the eventual allocation record. The two documents opened for this report establish the 7,100 UNI allocation, lock limits and timetable. They do not establish the future participation total or a fixed personal UNI amount.

For NexuAlpha research updates, follow the English Telegram channel.