Can a Token Lock Enforce the Rule 144 Holding Period?
The Rule 144 holding period is the minimum time, six months for SEC-reporting issuers and one year for all others, between acquiring restricted securities from the issuer or an affiliate and reselling them under Rule 144. It attaches to the securities, not the wallet, so an on-chain lock needs a per-lot acquisition record.
TL;DR — Key Takeaways
- ✓The clock: Rule 144(d) requires six months (reporting issuers) or one year (non-reporting issuers) from the later of acquisition from the issuer or an affiliate, for the acquiror or any subsequent holder.
- ✓The start: For a purchase, the clock starts only when the full price is paid. Splits, stock dividends, conversions, and gifts, trusts and estates of affiliates carry the original date forward.
- ✓The mismatch: A lock keyed to when a wallet received tokens resets on own-wallet moves and recoveries, and cannot see payment dates or tacking. It errs in both directions.
- ✓The code: None of the 11 compliance modules on the TokenySolutions/T-REX main branch stores a per-lot acquisition date. TimeTransfersLimitsModule is a rate limit, not a holding period.
- ✓The fix: Keep a per-lot record off-chain as the source of truth, and let the token check or pre-approve transfers against it, with an audit trail for every exception.
What does the Rule 144 holding period actually measure?
It measures time since the securities left the issuer or an affiliate: at least six months for an issuer that has been an SEC reporting company for 90 days, and at least one year for any other issuer. The rule ties it to the securities, not to the person holding them today.
Restricted securities are, among other things, securities acquired from the issuer or an affiliate in a transaction not involving a public offering, and securities subject to the resale limits of Regulation D. A tokenized private placement under Reg D produces restricted securities in the same way a paper one does. Rule 144 is the safe harbor that lets a holder resell them without being treated as an underwriter, provided its conditions are met. The holding period in paragraph (d) is one of those conditions.
“…a minimum of six months must elapse between the later of the date of the acquisition of the securities from the issuer, or from an affiliate of the issuer, and any resale of such securities in reliance on this section for the account of either the acquiror or any subsequent holder of those securities.”
17 CFR 230.144(d)(1)(i), Cornell LII; text matches eCFR, checked November 6, 2026
Three phrases in that sentence decide how a token has to be built. “The later of” means a new acquisition from the issuer or from an affiliate starts a new clock. “Acquisition of the securities” means the date belongs to a specific block of securities, not to an account. “The acquiror or any subsequent holder” means the clock keeps running when the securities pass to a later holder who is not the issuer or an affiliate.
| Issuer status at the time of sale | Minimum holding period | Source |
|---|---|---|
| Subject to section 13 or 15(d) reporting for at least 90 days before the sale | Six months | Rule 144(d)(1)(i) |
| Not reporting, or reporting for less than 90 days | One year | Rule 144(d)(1)(ii) |
Issuer status is measured “immediately before the sale”, so the applicable period can change during the life of a lot if the issuer starts or stops reporting. A lock that hard-codes one number at mint time cannot follow that change. The holding period is also not the whole of Rule 144. For non-affiliates of a reporting issuer, the current public information condition in paragraph (c)(1) still applies until one year has passed. Affiliates face further conditions under paragraph (b)(2). This article covers paragraph (d) only.
When does the clock start for a purchase?
Under Rule 144(d)(1)(iii), the holding period for purchased securities does not begin until the full purchase price or other consideration is paid. The date a token is minted or credited to a wallet is not the test.
“If the acquiror takes the securities by purchase, the holding period shall not begin until the full purchase price or other consideration is paid or given by the person acquiring the securities from the issuer or from an affiliate of the issuer.”
17 CFR 230.144(d)(1)(iii), Cornell LII
Paragraph (d)(2) closes the obvious workaround. Paying with a promissory note, another obligation to pay, or an instalment contract counts as full payment only if all three conditions hold: the instrument gives full recourse against the purchaser, it is secured by collateral other than the purchased securities with a fair market value at least equal to the purchase price, and it has been paid in full before the securities are sold.
Tokenized subscriptions make the gap between mint and payment more likely, not less. An issuer may mint against a signed subscription and a partial wire, or credit shares when a pending request is settled. In an ERC-7540 asynchronous subscription, the request date, the date the payment asset moves, and the date the investor claims shares can all differ. Rule 144 does not name any of those events, and which one counts as acquisition and full payment is a question for counsel. The record should store all of them, so the answer can be applied later without reconstructing history.
Which events carry the original date forward?
Rule 144(d)(3) lists ten cases that set the holding period by reference to an earlier acquisition. For a token, the ones that matter most are splits and stock dividends, conversions and exchanges, cashless exercise, and gifts, trusts and estates of affiliates.
| Paragraph | Event | Deemed acquisition date | Token event it maps to |
|---|---|---|---|
| (d)(3)(i) | Stock dividend, split, reverse split, recapitalization | Date of the original securities | Agent mint or burn to many holders |
| (d)(3)(ii) | Conversion or exchange solely for the same issuer's securities | Date of the surrendered securities, with an exception if the holder paid to amend them for cashless conversion | Burn of one token class, mint of another |
| (d)(3)(iv) | Bona fide pledge by an affiliate, sold after default | Date the pledgor acquired them, unless pledged without recourse | Forced transfer to a lender or buyer |
| (d)(3)(v) | Gift from an affiliate | Date the donor acquired them | Holder transfer with no payment |
| (d)(3)(vi) | Trust whose settlor is an affiliate | Date the settlor acquired them | Transfer to a trust wallet, then to beneficiaries |
| (d)(3)(vii) | Estate of a deceased affiliate | Date the deceased acquired them; no holding period if the estate, or the selling beneficiary, is not an affiliate | Forced transfer or recovery to an executor |
| (d)(3)(x) | Cashless exercise of the issuer's options or warrants | Date of the options or warrants, with an exception if the holder paid to add cashless exercise | Mint against a burned warrant token |
The remaining three cases are contingent issuance in an acquisition (d)(3)(iii), Rule 145(a) transactions (d)(3)(viii), and holding company formations (d)(3)(ix). They are rarer in tokenized private placements but follow the same pattern: the date comes from a defined earlier event, not from the moment the new securities appear.
“Securities acquired from the issuer as a dividend or pursuant to a stock split, reverse split or recapitalization shall be deemed to have been acquired at the same time as the securities on which the dividend… was paid, the securities involved in the split or reverse split, or the securities surrendered in connection with the recapitalization.”
17 CFR 230.144(d)(3)(i), eCFR
Two cases work the other way. A purchase from an affiliate is itself an “acquisition from an affiliate”, so under the “later of” wording it starts a new clock for the buyer. And the gift, trust and estate rules in (d)(3)(v) to (vii) are written for affiliates. A transfer between two non-affiliates is already covered by the “any subsequent holder” wording in (d)(1), so the original date carries without a special rule. That last point is our reading of the text, not SEC guidance; we found no SEC statement on on-chain holding-period enforcement.
Why does a wallet-age lock get it wrong?
A lock that says “this wallet cannot send until N days after it received tokens” measures the wrong thing. It resets when the same holder moves tokens, and it cannot see payment dates, affiliate status or tacking, so it blocks some lawful resales and allows some early ones.
The analysis below is our inference from the text of Rule 144(d) compared with how wallet-level locks behave. It is not a statement of how any particular issuer or platform has configured its token.
| Event | What Rule 144(d) says about the date | What a wallet-receipt lock does | Direction of error |
|---|---|---|---|
| Holder moves tokens to a second wallet of their own | No acquisition from issuer or affiliate; date unchanged | Starts a new lock on the second wallet | Blocks too long |
| Agent recovers a lost wallet | Same holder; date unchanged | Starts a new lock on the replacement wallet | Blocks too long |
| Private sale between two non-affiliates | Clock continues for the subsequent holder | Starts a new lock for the buyer | Blocks too long |
| Tokens minted before full payment | Clock starts only at full payment | Starts at mint | Opens too early |
| Split or stock dividend mint | New tokens take the original date | Starts a new lock on the new tokens | Blocks too long |
| Purchase from an affiliate | New clock from the purchase | New lock, which matches only if the wallet holds nothing else | Mixed |
| Issuer stops reporting | Period becomes one year if the issuer has not reported for 90 days before the sale | Keeps the period set at deployment | Opens too early |
The root cause is fungibility. An ERC-20 style balance is a single number per wallet. Rule 144 needs a date per block of securities, and one wallet can hold several blocks with different dates. Paragraph (d) also does not say which block a partial sale draws from, so any system that tracks lots needs an explicit, documented selection rule rather than one that depends on transfer order.
Illustrative example (invented dates, not a real issuer). A non-reporting issuer mints 1,000 tokens to an investor on 1 March. The investor pays half that day and the rest on 1 June. Under (d)(1)(iii) the one-year period runs from 1 June, so the earliest Rule 144 resale is 1 June of the next year. A one-year wallet-receipt lock opens on 1 March, three months early. In May of the next year the investor moves all 1,000 tokens to a new custody wallet. The lock on that wallet now runs to the following May, eleven months after the date the rule allows. A per-lot record carries 1 June through both events.
What does the T-REX reference code ship for this?
No module on the TokenySolutions/T-REX main branch stores an acquisition date per lot. The branch ships 11 compliance modules; the closest tools are a time-window transfer limit, per-transfer approvals and agent-controlled partial freezes, none of which knows when a lot was acquired.
ERC-3643 itself defines a compliance interface, not a module catalog. The EIP leaves rules such as holding periods to the issuer's compliance contract, which is the gap the smart contract compliance and Layer-0 governance guide describes: what the standard enforces is only what someone has coded into a module. The modules below were listed from the T-REX modules directory at commit f1390127 (October 28, 2025), which is still the head of the archived main branch.
| Module | What it restricts | Stores acquisition date per lot? |
|---|---|---|
| ConditionalTransferModule | Only transfers whose exact (from, to, amount) was pre-approved | No |
| CountryAllowModule / CountryRestrictModule | Receiver country, by allow list or block list | No |
| ExchangeMonthlyLimitsModule | Monthly value an investor can send to exchange-tagged identities | No |
| MaxBalanceModule | Maximum balance per investor identity | No |
| SupplyLimitModule | Total supply ceiling on mints | No |
| TimeExchangeLimitsModule | Value an investor can send to exchange-tagged identities per time window | No |
| TimeTransfersLimitsModule | Value an identity can send per configurable time window | No |
| TokenListingRestrictionsModule | Which investors may receive the token, by allow list or block list | No |
| TransferFeesModule | Charges a fee on transfers; never blocks one | No |
| TransferRestrictModule | Holder transfers pass only if the sender or the receiver is allow-listed | No |
TimeTransfersLimitsModule is the module whose name sounds closest to a lock-up. It keeps a counter per sender identity for each of up to four limits, each a window length in seconds and a maximum value. The window starts at the first transfer after the previous window has expired. Mints skip the check, and so do transfers sent by a token agent. It limits how fast an identity can sell, not when a block of securities may first be sold. The exchange-specific modules work the same way for deposits to a venue, as set out in how an ERC-3643 token can cap investor deposits to an exchange.
The token contract adds two agent tools. freezePartialTokens in Token.sol freezes an amount per wallet, with no date attached; an agent has to unfreeze it by hand, forcedTransfer unfreezes whatever it needs to move, and recoveryAddress re-freezes the same amount on the new wallet. pause stops holder transfers token-wide. Both are switches an operator flips, so the date logic stays off-chain either way. The successor ERC-3643/ERC-3643 repository ships only abstract and test modules in the same directory. We checked T-REX only; other token frameworks may include lock-up features, and nothing here generalises to them.
What does a per-lot record need to hold?
At minimum: the holder, the origin date, the full-payment date, the tacking basis with a link to the parent lot, the issuer's reporting status, and the holder's affiliate status. Every field comes from a clause of Rule 144; a wallet balance holds none of them.
| Field | Why it is needed | Rule 144 clause |
|---|---|---|
| Lot ID and parent lot ID | Lets split, dividend, conversion and partial-sale lots inherit a date | (d)(3)(i), (ii), (x) |
| Holder identity, not wallet | Own-wallet moves and recoveries must not change the date | (d)(1) “acquiror or any subsequent holder” |
| Acquired from: issuer, affiliate, or other holder | Only acquisition from the issuer or an affiliate starts a new clock | (d)(1) “the later of” |
| Origin date | The date the period counts from | (d)(1) |
| Full-payment date and note or instalment terms | The period starts only on full payment | (d)(1)(iii), (d)(2) |
| Tacking basis (gift, trust, estate, pledge) | Affiliate transfers can carry the donor, settlor or deceased's date | (d)(3)(iv) to (vii) |
| Issuer reporting status, with start date | Decides six months or one year at the time of sale | (d)(1)(i), (ii) |
| Holder affiliate status, current and recent | Non-affiliate status looks back three months; affiliates face more conditions | (b)(1), (b)(2) |
This record belongs where the legal register already lives. For a tokenized security that is the transfer agent's master securityholder file, not the token contract. The chain can mirror the result, for example as an unlock date per identity, but the inputs are documents: subscription agreements, wire confirmations, gift letters, affiliate questionnaires. Wallet recoveries need the same care, because the record has to follow the holder to the new wallet; the reconciliation steps in ERC-3643 lost wallet recovery apply to lot dates as well as balances.
Should the token block every transfer until the date?
Not necessarily. Rule 144 is a safe harbor, not the only lawful way to resell restricted securities, so a lock that blocks every transfer before the date also blocks transfers that rely on registration or another exemption. Treat the lock as a default that a named person can override, not as the rule itself.
Two patterns fit the T-REX tools without a custom module. The first keeps the date logic off-chain and uses ConditionalTransferModule: the compliance owner pre-approves each transfer that the lot record clears, by exact sender, receiver and amount. It is strict, but in the reference code it applies to mints as well, since mint runs the same compliance check with a zero sender. The second leaves transfers open and uses partial freezes on lots that are still inside the period, with an agent unfreezing them when the record says the date has passed. Both put the decision with a key holder and the evidence in the record, which is where an auditor will look.
A custom module that stores an unlock date per identity is the third option. It can block holder transfers automatically, but on our reading it still cannot compute the date by itself: payment, tacking and affiliate status are off-chain facts. A wrong date on-chain is a quiet error, so every write to it should cite the lot record that produced it. We know of no documented exploit of a permissioned RWA token through a holding-period lock; the risk described here is an operational one.
- Who this is for: issuers and transfer agents of tokenized Reg D or other restricted securities who want the token to stop early Rule 144 resales, and auditors checking how an unlock date was set.
- Who it is less relevant for: registered offerings with freely tradable securities, and Reg S distribution compliance periods, which run under a different rule.
- When this breaks: a single unlock date per wallet, set at mint, with no link to payment records; split or dividend mints that stamp a fresh date; recoveries that drop the date; and legend removals with no record of who approved them and on what basis.
The design Blockmaze argues for is a compliance check that reads the per-lot record kept by the transfer agent and logs every exception and legend removal against the lot it concerns. That check does not decide whether Rule 144 is available for a given sale. That remains a legal judgment for the issuer, the holder and their counsel, and this article is not legal advice.
Sources: 17 CFR 230.144, Cornell LII, 17 CFR 230.144, eCFR, T-REX compliance modules directory, TimeTransfersLimitsModule.sol, ConditionalTransferModule.sol, Token.sol, ERC-3643/ERC-3643 modules directory, EIP-3643. Rule text and repository contents checked November 6, 2026. T-REX code read at commit f1390127.
Frequently Asked Questions
How long is the Rule 144 holding period for tokenized restricted securities?
Six months if the issuer has been subject to Exchange Act reporting under section 13 or 15(d) for at least 90 days before the sale, and one year if it has not. Tokenization changes nothing in the count. The period runs from the later of the date the securities were acquired from the issuer or from an affiliate of the issuer, under 17 CFR 230.144(d)(1).
Does moving tokens to a new wallet restart the Rule 144 holding period?
Nothing in Rule 144(d) ties the clock to a wallet. The period runs from acquisition from the issuer or an affiliate and applies to resales for the acquiror or any subsequent holder. A move between wallets of the same holder is not an acquisition from the issuer or an affiliate, so on our reading it should not reset the date. A lock that keys on wallet receipt does reset it.
When does the holding period start if the investor pays in instalments?
For a purchase, the period does not begin until the full purchase price or other consideration is paid, under Rule 144(d)(1)(iii). A promissory note or instalment contract counts as full payment only if it gives full recourse, is secured by other collateral worth at least the purchase price, and is paid in full before the sale. The mint date of the token is not the test.
Do tokens minted in a stock split or dividend get a new holding period?
No. Rule 144(d)(3)(i) deems securities acquired from the issuer as a dividend, or in a split, reverse split or recapitalization, to have been acquired at the same time as the original securities. A token that stamps each mint with a fresh lock date treats split or dividend tokens as new acquisitions, which blocks them for longer than the rule requires.
Does the ERC-3643 reference code include a Rule 144 lock-up module?
No. The TokenySolutions/T-REX main branch ships 11 compliance modules, and none stores a per-lot acquisition date. TimeTransfersLimitsModule caps the value an identity can send per time window, which is a rate limit, not a holding period. The successor ERC-3643/ERC-3643 repository ships only abstract and test modules. We checked only T-REX code, not other frameworks.
Should a tokenized security block every transfer until the Rule 144 date?
That is a design choice, not a requirement of Rule 144. Rule 144 is a safe harbor for resales, and other exemptions or registration can cover a transfer before the date. A hard lock blocks those too. One compromise is to block by default and let a compliance agent approve named exceptions, with the legal basis for each exception kept in the audit trail.
Related Articles
Can You Add a Holding Cap to a Live ERC-3643 Token?
The ERC-3643 MaxBalanceModule keeps its own per-identity ledger, so adding a cap to a live token means hand-writing every balance first.
Who Really Controls an ERC-3643 Token's Agent Keys?
ERC-3643 exposes seven privileged functions that can move or immobilise investor holdings, and the standard requires no multisig, timelock or governance process for the keys that call them.
Can Expired KYC Make an ERC-3643 Position Unsellable?
ERC-3643 transfer checks can turn expired or revoked identity claims into a liveness dependency for tokenized securities.
RWA Secondary Market Liquidity and Compliance
RWA secondary market liquidity needs two fixes: compliance on who can hold under what limits, and a way for willing buyers and sellers to meet.