Multi-Chain & Post-Quantum SDK Suite
Every ecosystem has its own key derivation, address format, transaction envelope and signing ritual, and an application that touches several ends up with that variation smeared across its business logic. This SDK suite pushes all of it behind a single abstraction: one way to derive an account, one way to build a transaction, one way to sign — with the ecosystem and the signature scheme as parameters rather than as separate code paths. Post-quantum schemes sit alongside classical ones behind that same interface, which is what makes migration a configuration change instead of a rewrite.
Repository shape
Multi-package SDK repository covering crypto, chains, identity and transport
How this is presented
Documented as an architecture record. An SDK is judged by its interface design, which is better explained than deployed.
How chain and cryptography become parameters
Follow one call from application code through the abstraction. Notice that the branching happens inside the SDK, never in the caller.
Writes one flow. Never branches on which chain or which signature scheme is in use.
One call path, six possible destinations.
Highlights
- One account and signing interface across six ecosystems — chain choice becomes a parameter, not a code path.
- Post-quantum and classical signature schemes behind the same abstraction, making migration a configuration change.
- WebAuthn support on both browser and server, so a passkey can back an on-chain account.
- Standard hierarchical key derivation, so accounts remain portable to other tooling.
- Zero-knowledge proving included, so privacy features do not require a separate dependency stack.
- Peer-to-peer transport support for direct client-to-client flows.
One interface, many backends
The suite is layered so that the parts that vary — chain specifics and signature mathematics — sit behind stable interfaces, and everything above them is written once.
Crypto layer
Key derivation, signing and verification across signature families.
- Classical and post-quantum schemes implement the same contract.
- Standard mnemonic and hierarchical derivation keeps accounts portable.
Chain adapters
Per-ecosystem address formats, transaction envelopes and RPC access.
- Each ecosystem gets a real adapter rather than a lowest-common-denominator wrapper.
- Differences are contained here so callers never branch on chain type.
Identity layer
Mnemonic accounts, WebAuthn passkeys and delegated authorisation.
- Browser and server halves of WebAuthn are both supported.
- Lets an application offer a passkey login backed by a real account.
Transport
Node RPC and direct peer-to-peer channels.
- Peer transport supports flows that never touch a server.
Every SDK package
The suite is broad on purpose: chain access, cryptography, identity and messaging all sit behind one consistent interface so an application never branches on which chain it is talking to. 21 units across 5 groups.
Chain & assets
7Cryptography
4Identity & payments
3Data & messaging
4Foundations
3Stack by layer
Cryptography
Chain support
Identity
Transport
Delivered work
Cryptography and identity
- Unified signing contract across classical and post-quantum schemes.
- Standard mnemonic and hierarchical key derivation.
- WebAuthn support on both browser and server sides.
- Zero-knowledge proving included in-suite.
Chain and transport
- Adapters for six blockchain ecosystems behind one interface.
- Per-ecosystem RPC clients and transaction encoding.
- Peer-to-peer transport for direct client flows.
Key modules
Unified signing contract
Makes post-quantum migration a configuration change.
- Both signature families implement the same interface.
- Callers are unaware which one is in use.
Chain adapters
Contains ecosystem variation in one layer.
- Real adapters, not a generic wrapper.
- Keeps chain-specific branching out of application code.
Passkey identity
Removes the seed phrase from the onboarding path.
- Browser and server halves both provided.
Presentation approach
How this project is presented
- Interface design explained, since that is what an SDK is judged on.
- Abstraction boundaries shown as a flow.
- Verified file and ecosystem counts.
Documentation and notes
Interface reference
Chain support matrix
Cryptography notes
- Network and organisation names are intentionally omitted.
- Post-quantum readiness here means scheme agility, not an endorsement of any single algorithm.
- Scale figures are counted from the repository.