Created Hex'd, a fully onchain battle royale on Starknet, and Herit, an onchain inheritance platform. This paper collects 6 onchain projects (§2) and chains 8 dated events from them into a ledger (§3) that the reader can verify in the browser.
I'm a software engineer and blockchain security researcher.
I'm currently working on Aux, a shared space for discovering new music through other people, and learning about blockchain security.
The rest of this paper is organised as follows. §2 presents the onchain work, one paper per project. §3 sets the dated events behind that work down as a hash chain and gives the reader the means to check it. §4 defines the terms and lists the tools. §5 says where to write.
work
Provable Labs · Software Engineer. Implemented the rendering system for Loot Survivor 2 adventurers using modular, dynamic SVG components, and ported Dope Wars into the Embeddable Game Standard · 2025
open source
Daydreams, Dope Wars, Loot Survivor 2, DojoByExample, etc. · contributor
education
B.Sc. Computer Science · University of Lagos · 2020 - 2026 (Convocation March 2027)
learning
Blockchain Security
2Selected papers
paper 2.1 · live · testnet
2.1Hex'd
O. Ojetokun · 2026 · author
Abstract. A fully onchain asynchronous battle royale with fog of war. Players cross a hex grid where every empty tile is a gift or a curse, and walking into another player resolves combat by XP. All logic, state and randomness live on Starknet through Dojo; the client is a playable 3D board.
pub fn resolve_combat( ref world: dojo::world::WorldStorage, token_id: felt252, defender_token_id: felt252, ref state: PlayerState, direction: Direction,) -> CombatOutcome { let old_position = state.position; let next_vec = get_neighbor(old_position, direction); let mut attacker_stats: PlayerStats = world.read_model(token_id); let mut defender_stats: PlayerStats = world.read_model(defender_token_id); // Higher XP wins. Equal XP penalises defender (attacker wins). let attacker_won = attacker_stats.xp >= defender_stats.xp; let mut attacker_died = false; let mut defender_died = false;
Figure 1:combat.cairo; combat goes to the player with more XP, and a tie goes to the attacker.source ↗
Abstract. An onchain inheritance platform built on ENSv2 subnames and World ID: if an owner is no longer alive, their heirs gain access. Took first place for Best Use of ENSv2 at ETHOnline 2026.
Abstract. Provable Games' onchain adventure game on Starknet. Wrote its onchain renderer, merged upstream: Cairo that draws each adventurer as SVG NFT metadata, with inventory, item bag, battle and death pages.
Abstract. An onchain adaptation of the classic Drug Wars game, built with Dojo on Starknet. At Provable Labs I integrated it with the Embeddable Game Standard: each game is minted as a token, and play, leaderboards, claims and rewards follow whoever currently owns it.
Abstract. A Cairo contract that renders Loot Survivor adventurers as dynamic SVG NFT metadata: health bars coloured by remaining health, equipment icons, level and stats, all generated onchain and returned as Base64-encoded JSON.
Every submission, deployment and merged contribution behind §2 is a block. Each block’s hash is the SHA-256 digest [1] of the previous block’s hash and the block’s own entry, exactly as in (1), so no entry can be changed without changing every hash after it [2].2The ledger is not onchain. It is a hash chain computed when this site is built, and “verify chain” recomputes it in your browser. It shows that the table is internally consistent, nothing more.Each entry cites its source in the references.
Table 1: work history as a hash chain, newest first.
// Builds the ledger (Table 1). Runs at build time; "verify chain" repeats it in the browser.import { createHash } from 'node:crypto';export const GENESIS = '0'.repeat(64);/** * @template {{ slug: string, date: string, title: string }} E * @param {E[]} entries oldest first; `date` is YYYY-MM */export function buildChain(entries) { let prev = GENESIS; return entries.map((entry, height) => { const hash = createHash('sha256').update(`${prev}|${entry.slug}|${entry.date}|${entry.title}`).digest('hex'); const block = { ...entry, height, prev, hash }; prev = hash; return block; });}
Figure 2:chain.js;
the build code that writes Table 1. “verify chain” repeats it in the browser, from genesis upward.
4Methods
Definition 4.1 (Block). A block is one dated event in the work of §2: a submission, a deployment or a merged contribution. Its date is the day of the commit or push it cites, kept to the month.
Definition 4.2 (Entry). The entry en of block n is the text|slug|date|title. In (1) it is appended to the previous hash, written as 64 lowercase hexadecimal digits, and the result is hashed as UTF-8.
Definition 4.3 (Genesis). The genesis block is the earliest entry, at height 0. It has no parent, so its previous hash is 64 zeros.
Table 2: tools, by layer.
layer
tools
contracts
Cairo, Dojo
networks
Starknet
identity
ENSv2, World ID, Cartridge Controller
interface
TypeScript, React, Three.js, SVG
5Correspondence
Questions, corrections and proposals for work are welcome.