Bless/Burn Tracker
The Bless/Burn Tracker is a core component of the TRN platform’s engagement and moderation system. It records user feedback interactions across all posts and ties directly into earnings, moderation escalation, curator reputation, and reward eligibility (e.g., via the LottoModule).
This module ensures that all blessing (positive feedback) and burning (negative feedback) interactions are accurately logged and mapped to user wallets, post hashes, and time windows. These signals inform both platform health metrics and downstream content visibility logic.
✅ Key Behaviors
1. Tracking Blesses
A bless is a lightweight, affirmative engagement akin to a “like.”
Each bless:
Is stored against the post ID and user ID.
Can only be issued once per post per user.
Triggers a view-linked engagement bonus that boosts the fruit balance of the post’s creator.
May enhance a curator’s reputation if they consistently bless content that gets re-blessed or retrned by others.
2. Tracking Burns
A burn is a negative signal and an optional cost-based feedback mechanism.
When a user burns a post:
It is removed from their feed indefinitely.
They forfeit the original 1 TRN spent to view it.
The TRN from the burn is sent to the DAO vault.
Burned posts can no longer earn TRN from that user.
Burn signals contribute to the FlagEscalator and may initiate moderation escalations when thresholds are crossed.
The system prevents multiple burns on the same post by the same user.
Burning someone else’s post is a meaningful action — it costs TRN, thus discouraging frivolous abuse.
3. Earned TRN Adjustments
Burned TRN is subtracted from the post’s gross TRN tally:
E.g., if a post earned 100 TRN but received 10 burns, its adjusted tally is 90 TRN.
The remaining 10 TRN is routed to the DAO (not burned from supply).
Creators can track their gross vs. net earnings in real-time via the TRNUsageOracle ledger.
🔥 Anti-Gaming Safeguards
The Bless/Burn Tracker is tightly integrated with:
AI Bot Verifier – to detect manipulation patterns like bot-driven bless/burn farms.
RetrnIndex – ensures that retrning a burned post is impossible, as it's never shown again.
BoostingModule – boosted posts can be burned; if so, the campaign ends and unspent TRN is returned to the booster.
🧠 Smart Logic
Burn counts are recorded and influence moderation triggers.
Blesses can be used by the LottoModule to rank users for daily rewards.
The system calculates bless-to-burn ratios for both individual users and posts to assess content quality and user trustworthiness.
Curator reward logic uses this signal to reward users whose blesses align with platform resonance (posts that go viral or are widely retrned).
⛔ Burn Is Final
Once a post is burned:
It disappears from that user’s feed permanently.
It cannot be re-burned, retrned, or boosted by that user.
It becomes unpinned if it was pinned.
It remains stored on IPFS but is effectively inaccessible unless re-surfaced via admin review or audits.
🏛️ Related Modules
TRNUsageOracle
Ledger that settles bless/burn TRN transfers in real-time.
FlagEscalator
Uses burn thresholds to escalate potential moderation events.
BoostingModule
Handles refund logic when a boosted post is burned.
LottoModule
Uses bless ratios to help determine reward recipients.
📂 Suggested File
BlessBurnTracker.sol– Smart contract for logging bless/burn events.BlessBurnIndex.ts– Indexer-side logic for real-time view syncing.BlessBurnMetrics.ts– Derived metrics processor (bless-to-burn ratio, reputation score).
Last updated