Launch Online IDE

Your first CorDapp

Create a state and a contract

Let's dive right away into the exercise, starting with something simple, and approximately universal: a token.

The goal

Your goal is to create the state and contract, and eventually flows that implement a token. In this context, token means a fungible token. Fungibility is a property of a commodity whose individual units are indistinguishable from others. Pure gold is fungible because an ounce of it is materially indistinguishable from any other. Fungibility is an important property of money, currency, many securities and commodities because it implies that quantity alone is a sufficient description. If someone says "USD $100," everyone knows what that means because US Dollars are fungible. One would not ask "Which dollars?"

For this exercise, you will avoid some of the regulatory concerns. Instead of creating a general-purpose currency, you will modestly assume that the airlines of the world have decided to come together to create a shared system that will record their digital mileage rewards. The immediate exercise is to establish the basics correctly so that, with these basics in place, airlines and passengers may eventually enable secondary facilities such as trading.

So yes, an air-mile will be a token. It stands to reason to assume that each airline wants to control the supply of their own air-miles. If any airline could issue universally-valid air-miles, nothing would prevent a rogue airline from offering excessive air-miles and burdening competitors with liabilities. An airline also wants to control redemption because, after all, if you want to redeem your air-miles with a trip, there needs to be an available seat in the first place. In the spirit of decentralisation, and with a view to enabling future secondary markets, you will make it such that a token is truly owned by the bearer, and not just in a symbolic sense, as they are nowadays. The bearer, or holder, will have full control except for issuance and redemption.

More details

With this in mind, you will begin to see the outlines of the design.

  • The actions:
    • Issue tokens, a.k.a. mint, create.
    • Move tokens, a.k.a. transfer, pay.
    • Redeem tokens, a.k.a. destroy, burn.
  • The actors:
    • Airlines, a.k.a. issuer, minter, redeemer(??).
    • Passengers, a.k.a. holder, bearer, owner.

For now, focus on the state and contract. You will focus on flows when those issues are well-solved.

tip icon

Why not code the flows as well, and attempt it in one sweep?

  1. When deploying your CorDapp, it is a good practice to distribute the state + contract JAR together and distribute a separate JAR with the flows. So let's conceptually separate the two now.
  2. It is a devastating rookie mistake to leave the contract overly permissive and enforce restrictions at the flow level. By focusing exclusively on the contract first, you will form the habit of observing this best practice.
  3. You have enough on your plate already just with the state, the contract and tests. Yes, you do.

Write code

Your best starting point at this stage is to either use the Java template or the Kotlin template and create your classes as necessary. Don't hesitate to peek back at the previous chapter where you walked you though the CordDapp example. If you still feel uncomfortable with an empty template, you can use the CorDapp example as a starting point and modify it as necessary.

Add unit tests that cover all actions and situations. Yes, tests! You are not going to release untested state and contracts in the wild. Try to think creatively and adversarially, whereby an airline or a passenger would try to game the system to gain an unfair advantage. Your code should prevent such possibilities and your tests should prove that your defenses are effective.

Keep the code generic. In particular when naming entities, you want your code to be reusable at a later stage when, say, another consortium decides to tokenize something else.

Some hints are rolled up below. Think on your own before you unroll them. In the next chapter is an example implementation. Again, for your benefit, resist the urge to peek unless you are utterly stuck.

support icon

Get 3 months access to the authors and experts who created this training.

  • Expert instructors will review your code and help you to refine it.
  • One-on-one support and mentoring from expert instructors.
  • Collaboration with fellow students in a dedicated Training Slack channel.
Discuss on Slack
Rate this Page
Would you like to add a message?
Thank you for your Feedback!