Our Projects

Real, working applications built and run by Crumby Labs.

Bitcrumb


Bitcrumb is a distributed identity and trust protocol. Nodes cluster together over Apache Ignite, and every action in the network produces a cryptographically signed, hash-chained certificate that any node can independently re-verify. There's no central authority deciding what's true. Trust comes from the chain of signatures itself, not from a validator we're asking you to believe.

Identity and consensus signing run on Ed25519, with RSA-2048 using SHA-256 PSS for identity keys and PBKDF2 for key derivation underneath. CRUMB, the network's token, is mined by events and activity across the network rather than issued centrally. It's tradeable, and its value is whatever traders attach to it, not something we set.

That same trust layer is built to work across identity, IoT, and proof of origin, and to tokenize anything backed by verifiable trust, real-world assets and digital ones alike. Any platform that plugs into it inherits that trust directly, making it trustless and interoperable with every other system doing the same, without needing a shared chain, a shared vendor, or a central party to vouch for it. Aggregate Pools give it a deterministic way to run group processes on top of that foundation, from voting, to bill-splitting, to escrow approval, without a central coordinator.

We built real audit tooling to back this up: exporting live certificates from a running cluster and independently re-verifying every signature, hash chain, and quorum calculation against them. It's the kind of verification we want in place before trusting a system like this with anything that matters.

Tapin Wallet


Tapin Wallet is a self-custodial mobile wallet built natively for Android, with an iPhone version coming soon. Every private key is generated and held on the device, protected by AES-256-GCM encryption, PBKDF2 key derivation, and the Android Keystore's hardware-backed storage, and it never leaves the device. Identity runs through Bitcrumb: the wallet generates its own Ed25519 keypair locally, and Bitcrumb issues a decentralized identifier tied to the public key, seeing only public keys, hashes, and signed proofs, never a private key or raw data.

It carries full native support for the XRP Ledger, handling payments, trust lines, and escrow directly, with its own XRPL implementation rather than a third-party library.

On top of that sits a permissioned module system. Developers build small HTML-based apps that run in a sandbox inside the wallet, using a built-in API to tap into the Tapin runtime itself, identity, authentication, storage, signing, and payments, each limited to only the permissions it declares.

That same foundation extends to identity and assets. Every module and record ties back to a DID issued through Bitcrumb, so authentication travels with the same verifiable identity across every app in the wallet. NFTs, digital assets, and tokenized real-world assets can all be represented, owned, and transferred as verifiable records, with a single field, like a credential or attestation, shareable and checkable against a hash commitment without exposing the rest of the record. That's what makes any platform speaking the Tapin API interoperable with any other, without needing to trust a central validator.

Michael's Crumbs


Read All the Notes

Ask About Consulting


Or see the full consulting page.