23.101. DD 100: Share Tokenization#

Design status:

Draft

Implementation status:

Not started

DD shepherd:

TBD

Historical contributors:

Christian Grothoff

First published:

2026-08-09

Last substantive change:

2026-11-14

23.101.1. Summary#

This document specifies how GNU Taler can be used to support registered shares (Namensaktien) for which a new share register keeps the authoritative record of the registered shareholders and of the number of shares attributed to each of them. The new share register provides the cryptographic machinery for recording issuance, transfer, dividends and e-voting based on shares held. The share register is maintained by the issuer or by an operator designated by the issuer and modifying it is guarded by requiring consent from an independent second party, the share guard. The Taler exchange and merchant continue to process the electronic-money payments used to buy or sell shares and to receive dividends.

Private shareholder keys stored in the Taler wallets only serve to authorize certain operations on the shares (such as withdrawing dividends, e-voting or receiving information from the company). They also can serve as one of multiple authentication factors required to authorize selling shares. Any change of the registered ownership of a share is only effective once it has been processed by the share register and authorized by the share guard. A transfer request starts the process to update the register, and only a successful registration in the register and approval by the share guard triggers the issuance of share tokens to the buyer.

23.101.2. Motivation#

Taler can tokenize assets other than fiat-money or crypto-currencies. One asset class that could be particularly promising are shares in companies. This design document specifies how Taler could be used to tokenize shares and pay out dividends.

For registered shares, the system must associate every share position with an identified shareholder and keep a reliable record of the changes of ownership. Simply moving bearer-style tokens from one wallet to another would not keep the wallet balances and the shareholder register synchronized and not meet legal registration requirement. Furthermore, the law requires an independent entity to approve every update to the register. The design therefore does not directly use the Taler cryptography to represent shares, but merely integrates with it for buying and selling shares against cash, issuing new shares against cash, paying out dividends and providing e-voting tokens for shareholder decisions. Storing private shareholder keys in the Taler wallet is also convenient as a way to provide an additional authentication factor that is backed up with the regular wallet backup mechanisms. The actual implementation is provided by new shareholder register and register guard components.

23.101.3. Requirements#

User stories include:

  • emit shares for fiat money (raising capital), showing investor brief / shareholder agreement before purchase

  • sell of shares by a shareholder for fiat money to a new shareholders

  • sell of shares by a shareholder for fiat money to existing shareholders

  • buy shares for fiat money from existing shareholders as a new shareholder (with legitimization)

  • buy shares for fiat money from existing shareholders as an existing shareholder (without legitimization)

  • issue dividends from the business to shareholders

  • notify shareholders about business developments, such as shareholder meetings

  • issue shareholders e-voting tokens using blind signatures to enable voting on business decisions

Enabling shareholders to vote (e-voting) on business decisions is out of scope for this initial design and left for a future design document.

The share register must in particular:

  • register shareholders following a successful legitimization (identity verification) step and confirmation from the register guard

  • record the allocation of newly issued shares to identified shareholders after approval by the register guard

  • initiate a transfer by reserving shares and complete the transfer to a registered shareholder upon confirmation from the register guard; the reservation must prevent the same shares from being used in multiple concurrent transfers, and it must expire if the transfer does not complete by some deadline; proof of payment by the buyer before the deadline must be the last step

  • record which shareholders have outstanding dividends for a particular period, and updating the outstanding dividend amount atomically when irrevokably paying the dividend

  • record which shareholders have received ballots for a particular vote

  • maintain an auditable history of share issuances, transfers, redemptions and dividend distributions

Electronic-money payments continue to use the existing Taler exchange: share-specific functionality must not be implemented as a new asset class inside the exchange itself (see Alternatives).

23.101.4. Proposed Solution#

23.101.4.1. Components#

A share register service is introduced to a avoid overloading existing components with share-specific responsibilities. The components have the following responsibilities:

  • share register: the REST API and backend for share purchases, transfers and shareholder information, including the relevant legal documents

  • share guard: independent 2nd party receiving additional authorizations (MFA) for share transfers; its consent is required for critical updates to the share register (Note: find out what is legally critical and what is not!)

  • merchant backend: purchase orders, payment references and the integration with Taler’s contracts

  • exchange: the electronic-money operations, that is the purchase payments and the dividend payouts

23.101.4.2. Share Tokens#

Shares are something the new share register allows users to buy and sell (or the company to emit):

  • shareholder registration records legitimization data (at least 3 factors) with both share register and share guard. Only registered shareholders are allowed to transact with shares. One of the factors is a private shareholder key stored in each wallet. For some operations the private shareholder key may be configured to suffice to authorize them. Some factors are exclusively used by the share guard.

  • share register tracks number of shares issued to each registered shareholder

  • buying shares is a regular contract with the contract terms specifying the number of shares to be transferred; it must additionally be signed by the private shareholder keys of buyer and seller. The contract only becomes valid with the signatures of share register and share guard; the share guard requires at least one more authentication factor by the seller before providing its signature. Share register and share guard update the register upon receiving confirmation of the payment by the exchange during the reservation window. The wallet of the buyer understands the share purchase contract and only signs the deposit confirmations if all required approvals are present and the time is significantly before the end of the reservation window.

  • the share register includes endpoints to send notifications to wallets for issued shares, such as dividend notifications or shareholder meeting announcements; wallets should request updates at a frequency specified in /config of the share register; all notifications are ordered (numerically), with an endpoint to list all notifications past a given serial ID, and another to download each of the (historic) notifications; once issued, notifications never change; notifications are signed by a long-term share register key.

  • wallets can use their private shareholder key to request dividend distribution. Dividend distribution happens via a new type of contract where either a p2p-pull request instructs to pay to a wallet, or where a deposit request instructs the share register to deposit the funds into a bank account. Note that the share register should handle the case where it does not directly make the payment and merely exports the list of dividend payment requests (with signatures) to its operator. It might be good if it could see if the operator satisfied the request.

  • the share-register allows admin to emit new shares; as always, the share-guard must confirm.

  • all requests are stored, and a single sequential timeline is preserved by linking them blockchain-style, ensuring a single top-level hash is enough to check consistency between share-register and share-guard.

23.101.4.3. Shareholder Register#

A new share register service maintains the shareholder records and the share positions. Every shareholder has a unique internal identifier that is associated with a verified customer identity. The service stores the information required for the register and keeps a history of all changes.

The register contains at least:

  • the shareholder identifier and the required shareholder information

  • the relevant share class

  • the number of shares attributed to each shareholder

  • the registration date and the applicable effective date of each change

  • references to the transactions that caused each change

The register is authoritative for determining which shareholder is recorded as holding a given number of shares.

Every register change is recorded as an immutable event. Events include:

  • the initial share issuance

  • the allocation of newly issued shares

  • a transfer between shareholders

  • a share buyback or cancellation

  • a correction of a previously recorded event

  • any other change affecting a shareholder’s position

The register must support reconstructing the shareholder positions at an earlier point in time. The current position may be stored as a materialized balance, but every change must be traceable to a recorded register event.

An event records the affected shareholders, the share class, the quantity, the effective time, the recording time and the corresponding transaction identifier. Corrections are represented by additional events rather than by silently overwriting historical records. The service maintains the current share positions derived from these events and provides the audit trail used for reconciliation.

23.101.4.4. Shareholder MFA update#

Using a sufficient number of authorization mechanisms (possibly excluding the private shareholder key) the share register and share guard allow the shareholder to update the authorization mechanisms and to update their legitimization data. This could in particular involve online legitimization against the existing legitimization records.

Todo: which authorization mechanisms should be implemented, what are good thresholds for sufficient, are they configurable, and if so by the share register/guard or by the shareholder individually?

23.101.4.5. Share Issuance#

Shares are purchased through the share register, which uses a merchant backend for the purchase order and for the payment. The buyer must have a verified shareholder identity before a purchase can be completed.

For example, a customer purchases ten shares at EUR 100 each:

  1. the share register and share guard register the buyer, with its shareholder public key and additional authorization factors

  2. share register and share guard confirm the sell authorization of the issuer and reserve the shares from the issuer’s quota

  3. the share register creates a purchase order for ten shares, including the public shareholder key of the buyer at a merchant backend

  4. the customer pays EUR 1000 using their Taler wallet

  5. the merchant backend confirms the successful payment

  6. the share register and share guard verify the payment and update the register, both arrive at the same hash chain and sign the update; with both signatures, the update is complete

  7. only following the successful registration does the private shareholder key of the buyer yield rights to the shares

Note: do we need some logic to refund share purchase prices if the share issuance date expired without the transfer having been executed?

23.101.4.6. Share Transfer#

A transfer begins when a shareholder initiates a transfer of share tokens to another party. Such a transfer is treated as a request to sell or transfer the corresponding share position, and not as an unconditional transfer of the registered shares.

The transfer protocol proceeds as follows:

  1. the recipient is identified and verified against the applicable eligibility requirements; the recipient’s wallet must be bound to a verified customer identity (see Identity and Privacy)

  2. the seller initiates a transfer of a given number of shares

  3. the share register service checks the seller’s registered position, the requested quantity and any applicable transfer restrictions

  4. the share backend creates a unique transfer request and reserves the corresponding tokens, or otherwise prevents their concurrent use

  5. the share guard also receives and authorization for the sale and adds its own signature

  6. an pay-pull request is created by the wallet of the seller with all of the authorizations, including the public shareholder key of the buyer

  7. the successful payment event (proof of purchase) transfers the rights to the corresponding shares to the buyer; the buyer has time to submit their proof of purchase until the reservation expires to either the share register or the share guard

  8. both the share register and the share guard sign over the new share register chain head including a date and all of the share transfers since the last generation. Once both signatures are present, the register is considered consistent. Reservations only expire after a new share register generation has achieved consistency and where the respective reservation is either marked as expired (date above expiration) or where the share transfer was executed.

23.101.4.7. Dividends and Ballot Token Generation#

For registered shares, the share backend determines the number of shares eligible for the distribution and the corresponding dividend amount from the shareholder register and the applicable entitlement rules.

For example, a shareholder holds ten shares and is entitled to a dividend of EUR 1 per share. The share register would then increase their dividend entitlement by EUR 10, adding the new entitlement on top of one that might be outstanding from a previous round.

The share position itself remains unchanged. The backend must ensure that each dividend entitlement can be claimed only once. It must also handle transfer requests consistently around the applicable dividend entitlement date so that it is clear if shares are reserved for transfer before or after a dividend distribution.

23.101.4.8. Data Model#

The implementation requires persistent records for:

  • shareholders and their verified customer identities

  • share classes and issued shares

  • the current shareholder positions

  • purchase orders and the associated payments

  • share transfer requests and their states

  • share register events

  • share token generations and issuance records

  • dividend distributions and individual entitlement claims

  • token refresh operations and electronic-money payouts

Every operation must have a unique identifier that connects the relevant payment, register event and token operation.

23.101.4.9. Identity and Privacy#

The share register uses the customer identity established through the applicable verification process. Private shareholder keys in wallets are associated with customer identities through explicit backend records; a wallet identifier alone must not be treated as proof of a shareholder’s authoriztion.

Identity information should only be exposed to the components that require it. The protocols should use transaction references and other strictly necessary technical identifiers instead of unnecessarily distributing personal information.

23.101.4.10. Audit and Reconciliation#

The system must support reconciliation between:

  • the share register and the share guard

  • the merchant/exchange payments for shares

  • the dividend entitlements and payouts

The reconciliation process must identify discrepancies such as incomplete transfers, duplicate processing attempts and unpaid dividend obligations.

A transfer or dividend operation must not be considered complete merely because a request was submitted: completion requires the relevant register and token operations to have reached their defined successful states.

23.101.5. Test Plan#

  • backend logic to issue, sell, buy shares

  • pay out dividends

  • wallet-core and wallet-UI tests

  • initial issuance of shares following a successful payment and registration

  • rejection of purchases by customers that do not satisfy the eligibility requirements

  • transfers between registered shareholders

  • rejection of transfers to ineligible recipients

  • concurrent transfer requests involving the same tokens

  • failed registration with safe cancellation or retry

  • repeated processing of the same registration event without duplicate issuance

  • refresh from one share-token generation to the next

  • correct dividend calculation and payout

  • reconciliation between register positions and token issuance records

  • recovery following a service interruption between registration and token issuance

23.101.6. Definition of Done#

  • shares can be purchased using ordinary Taler digital cash

  • a successful purchase results in a registered shareholder position and in the corresponding share tokens

  • transfers initiate a registration process and do not issue tokens to the recipient before the registration succeeded

  • failed transfers do not create shares

  • all operations can be audited and reconciled

  • the wallet and the merchant backend can recover safely from retries and interruptions

23.101.7. Alternatives#

  • Using the exchange as the emitter of shares; not so good as it is single-currency by design and not setup for dealing with purchases; it might make p2p transfers easier, but regulation on trading is different for shares and the mismatch is likely big enough that not overloading the exchange code with is it is a good idea.

  • Using the merchant backend as the emitter of shares; again, there is a mismatch in requirements and combining the two is likely to increase technical complexity without adequate gains.

  • Transferring bearer-style share tokens between wallets without a registration step; this does not provide the synchronization between wallet balances and the shareholder register that registered shares require.

23.101.8. Drawbacks#

23.101.9. Open Questions#

The implementation must be reviewed against the applicable corporate-law and securities-law requirements before deployment. The design separates the technical representation of the shares from the shareholder register, but that separation alone does not establish the legal classification of the tokens or the regulatory status of the resulting system.

23.101.10. Discussion / Q&A#

(This should be filled in with results from discussions on mailing lists / personal communication.)