Blastscore
Blastscore bXP: quest completion and point credits
Blastscore bXP records participation in BH Quests as points within Blast Hub's design. Completing a qualifying quest earns points that social ranking uses as an additional engagement measure. The point record has a different purpose from wallet reputation and a later reward allocation. Current quest access and point-crediting availability remain unconfirmed.
The task requirements behind a bXP award
A BH Quest connects its completion requirements to an engagement award. Blast Hub is designed to let projects customise tasks involving on-chain or Web2 interactions. A general record of ecosystem activity does not establish that a particular BH Quest has been completed.
Completion and the point credit
Recognised quest completion is the prerequisite for earning bXP in the quest model. An attempted action establishes less than a completed quest; the completion condition determines whether the attempt fulfils the task.
Blast Hub's design uses automatic task verification to assess completion. The particular quest determines which interaction is relevant to that assessment.
A point total expresses credited engagement. Where a quest credit and a total are displayed, the credit identifies the award, while the total gives its accumulated context. A total alone may leave the contribution of a particular quest unclear. Task completion and point crediting therefore need separate interpretation when diagnosing an expected award.
The social-ranking design describes bXP as an engagement metric used in real time. A fixed crediting interval for every quest remains unconfirmed. Real-time use of an engagement metric does not establish that each attempted action produces an immediate point credit.
On-chain and Web2 quest inputs
The hub's task design covers both blockchain interactions and Web2 participation. These are different inputs to a quest, while the relationship between completing a BH Quest and earning bXP remains the same.
On-chain interactions
A blockchain interaction can supply the activity that an on-chain quest evaluates. For activity on Blast, public transaction history makes that participation visible. The quest requirement determines what the recorded action means for completion. Its transaction record alone does not state a bXP award amount or the terms of a later reward.
Web2 interactions
Web2 tasks broaden the hub's participation model beyond blockchain transactions. Their requirements concern the interaction that the project has selected. Each task needs its own completion condition, even when several tasks involve the same kind of participation. An on-chain record cannot stand in for a required Web2 interaction.
What do bXP points add to social ranking?
Social ranking uses bXP as an additional engagement metric in the Blastscore design. Points give quest participation a measurable representation. The underlying task explains what activity produced the award, which matters when interpreting a count without its quest context.
A ranking position and a credited point total also describe different things. The total represents points credited to the participant; a position expresses placement under the ranking method. An exact ranking formula and refresh schedule remain unconfirmed. A ranking position alone cannot establish a reward amount.
bXP alongside wallet reputation
S.C.O.R.E. is the wallet reputation rating, while bXP measures BH Quest engagement. For campaigns requiring experienced crypto users, Blast Hub's anti-bot design uses S.C.O.R.E. to restrict bot access. The reputation algorithm evaluates the quality and diversity of on-chain involvement. A point total records quest engagement without providing a reproducible calculation of the wallet rating. When a quest involves a blockchain interaction, that action can also appear in wallet history. Its bXP award still does not reveal how the reputation algorithm weights that action. A changed S.C.O.R.E. value, by itself, is insufficient evidence that a BH Quest produced a point credit.
A quest credit compared with a rating change
Consider a hypothetical case: a BH Quest is available, the starting balance is 23 bXP, the advertised award is 17 bXP, and the wallet rating has changed. The reader wants to establish whether completing the quest has added points. The completion and display states that follow are also hypothetical.
A changed reputation rating concerns the wallet assessment. A recognised BH Quest completion concerns the activity that earns quest points. To check this quest's award, compare its credited points with the change in the point total.
Suppose the quest requirements are met and its credited award becomes visible. The expected arithmetic is 23 + 17 = 40 bXP. A quest-specific credit of 17 bXP together with a total of 40 bXP establishes the assumed award in this example. The rating change supplies no additional proof of that credit.
If an earlier check shows 23 bXP and a later check shows the quest credit and 40 bXP, those observations show that the credit was visible by the later check, without pinpointing when it appeared. They do not establish a universal waiting period. Without the quest credit or another explanation of the change, a new total alone would leave the award's origin unresolved.
Airdrop criteria and reward allocation
The bXP design includes an intended role for points in airdrop selection. This connects quest engagement to a possible distribution criterion, while leaving the actual benefit dependent on the applicable distribution terms. It does not establish that an airdrop is currently open or that every point has a fixed redemption value.
Participation criteria
Using bXP as a selection criterion would make recorded quest engagement relevant to eligibility. It would still require terms explaining how that record affects eligibility or allocation; the existence of points alone cannot settle those decisions.
Allocation terms
A reward rule must identify the benefit and explain how an eligible participant's points affect it. The point count alone supplies no token amount, payment date, or exchange rate. Partner benefits tied to S.C.O.R.E. have their own reputation conditions, which cannot be inferred from a bXP balance.
Quest availability and changing terms
To earn bXP through a BH Quest, the quest must be available and its applicable completion requirements must be met. Live quest access and current bXP crediting remain unconfirmed. An existing point record concerns earlier participation; another quest award requires a qualifying completion under the terms of an available quest.
Helpful answers about Blastscore bXP
Are all BH Quests worth the same number of bXP?
A universal bXP award size for BH Quests has not been established. Any amount attached to a particular quest applies within that quest's terms; an illustrative calculation does not set the award for other quests.
Does repeating a completed BH Quest qualify for another bXP credit?
A repeat bXP award depends on the quest recognising another eligible completion. The general relationship between completion and points does not establish that every task is repeatable.
Do BH Quests require Proof-of-Yield certification?
The Proof-of-Yield design connects certification with access to quest and reward opportunities on Blast L2. This does not establish certification as a universal prerequisite for BH Quests. An attestation requirement must apply to the particular opportunity before it can be treated as a condition for earning its points.
Will earned bXP expire when a quest ends?
A quest ending does not, by itself, determine whether previously earned bXP expires. Point expiry would need an applicable rule for the existing balance. No general bXP expiration schedule is confirmed, so neither unlimited validity nor automatic expiry at campaign closure can be assumed.
Is bXP transferable between wallets?
Wallet-to-wallet transfer of bXP remains unconfirmed. No transfer procedure or wallet-migration rule is confirmed.
Last updated: