Work
We write up delivered work as problems, not feature lists. There are no outbound links — sites close down, but the problem and the solution stay readable.
Issuer and verifier are separate legal entities. Merge their consoles into one and a session on one side reaches data on the other. We deployed the two consoles as separate applications and split the token store namespaces as well, so a token from one is worthless on the other.
8 issuer screens · 8 verifier screens · UI in 6 languages
How do you move the authenticity of a physical artwork into digital form? We paired the art archive with a certificate bound to the physical piece, and built KYC, registration, trading, lending and gifting as one flow. Planning, design, app, web, server and chain were all ours.
Planning · UI/UX · app · web · infrastructure · smart contracts
To let a business use wallet features without learning the chain, key management and multi-signature had to sit behind an API. We shipped an SDK together with customer admin features — role granting and an access allow-list.
Ethereum · BSC node operation · SDK · admin features
We gathered NFTs scattered across several exchanges into one listing and let holders download the original file instead of screenshotting it. Cross-chain payment — buying a Polygon NFT with ETH — was the core of it.
4 chains · cross-chain settlement
Coin donations, NFT meeting passes and NFT auctions had to run inside a single service, each with a different lifecycle. We took the blockchain layer and the integration server and tied the three flows to one shared user state.
Blockchain · backend server
We name a client only where we hold written consent. Everything else is described by type.
Tell us where you are stuck and we can tell you what we did standing in the same place.