Use the Gumball Machine on Stokenet
  • 05 Feb 2024
  • 2 Minutes to read
  • Dark
  • PDF

Use the Gumball Machine on Stokenet

  • Dark
  • PDF

Article Summary

In the previous Step-by-Step section we allowed our gumball machine to mint its own gumballs. The blueprint still isn't quite ready for us to publish on the ledger though. Currently anyone can mint gumballs, so let's look at restricting it to the component it's methods. We'll also add an icon for the gumball token, so it's easily identifiable in wallets and explorers.

The scrypto package referenced in this section can be found in our official examples here.


Virtual Badges

The Owner badge, like other badges we might make, is a resource. We make it the required evidence of ownership in one of the instantiation steps. In some cases it makes more sense to use a component's own address instead of creating a badge. This is known as the Virtual Badge pattern.

The Virtual Badge pattern

A component does not need to have its own badge to provide permission and perform authorized actions. Instead of a badge the component address itself can act as evidence to perform a action that requires permission.

Address Reservation

All components on the Radix ledger have a unique address assigned at instantiation, but the gumball token is defined inside the instantiate function. So we have access to the a component address inside the function before it's complete, we need to reserve it. We do so right at the start of instantiate_gumball_machine.

let (address_reservation, component_address) =

This give us the component_address to use for the minter rule, and the
address_reservation to apply to the component in the last instantiation step.

Restricting Mint Roles

We update the minter rule to now require the component's own address to mint new gumballs. Only the component and therefore it's methods will be able to mint.

.mint_roles(mint_roles! {
    minter => rule!(require(global_caller(component_address)));
    minter_updater => rule!(deny_all);

The address_reservation is applied in the last instantiation step, giving our component the address we reserved and same address as used to mint new gumballs.

    // Apply the address reservation

Icons for Tokens

We now have one last thing to do before we publish the gumball machine. Outside of resim the token will be displayed in a variety of ways in dapps and wallets. So these can be more visually appealing we need to add an icon for the gumball token. This is done with just an extra metadata field called icon_url.

   "icon_url" => Url::of(""), locked;

URLs and strings are not treated the same in the Radix ledger and so we need to use the Url type. The locked keyword, as before, is used to prevent the icon URL from being changed after the component is instantiated.

We now have a blueprint we can publish on the ledger.

Publishing the Package and Using the Gumball Machine

The steps to build and publish the package, then use the Gumball Machine blueprint on the Stokenet test network are in our official examples repo.

Was this article helpful?