Payment and asset platforms
Platforms that must verify business counterparties check the organization seal instead of running a separate onboarding for each company
An organization seal answers it: the company signs with the electronic signature it already holds, and applications check the seal
Try: Acme Robotics OÜ, EU · ТОО «Ромашка», Kazakhstan · unsealed wallet
Seal your walletLive extract from Solana devnet: a demo company sealed through the test attestor
Problem
A Solana wallet shows its full transaction history but not the legal counterparty behind it. Company identity and wallet control require additional evidence
So each platform runs its own onboarding and verification for business counterparties, and the result stays inside that platform
Rules for banks, payment providers and digital-asset service providers already ask who receives a transfer.[1][2][3][4] In Kazakhstan, licensed digital-asset providers must also check their customers[5][6]
Sources checked on 3 October 2026. This is not legal advice
Use cases
Platforms that must verify business counterparties check the organization seal instead of running a separate onboarding for each company
Transfers between sealed wallets show the company on each side. We see the first pilot opportunity in the Alatau City ecosystem
First users: corporate wallets with electronic signatures. Kazakhstan comes first, then compatible EU organization certificates
Switch the ledger to see what a reporting team would see, with and without seals
| Date | Payer | Payee | Amount | Purpose |
|---|---|---|---|---|
| 2027-03-02 | Bp75…eALw | 7kF3…9xQ2 | 48,000,000 | Office purchase, block 4 |
| 2027-03-02 | 3nVp…aL9e | 7kF3…9xQ2 | 52,500,000 | Office purchase, block 7 |
| 2027-03-03 | 7kF3…9xQ2 | DERF…5GmF | 1,200,000 | Building automation |
| 2027-03-04 | DERF…5GmF | Bp75…eALw | 300,000 | Consulting |
The state issues a token that moves only to sealed wallets
A verified company pays for a property. MOR checks the buyer and seller wallets
The receipt feeds an authorized reporting integration
Planned scenario with example data.[7][8] Asset registries and reporting require integration with the city
Mechanism
The company signs a short request with its electronic signature: an NCA key in Kazakhstan or an organization certificate in the EU
MOR-SEAL-REQUEST-V1 program: Cqbw…P1aP address: Bp75…eALw kind: wallet controller: Bp75…eALw
An attestor checks a Kazakhstan signature off-chain, and the program verifies an EU certificate and signature on-chain
{ "name": "ТОО «Ромашка»",
"trustService": "Gfmd…EFnJ",
"identifierHash": "…",
"signature": "…" }The wallet controller registers the seal: the company name and a salted hash of its BIN or registry number go on-chain
seal 3iQx…fjaL name ТОО «Ромашка» jurisdiction KZ trust level attested valid until 30 Mar 2027
Any Solana program can check the seal; the Token-2022 transfer hook checks it on every transfer
Program 2A8c…khz2 failed: custom program error: 0x238c 9100: recipient has no seal
Valid required seal: allow. Missing or expired seal: reject
let seal = mor_verify_seal::verify_seal(&seal_account, &owner, TrustLevel::Attestor)?;
One call from the mor-verify-seal crate, in any Solana program
Try the sealed transferIn Kazakhstan, individuals declare digital assets on tax forms 270.00 and 250.00, which ask for the exchange or wallet name and the wallet address[9]
The wallet address is already what the state asks for. MOR adds the company behind the address, confirmed by its electronic signature
| Approach | Identity source | Application access | Main dependency |
|---|---|---|---|
| Licensed exchanges | Customer onboarding | Exchange integration | Licensed operator |
| KYB platforms, e.g. Sumsub | Documents and company registries | Provider API | Verification provider |
| Attestations, e.g. EAS | Issuer-defined claims | Attestation schema | Attestation issuer |
| MOR | Electronic signatures of organizations | Solana registry + Token-2022 hook | Trusted CAs + Kazakhstan attestor |
Reusable verification across Solana applications. The trust model stays explicit: accepted certificate authorities and attestors
Now: company-wallet registry and Token-2022 demo on Solana devnet
Months 1 to 2
Interview public-sector and platform teams. Define reporting needs and regulatory scope
Months 3 to 4
Improve revocation. Prepare audits and tests. Research ZK proofs for the planned privacy layer
Months 5 to 6
Prepare the mainnet launch. Complete the security review and required approvals. Run an approved pilot
Next product scope: individual users and additional jurisdictions
Targets depend on pilot access, regulatory requirements and security review
Both founders study Information Systems at KBTU
Technical co-founder
Cryptography and infrastructure. Security engineer at Gamma Technologies: PKCS#11, HSMs and key management
Telegram @dtorossyan
Product co-founder
Design and customer development. Startup and Web3 product focus
Telegram @ablStartup
No. A seal holds company data only: the company name and sha256(salt, jurisdiction, BIN or registry number). The salt stays with the owner, and the registry does not record the person who signed for the company
A company that holds an electronic signature. In Kazakhstan, its head or an employee with signing rights signs with an NCA key; in the EU, the company signs with a compatible organization certificate. The wallet controller then registers the seal
The Token-2022 transfer hook rejects it. The same happens when the recipient's seal has expired or its trust level is below what the token requires. On this site the transfer fails simulation, so your wallet never asks you to sign
Kazakhstan: signatures made with NCA keys through NCALayer, checked off-chain by an attestor. EU: P-256 eIDAS certificates, with the certificate and signature verified by the program on-chain. The seal records the path as its trust level: Attested or On-chain
Not yet. The registry and the demo token run on Solana devnet, and the certificate authority and attestor use public test keys, so anyone can mint such seals. Mainnet readiness is planned for months 5 to 6 of the roadmap