Hello again, my friends!
Spring showed up two months ago, and I already can’t stand the heat 🥵
Is it like this everywhere, or is Spain getting special treatment?
Summary of Work Done
- Writing content
I expected to be working mostly on content, since the site now supports all the features I had in mind. As you can see in the plots at the bottom, this has been mostly the case.
- :task-docs-dev: ****Finished the first two developer tutorials: Hello World and Transfer Transactions.
While working on these, I realized that the multi-language SDK links I had implemented were a bit too cumbersome. So I came up with a simpler solution.
- :task-docs-textbook: Worked on the first long textbook page: Transactions. Still work in progress. This opened a whole new can of worms: diagrams! Mermaid, the default diagram tool bundled with MkDocs, was a bit too simple for my needs, so I switched to Graphviz and had to style it to match the rest of the site. Do you like them?
- Site configuration
Some more work was needed on the infrastructure side, but now tooltips on method and class links work across all supported languages, including REST!
I’ve also added some more small writer-quality-of-life items, like automatic handling of plurals in links to the glossary.
- Management
Very little management this month. See this face? → 😁 ← This is my face.
I joined a couple of brainstorming sessions with the Captains about Kasane and Daruma.
- Daruma
I wanted to quickly test how easy it would be to add blockchain to a classic game, and I ended up spending 4 days, just because I was having so much fun. Read about it below.
- Learning
We’ve noticed that people like storing stuff on-chain, so doing it right is naturally a concern for Kasane. I spent a couple of days studying the Walrus protocol, at Jaguar’s suggestion.
Here you have each task’s relative time distribution for this month:

Documentation Status
This is the current status of all documentation tasks. The main line to watch is Symbol Documentation at the top, with all other entries listed as its subtasks. The bars in the chart represent how many of those subtasks have been completed.

The XYMDoom Experiment
After writing the first developer tutorial about sending a transaction, I thought that it would be very simple to add that capability to an old favorite game of mine: Doom. I had some experience creating maps for this game when I was a kid, so this was bound to be a very fun quick experiment…
https://youtu.be/ZXxwspQBG1I
What Was the Experiment About?
- Coins
The spinning objects on the floor are XYM coins. They start in the game’s wallet, and when the player picks them up, a transfer transaction sends them to the player’s wallet. The current balance is displayed in the bottom-right corner. While a transaction is in progress, coins appear as “incoming” to indicate that they are not yet available but will be soon.
- Doors
The door with the XYM symbol requires 5 coins to open. If the player does not have enough balance, a message appears. If they do, another transfer transaction is initiated, and the door updates its symbol to show that the process has started. After a short delay, the door opens.