02 · Transfer rules
Why would this transfer pass or fail?
Build a rule set, pick each side's claims, enter an amount. Each of the eight rules answers on its own with the code EligraRuleEngine returns. Issuers then write the same rules on chain from their own wallet.
Simulation · computed in your browser
Rules
Claims required (receiver)
Allowed countries (empty = any) · read from claim 3
RejectedSimulation: RECEIVER_CLAIM_EXPIRED
| # | Rule | Result | Why |
|---|---|---|---|
| 0 | Product not paused | Pass | — |
| 1 | Sender on the allowlist | Not set | — |
| 2 | Receiver on the allowlist | Not set | — |
| 3 | Sender holds the required claims | Not set | — |
| 4 | Receiver holds the required claims | Fail | 11 RECEIVER_CLAIM_EXPIRED · claim 2 (Eligible investor) A required claim of the receiver has expired. |
| 5 | Country allowed | Not set | — |
| 6 | Lock-up over | Not set | — |
| 7 | Balance and holder caps | Not set | — |
Same rule order and reason codes as EligraRuleEngine (unit tests mirror the contract tests). Lock-up compares with the chain's latest block time.
On chain · one eth_call, no gas
Test real wallets against a deployed product
No product exists yet.
Issuer actions · your wallet signs