A consortium runs a permissioned Evergreen L1. Its reward-manager precompile pays block rewards to a configured recipient list. At quarter-end close the controller has to answer a question: are any of those recipients related parties of the reporting entity, and is what they received material? This node takes the transcribed recipient list, your own entity-ownership map, the per-period amounts from your own accounting export and a materiality threshold, and returns a per-recipient classification, the aggregate related-party amount measured against the threshold, a gap list naming every recipient it could not resolve, and draft disclosure language for review. It carries its own versioned ruleset and imports none from any other control family. Related question, different node: see ART-459 for a segregation-of-duties conflict matrix over role assignments.
Own versioned rulesetASC 850 and IAS 24 pinnedTranscribed, no chain observationGap list, no coverage ratio
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Reporting Entity and Period
Issuer ref
Issuer ultimate parent ref
Period ref
Ruleset version
Materiality threshold
Currency
As-of date
Co-consortium member refsComma separated entity refs. Opaque references only.
Entity Ownership Map
One entity per lineFormat: entity_ref, ultimate_parent_ref, member (the third field is optional and marks a co-consortium member). Use opaque references. Legal names and addresses are not fields here and must not be entered.
Reward-Manager Recipients
One recipient per line, amounts transcribed from your accounting exportFormat: recipient_ref, entity_ref, reward_amount. Leave entity_ref blank to look the recipient ref up directly in the ownership map.