<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by JUNI - Jackpot Universe on Medium]]></title>
        <description><![CDATA[Stories by JUNI - Jackpot Universe on Medium]]></description>
        <link>https://medium.com/@juniversebsc?source=rss-8d1dce64e151------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*etyk6w6EgmtE7N7UnEYiIA.png</url>
            <title>Stories by JUNI - Jackpot Universe on Medium</title>
            <link>https://medium.com/@juniversebsc?source=rss-8d1dce64e151------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 17 May 2026 16:44:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juniversebsc/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Architecting the Jackpot Universe]]></title>
            <link>https://medium.com/@juniversebsc/architecting-the-jackpot-universe-cef7bdf7f878?source=rss-8d1dce64e151------2</link>
            <guid isPermaLink="false">https://medium.com/p/cef7bdf7f878</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[bsc]]></category>
            <category><![CDATA[jackpot]]></category>
            <dc:creator><![CDATA[JUNI - Jackpot Universe]]></dc:creator>
            <pubDate>Sat, 27 Aug 2022 18:57:20 GMT</pubDate>
            <atom:updated>2022-08-27T19:02:00.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*AyXppxTWLcnJtNVbpvF7qA.png" /></figure><p>The <a href="https://juni.gg">Jackpot Universe</a> (JUNI) is an innovative BSC project that’s slated for a launch in early September. JUNI is the natural extension of LAS (Last Ape Standing) project which ended prematurely with very identifiable caveats.</p><p>JUNI fixes those caveats and introduces a multi-contract token ecosystem that elevates the LAS protocol to new heights.</p><p><strong>But, what’s LAS?</strong></p><p>LAS was launched approximately 4 months ago on the Binance Smart Chain as a BEP-20 token, introducing unique tokenomics. The gist is this:</p><p><strong>Buy 0.1 BNB of tokens, stay as the last buyer for 10 mins, win the jackpot.</strong></p><p>Simple, right? LAS garnered a ton of attention within the crypto communities. At some point, we had more than 2000 users actively looking at the jackpot dashboard, monitoring buys and waiting eagerly for a random user to win the jackpot. LAS eventually failed due to a couple of reasons, biggest of which is the lack of a bot blacklist and an isolated focus on a single jackpot and a big bang milestone. If buys keeps accumulating and nobody wins, the jackpot triggers the big bang. The BB is reached when the jackpot hits $100,000. Half of that amount gets sent to a buyback wallet which then buys and burns $50,000 worth of tokens in one transaction.</p><p>The vision of LAS was grand, hampered by security measures that were not condoned. The Jackpot Universe had to go bigger, better and reasonably more secure. How big did we try to get? 7 contracts. SEVEN contracts need to communicate to perform all JUNI’s functionalities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/1*wBhvO6EfwRysS8ImzuhhfA.png" /><figcaption>Jackpot Universe (JUNI) Architecture</figcaption></figure><p>This diagram illustrates the contracts required to be deployed for JUNI. The center stage is definitely “Jackpot Universe”, but how do all the other contracts interact with it? We’ll go over this in a bottom up approach.</p><p><strong>Bronze/Silver/Gold Tickets</strong></p><p>These are BEP-20 tokens that will be used as tickets for the secondary jackpots which will be introduced in JUNI. Four new jackpots were introduced, for a total of five. These jackpots are bronze, silver, gold and partnership jackpots. A bronze ticket allows you to participate in the bronze jackpot, silver for the silver jackpot, etc…. The partnership jackpot is a bit more special as both the award and ticket tokens can be changed to whatever the JUNI team decides. Win SafeMoon tokens by contributing Cake as tickets? Yes, you can. Win BUSD by contributing SafeMoon tokens as tickets? Yup. Crazy, new, innovative. All of these tickets will function like regular tokens, so users can freely transfer them from one wallet to the other.</p><p>Now, in addition of being the last buyer for the major jackpot when you buy 0.1 BNB worth of JUNI, you will receive a scaled amount of bronze tickets. These tickets will drive the interest in all other features of JUNI.</p><p><strong>Jackpot Broker</strong></p><p>Somebody has to be responsible for awarding the secondary jackpots (bronze, silver, gold, partnership) as well as allowing users to upgrade their bronze tickets. This is the responsibility of the jackpot broker. Bronze tickets can be exchanged to silver ones. Silver tickets can be exchanged for gold. The rates are configurable, but it’s 3B = 1S and 5S = 1G. The jackpot broker supports resetting, activating, and deactivating jackpots.</p><p>One extremely important detail about the broker is that it keeps track of all users who have contributed to the secondary jackpots. There are a couple of challenges here, for example:</p><ul><li>How do you properly reset the user state after each jackpot award?</li><li>How are users stored? What’s being tracked per user?</li><li>How do you award the secondary jackpots in a fair manner?</li></ul><p>These are necessary questions for necessary answers that will drive the responsibilities of the broker.</p><ul><li>We should not count users who have participated in an old bronze jackpot for the latest win.</li><li>We can’t be using randomness within Solidity to award the jackpot. There must be an external service that’s supplying this random factor.</li><li>The jackpot broker needs to keep the state of the jackpots up-to-date.</li></ul><p>Most state changes happen within a token transfer, buy or sell. In this case, we’ll be wiring the broker to JUNI’s main token contract to ultimately achieve this behavior.</p><p><strong>Jackpot Referral</strong></p><p>JUNI offers its investors the opportunity to refer other wallets and redeem a daily reward package. This package comes in the form of X amount of bronze tickets. Wallets must hold a certain amount of JUNI to be eligible for the daily reward.</p><p>Referring other wallets needs only a single token transfer. When the referred wallet buys, the main referrer gains bronze tickets based on the amount of tokens the referrer holds. JUNI introduces multiple holding tiers (1000, 5000, 10000) and these tiers dictate the amount of bronze tickets the user earns from a buy and that of when his referred wallets buy.</p><p>The responsibilities of the jackpot referral contract are well-defined and straightforward. It must track the last time a user has claimed his or her rewards. In addition, it needs to have the ability to void referrals and ban certain referral abusers. This contract needs to be able to mint bronze tickets to reward people on a daily basis.</p><p><strong>Jackpot Guard</strong></p><p>As the name suggests, the Jackpot Guard is the watcher on the walls. It can determine whether a user is eligible for the jackpot award or whether it’s a restricted user. The latter can’t initiate any transfer. This applies on both sending and receiving. This guard module can also determine the amount of tickets a certain buy should be awarded. Similarly to the broker and referral contracts, the guard contract can authorize wallets with elevated access to further ban jackpot abusers. The usage of this guard module is straightforward and is abundant in the main Jackpot Universe token contract.</p><p><strong>Jackpot Universe</strong></p><p>This is the main BEP-20 token contract of JUNI. On top of integrating all the contracts mentioned above, JUNI introduces a multi-layer abstracted contracts that enhances code readability and writability of taxed tokens. These same contracts could be used in other tokens as a plug-and-play abstract contract.</p><p>I’ve previously touched based on this in one of the early LAS Telegram posts. Essentially, JUNI introduces a Treasury module with abstracted tax handling. Why? Well, given that our tax distribution is now even more diverse due to the additional jackpots being introduced, it was natural to simplify the taxation system to be able to dynamically assign taxes and their corresponding percentages. With this new innovative system, it takes a single line of code to add a new tax type.</p><p>Types of taxes in JUNI:</p><ul><li>Liquidity</li><li>Marketing</li><li>Team</li><li>Main Jackpot</li><li>Bronze Jackpot</li><li>Silver Jackpot</li><li>Gold Jackpot</li></ul><p>There had to be a better system than the conventional hardcoded one to support more tax structure. JUNI achieves this and provides an easy way to determine buy and sell taxation. Hurray!</p><p>Great, we still need to bridge all the other contracts through the JUNI contract.</p><ul><li>Jackpot Broker — JUNI will call a specialized method on the broker to process the state of all pending jackpots. It will appropriately advance jackpot states based on whether the jackpot has expired and is pending a decision. This is where all token transfers essentially introduce a broker trigger to keep the jackpot states up-to-date.</li><li>Jackpot Guard — JUNI calls the guard contract on multiple occasions. It will restrict transfers, figure out bronze ticket rewards and reset the jackpot if it determines that the main jackpot is being awarded to a bot-identified wallet.</li></ul><p>JUNI supports multiple DEXs and the team behind the project is determined to carry extraordinary partnerships going forward.</p><p>There’s still one missing piece to the puzzle, people’s all-time favorite:</p><p><strong>The Jackpot Universe Bot</strong></p><p>This Telegram bot will update the group with the countdown timer of the main jackpot. However, starting with JUNI, it will now trigger secondary jackpot decisions and inform the group of the winner in a very transparent manner. Additional enhancements have been integrated into the bot ever since its inception in LAS. The bot can also show top buyers in multiple categories (it started the entire biggest buy bot meta). It will also track staking stats and provide various admin tools for moderation.</p><p>JUNI will be a fair launch on Pinksale. The bot has been updated to report fair launch contributions. The JUNI team might be using these live contributions to award bronze tickets to contributors. This has not been officially announced, but the bot is versatile enough to provide FOMO before and after launch.</p><p><em>One last note on all things JUNI </em>— <strong>High APR staking</strong> will have a comeback albeit not as pronounced as it used to be in LAS. The staking contract is the 8th contract developed for JUNI and will now support compounding.</p><p>All JUNI contracts, staking, bot and dApp JS development has been done by our CTO <a href="https://t.me/addo47">@addo47</a>. Genuinely, there’s nothing better than a fully-fledged in-house software development for a beautifully complex solution for an extremely innovative meta.</p><p>You can find more info about the Jackpot Universe on their <a href="https://juni.gg">website</a> and <a href="https://t.me/JackpotUniverse">TG group</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cef7bdf7f878" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>