Skip to content
eligra

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

Works without contracts

Claims required (receiver)

Allowed countries (empty = any) · read from claim 3

Sender

Sender

Receiver

Receiver

RejectedSimulation: RECEIVER_CLAIM_EXPIRED
#RuleResultWhy
0Product not pausedPass—
1Sender on the allowlistNot set—
2Receiver on the allowlistNot set—
3Sender holds the required claimsNot set—
4Receiver holds the required claimsFail11 RECEIVER_CLAIM_EXPIRED · claim 2 (Eligible investor)
A required claim of the receiver has expired.
5Country allowedNot set—
6Lock-up overNot set—
7Balance and holder capsNot 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

Create products, trust issuers, attest, set rules

reading chain…