JUST’s GasFree Carnival Shows How Blockchain Payments Are Becoming Simpler
For years, one of the biggest challenges in crypto payments was complexity.
Even users sending stablecoins like USDT still need to manage gas fees, hold separate network tokens, and understand transaction mechanics before completing a transfer.
That process slowed adoption and made blockchain payments feel more technical than necessary.
The latest initiative from JUST reflects how that experience is beginning to change.
As part of its sixth anniversary celebration, the JUST ecosystem launched the GasFree Super Carnival across the TRON DAO network, combining real transaction utility with rewards designed around everyday stablecoin usage.
Running from May 25 to May 31, the campaign allows users to participate in a 10,000 USDT reward pool while using GasFree-powered transfers that remove traditional gas token requirements.
The campaign includes: • 100% transfer fee reimbursement
• Up to 66 USDT refund per wallet
• Easter Egg rewards for qualifying new users
• “Most 6 Lucky Koi” bonus events
• Additional social participation rewards
What makes the campaign important is that participation is tied directly to real on-chain activity.
Users interact with the GasFree infrastructure itself while completing stablecoin transfers.
How It Works
Users can create or access a GasFree wallet through supported platforms such as: • TronLink
• Klever Wallet
• Guarda Wallet
• NOW Wallet
After funding the wallet with USDT, including direct transfers from centralized exchanges, users can begin making GasFree transfers immediately.
Each transfer automatically contributes toward reimbursement eligibility and leaderboard participation.
The system removes several traditional friction points: • no separate gas token management
• fewer failed transactions from insufficient fees
• smoother onboarding for newer users
• simpler stablecoin transfers overall
Why This Matters
Stablecoins continue becoming one of blockchain’s most practical financial tools for: • payments
• cross-border transfers
• savings
• business settlement
• digital commerce
As adoption grows, usability becomes increasingly important.
Most users simply want transfers to work efficiently without dealing with unnecessary network complexity.
GasFree moves blockchain payments closer to that experience by simplifying how transactions are executed underneath the surface.
The Bigger Picture
The “Most 6 Lucky Koi” event also adds transaction-based rewards for users landing specific transfer sequence positions: 6 / 66 / 166 / 666 / 1666 / 2666 / 3666 / 4666 / 5666 / 6666
Eligible users can receive instant 20 USDT rewards during the campaign period.
More importantly, the initiative reflects a larger direction across blockchain infrastructure:
making digital payments simpler, faster, and more accessible for ordinary users.
The technology becomes far more practical when users can focus on transferring assets instead of managing network mechanics.
And that is exactly the direction GasFree infrastructure is helping move toward within the TRON ecosystem.
🔗 [GasFree Official Website](
🔗 [JUST Official Website](
🔗 [TronLink Wallet](
@justinsuntron @DeFi_JUST #
TRONEcoStar#
Show more
LLM Knowledge Bases
Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So:
Data ingest:
I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them.
IDE:
I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides).
Q&A:
Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale.
Output:
Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base.
Linting:
I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into.
Extra tools:
I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries.
Further explorations:
As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows.
TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
Show more