
PaymentPolicyChangePreview.
Replay Past Transfers Before Changing Rules. Same history, two rule sets, every changed outcome with its reason.
Prototype · Elysium · no token needed

Same history.
Two rule sets.

Replay layer
One history, judged twice: under the rules you run now and the rules you want next.
Load sample data, a CSV or JSON file read in your browser, or a wallet's outgoing transfers on Elysium. Nothing is uploaded from a file.
Under each rule set, a transfer that fails is treated as blocked: it does not count toward later daily or weekly totals, or the cooldown. So rule set B is judged as if it had been in force from the first transfer.
Reason layer
Every transfer that changes says which rule stopped it, and the numbers behind it.
- 01Recipient is on the blocklist
- 02Recipient is not on the allowlist
- 03Token is not on the token allowlist
- 04Sent outside the allowed hours (UTC)
- 05Sent on a day that is not allowed (UTC)
- 06Too soon after the previous allowed transfer
- 07Amount is over the per-transfer cap
- 08Rolling 24-hour total would pass the daily cap
- 09Rolling 7-day total would pass the weekly cap

Chain layer
Policy versions on Elysium, judged by the same rules as the page.
9
rules, checked in a fixed order
400
transfers per on-chain check
0
funds the contract can hold
The platform
What runs today, and what is still a concept.
Evidis is a prototype. The replay runs today on sample data, your own file or a wallet's real Elysium history. Nothing here enforces a rule on a wallet yet.
Sample data, a CSV or JSON file read in your browser, or a wallet's outgoing transfers on Elysium from the explorer API, with the newest transfer re-read from the chain.
OpenPer-transfer, rolling 24-hour and 7-day caps per token, recipient allowlist and blocklist, token allowlist, allowed hours and days (UTC) and a cooldown.
OpenEvery transfer judged under A and under B. Newly blocked, newly allowed and unchanged, with the first failing rule, all failing rules and the numbers behind each.
OpenThe same history replayed inside EvidisPolicyBook through eth_call. The page lists every transfer where the contract and the site disagree (there should be none).
OpenBooks of append-only policy versions with an owner, editors and a notice period before a version can be put in force. Contract tested, not deployed yet.
OpenA module that refuses a transfer the active policy fails. Not built: today Evidis only previews.
A tighter rule set would have blocked 16 of 107 transfers.
16
newly blocked under B
3,150 USDC
in those transfers
9
rolling 24-hour total would pass the daily cap
3
sent outside the allowed hours (utc)
Sample data: an invented three-week history of an agent wallet. The recipients are made-up addresses, not real businesses.
Open it inPolicy ReplayKnow what breaks
before you switch.
1 file or 1 address
is all a replay needs
0 wallets
must be connected to replay
0 uploads
a file never leaves your browser
Load a history
Sample data, a file, or a wallet's outgoing transfers on Elysium with the newest one re-read from the chain.
Write rule sets A and B
Caps per token, recipients, tokens, hours, days and a cooldown. Start B as a copy of A and change one thing.
Read what changes
Newly blocked, newly allowed and unchanged, with the first failing rule and every other rule that failed.
Publish, if you want
Propose B as a version in a policy book on Elysium, wait out the notice period, then put it in force.
Rules used to change on a hunch.
Now they change after a replay.
Built for agent wallets.
Data sources
The Elysium explorer's API for a wallet's history, the Elysium RPC to re-read the newest transfer and to run the contract check. No key, no account, no tracking.
What it never does
It never holds funds, never signs for you and never blocks a real transfer. Nothing on this site needs $EVIDIS. Replay, parity check and the policy book work without it.
What it
does not claim.
“A replay is a preview. It never stops, delays or signs a transfer.”
“Wallet history covers top-level HYPE sends and ERC-20 Transfer events sent by the wallet, newest 400. HYPE moved by internal contract calls is not covered.”
“Caps are in token units per token. There is no dollar conversion and no price feed.”
“Times are UTC. The explorer's timestamps are used as given; the newest transfer of each kind is re-read from the RPC.”
“A token's symbol is what its contract reports. Only HYPE, USDC and WHYPE are named by address.”
“The contract is new and has had no outside security review. It holds no funds by design.”
Replay first, switch second.
Free to use. Nothing to install.
FAQs
How the replay counts, where the data comes from, and what the contract does.
It replays a wallet's past outgoing transfers under the payment rules you run today (A) and the rules you plan to switch to (B), and lists every transfer whose outcome changes, with the rule and the reason. Nothing is sent or signed.
Three places: built-in sample data (labelled), a CSV or JSON file you choose (read in your browser, never uploaded), or a wallet's outgoing transfers on Elysium from the explorer's API. For chain data the newest transfer of each kind is re-read from the Elysium RPC to confirm the explorer.
Rolling windows: the last 86,400 seconds and the last 604,800 seconds before each transfer, per token, counting only transfers that passed under that rule set. Under each rule set, a transfer that fails is treated as blocked: it does not count toward later daily or weekly totals, or the cooldown. So rule set B is judged as if it had been in force from the first transfer.
All failing rules are listed. The reason shown first follows a fixed order: blocked recipient, recipient not on the allowlist, token not allowed, hours, days, cooldown, per-transfer cap, daily cap, weekly cap. The contract uses the same order.
The repository has a fixture that the site's engine and the contract's tests must agree on transfer by transfer, and the replay page can run your own history through the contract code with eth_call. EvidisPolicyBook is written and tested but not deployed yet. Until it is, the parity check runs this build's compiled contract code through a read-only eth_call.
No. EvidisPolicyBook has no payable function and makes no token calls. Publishing a policy version only costs gas.
No wallet is needed to replay. A wallet is used only to load your own address quickly and to publish policy versions. Nothing on this site needs $EVIDIS. Replay, parity check and the policy book work without it.
A replay can only be as good as its history: transfers the history misses are not judged, and a rule set that looks fine on three weeks of data can still block something next month. The contract is new and has had no outside security review. Use small, reversible steps when you change real limits.