GodwinXbt

Engineer building financial systems, protocols, and infrastructure.

I build software around payments, blockchain systems, developer infrastructure, and security. Focus: how systems behave when the environment does not cooperate.

Software · Protocols · Payments · Infrastructure · Security

View workGitHub

Selected work

All work
RAGNAROK
problem  → A finding is not a finding until valid calls reach an impossible state o
approach → source, state, fork
result   → A research harness, not a scanner. Contradiction first. Runtime proof re

Adversarial protocol research infrastructure

Ragnarok

Problem
A finding is not a finding until valid calls reach an impossible state on a fork.
Approach
Invent a state the designers never wrote down. Reach it with real calls. Prove economics. Kill it if you cannot.
Result
A research harness, not a scanner. Contradiction first. Runtime proof required.
  • Security
  • EVM
  • Research
  • TypeScript
GitHubAll work
THEMIS
problem  → Most monitors tell you the node is down. The harder failure is the node 
approach → source, state, fork
result   → HEALTHY / BROKEN / UNKNOWN as explicit states, not a green dashboard.

Runtime invariant monitoring

Themis

Problem
Most monitors tell you the node is down. The harder failure is the node is up and the state is wrong.
Approach
Observe protocol state across independent RPCs. Quorum and finality first. Then evaluate invariants.
Result
HEALTHY / BROKEN / UNKNOWN as explicit states, not a green dashboard.
  • Infrastructure
  • Distributed systems
  • EVM
GitHubAll work
AGENTPAY
problem  → An agent that can spend without an on-chain policy is just a key with a 
approach → source, state, fork
result   → Autonomous payment flow where authorization is a contract, not a prompt.

Programmable payment infrastructure

AgentPay

Problem
An agent that can spend without an on-chain policy is just a key with a story.
Approach
Decision off-chain. Permission on-chain in AgentVault. Policy constrains what the agent may sign.
Result
Autonomous payment flow where authorization is a contract, not a prompt.
  • Payments
  • Agents
  • Solidity
GitHubLiveAll work
Paidline

Payment and settlement infrastructure

Paidline

Problem
An invoice that dies at the settlement hop is not a paid invoice.
Approach
Invoice in. USDC on Ethereum. Settlement on Creditcoin. Status follows the money.
Result
A live status page for a cross-rail payment, not a screenshot of a dashboard.
  • Payments
  • Fintech
  • Solidity
GitHubLiveAll work